Inbound Connectivity Outbound Connectivity

21 Establishing Resource Connectivity 21-1 21 Establishing Resource Connectivity This chapter describes how Oracle Application Integration Architecture AIA services interact with external resources and discusses inbound and outbound connectivity. The final sections describe specific guidelines for establishing connectivity with Siebel applications as well as Oracle E-Business Suite. This chapter includes the following sections: ■ Section 21.1, Introduction to Resource Connectivity ■ Section 21.2, Modes of Connectivity ■ Section 21.3, Siebel Application-Specific Connectivity Guidelines ■ Section 21.4, Oracle E-Business Suite Application-Specific Connectivity Guidelines ■ Section 21.5, Design Guidelines

21.1 Introduction to Resource Connectivity

Participating applications drive the business processes. They are either initiators of the business process or play roles in one or more steps in the business process. The interactions of the participating applications with the business process can be either outbound or inbound from the AIA layer perspective. A business process is a combination of outbound and inbound interactions with various participating applications.

21.1.1 Inbound Connectivity

Inbound means inbound into the AIA layer, as shown in Figure 21–1 . Figure 21–1 illustrates how an inbound interaction to the business process is made by a participating application. Clicking the submit button in the order capture module within a CRM application results in the initiation of the Order Fulfillment business process. ■ Services exposed by AIA services are invoked by proxies created by applications. Inbound interactions with AIA might occur due to the notification or broadcast of an event by the participating application or for retrieval of information from external sources. For example - clicking of the Get Account Balance button in a CRM application module could result in invocation of an AIA service by sending a SOAP message over HTTP. ■ Applications push messages to JMS queues and topics. JMS servers trigger registered JMS adapter agents and JMS adapter agents trigger AIA services. For 21-2 Developers Guide for Oracle Application Integration Architecture Foundation Pack example, creation of a customer or submission of an order within CRM modules could trigger the broadcast of these events to AIA in the form of messages to JMS queues and topics. Figure 21–1 Example of Inbound Connectivity

21.1.2 Outbound Connectivity

Outbound means outbound from the AIA layer, as shown in Figure 21–2 . ■ AIA services invoke services exposed by applications. AIA services could invoke the application services or the external services to retrieve additional information, to send business events, or to request a task be done. An example is the creation of a customer in billing application when an order is created in the CRM module or an order is submitted for an existing customer in CRM module, but that customer profile is not available in the billing application. Most manufacturing systems publish an event when an item is added however these events contain minimal information about the item. The AIA service consuming the event must invoke an application service to get complete information about the item. ■ AIA services interact with applications using JCA adapters and push messages to JMS queuestopics. JMS servers trigger JMS adapter agents registered by applications. Figure 21–2 illustrates how an outbound interaction is made by the business process. A step within that business process could result in invocation of CRM Order Capture application to send the order status updates. Establishing Resource Connectivity 21-3 Figure 21–2 Example of Outbound Connectivity

21.2 Modes of Connectivity