Resubmitting a Message Oracle Fusion Middleware Online Documentation Library

20 Using the Oracle B2B Web Services 20-1 20 Using the Oracle B2B Web Services This chapter provides information about using the Oracle B2B Web Services. It contains the following topics: ■ Section 20.1, Introduction to Oracle B2B Web Services ■ Section 20.2, Using the Outbound Web Service ■ Section 20.3, Using the Translation Web Service ■ Section 20.4, Using the Query API ■ Section 20.5, Securing Oracle B2B Web Services

20.1 Introduction to Oracle B2B Web Services

Oracle B2B exposes web services to retrieve the document details in Oracle JDeveloper. These are partner-facing web services, where the user can send messages to Oracle B2B. Similarly, Oracle B2B provides a web service exposed to the back end to receive the messages, and process and send to partner, based on the agreements deployed in Oracle B2B. To use the Oracle B2B web services, create a web service proxy in your application in Oracle JDeveloper. The Web Services Description Language WSDL files for the web services are available at the following URLs on the system where Oracle B2B is installed. http:host_name:port_numberb2bservices A URL suffixed with just a URL pattern of Servlet entered in the Web browser, without any URI, provides the list of WSDLs available for download with no security restrictions. Oracle B2B provides the following web service APIs: ■ Outbound Web Service API provides a built-in internal listening channel. See Section 20.2, Using the Outbound Web Service for more information. ■ Translation Web Service API is exposed to translate the native payload, such as HL7, EDI, to XML format. See Section 20.3, Using the Translation Web Service for more information. ■ Query API helps to retrieve the configured details in Oracle B2B. See Section 20.4, Using the Query API for more information. Security For Oracle B2B Web Services Oracle Web Services Manager allows integrating various types of policies without impacting the run time and flow of the web service, and it provides security of service 20-2 Oracle Fusion Middleware Users Guide for Oracle B2B infrastructure. Signing, encryptiondecryption, authentication, authorization, auditing, and reporting will be provided by this tool kit. Hence, this web service implementation will not address the details of security, signing, and encryption. Web service methods hold the business logic instead of security details. Based on the policy enforced in Oracle Weblogic Server console, the web service client must attach security details with the web services port.

20.2 Using the Outbound Web Service

The Outbound Web Service is exposed as a built-in internal listening channel, and messages are enqueued to this service. Based on the details and headers in soap:body, agreement identification is done and the message are routed to the partner. Table 20–1 , Table 20–2 , and Table 20–3 describe the Outbound Web Service request, response and fault notification message parameters. Table 20–1 Outbound Web Service Request Parameters Header Data Type Description Required from String Host name or identification value No to String Trading Partner name or identification value Yes type String Example: DUNS Identification type No documentProtocolVersion String Example: 4010 Document type version Yes 1 1 Either documentProtocolVersion and documentTypeName must be present, or action, service, and serviceType must be present. A custom generic case only requires action and not the others. documentTypeName String Example: 850 Document type name action String Example: PurchaseOrder ebMS action name service String Example: OrderProcessing ebMS service name serviceType String Example: string Default: string ebMS service type messageId String Message ID given in this parameter is used to create APP_Message. No replyToMessageId String Example: reply_msgID:collaborationID Holds the message ID of which message this reply goes to, along with the collaboration ID. No messageType String Type of the message No encoding String Example: ISO-8859-1 Default: UTF-8 Encoding format No payload Xsd:anyType Holds the payload Yes attachment Xsd:anyType Attachment, if any No