8 Upgrading to Oracle AIA 12.2

This chapter describes how to upgrade Oracle Application Integration Architecture (Oracle AIA).

About Upgrading to Oracle AIA 12.2

This chapter describes the upgrade procedure for Oracle AIA pre-built integrations and Oracle AIA Foundation Pack to Oracle AIA 12.2. It applies to upgrades from Oracle AIA versions deployed on Oracle Fusion Middleware 10g and 11g, referred to as the source versions.

Oracle AIA 12.2 includes significant structural changes, including compatibility with Oracle Service Oriented Architecture (SOA) 12.2.1.1. Because of these changes, you cannot perform a traditional upgrade, and instead must perform a new installation of SOA 12.2.1.1 and migrate any relevant data.

Pre-Upgrade Tasks

Before upgrading to Oracle AIA 12.2, 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 a new version of SOA Suite and create a new domain. Because Oracle AIA 12.2 requires a custom domain extension, you cannot simply 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, search for Oracle AIA on the My Oracle Support Certifications tab.

Upgrading to Oracle AIA 12.2

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

See "Oracle AIA Installation Overview" for more information about the installation process.

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

Post-Upgrade Tasks

After upgrading to Oracle AIA 12.2, perform the following tasks:

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

  2. Manually migrate any customizations or extensions that you made in source files and composites to 12.2 versions. See "Migrating Custom Data" for more information.

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

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

  5. Perform post-installation tasks as described in "Oracle AIA Post-Installation Tasks".

Setting JVM Parameters for Siebel CRM

After upgrading installing Oracle AIA 12.2, 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.1 host, navigate to the following directory:

      MW_home/wlserver/server/lib

    2. Run the following command:

      java -jar wljarbuilder.jar

      The wlthint3client.jar file is generated.

    3. Copy the wlthint3client.jar file to the JMS directory on the Siebel CRM host. This is the directory containing the JNDI properties, siebel.jar, and siebelUI_enu.jar files.

    4. 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, select the row with JAVA in the Alias column.

  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 files in this field with a colon (:). On Windows, separate 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 Data

After installing Oracle AIA 12.2, you must manually migrate any customizations you made to the source data. There are no automated scripts or tools to assist in this task.

To migrate custom data:

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

    Table 8-1 Customized Oracle AIA Artifacts to Migrate

    Artifact 12.2 Directory and Modified Artifacts

    Enterprise Business Objects

    Enterprise Business Services

    WSDL schemas

    Directory:

    The appropriate subdirectory under Comms_home/source/soainfra/apps/AIAMetaData/AIAComponents

    No modified artifacts.

    Cross reference files

    Directory:

    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:

    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:

    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.1, 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. Open JDeveloper 12.2.1.1.

      The Select Role dialog box appears.

    2. Select Default Role and click OK.

    3. In the Projects section, select the top-level element.

    4. From the File menu, select Import.

    5. Select SOA Archive Into SOA Project and click OK.

    6. Click Browse.

    7. Browse to the directory where the upgraded version of the deployed composite is copied. For example:

      C:\DeployedCodeFromServer\ABCS\ABCS_V2\deploy

      where DeployedCodeFromServer is the directory where the deployed composite is copied, ABCS is the composite name, and ABCS_V2 is the upgraded version of the composite.

    8. Select the .jar file for the new composite and click Open.

    9. Select the Import for Customization option and click Finish.

    10. From the Tools menu, select Preferences.

    11. From the navigation tree, select Roles.

    12. Under Roles, select Customization Developer.

      JDeveloper reopens in the new role.

    13. In the Projects section, expand the composite and double-click the BPEL file.

    14. Locate the customizable scope where the customizations were made.

    15. Confirm that the customizations appear and resolve any conflicts.

    16. Redeploy the custom composite using JDeveloper or a deployment plan.

  5. For the Agent Assisted Billing Care pre-built integration, manually migrate any customizations made in source Oracle Data Integrator integration projects to 12.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.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.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.1 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 12.2 environment and open it in a text editor.

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

  6. On the 12.2 environment in SQL Developer, open the SQL Worksheet for your 12.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.