Integrating OSB - B2B for a healthcare scenario
- by Ramesh Nittur
Usecase
1: Admin to send a HL7 Message to Pharmacy.
OSB
to use B2B for translating the XML document to HL7 native document
using the translation webservice exposed by B2B.
B2B
configuration
Oracle
B2B 11g PS2 release has exposed a webservices to translate XML
document to Native document. This service needs an outbound agreement
configured with "HL7 Message Facility ID" as the Identifier.
Document Type and revision can be identified from the document
itself.
B2B
translation webservice can be used in two mode, one for only
translation and another for translation and routing.
OSB-B2B
Integration sample are developed based on the "b2b-005-hl7"
sample in OTN.
We
are not going to discuss about the b2b metadata configuration
creation details, as it is dealt detail in OTN sample document.
OSB
Configuration
Steps
to create OSB Configuration sample:
Create
a OSB Project with name OSB-B2B
Create
BusinessService with name B2BBusinessService to consume B2B
TranslateService
URL
http://<host:8001>/b2b/services/
TranslateService