Inbound: Siebel Application Interaction with AIA Services Creating JMS Consumers to Consume Siebel Messages from JMS QueuesTopics

Establishing Resource Connectivity 21-13 ■ Different components are involved in the processing of messages. They can be JMS consumer adapter services, BPEL processes, Mediator services, cross reference calls, and JMS Producer adapter services. ■ Global transactions are enabled across all the components, and the transaction boundary is established between the integration milestones, which ensures that the messages are persisted in the source milestone until delivered to the target milestone.

21.2.8 When to Use JCA Adapters

Use JCA adapters when the application has the implementation of an adapter based on the Oracle FMW-supported JCA specifications. These adapters can be purchased from Oracle certified third-party vendors if they support the required JCA specifications. JCA adapters should be transactions enabled. To ensure guaranteed delivery and get the participating application to enlist in the XA transactions, the JCA adapter and the application should build the capabilities which are required for building the AIA composite business processes. The JCA adapter can be a queue or topic adapter for AQ or JMS. Also, the JCA adapter can expose the business object APIs of a particular application. The granularity of the API demands chatty conversations with the participating application. AIA recommends that an application should expose the coarse-grained API though it might call multiple fine-grained APIs in the applications implementation. This exposure avoids chatty conversations and improves the overall performance for a business transaction. For more information about JMS Adapters, see Oracle Fusion Middleware Configuring and Managing JMS for Oracle WebLogic Server.

21.3 Siebel Application-Specific Connectivity Guidelines

The following sections discuss how to establish inbound and outbound connectivity with Siebel applications: ■ Section 21.3.1, Inbound: Siebel Application Interaction with AIA Services ■ Section 21.3.2, Web Services with SOAPHTTP ■ Section 21.3.3, Creating JMS Consumers to Consume Siebel Messages from JMS QueuesTopics ■ Section 21.3.4, Outbound - Siebel Application Interaction with AIA Services ■ Section 21.3.5, Web Services with SOAPHTTP

21.3.1 Inbound: Siebel Application Interaction with AIA Services

Siebel applications present requests to AIA services when the Siebel application is the driving application initiating business processes, business activities, and business tasks. The Siebel application can either invoke AIA services exposed as Web services or push messages directly to JMS queues triggering AIA JMS consumers. The format of the requesting messages can either be native to Siebel or conform to the AIA Enterprise Business Objects EBO. If the format is native, Siebel Tools generate schemas for the Siebel Integration Objects and provide for creating AIA services. 21-14 Developers Guide for Oracle Application Integration Architecture Foundation Pack For more information, see Integration Platform Technologies: Siebel Enterprise Application Integration.

21.3.2 Web Services with SOAPHTTP

Siebel Tools Siebel IDE needs AIA service WSDLs. Siebel Tools introspects the WSDLs and generates proxies to invoke AIA services at run time. Siebel Tools generates schemas for the Siebel Integration Objects, and these are used to develop AIA requester ABCS. Perform the following tasks as part of the AIA Project Management Lifecycle for the Service Conception and Definition phase and the Service Design and Construction phase. For more information about these AIA lifecycle phases, see Section 20.2.3, Introduction to the Business Process Decomposition and Service Conception Phase and Section 20.2.4, Introduction to the Service Design and Construction Phase Tasks for Solution Architects in the Service Conception and Definition phase: 1. Identify the requester ABCS for the Siebel application and add them to the AIA project definition.

2. For new services, work with business analysts to capture the requirements in

detail.

3. For existing services, work with business analysts to capture details of changes to

be carried out.

4. Work with developers and drive the design of the services.

5. Finalize the format of the message.

6. Finalize the WSDL of the AIA requester ABCS.

7. Ensure the metadata of the service is captured in the Oracle Enterprise Repository.

8. Add the service to the deployment plan of the AIA project definition.

Tasks for Developers in the Service Design and Construction phase: 1. Analyze the Siebel requester Application Business Service definition provided by the Solution Architect. 2. Work with Siebel Application development and discuss the possible design. 3. Finalize the content of the message from Siebel. 4. Get the schema of the message from Siebel and ensure the following: a. TargetNameSpace - If higher than version 0, must have suffix VN where V is abbreviation for version and N is the version number. If there is no version number, it is considered to be version 0. Example 21–4 provides an example of version 1. Example 21–4 Example of a Version 1 TargetNameSpace xsd:schema xmlns:xsd=http:www.w3.org2001XMLSchema targetNamespace= http:siebel.comasiV1 xmlns:xsd=http:www.siebel.comxmlSWICustomerPartyIO b. Custom Attributes - Attributes in Example 21–5 are required: Establishing Resource Connectivity 21-15 Example 21–5 Required Custom Attributes xsd:attribute name=Language type=xsd:string xsd:attribute name=Locale type=xsd:string xsd:attribute name=MessageId type=xsd:string xsd:attribute name=EnterpriseServerName type=xsd:string A sample of custom attributes is provided in Example 21–6 . Example 21–6 Sample Custom Attributes xsd:complexType name=ListOfSwicustomerpartyio xsd:sequence xsd:element name=Contact type=xsdLocal:Contact minOccurs= 0 maxOccurs=unboundedxsd:sequence xsd:attribute name=Language type=xsd:string xsd:attribute name=Locale type=xsd:string xsd:attribute name=MessageId type=xsd:string xsd:attribute name=EnterpriseServerName type=xsd:string xsd:complexType 5. Construct a requester ABCS using the AIA Service Constructor. 6. Provide the WSDL from this service to the Siebel Application development team.

21.3.3 Creating JMS Consumers to Consume Siebel Messages from JMS QueuesTopics

Siebel Tools generates schemas for the Siebel Integration Objects, and these are used to develop AIA requester ABCS. Perform the following tasks as part of the AIA Project Management Lifecycle, during the Service Conception and Definition phase and the Service Design and Construction phase. For more information about these AIA lifecycle phases, see Section 20.2.3, Introduction to the Business Process Decomposition and Service Conception Phase and Section 20.2.4, Introduction to the Service Design and Construction Phase . Tasks for Solution Architects in the Service Conception and Definition phase: 1. Analyze the message to be pushed by the Siebel application. Since the Siebel application pushes the message using the Siebel Web Service framework, it is wrapped in the SiebelMessage envelope. This must be stripped off in the JMS consumer. 2. Create the definition of JMS consumer solution component in the AIA Lifecycle Workbench and mark it as of suitable asset type. Tasks for Developers in Service Design and Outline Construction phase: 1. Create a JMS Consumer Service Composite to be triggered by the message in the JMS queue and invoke the above ABCS. 2. Identify the name of the Queue. 3. Use the SOA Mediator component to create the adapter composite. 4. Annotate the composite.xml. For more information see Section 9.6, How to Annotate the Transport Adapter Composite . 5. Harvest to Oracle Enterprise Repository. 21-16 Developers Guide for Oracle Application Integration Architecture Foundation Pack For more information see Chapter 3, Harvesting Oracle AIA Content .

21.3.4 Outbound - Siebel Application Interaction with AIA Services