Oracle® Application Integration Architecture

Simplified Installation

Release 12.2 provides all Oracle AIA software in one installation package.

In previous releases, the Oracle AIA installation was a two-step process: First you installed the Oracle AIA Foundation Pack and then you installed and configured the pre-built integrations.

In release 12.2, because all foundational components are bundled within Oracle Service Oriented Architecture (SOA) Suite and the pre-built integrations, you install and configure all Oracle AIA software in one step.

Simplified Packaging

Release 12.2 provides new packaging and deployment for the Communications Order to Cash pre-built integration options.

In previous releases, the pre-built integration options aligned with business processes, such as Order to Bill, Order to Activate, and Order to Cash.

In release 12.2, the pre-built integration options align with the integrated applications with the following options:

• Communications Order to Cash for Siebel CRM

• Communications Order to Cash for OSM

• Communications Order to Cash for BRM

The Oracle AIA Installer and Configuration Wizard support these changes.

Configuration Wizard Fails on Windows

BugDB number: 25246380

This problem applies to all pre-built integrations.

When installing Oracle AIA on Windows, the Configuration Wizard fails when it attempts to run the SOA createStore utility.

There is no workaround for this problem.

Not All Agent Assisted Billing Care Services Undeployed

BugDB number: 23053792

This problem applies to the pre-built integration for Agent Assisted Billing Care when the pre-built integration for Order to Cash is also deployed.

When undeploying the pre-built integration for Agent Assisted Billing Care after you have undeployed the pre-built integration for Order t o Cash, some Siebel CRM services are not undeployed.

To resolve this problem, restart the Oracle WebLogic servers and the database before running the undeployAABC.sh script.

Undeployment Fails

BugDB number: 25371250This problem applies to all pre-built integrations.When undeploying the pre-built integrations, if you have never restarted the WebLogic servers and database after deploying the pre-built integrations, the undeployment scripts fail.To resolve this problem, restart the WebLogic servers and the database before running the undeployment scripts.

Oracle Web Services Manager Policy Manager in Admin State and Managed Server Slow to Start After Upgrade

This problem applies to pre-built integrations that use the BRM JCA Resource Adapter.

After upgrading to Oracle AIA 12.2, if you are using a BRM JCA Resource Adapter of version 7.5 with patch set 12 or earlier, the wsm-pm component is in the Admin state and the managed server is slow to start.

To resolve this problem:

1. Log in to the WebLogic Server Administration console.

2. From the Domain Structure tree, select Deployments.

3. From the table of deployments, select OracleBRMJCA14Adapter.

   You may need to page through the table to locate this deployment.

4. In the Deployment Order field, enter 100.

5. Click Save.

6. Restart the managed server.

AIASecurityConfigurationProperties.xml Does Not Exist

BugDB number: 22754867

After running the deployment script for the Communications Order to Cash pre-built integration option for BRM, the following error message appears in the deployment log file:

AIASecurityConfigurationProperties.xml does not exist in
Install_directory/comms_home/source/soainfra/apps/services/industry/Communications/BRM/ProviderABCS/CreateReceivedPaymentListBRMCommsProvABCSImpl/SOA

where Install_directory is the directory where you installed Oracle AIA.

This error appears because, although the AIASecurityConfigurationProperties.xml file is no longer delivered with Oracle AIA, the SOA deployment tool still checks for the file and adds the error message when it fails to find the file. Because the missing file does not interfere with deployment or functionality, you can ignore this error.

Missing Test Orchestration Process Connection Factories Preventing Order Processing

If you are deploying the Order to Cash for Siebel CRM and Order to Cash for BRM pre-built integration options and are using your own order management system (other than OSM), you must deploy the required connection factories for the test orchestration process or orders will fail.

To resolve this problem:

1. Create an XML file containing the following:

   <?xml version="1.0"?>
   <DeploymentPlan component="O2C" version="12.0">
   <Configurations>
   <ManagedServer wlserver="pips.O2C" action="shutdown" failonerror="true"/> 
   <JMSConnectionFactory connFacName="COMMS_ORDERORCHESTRATION_PRODUCER" connFacJNDI="jms/aia/COMMS_ORDERORCHESTRATION_PRODUCER" jmsModuleName="AIAJMSModule" jmsSubDeploymentName="AIASubDeployment"  action="create" wlserver="pips.O2C" isXA="true"/>
   <JmsAdapter jndi-name="eis/wljms/COMMS_ORDERORCHESTRATION_PRODUCER" connection-fac-Location="jms/aia/COMMS_ORDERORCHESTRATION_PRODUCER" isTopic="false" isTransacted="false" action="create" wlserver="pips.O2C"/>
   <JMSConnectionFactory connFacName="COMMS_ORDERORCHESTRATION_CONSUMER" connFacJNDI="jms/aia/COMMS_ORDERORCHESTRATION_CONSUMER" jmsModuleName="AIAJMSModule" jmsSubDeploymentName="AIASubDeployment"  action="create" wlserver="pips.O2C" isXA="true"/>
   <JmsAdapter jndi-name="eis/wljms/COMMS_ORDERORCHESTRATION_CONSUMER" connection-fac-Location="jms/aia/COMMS_ORDERORCHESTRATION_CONSUMER" isTopic="false" isTransacted="false" action="create" wlserver="pips.O2C"/>
   <ManagedServer wlserver="pips.O2C" action="start" failonerror="true"/> 
   </Configurations> 
   </DeploymentPlan>
   

2. Save the file as DeployTOPConnFactories.xml.

3. Create one of the following scripts, depending on your environment:

   • For UNIX, create a script named deploy.sh containing the following:

     source $COMMS_HOME/bin/commsenv.sh
     ant -f $SOA_HOME/aiafp/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=New_DP_Path -DPropertiesFile=$DOMAIN_LOCATION/soa/aia/bin/AIAInstallProperties.xml
     

   • For Windows, create a script named deploy.bat containing the following:

     source %COMMS_HOME%\bin\commsenv.bat
     ant -f %SOA_HOME%\aiafp\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=New_DP_Path -DPropertiesFile=%DOMAIN_LOCATION%\soa\aia\bin\AIAInstallProperties.xml
     

   where New_DP_Path is the path to the newly-created DeployTOPConnFactories.xml file.

4. From the command line, run deploy.sh or deploy.bat.

   The required connection factories are created and deployed.

Publication of Hierarchical Item Catalog Categories Fails

BugDB number: 25222766

When using Siebel version 8.1.1.16, publishing parent and child item catalog categories together from Oracle Product Hub to Siebel CRM fails.

To resolve this problem, publish the parent and child item catalog categories separately and manually create the hierarchy in Siebel CRM.

Note: This problem does not exist when using Siebel version 8.1.1.14.

Extra Child Component Created When Changing Product Name

BugDB number: 22390890

When changing the name, description, or long description of a product in Oracle Product Hub and resynchronizing the product to Siebel CRM, a new child component with the new name is created for the product in Siebel CRM and the original child component retains the original name.

To resolve this problem, delete the child component with the original name.

Product Lines with Multiple Products Overwriting Existing Products

BugDB number: 23031264

When synchronizing a product line with multiple products from Oracle Product Hub to Siebel CRM, the product synchronization succeeds, but each product associated with the product line overwrites the previous product. This results product lines with single products rather than the intended multiple products.

To avoid this problem, associate each product line with one product only. You can also associate a single product to multiple product lines.

This problem also applies to version 11.6.