For new services, work with business analysts to capture the requirements in For existing services, work with business analysts to capture details of changes to Work with developers and drive the design of the services. Finalize the format of the message.

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