Home
Forums
New posts
What's new
New posts
Latest activity
Advertise
Resources
Log in
Register
What's new
New posts
Menu
Log in
Register
Install the app
Install
Home
Forums
JD Edwards® Enterprise One / One World Discussions
JD Edwards® EnterpriseOne Technical
E9200 Integration Options
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Alex_Pastuhov" data-source="post: 189044" data-attributes="member: 2428"><p>Interestingly, JDE provides a way to do complex interfacing with just XML: they support a complex XML format with variables, error handling, code forking and multiple BSFN calls passing parameters to each other, plus built-in transaction support. There's some doco available from Oracle on this syntax too. Such XML calls do not have any licensing implications, so there's clear savings here compared to either BSSV or AIS. And our EveREST2JDE middleware offers REST interface to this functionality as well.</p><p></p><p>So basically, the "programming" part with this approach can be done using this extended JDE XML syntax, it can be submitted to JDE through an easy to use REST front-end interface and the end result can be almost as complex as running an APPL through AIS. The difference is that with a ready APPL you just need to figure out the forms and the fields and with this extended XML you would need to reverse-engineer the business logic and program it into XML as a series of BSFN calls, but it would run a lot faster. Which all boils down to how complex the logic here is: it may not be practical trying to replicate a complex APPL logic splitting it into single function calls, but for many simpler processes the AIS with it's "screen scraping" would look too heavy and convoluted instead...</p><p></p><p>Just my 2c ;-)</p></blockquote><p></p>
[QUOTE="Alex_Pastuhov, post: 189044, member: 2428"] Interestingly, JDE provides a way to do complex interfacing with just XML: they support a complex XML format with variables, error handling, code forking and multiple BSFN calls passing parameters to each other, plus built-in transaction support. There's some doco available from Oracle on this syntax too. Such XML calls do not have any licensing implications, so there's clear savings here compared to either BSSV or AIS. And our EveREST2JDE middleware offers REST interface to this functionality as well. So basically, the "programming" part with this approach can be done using this extended JDE XML syntax, it can be submitted to JDE through an easy to use REST front-end interface and the end result can be almost as complex as running an APPL through AIS. The difference is that with a ready APPL you just need to figure out the forms and the fields and with this extended XML you would need to reverse-engineer the business logic and program it into XML as a series of BSFN calls, but it would run a lot faster. Which all boils down to how complex the logic here is: it may not be practical trying to replicate a complex APPL logic splitting it into single function calls, but for many simpler processes the AIS with it's "screen scraping" would look too heavy and convoluted instead... Just my 2c ;-) [/QUOTE]
Verification
Post reply
Home
Forums
JD Edwards® Enterprise One / One World Discussions
JD Edwards® EnterpriseOne Technical
E9200 Integration Options
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top