How to Annotate the Reference Element in a Requester ABCS Composite How to Annotate the Service Element in a Provider ABCS Composite

9-12 Developers Guide for Oracle Application Integration Architecture Foundation Pack svcdoc:ServiceOperation svcdoc:ImplementationDetails svcdoc:Service svcdoc:AIA-- service In Example 9–6 , the value of the element, ArtifactType, is provided as RequesterABCSImplementation because the composite represents a Requester ABCS. The value of the element, ServiceOperationName, should be same as the value defined for the operation in the WSDL of the ABCS.

9.3 How to Annotate the Reference Element in a Requester ABCS Composite

To annotate the Reference Element in a requester ABCS composite: 1. Annotate the Reference Element in the composite, as shown in Example 9–7 , providing the details of the Service being invoked. Example 9–7 Reference Element in Requester ABCS Composite Annotation Example reference ui:wsdlLocation…………………………………………. interface.wsdl ……………………………………………. binding.ws………………………………………………….. --svcdoc:AIA svcdoc:Reference svcdoc:ArtifactTypeEnterpriseBusinessServicesvcdoc:ArtifactType svcdoc:ServiceOperation svcdoc:NameCreateCustomerPartyListsvcdoc:Name svcdoc:ServiceOperation svcdoc:Reference svcdoc:AIA-- reference ■ In Example 9–7 , the value of the element, ArtifactType, is provided as EnterpriseBusinessService because it references an external service in the composite. ■ In cases when the external service is an infrastructure utility, such as AIAAsyncErrorHandlingBPELProcess, then the value should be UtilityService. ■ The value of the element, ServiceOperationName, should be the same as the value defined for the operation in the WSDL of the service being referenced.

9.4 How to Annotate the Service Element in a Provider ABCS Composite

To annotate the Service Element in a provider ABCS composite: 1. Furnish the details of the interface that this ABCS is implementing.

2. Match the values for elements ServiceName, Namespace, and

ServiceOperationname with the corresponding values defined in the interface services WSDL target participating application as shown in Example 9–8 . Annotating Composites 9-13 Example 9–8 Service Element in a Provider ABCS Composite Annotation Example service ui:wsdlLocation=……………… interface……………………………… binding.ws ……………………….. --svcdoc:AIA svcdoc:Service svcdoc:InterfaceDetails svcdoc:ServiceNameCustomerPartyEBSsvcdoc:ServiceName svcdoc:Namespacehttp:xmlns.oracle.comEnterpriseServicesCoreCustomerParty V2svcdoc:Namespace svcdoc:ArtifactTypeEnterpriseBusinessServicesvcdoc:ArtifactType svcdoc:ServiceOperation svcdoc:NameCreateCustomerPartyListsvcdoc:Name svcdoc:ServiceOperation svcdoc:InterfaceDetails svcdoc:ImplementationDetails svcdoc:ApplicationNameSamplePortalsvcdoc:ApplicationName svcdoc:BaseVersion1.0svcdoc:BaseVersion svcdoc:DevelopedByOraclesvcdoc:DevelopedBy svcdoc:OracleCertifiedYessvcdoc:OracleCertified svcdoc:ArtifactTypeProviderABCSImplementationsvcdoc:ArtifactType svcdoc:ServiceOperation svcdoc:NameCreateCustomersvcdoc:Name svcdoc:ServiceOperation svcdoc:ImplementationDetails svcdoc:Service svcdoc:AIA-- service ■ In Example 9–8 , the value of the element, InterfaceDetailsArtifactType, is provided as EnterpriseBusinessService because it defines the interface that is being implemented by the Provider ABCS. ■ ImplementationDetailsArtifactType , is provided as ProviderABCSImplementation because the composite represents a provider ABCS. ■ The value of the element, ServiceOperationName, should be same as the value defined for the operation in the WSDL of the ABCS.

9.5 How to Annotate the Reference Element in a Provider ABCS