How to Create the ABCS in the Service Constructor How to Complete ABCS Development for the AIA Service Constructor

12-6 Developers Guide for Oracle Application Integration Architecture Foundation Pack

12.2.1 How to Create the ABCS in the Service Constructor

See Chapter 19, Working with Service Constructor.

12.2.2 How to Complete ABCS Development for the AIA Service Constructor

After the ABCS is created in the Service Constructor, the following post-ABCS construction tasks must be performed manually. Complete the following manual post-ABCS construction tasks: 1. Move abstract WSDLs of Application Business Service Connector to the MDS. Refer to Section 20.1.3.4, Using MDS in AIA. 2. Configure the JDeveloper to access the MDS repository. Refer to Section 20.1.3.4, Using MDS in AIA. To complete ABCS development for the AIA Service Constructor: 1. Rearrange service invocations, if necessary. The AIA Service Constructor generates relevant definitions for all external service invocations in a sequence in the order that you specify while using the wizard. If your ABCS requires that the invocations be done either in parallel or based on certain other conditions, rearrange the services as needed using Oracle BPEL Designer. 2. Complete the business payload transformation. The AIA Service Constructor generates transformations only if the target document is an Enterprise Business Message and generates root element business transformations only. It generates the transformation mapping pertaining to most of the header elements, and the XSL code pertaining to the business payload that is common to all of the ABCSs. Use Oracle BPEL Designer to develop the transformation code for transforming remaining parts of the message document to complete the business payload and header transformation. 3. Configure correlation properties for asynchronous application service invocation. The AIA Service Constructor does not generate correlation properties for any application target service that is being invoked using an asynchronous request-response MEP. Use Oracle BPEL Designer to configure the correlation upon the invoke activity and subsequent receive activity. 4. Create invocations for other operations when a service is called multiple times. If a service is called multiple times, the AIA Service Constructor does not generate code for multiple invocations. Copy and paste the invocation code generated for the first service invocation from the same process and rename operations and variables. 5. Populate attributes of binding.ws element of the reference services in the composite.xml file. Tip: Ensure that the required AOL schemas are available in the MDS on the server. Constructing the ABCS 12-7 For a better understanding of why this is recommended, see Section 27.1.6, Separation of Concerns. In the composite.xml file, under the element reference, the AIA Service Constructor generates empty attributes, port, and location for the element binding.ws. Populate the attributes with relevant values as specified in the following list. a. When the referenced service is BPEL-based, the binding.ws element should be populated as shown in Example 12–1 . Example 12–1 Binding.ws element for BPEL-based Service binding.ws port=[Namespace of the Service as defined in the wsdl]wsdl.endpoint[Name of the Service as given in the WSDL][ Name of the Porttype as given in the WSDL location= URL of the concrete WSDL] This follows from naming conventions for the Service name in the ABCS Composite. The name of the service is name of the composite, which in turn is the value of the attribute name, of the element definitions, in the WSDL. The URL of the concrete WSDL uses this format as shown in Example 12–2 : http:{host}:{port}soa-infraservicesdefault[Name of the Service as given in the attribute name of the element definition in the WSDL][Name of the Porttype element as given in the WSDL]?WSDL Example 12–2 URL of the Concrete WSDL for BPEL-based Service binding.ws port=http:xmlns.oracle.comSamplePortalAppwsdl.endpointSamplesCreateCustomer PartyPortalProviderSamplesCreateCustomerPartyPortalProvider location=http: {host}:{port}soa-infraservicesdefaultSamplesCreateCustomerPartyPortalProvider SamplesCreateCustomerPartyPortalProvider?WSDL

b. When the referenced service is mediator-based, then the binding.ws element