1. Cloud Native Deployment Guide
  2. Upgrading to AIA Cloud Native 12.3.2

9 Upgrading to AIA Cloud Native 12.3.2

This chapter describes how to upgrade to AIA cloud native 12.3.2 from a prior release of AIA traditional deployment.

About Upgrading to AIA Cloud Native 12.3.2

As a part of upgrading to AIA, you upgrade Oracle AIA pre-built integrations and Oracle AIA Foundation Pack to Oracle AIA cloud native.

It applies to upgrades from Oracle AIA version 12.3 deployed on Oracle Fusion Middleware 12.2.1.4, referred to as the source version. Oracle AIA cloud native 12.3.2 includes significant structural changes, including compatibility with Oracle Service Oriented Architecture (SOA) 12.2.1.4. Because of these changes, you cannot perform a traditional upgrade, and instead must perform a new installation of SOA 12.2.1.4 and migrate any relevant data. SOA 12.2.1.4 does not support in-place migration if the domains include SOA Core Extension. Hence, perform a side-by-side migration. For more information about SOA domain upgrade restrictions, see Oracle Fusion Middleware Upgrading SOA Suite and Business Process Management for release 12c (12.2.1.4.0).

Performing Pre-Upgrade Tasks

Before upgrading to this release of Oracle AIA, perform the following pre-upgrade tasks:
  1. Back up your source version of Oracle AIA, including the Oracle AIA home directory and any customized Oracle AIA artifacts in the enterprise object library. This includes customizations to:
    • Enterprise Business Objects (EBOs), including custom XSD files in the following directories:
      • Install_home/comms_home/source/soainfra/apps/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/Custom/EBO/
      • Install_home/comms_home/source/soainfra/apps/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Industry/Industry_Name/Custom/EBO
    • Extensible style sheet language transformations (XSLTs)
    • Enterprise Business Services (EBS)
    • Web Service Definition Language (WSDL)
    • Any EBS with custom routing rules
    • The AIAConfigurationProperties.xml file.
  2. Install or upgrade to compatible versions of the foundational software, as described in "Software Requirements".

    Note:

    You must install SOA Suite 12.2.1.4 and create a new domain. Because Oracle AIA cloud native 12.3.2 requires a custom domain extension, you cannot upgrade an existing SOA domain.

    For information about installing SOA Suite, see Oracle Fusion Middleware Upgrading SOA Suite and Business Process Management.

    For information about version compatibility, see Application Integration Architecture Compatibility Matrix.

Performing the Upgrade

To upgrade to Oracle AIA Cloud Native 12.3.2, install and configure Oracle AIA Cloud Native 12.3.2 as described in this guide. Because of the structural changes between source versions and Oracle AIA Cloud Native 12.3.2, you must perform a new installation of Oracle AIA.

Also, refer to "Overview of Oracle AIA Installation Procedure" for an overview of the installation process.

Do not deploy the pre-built integrations until after you have performed the other post-upgrade tasks described in "Performing Post-Upgrade Tasks".

Performing Post-Upgrade Tasks

After upgrading to this release of Oracle AIA, perform the following tasks:

  1. Set JVM parameters for Siebel CRM. See "Setting JVM Parameters for Siebel CRM" for more information.

  2. Migrate any customizations or extensions that you made in source files and composites to 12.3.2 versions manually. See "Migrating Custom Artifacts" for more information.

  3. Migrate Oracle AIA database tables, including error tables and cross-reference tables to the 12.3.2 database schema. See "Migrating Database Tables" for more information.

  4. Deploy the 12.3.2 pre-built integrations as described in "Deploying Pre-built Integrations."

  5. Perform post-installation tasks as described in "Performing Post-deployment Tasks."

Setting JVM Parameters for Siebel CRM

After the upgrade, the Siebel CRM administrator must perform the following tasks for Siebel CRM:

  1. Set up the Oracle WebLogic Server thin client for Siebel CRM:
    1. On the SOA 12.2.1.4 host, navigate to MW_home/wlserver/server/lib.
    2. Copy the wlthint3client.jar file to the JMS directory on the Siebel CRM host. This is the directory that contains the JNDI properties, siebel.jar, and siebelUI_enu.jar files.
    3. If the wlfullclient.jar file also appears in the JMS directory on the Siebel CRM host, back the file up to another location and remove it from the JMS directory.
  2. In Siebel CRM, from the site map, select Administration - Server Configuration and then select Profile Configuration.
  3. In the Enterprise Profiles list, in the Alias column, select the row with JAVA.
  4. In the Profile Parameters list, select the JVM DLL Name row.
  5. In the value column, update the value to the path to the JVM library file for Java Development Kit (JDK) version 1.8. For example, Oracle_home/Java/jdk1.8.0_102/jre/lib/i386/client/libjvm.so.
  6. Select the JVM Classpath row.
  7. In the value column, add the path to the newly-copied wlthint3client.jar file. On UNIX, separate the files in this field with a colon (:). On Windows, separate the files in this field with a semicolon (;). For example, on UNIX, Oracle_home/jms/Siebel.jar:Oracle_home/jms/wlthint3client.jar.
  8. Restart the Siebel CRM services.

Migrating Custom Artifacts

After installing AIA, you must manually migrate any customizations you made to the source data.

