Web Services with SOAPHTTP

21-4 Developers Guide for Oracle Application Integration Architecture Foundation Pack

21.2.1 Web Services with SOAPHTTP

For inbound interaction, the participating application invokes the Application Business Connector Services ABCS provided by AIA as Web services. The participating application uses the ABCS WSDL for invoking the ABCS Web services. The ABCS WSDLs are consumed by the participating application to create stubs or proxies. These are internally invoked in the participating application leading to the invocation of the ABCS. AIA recommends that participating applications leverage Web services transport, as shown in Figure 21–3 , for invoking AIA services only to fetch information residing in external systems. For example, querying the account balance details of a customer from billing application using CRM application by a CSR or a self-service application screen. Figure 21–3 Illustration of Using Web Services with SOAP HTTP In other types of interactions, like create customer, submit order, and so on, AIA recommends that you use either JCA or JMS transports to ensure the interaction is reliable and transactional. If the participating application does not have the capability to use either JMS or JCA transports to publish events to the AIA layer, then you can use the Web services transport, which can help in publishing the events to a queue in the AIA layer for further processing. Since the ABCS is developed using the schemas from the participating applications, the outbound message format and the ABCS message format are the same. Inbound Interaction Inbound messages should have the following attributes: ■ Message ID The Message ID is the unique identifier for a message generated by the application and stamped on the message. For example, a customer ID or an order ID would be unique in the payload. ■ Message payload name The name of the business object should be passed. ■ Participating application instance Establishing Resource Connectivity 21-5 A unique identifier for the application instance is needed to set the cross reference for the entity IDs, so this is also expected in the payload. ■ Event session locale The locale information from the client session provides context to the request being made by the application. This helps in ensuring the response is in the same locale context. The locale specific headers should be negotiated with the application teams to decide upon the ABM header attributes. Setting and retrieving the locale specific information is a factor in the ABCS implementation during the request and response transformation steps done on ABM. Outbound Interaction For outbound interactions, the ABCS invokes the participating application APIs exposed as Web services. The WSDLs of the participating application Web services are consumed by the ABCS.

21.2.2 When to Use Web Services with SOAPHTTP