How to Create References, Services, and Components Moving Abstract Service WSDLs in MDS

12-12 Developers Guide for Oracle Application Integration Architecture Foundation Pack ■ Extensibility ■ CAVS enablement ■ Security context implementation For more information about completing ABCS development, see Chapter 13, Completing ABCS Development .

12.3.3 How to Create References, Services, and Components

■ For each target, add a reference. – The target can be a web service or adapter. – If the target service requires transformation, create a mediator component in between. ■ For each interface, add a service. – The service can be a web service or adapter. – If the adapter interface requires transformation, create a mediator component in between.

12.3.4 Moving Abstract Service WSDLs in MDS

SOA Suite 11g has introduced a central repository, Metadata Service MDS, that backs up your application and hence your composites at design time and run time. MDS is like a version management system, where you can store and use the shared common artifacts at design and run time. AIA leverages the MDS repository to store common design time artifacts that are shared with all developers. There is a common directory of abstract WSDLs in the MDS, which is a centrally accessible endpoint. The artifacts that are stored in the MDS include: ■ Schemas: EBO schemas and ABM schemas ■ WSDLs: Abstract WSDLs of EBS, ABCS, Adapter Services, CBPs and EBFs All the abstract WSDLs of all AIA services are put in MDS. You build your consuming AIA service composite application using the abstract WSDL of a referenced service. No dependency exists on the order of deployment for composites. Since there is no dependency on the referenced services during the deployment of the composites, there is no dependency on the order of deployment for the composites. A referenced service does not have to be deployed in order to be referenced by another service. This also resolves the cases where there are cyclic references involved among the services. To get a better understanding of why this is recommended, see Section 27.1.6, Separation of Concerns. Tip: Always use the abstract WSDL to refer to the services that must be invoked. The reference binding component should always use the abstract WSDL. Do not use the concrete WSDLs directly in your consuming artifacts. Do not reference the deployed concrete WSDL of a Service Provider The following paragraphs describe how this can be accomplished. Constructing the ABCS 12-13 For details of how MDS is used in AIA, refer to Section 20.1.3.4, Using MDS in AIA. For ABCSs and Adapter services, the abstract WSDLs are to be located in MDS at: AIAMetaDataAIAComponentsApplicationConnectorServiceLibraryPRODUCT_ CODEVersion NumberService Type Possible values for Service Type are RequesterABCS, ProviderABCS, AdapterServices. Possible values for Version Number are V1, V2. The utility for moving artifacts to MDS is described in Section 20.1.3.4, Using MDS in AIA . Examples: AIAMetaDataAIAComponentsApplicationConnectorServiceLibrarySiebelV1RequesterAB CS AIAMetaDataAIAComponentsApplicationConnectorServiceLibrarySiebelV1ProviderABC S

12.4 Implementing the Fire-and-Forget MEP