November 8, 2015 Leave a comment
For some time now, Oracle B2B has exposed several methods of accessing it’s partner and message metadata from a custom application. This has been improved even further with B2B 12c.
In this post I’ll guide you through the 2 most common ways of accessing B2B’s metadata programmatically and some news of the 12c version.
The 2 main ways of accessing the metadata stored in B2B are:
- Web Services exposed by B2B
- Java API
Web Services exposed by B2B
You can access the WSDL’s for the available web services at the following URL:
The most common services are:
- Outbound Web Service – Works as an internal Listening Channel. Based on the details and headers in the soap:body, the agreement identification is done and the message is routed to the partner.
- Translation Web Service – Allows to translate documents such as EDI and HL7 from Native to XML format (NativeToXMLService) and from XML to Native format (XMLToNativeService)
- Query API (GetTPAConfigService) – Allows for retrieval of different metadata such as active agreements for a Trading Partner or checking if a Trading Partner has an agreement for a specific Document.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.