Oracle® Application Integration Architecture

Release Notes

Release 12.2.1

F26888-01

March 2020

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

This document contains the following sections:

New Features

Release 12.2.1 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.2.1 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

Fixes in This Release

This section lists the fixed issues and provides a brief description of the resolution.

Issue: BRM extends the global transaction to ECE and does not close the transaction even after a response is sent back to AIA. After a response from BRM, AIA continues the flow further to get it closed, but the transaction is still with ECE and rolls back after AIA completes the process. The AIA processes are also part of the same global transaction. Hence, AIA is not able to handle the rollback of the extended ECE transaction.

Resolution: To resolve this issue, a master process has been introduced. This master process is a pass-through and does not participate in the global transaction. With this configuration, AIA master process can handle a rollback of global transaction, which is extended to ECE by BRM.

Known Problems

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

Known Issue with Siebel 19.11

Siebel account updates are not getting populated into AIA. Although WorkflowProcess is enabled, the State field shows “Not Online”. As a result, AIA is not receiving the account update triggers from Siebel. There is no workaround for this issue.

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

This 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.

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.

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.


Oracle Application Integration Architecture Release Notes, Release 12.2.1

F26888-01

Copyright © 2020, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or “commercial computer software documentation” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.