I have recently had to investigate integrating BizTalk 2006 R2 to JD Edwards version 8.12 (latest version). My first thought was to use the BizTalk JDE Adapter. I enquired about it on the BizTalk MSDN forums and also on a mailing list we have between our Auckland Connected Systems User Group and the Sydney and Brisbane BizTalk user groups. No responses.
I reviewed the BizTalk JD Edwards Adapter documentation. I reviewed the 376 pages of Oracle’s JD Edwards EnterpriseOne Tools Interoperability Guide. I also checked out the JD Edwards EnterpriseOne Business Services Data Sheet and the Extending with Service Oriented Architecture White Paper.
After all this, the solution was quite simple: nowadays JD Edwards EnterpriseOne offers native support of Web Services. You still need a JD Edwards developer to expose them, but this means there is no need to install the java components and go through the long list of steps to get the JD Edwards Adapter installed and working correctly on the BizTalk Server. It’s much nicer and cleaner to have Web Services exposed directly from the JD Edwards server. It is also beneficial to the company because other systems can call the same Web Service, especially if they are looking at an SOA approach.
This is probably the reason why Microsoft didn’t release a JD Edwards adapter with the latest WCF based Adapter Pack.
I will post back here or update this post when I get more information on how much is involved to expose JD Edwards objects via Web Services.