18 Loading AIA Metadata to Oracle Metadata Services Repository

You must upload Oracle Application Integration Architecture (AIA) metadata artifacts to the AIA MetaData folder in the SOA partition of the Oracle Metadata Services repository (MDS) after performing any of the following tasks:

Migrating services.

Making schema changes.

Making changes to configuration files AIAConfigurationProperties.xml and AIAEHNotification.xml.

18.2 Moving Abstract Service WSDLs into MDS

Abstract WSDLs of all AIA services must be stored in MDS.

For information about how MDS is used in AIA and the utility used to move artifacts to MDS, see "Using MDS in AIA" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

Note:

Abstract WSDLs should be modified to access the required schemas from MDS and then be moved to MDS.

For Application Business Connector Services (ABCS) and adapter services, abstract WSDLs are stored in MDS using the following structure: AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/<PRODUCT_CODE>/<Version Number>/<Service Type>.

Possible values for <Version Number> are V1, V2, and so on.

Possible values for <Service Type> are RequesterABCS, ProviderABCS, and AdapterServices.

Modify the abstract WSDLs to access the required schemas from the MDS and then load them to MDS.

The application entity schemas, or Application Business Message (ABM) schemas, should be accessible from MDS. They should not be a part of each ABCS project.

For ABCSs, abstract WSDLs are located here in MDS: AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/<PRODUCT_CODE>/<Version Number>/<Service Type>

Possible values for <Version Number> - V1, V2, and so on.

Possible values for <Service Type> are RequesterABCS and ProviderABCS.

For Composite Business Processes (CBPs) and Enterprise Business Flows (EBFs), abstract WSDLs are stored in MDS using the following structure: AIAMetaData\AIAComponents\BusinessProcessServiceLibrary\<Service Type>

For example:

AIAMetaData\AIAComponents\BusinessProcessServiceLibrary\CBP

AIAMetaData\AIAComponents\BusinessProcessServiceLibrary\EBF

To configure the artifacts before moving the abstract WSDLs into MDS:

Configure the ComponentType file to point to the abstract WSDLs in the MDS.

The ui:wsdlLocation attribute in the service element should point to the abstract WSDLs in the MDS.

Service Constructor generates empty port and location attributes for the binding.ws element under the reference element in the composite.xml file. Populate the attributes with relevant values as follows.

When the reference service is a BPEL component, the binding.ws element should be populated as shown here.

<binding.ws port="[Namespace of the Service as defined in thewsdl]
#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]"/>

The name of the service is the value of the attribute definition/name in the abstract WSDL. This follows the Service naming convention in the ABCS composite.

For example, Name of the Service is the <name of the composite>, which in turn is the value of the name attribute of the definitions element in the WSDL.

The URL of the concrete WSDL should use the following format: http://{host}:{port}/soa-infra/services/default)/[Name of the Service as given in the name attribute of the definition element in the WSDL]/[Name of the Porttype element as given in the WSDL]?WSDL

When the reference service is a mediator component, the binding.ws element should be populated as shown here:

<binding.ws port="[Namespace of the Service as defined in thewsdl]
#wsdl.endpoint([Name of the Porttype element as given in the WSDL]_ep/
[Name of the Porttype element as given in the WSDL]_pt)" location=
"[URL of the concrete WSDL]"/>

The URL of the concrete WSDL should use the following format: http://{host}:{port}/soa-infra/services/default)/[Name of the Porttype element as given in the WSDL]/[Name of the Porttype element as given in the WSDL]_ep?WSDL

18.3 Migrating the AIA Configuration Properties File

The AIAConfigurationProperties.xml file is a central place for system-, module-, and service-related settings in an AIA Foundation Pack environment. Starting with AIA Foundation Pack 11g Release 1, this file is placed in MDS.

The installation of AIA Foundation Pack 11g Release 1 includes a default configuration file and you must manually migrate any custom system and module settings from the AIA 2.4 or 2.5 environment. Specifically, these are the configurations that are part of the AIA configuration properties file, which is available on the server but not at the project folder.

See the following procedure for information about how to update AIAConfigurationProperties.xml with custom Service Configuration elements.

Service-related settings are handled by the AIA Migration Utility, which migrates them into a file called AIAServiceConfigurationProperties.xml for each migrated service.

AIA Installation Driver merges the content in AIAServiceConfigurationProperties.xml into AIAConfigurationProperties.xml as a part of the service deployment and uploads it into MDS.

Note that this does not happen when deploying from Oracle JDeveloper. In this case, the AIAConfigurationProperties.xml must be manually updated and uploaded to this location in MDS: SOA-MDS > apps/AIAMetaData/config.

To update AIAConfigurationProperties.xml with custom service configuration elements:

Access the $AIA_HOME/aia_instances/$INSTANCE_NAME/config folder.

Open AIAConfigurationProperties.xml and add the custom elements under respective service configurations.

Open the deployment plan file, UpdateMetaDataDP.xml. Update UpdateMetaDataDP.xml by inserting include tags for AIAConfigurationProperties.xml, which you want to add to the MDS: