This document provides release notes for Oracle Application Integration Architecture release 12.3.

This document contains the following sections:

Note:

For this release, Application Integration Architecture Installation Guide has been updated. The following documents have not been updated for this release:
  • Application Integration Architecture Agent Assisted Billing Care Integration Pack Implementation Guide
  • Application Integration Architecture Oracle Communications Order to Cash Integration Pack Implementation Guide

New Features

Release 12.3 is primarily a technology stack uptake and alignment release. In addition, this release is certified with the latest RODOD application versions of Siebel, OSM, and BRM. See the Oracle AIA compatibility matrix available on My Oracle Support for details about compatible versions: http://support.oracle.com/epmos/faces/DocumentDisplay?id=2226851.1

This release complements existing implementations of AIA for Communications and RODOD if you are planning to upgrade your technology and application stack either due to end of error correction or to take advantage of new features. In addition to the technology stack uptake, several issues have been resolved.

Release 12.3 is supported on:

  • Oracle Fusion Middleware 12.2.1.4
  • Oracle Database 19c and 18c
  • Oracle Software Oriented Architecture (SOA) Suite 12.2.1.4

Known Problems

This section describes the known problems and fixes that apply to release 12.3.

TLS 1.0 and 1.1 Disabled with JDK 1.8_291 and Higher

TLS 1.0 and TLS 1.1 protocols are now disabled in JDK version 1.8_291 and higher. For HTTPS connectivity, you should continue to configure the edge applications such as Siebel with TLS 1.2 or higher. For more details, see the JDK 8u291 Update Release Notes at: https://www.oracle.com/java/technologies/javase/8u291-relnotes.html.

Known Problems for Multiple Pre-Built Integrations

The known problems in this section apply to multiple pre-built integrations.

Not All Agent Assisted Billing Care Services Undeployed

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 to 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

This problem applies to all pre-built integrations. When undeploying the pre-built integrations, if you have never restarted the WebLogic servers and the 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.

Known Problems for Communications Order to Cash

The known problems in this section apply only to the Communications Order to Cash pre-built integration.

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. Otherwise, the orders will fail.

Note:

If you have also deployed the Order to Cash for OSM pre-built integration option, this problem does not apply.

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:
    1. 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
    2. 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.

Deprecated and Removed Features

This section lists deprecated and removed features in AIA 12.3.

Email Error Notification

Email error notification has been obsoleted in this release.

Windows Support

Windows support for Order-to-Cash Integration Pack and Agent Assisted Billing Care Integration Pack has been removed.

Test Orchestration Process

Test orchestration process in the Order to Cash pre-built integration pack has been removed.

Pre-built Integration Options

The following pre-built integration options have been removed:
  • Customer MDM Base
  • Customer MDM for Siebel CRM
  • Customer MDM for E-business Suite
  • Product MDM for Siebel CRM

Resubmission Utility

The Resubmission utility has been deprecated in this release.

Composite Application Validation System (CAVS)

Composite Application Validation System (CAVS) has been deprecated in this release.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.