K Composite Application Validation System Changes

This appendix discusses how the Composite Application Validation System (CAVS) has changed from the Oracle Application Integration Architecture (Oracle AIA) Communications 11.1 release to the Oracle AIA Communications 11.2 release and provides details on Requestor application business connector services (ABCSs) and Provider ABCSs.

Configuration Properties for CAVS Enablement in 11.1

In the 11.1 Oracle AIA CAVS implementation, every service has a number of configuration properties.

See Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack for more information on configuration properties.

For the RouteToCAVS property, the ready-to-use value is False. Oracle AIA provides a user interface (UI), which allows the user to toggle this property value between True and False for each service listed.

To navigate to this UI:

1. Log in to the AIA Console (http://<host>:<port>/AIA).

2. Go to Setup.

3. Select the AIA Configuration tab.

Configuration Properties for CAVS Enablement in 11.2

CAVS enablement has been reorganized. As a result, the UI can no longer be used to toggle the value of the RouteToCAVS property for the Communications Order to Cash services, which are part of the 11.2 release.

The following instructions describe how to modify the configuration properties for Requestor ABCS and Provider ABCS to enable CAVS.

Note:

Any change in the System Configuration screen does not enable CAVS for a service. You must make changes manually in the Oracle AIA configuration file to make the service CAVS enabled.

Requestor ABCS

For CAVS enablement of Requestor ABCS, a single configuration property is maintained.

For example,

EBSOverride.CommunicationsSalesOrderEBSV2.ProcessSalesOrderFulfillment.Address

In order to enable CAVS, you must manually edit the AIAConfigurationProperties.xml file, which is located in: $AIA_HOME/aia_instances/$INSTANCE_NAME/AIAMetaData/config. Entries in the AIAConfigurationProperties.xml file are case sensitive.

To enable CAVS for Requestor ABCS:

1. Open the AIA configuration properties file.

2. Set the Address property to the CAVS URI for each service that you want to be CAVS enabled.

   For example:

   http://<soa_server>:<soa_port>/AIAValidationSystemServlet/asyncrequestrecipient
   

3. Save and close the file after you have set this property for all desired Requestor ABCSs.

4. To make your changes effective. Login to the AIA Console (http://<host>:<port>/AIA).

5. Go to Setup and select AIA Configuration tab.

6. Click Reload to reload the configuration file and make your changes effective.

Provider ABCS

For CAVS enablement of a Provider ABCS, two configuration properties are maintained. For example:

• "Routing.SWI_spcOrder_spcUpsert.RouteToCAVS"

• "Routing.SWI_spcOrder_spcUpsert.SEBL_01.EndpointURI"

In order to enable CAVS, you must manually edit the AIAConfigurationProperties.xml file, which is located in: $AIA_HOME/aia_instances/$INSTANCE_NAME/AIAMetaData/config. Entries in the AIAConfigurationProperties.xml file are case sensitive.

To enable CAVS for Provider ABCS:

1. Open the AIA configuration properties file.

2. Set the RouteToCAVS property value to True and set the EndpointURI property value to the actual CAVS URL for each service that you want to be CAVS enabled.

3. Save and close the file after you have set this property for all desired Provider ABCSs.

4. Login to the AIA Console (http://<host>:<port>/AIA). Go to Setup, and then select the AIA Configuration tab. Click Reload to relaod the configuration file and make your changes effective.