To migrate custom artifacts:

  1. For any of the Oracle AIA artifacts listed in the table that follows, merge any customizations to ready-to-use artifacts and copy custom-created artifacts into the 12.3.2 directory. The artifacts listed in the 12.3.2 Directory and Modified Artifacts column have been updated for 12.3.2. When merging customizations to these artifacts, be careful not to overwrite the updated functionality.

    Table 9-1 Customized Oracle AIA Artifacts to Migrate

    Artifact 12.3.2 Directory and Modified Artifacts

    Enterprise Business Objects

    Enterprise Business Services

    WSDL schemas

    Directory:

    The appropriate subdirectory under $AIA_PV/aia-comms/commsOracleHome/comms_home/source/soainfra/apps/AIAMetaData/AIAComponents

    No modified artifacts.

    Cross-reference files

    Directory:

    $AIA_PV/aia-comms/commsOracleHome/comms_home/source/soainfra/apps/AIAMetaData/xref

    Modified artifacts:

    • CUSTOMERPARTY_PARTYLOCATIONID

    • CUSTOMERPARTY_PAYPROFILEID

    • CUSTOMERPARTY_LOCATIONREFID

    • CUSTOMERPARTY_PARTYCONTACTID

    • CUSTOMERPARTY_BILLPROFILEID

    • SALESORDER_LINEID

    • CUSTOMERPARTY_ACCOUNTID

    • ITEM_ITEMID

    • CUSTOMERPARTY_CONTACTID

    • CUSTOMERPARTY_CONTACT_PHONECOMMID

    • CUSTOMERPARTY_ADDRESSID

    • CUSTOMERPARTY_HIERARCHYBILLINFO

    • CUSTOMERPARTY_PARTYID

    • INSTALLEDPRODUCT_ID

    • CUSTOMERPARTY_DEFAULTBALANCEGROUPID

    • SALESORDER_ID

    • CUSTOMERPARTY_CONTACT_EMAILCOMMID

    Domain value maps

    Directory:

    $AIA_PV/aia-comms/commsOracleHome/comms_home/source/soainfra/apps/AIAMetaData/dvm

    Modified artifacts:

    • SALESORDER_STATUS

    • ADDRESS_COUNTRYID

    • PRICE_OVERRIDETYPECODE

    • CUSTOMERPARTY_ACCOUNTTYPECODE

    • APPLIES_TO

    • PRICECHARGETYPE

    • SALESORDER_LINESTATUS

    • CUSTOMERPARTY_PAYPROFILE_PAYMETHODCODE

    • ITEM_BILLINGTYPECODE

    • CURRENCY_CODE

    • STATE

    XSLT files

    Directory:

    $AIA_PV/aia-comms/commsOracleHome/comms_home/source/soainfra/apps/services/…/service_name/SOA/Transformations

    No modified artifacts.
  2. Upload any new or changed files to the Oracle Metadata Services repository as described in "Managing Oracle AIA Files in the MDS Repository".
  3. For any custom-created source services:
    1. In Oracle JDeveloper version 12.2.1.4, open the .jpr file for the service. JDeveloper updates the composite.
    2. Save the project and files under the appropriate directories. For example, save .wsdl files in the WSDL directory.
    3. Deploy the custom services from the JDeveloper context menu. Use the composite.xml file in the service's SOA directory as the deployment descriptor file. For information about deploying applications using JDeveloper, see Oracle Fusion Middleware Developing Applications with Oracle JDeveloper.
  4. For any ready-to-use source services that you have customized within customizable scopes:
    1. Copy the required composite from the AIA server COMMS_Home/comms_home/source/soainfra/apps or COMMS_Home/comms_home/pips to your local JDeveloper.
    2. Open the project in JDeveloper 12.2.1.4 and customize the customizable scopes.
    3. Copy the composite and files back to the AIA server location from where they were copied.
    4. Deploy the customized composite from the AIA server using PIP depolyment scripts.
  5. For the Agent Assisted Billing Care pre-built integration, manually migrate any customizations made in the source Oracle Data Integrator integration projects to 12.3.2. See Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator for information about customizing Oracle Data Integrator integration projects.

Migrating Database Tables

After migrating customizations, you must migrate the data in the following Oracle AIA database tables:

  • Migrate the data in the source domainName_AIA schema to the 12.3.2 SOAINFRA schema for the following tables:

    • AIA_ERROR_MONITOR

    • AIA_ERROR_FLEX_FIELD

    Note:

    Because AIA_ERROR_FLEX_FIELD depends on AIA_ERROR_MONITOR, you must migrate the data in AIA_ERROR_MONITOR first.

  • Migrate your Oracle AIA cross-reference data from the source AIAInstanceName_XREF schema to the 12.3.2 domainName_COMMS_XREF schema created by the Oracle AIA Configuration Wizard (where AIAInstanceName is the name of the source Oracle AIA instance and domainName is the name of the 12.2.1.4 SOA domain). You must migrate one cross-reference table at a time.

You can use Oracle SQL Developer to migrate the data as follows:

  1. On the source environment in SQL Developer, in the Connections navigator, expand your source database connection, then expand Tables.

  2. Right-click the table you want to export and select Export.

  3. Select the Export Data option, specify the SQL format, and complete the export.

  4. Move the exported SQL file from the source environment to the AIA 12.3.2 environment and open it in a text editor.

  5. Remove the schema name and keep the file open.

  6. On the 12.3.2 environment in SQL Developer, open the SQL Worksheet for your 12.3.2 database connection.

  7. From the exported SQL file, copy all SQL statements and paste them into the SQL Worksheet.

  8. Click the Run Script icon.

    The data is imported.

Note:

If you see an error about large data size in the stack trace column, edit the SQL file to make one insert statement in a single line and try the import again.

Consult your database administrator for help migrating database data and see Oracle SQL Developer User's Guide for more details about using SQL Developer.