5 Upgrading Oracle SOA Suite with Oracle Business Activity Monitoring from 11g

You can upgrade from a supported Oracle SOA Suite 11g environment that includes Business Activity Monitoring (BAM) to a SOA 12c (12.2.1.4.0) environment with the newly redesigned Oracle BAM 12c.

Note:

If you are upgrading from a previous Oracle SOA Suite with BAM 12c release, seeUpgrading Oracle SOA Suite with Business Activity Monitoring from a Previous 12c Release

Understanding an Upgrade to Business Activity Monitoring 12c (12.2.1.4.0)

Upgrading from Oracle BAM 11g to BAM 12c cannot be handled with the standard upgrade procedures. You will need to perform several manual configuration tasks to complete the upgrade.

Note:

The procedures described in the following sections apply only to upgrades from 11g. If you are upgrading an already upgraded 12c domain to this 12c release, you will follow the standard upgrade procedures described in Upgrading Oracle SOA Suite and Business Process Management from a Previous 12c Release

Oracle Business Activity Monitoring (BAM) 12c has been completely redesigned for use with Oracle SOA Suite 12c, so there is no direct upgrade path. The schemas, binaries, and directory structure used in Oracle BAM 12c are different than those used with Oracle BAM 11g. Therefore, upgrading from Oracle BAM 11g to BAM 12c cannot be handled with the standard upgrade procedures. You will need to perform several manual configuration tasks to complete the upgrade.

It is also important to understand that the only Oracle BAM 11g objects that can be used in your BAM 12c domain are data objects (DOs) and enterprise message sources (EMS). You will need to manually export these objects to an XML file and then import them into the BAM 12c domain. The other Oracle BAM 11g artifacts, such as dashboards for example, will have to be manually recreated in Oracle BAM 12c domain.

Oracle recommends that you continue to use your Oracle BAM 11g domain after the upgrade to allow time to create and test all of the necessary artifacts. Therefore, before you begin the SOA with Oracle BAM upgrade process, it is strongly recommended that you reinstall the Oracle BAM 11g domain in a separate location so that the source files remain untouched during the domain reconfiguration. You will configure SOA 12c to point to this new 11g domain after the upgrade as your existing 11g Oracle BAM domain will be altered and will not function with SOA 12c.

Note:

There is no upgrade support for an Oracle BAM-only domain (a domain without SOA). If you have a BAM-only domain, and want to upgrade to Oracle BAM 12c, then you must create a new Oracle BAM 12c domain and import data objects and recreate all the dashboards and alerts.

Understanding the SOA with Oracle BAM 11g Upgrade Process Flow

The following flowchart shows a process overview of upgrading a SOA 11g domain with Oracle BAM to a SOA 12c domain with Oracle BAM 12c.

Performing the Pre-Upgrade Tasks for Oracle BAM

The tasks in this section should be performed when upgrading a SOA domain with Oracle BAM 11g to 12c.

Creating a New Oracle BAM 11g Domain Before You Upgrade

You will continue to use your existing Oracle Business Activity Monitoring (BAM) 11g domain after the upgrade, so you must install BAM 11g in a new domain home before you upgrade. If you do not create a new (separate) BAM 11g domain, you will not have a functioning BAM domain after the upgrade and you will lose many of your artifacts and configurations.

Note:

If you do not create separate domain for Oracle BAM 11g, then you will lose BAM artifacts and BAM-related configurations only (SOA artifacts will not be impacted).

In addition, any composites referring to BAM artifacts (such as adapters) or new instances will be faulted during runtime.

Use the installation instructions in the 11g version of the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite.

To preserve your existing 11g BAM environment, use the 11g ICommand to export ALL of your Oracle BAM 11g artifacts (not just DOs and EMS), and then import them into your new Oracle BAM 11g domain so you have a fully functional Oracle BAM 11g domain after the upgrade.

After the upgrade, you can continue using the Oracle BAM 11g domain. Alternatively, you can extend the 12c SOA domain with Oracle BAM 12c and export the DOs and EMS artifacts from 11g domain and import them into extended Oracle BAM 12c domain. For more information, see Extending the SOA Domain with Oracle BAM 12c.

Exporting All Oracle BAM 11g Artifacts from the Existing Domain

After you install and configure your new Oracle BAM 11g domain in its new location, you will have to use 11g Oracle BAM ICommand utility to export the data from the existing (old) Oracle BAM 11g domain and then import it into the new Oracle BAM 11g domain before you upgrade.

For more information on using the 11g Oracle BAM ICommand command-line utility to export data files, see the "Export" section of Monitoring Business Activity with Oracle BAM.

Importing Oracle BAM 11g Artifacts into the New Oracle BAM 11g Domain

After you have created a complete export XML of your Oracle BAM 11g artifacts (not just the DOs and EMS), you must import the XML file into the newly created Oracle BAM 11g domain. This will ensure that you continue to have a fully functioning Oracle BAM domain after the upgrade and domain reconfiguration.

For more information on using the 11g Oracle BAM ICommand command-line utility to export data files, see the "Import" section of Monitoring Business Activity with Oracle BAM.

Creating a Complete Backup of the Oracle BAM 11g Domain

In the event that the upgrade fails, you will need to restore the entire pre-upgrade environment using a backup version. Make sure that you have created a backup version of the entire Oracle BAM 11g environment before you continue with the upgrade process. Note that the backup domain is separate from the new Oracle BAM11g domain you created in Creating a New Oracle BAM 11g Domain Before You Upgrade.

For more information, see "Backup and Recovery Strategies for Upgrade" in the Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.

Upgrading a SOA with Oracle BAM Domain to 12c

Use this procedure to upgrade a SOA 11g domain that includes Oracle BAM to a SOA 12c (12.2.1.4.0) domain that will also include Oracle BAM.

Do not perform these tasks until you have created a complete backup of the Oracle BAM 11g domain.

Installing the 12c (12.2.1.4.0) Product Distributions for Oracle SOA Suite and Business Process Management

Before beginning your upgrade, use the Oracle Universal Installer to install the Oracle Fusion Middleware Infrastrucutre distribution, the Oracle SOA Suite and Business Process Management 12c (12.2.1.4.0) distribution, and any other SOA Suite products on the target system.

Note:

When Infrastructure is required for the upgrade, you must install the Oracle Fusion Middleware distribution first before you install other Fusion Middleware products.
Before you begin, note the following:
  • If you are upgrading from a previous 12c release you must install the 12c (12.2.1.4.0) distributions into a new Oracle home. Do not attempt to reuse the existing Oracle home for this upgrade. Upgrading to 12c (12.2.1.4.0) is not a patch release.

  • Oracle SOA Suite requires the Oracle Fusion Middleware Infrastructure (Oracle WebLogic Server and JRF).

    Installing Fusion Middleware Infrastructure creates an Oracle home directory and lays supporting software to install other Fusion Middleware products.

  • If your SOA domain has other SOA-integrated components, such as Oracle Service Bus, Managed File Transfer, or Oracle B2B, you must install those distributions into the same new Oracle home. Oracle Business Activity Monitoring and Business Process Management are part of the generic SOA distribution.
To install the Oracle SOA Suite component distributions:
  1. Sign in to the target system.
  2. Download the following distributions from Oracle Technology Network or Oracle Software Delivery Cloud to your target system.:
    • Fusion Middleware Infrastructure distribution (fmw_12.2.1.4.0_infrastructure.jar)
    • Fusion Middleware SOA Suite and Business Process Management distribution (fmw_12.2.1.4.0_soa.jar)
    • If you are running Managed File Transfer, Oracle Service Bus or Oracle B2B, download the Managed File Transfer distribution (fmw_12.2.1.4.0_mft.jar), Oracle Service Bus (fmw_12.2.1.4.0_osb.jar), and Oracle B2B (fmw_12.2.1.4.0_b2b.jar)
  3. Change to the directory where you downloaded the 12c (12.2.1.4.0) product distribution.
  4. Start the installation program for Oracle Fusion Middleware Infrastructure:
    • (UNIX) JDK_HOME/bin/java -jar fmw_12.2.1.4.0_infrastructure.jar
    • (Windows) JDK_HOME\bin\java -jar fmw_12.2.1.4.0_infrastructure.jar
  5. On UNIX operating systems, the Installation Inventory Setup screen appears if this is the first time you are installing an Oracle product on this host.
    Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location, and click Next.

    Note:

    The Installation Inventory Setup screen does not appear on Windows operating systems.
  6. On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
  7. On the Auto Updates screen, select an option:
    • Skip Auto Updates: If you do not want your system to check for software updates at this time.

    • Select patches from directory: To navigate to a local directory if you downloaded patch files.

    • Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.

    Click Next.
  8. On the Installation Location screen, specify the location for the Oracle home directory and click Next.
    For more information about Oracle Fusion Middleware directory structure, see Understanding Directories for Installation and Configuration in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.
  9. On the Installation Type screen, select the product(s) to install. Product dependencies will be automatically selected, and click Next.
  10. The Prerequisite Checks screen analyzes the host computer to ensure that the specific operating system prerequisites have been met.
    To view the list of tasks that are verified, select View Successful Tasks. To view log details, select View Log. If any prerequisite check fails, then an error message appears at the bottom of the screen. Fix the error and click Rerun to try again. To ignore the error or the warning message and continue with the installation, click Skip (not recommended).
  11. On the Installation Summary screen, verify the installation options that you selected.
    If you want to save these options to a response file, click Save Response File and enter the response file location and name. The response file collects and stores all the information that you have entered, and enables you to perform a silent installation (from the command line) at a later time.

    Click Install to begin the installation.

  12. On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
  13. The Installation Complete screen displays the Installation Location and the Feature Sets that are installed. Review this information and click Finish to close the installer.
  14. After you have installed the Infrastructure, repeat steps 3 through 13 to install the other product distributions.

Creating the Required 12c Schemas with the RCU

When upgrading from 11g, you must create the required 12c schemas. You can use the Repository Creation Utility (RCU) to create customized schemas or, optionally, you can use the Upgrade Assistant to create schemas using the default schema settings. This procedure describes how to create schemas using the RCU. Information about using the Upgrade Assistant to create schemas is covered in the upgrade procedures.

In Oracle Fusion Middleware 11g releases it was possible to run Business Activity Monitoring (BAM) without a database, as the SOA schema was not required. In 12c, however, you must have a supported database configured with the required SOA schemas before you can run Business Activity Monitoring 12c (12.2.1.4.0)

Note:

If you are upgrading from a previous 12c release of Oracle Fusion Middleware, you do not need to re-create these schemas if they already exist. Refer to the steps below to identify the existing schemas in your domain.

The following schemas must exist before you upgrade to 12c. If you are upgrading from 11g, and you are not sure which schemas you currently have, refer to the steps below to identify the existing schemas in your domain. You do not need to re-create these schemas if they already exist.

  • Service Table schema (prefix_STB). This schema is new in 12c and is required for domain-based upgrades. It stores basic schema configuration information (for example, schema prefixes and passwords) that can be accessed and used by other Oracle Fusion Middleware components during the domain creation. This schema is automatically created when you run the Repository Creation Utility (RCU), where you specify the existing schema owner prefix that you used for your other 11g schemas.

    Note:

    If the Service Table schema does not exist, you may encounter the error message UPGAST-00328 : The schema version registry table does not exist on this database. If that happens it is necessary to create the service table schema in order to run Upgrade Assistant

  • Oracle Platform Security Services (OPSS) schema (prefix_OPSS). This schema is required if you are using an OID-based security store in 11g. This schema is automatically created when you run the Repository Creation Utility (RCU). The only supported LDAP-based OPSS security store is Oracle Internet Directory (OID). An LDAP-based policy store is typically used in production environments. You do not need to reassociate an OID-based security store before upgrade. While the Upgrade Assistant is running, you can select the OPSS schema. The Upgrade Assistant upgrades the OID-based security store automatically.

    Note:

    The 12c OPSS database schema is required so that you can reference the 12c schema during the reconfiguration of the domain. Your domain continues to use the OID-based security store after the upgrade is complete.

  • Audit Services (prefix_IAU)

  • WebLogic Services (prefix_WLS). This schema is required for BAM in 12c; BAM does not have its own separate schema in 11g.

  • Managed File Transfer (prefix_MFT). This schema was introduced in Release 12c (12.1.3) and is only needed if MFT is part of your domain.

To create the 12c schemas with the RCU:
  1. (Optional) If you are upgrading from 11g, and you wish to confirm the schemas which are present in your existing domain, then connect to the database as a user with DBA privileges, and run the following code from SQL*Plus:
    SET LINE 120
    COLUMN MRC_NAME FORMAT A14
    COLUMN COMP_ID FORMAT A20
    COLUMN VERSION FORMAT A12
    COLUMN STATUS FORMAT A9
    COLUMN UPGRADED FORMAT A8
    SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID ;
    
  2. Verify that a certified JDK already exists on your system by running java -version from the command line. For 12c (12.2.1.4.0), the certified JDK is 1.8.0_211 and later.
    Ensure that the JAVA_HOME environment variable is set to the location of the certified JDK. For example:
    • (UNIX) setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0_211
    • (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_211
    Add $JAVA_HOME/bin to $PATH.
  3. Go to the oracle_common/bin directory:
    • (UNIX) NEW_ORACLE_HOME/oracle_common/bin
    • (Windows) NEW_ORACLE_HOME\oracle_common\bin
  4. Start the RCU:
    • (UNIX) ./rcu
    • (Windows) rcu.bat
  5. On the Welcome screen, click Next.
  6. On the Create Repository screen, select Create Repository and then select System Load and Product Load.
    If you do not have DBA privileges, select Prepare Scripts for System Load. This will generate a SQL script containing all the same SQL statements and blocks that would have been called if the RCU were to execute the actions for the selected components. After the script is generated, a user with the necessary SYS or SYSDBA privileges can execute the script to complete the system load phase.

    Click Next.

  7. On the Database Connection Details screen, select the Database Type and enter the connection information for the database that hosts the 11g schemas. See the pertinent table below.

    Table 5-1 Connection Credentials for Oracle Databases and Oracle Databases with Edition-Based Redefinition

    Option Description and Example
    Host Name

    Specify the name of the server where your database is running in the following format:

    examplehost.exampledomain.com

    For Oracle RAC databases, specify the VIP name or one of the node names in this field.

    Port

    Specify the port number for your database. The default port number for Oracle databases is 1521.

    Service Name

    Specify the service name for the database. Typically, the service name is the same as the global database name.

    For Oracle RAC databases, specify the service name of one of the nodes in this field. For example:

    examplehost.exampledomain.com

    Username Enter the user name for your database. The default user name is SYS.
    Password Enter the password for your database user.
    Role

    Select the database user's role from the drop-down list:

    Normal or SYSDBA

    Table 5-2 Connection Credentials for MySQL Databases

    Option Description and Example
    Host Name

    Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.

    Port

    Specify the port number for your database.

    Database Name

    Specify the name of your database.

    Username Specify the name of a user with administrator privileges.
    Password Enter the password for your database user.

    Table 5-3 Connection Credentials for Microsoft SQL Server Databases

    Option Description and Example
    Unicode Support

    Select Yes or No from the drop-down list.

    Server Name Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.

    MSSQL named instances: A named instance is identified by the network name of the computer and the instance name that you specify during installation. The client must specify both the server name and the instance name when connecting.

    Port

    Specify the port number for your database.

    Database Name

    Specify the name of your database.

    Username Specify the name of a user with administrator privileges.
    Password Enter the password for your database user.

    Table 5-4 Connection Credentials for IBM DB2 Databases

    Option Description and Example
    Server Name Specify the host name, IP address, or complete server name in host\server format of the server where your database is running.
    Port

    Specify the port number for your database.

    Database Name

    Specify the name of your database.

    Username Specify the name of a user with DB Owner privileges. The default user name for IBM DB2 databases is db2admin.
    Password Enter the password for your database user.
    If the prerequisite check is successful, click OK to continue to the next screen. If the check fails, review the details you entered and try again.
  8. On the Select Components screen, select Select existing prefix and select the prefix that was used to create the existing 11g schemas from the drop-down menu (for example, DEV11G). This prefix is used to logically group schemas together for use in this domain.

    Select the schemas required for Oracle BAM.

    Note:

    The Common Infrastructure Services (prefix_STB) and Oracle Platform Security Services (prefix_OPSS) schemas are selected by default if they have not yet been created.

    Make a note of the prefix and schema names for the components you are installing as you will need this information when you configure the installation. Click Next.
  9. In the Checking Prerequisites dialog, verify that the prerequisites check is successful, then click OK.
  10. On the Schema Passwords screen, specify the passwords for your schema owners.
    Make a note of the passwords you enter on this screen as you will need this information while configuring your product installation.
  11. On the Map Tablespaces screen, configure the required tablespace mapping for the schemas you want to create.
    Click Next, then click OK in the confirmation dialog. When the progress dialog shows the tablespace creation is complete, click OK.
    You see the Encrypt Tablespace check box only if you have enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU. Select the Encrypt Tablespace check box on the Map Tablespaces screen to encrypt all new tablespaces that the RCU creates.
  12. Verify the information on the Summary screen and click Create to begin schema creation.
    This screen contains information about the log files that were created from this RCU operation. Click on the name of a particular log file to view the contents of that file.
  13. Review the information on the Completion Summary screen to verify that the operation is completed successfully. Click Close to complete the schema creation.

Renaming the Oracle BAM Templates Before Upgrading the 11g Schemas

Before upgrading the 11g schemas with the Upgrade Assistant, you must change the names of the following Oracle BAM reconfiguration templates upgrade will fail.

Make sure that you have exported your 11g Oracle Business Activity Monitoring (BAM) data before completing this step. If you are unsure, read Exporting All Oracle BAM 11g Artifacts from the Existing Domain.

The templates can be found in the following 12c directory: $ORACLE_HOME/soa/common/templates/wls

Template Name Rename To:

oracle.bam.reconfig_template_11g_12.2.1.jar

oracle.bam.reconfig_template_11g_12.2.1.jar-old

oracle.bam.reconfig.template_11g_12.2.1.jar.rename

oracle.bam.reconfig_template_11g_12.2.1.jar

Stopping Servers and Processes

Before you run the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all of the pre-upgrade processes and servers, including the Administration Server and any managed servers.

An Oracle Fusion Middleware environment can consist of an Oracle WebLogic Server domain, an Administration Server, multiple managed servers, Java components, system components such as Identity Management components, and a database used as a repository for metadata. The components may be dependent on each other, so they must be stopped in the correct order.

Note:

The procedures in this section describe how to stop the existing, pre-upgrade servers and processes using the WLST command-line utility or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console. See Starting and Stopping Administration and Managed Servers and Node Manager.

To stop your pre-upgrade Fusion Middleware environment, navigate to the pre-upgrade domain and follow the steps below:

Step 1: Stop System Components

To stop system components, such as Oracle HTTP Server, use the stopComponent script:

  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopComponent.cmd component_name

You can stop system components in any order.

Step 2: Stop the Managed Servers

To stop a WebLogic Server Managed Server, use the stopManagedWebLogic script:

  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Stop SOA servers and processes in this order:

  1. Business Activity Monitoring (BAM) Managed Server

  2. Oracle Service Bus (OSB) Managed Server

  3. Service-Oriented Architecture (SOA) Managed Server

  4. Oracle Web Services Manager (OWSM) Managed Server

Step 3: Stop Oracle Identity Management Components

Stop any Oracle Identity Management components, such as Oracle Internet Directory:
  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopComponent.cmd component_name

Step 4: Stop the Administration Server

When you stop the Administration Server, you also stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To stop the Administration Server, use the stopWebLogic script:

  • (UNIX) EXISTING_DOMAIN_HOME/bin/stopWebLogic.sh

  • (Windows) EXISTING_DOMAIN_HOME\bin\stopWebLogic.cmd

When prompted, enter your user name, password, and the URL of the Administration Server.

Step 5: Stop Node Manager

To stop Node Manager, close the command shell in which it is running.

Alternatively, after setting the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. See stopNodeManager in WLST Command Reference for WebLogic Server.

Running the Upgrade Assistant to Upgrade Schemas

Follow the standard procedure for upgrading schemas using the Upgrade Assistant.

When upgrading SOA Suite and BPM with Oracle BAM 11g schemas, select the following options on the Available Components screen (the schema names are listed for each):

  • Oracle Platform Security Services (_OPSS)

  • Oracle SOA (_SOAINFRA)

  • Oracle Managed File Transfer (_MFT)

When Oracle Platform Security Services and Oracle SOA are selected, the following dependencies are also selected:

  • Oracle Audit Services (_IAU)

  • Oracle Metadata Services (_MDS)

  • User Messaging Service (_ORASDPM)

    NOTE: The 11g _ORASDPM schema has been renamed to _UMS in 12c. However, you must provide the 11g schema name prefix_ORASDPM when prompted in the Upgrade Assistant. The schema will continue to be <prefix>_ORASDPM for upgraded domains since schema names cannot be changed by Upgrade Assistant.

Upgrading Product Schemas

After stopping servers and processes, use the Upgrade Assistant to upgrade supported product schemas to the current release of Oracle Fusion Middleware.

The Upgrade Assistant allows you to upgrade individually selected schemas or all schemas associated with a domain. The option you select determines which Upgrade Assistant screens you will use.

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.4.0). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.

To start the Upgrade Assistant:

Note:

Before you start the Upgrade Assistant, make sure that the JVM character encoding is set to UTF-8 for the platform on which the Upgrade Assistant is running. If the character encoding is not set to UTF-8, then you will not be able to download files containing Unicode characters in their names. This can cause the upgrade to fail.

  1. Go to the oracle_common/upgrade/bin directory:
    • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
    • (Windows) ORACLE_HOME\oracle_common\upgrade\bin
  2. Start the Upgrade Assistant:
    • (UNIX) ./ua
    • (Windows) ua.bat

For information about other parameters that you can specify on the command line, such as logging parameters, see:

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 5-5 Upgrade Assistant Command-Line Parameters

Parameter Required or Optional Description

-readiness

Required for readiness checks

Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).

Performs the upgrade readiness check without performing an actual upgrade.

Schemas and configurations are checked.

Do not use this parameter if you have specified the -examine parameter.

-threads

Optional

Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas.

The value must be a positive integer in the range 1 to 8. The default is 4.

-response

Required for silent upgrades or silent readiness checks

Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).

-examine

Optional

Performs the examine phase but does not perform an actual upgrade.

Do not specify this parameter if you have specified the -readiness parameter.

-logLevel attribute

Optional

Sets the logging level, specifying one of the following attributes:

  • TRACE

  • NOTIFICATION

  • WARNING

  • ERROR

  • INCIDENT_ERROR

The default logging level is NOTIFICATION.

Consider setting the -logLevel TRACE attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if -logLevel TRACE is used.

-logDir location

Optional

Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files.

The default locations are:

(UNIX)

ORACLE_HOME/oracle_common/upgrade/logs
ORACLE_HOME/oracle_common/upgrade/temp

(Windows)

ORACLE_HOME\oracle_common\upgrade\logs
ORACLE_HOME\oracle_common\upgrade\temp

-help

Optional

Displays all of the command-line options.

Upgrading SOA Schemas Using the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade the product schemas.

Caution:

Do not start the Upgrade Assistant if purge scripts or scheduled database jobs are running.

Wait until the purge or upgrade is complete before starting the upgrade process. The upgrade will fail if the purge scripts or instance upgrade jobs are running while using the Upgrade Assistant to upgrade your schemas.

If you must start the Upgrade Assistant, stop the purge and be sure to disable any scheduled jobs as described in Enabling and Disabling Background Control Job (Option 6).

To upgrade product schemas with the Upgrade Assistant:
  1. On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

    Note:

    For more information about any Upgrade Assistant screen, click Help on the screen.
  2. On the Selected Schemas screen, select the schema upgrade operation that you want to perform:
    • All Schemas Used by a Domain to allow the Upgrade Assistant to discover and select all components that have a schema available to upgrade in the domain specified in the Domain Directory field. This is also known as a domain assisted schema upgrade. Additionally, the Upgrade Assistant pre-populates connection information on the schema input screens.

      Note:

      Oracle recommends that you select All Schemas Used by a Domain for most upgrades to ensure all of the required schemas are included in the upgrade.
    • Individually Selected Schemas if you want to select individual schemas for upgrade and you do not want to upgrade all of the schemas used by the domain.

      Caution:

      Upgrade only those schemas that are used to support your 12c (12.2.1.4.0) components. Do not upgrade schemas that are currently being used to support components that are not included in Oracle Fusion Middleware 12c (12.2.1.4.0).

    Click Next.

  3. If you selected Individually Selected Schemas: On the Available Components screen, select the components for which you want to upgrade schemas. When you select a component, the schemas and any dependencies are automatically selected.

    For example, when Oracle SOA is selected, the Oracle SOA (_SOAINFRA), Audit Services (_IAU), Metadata Service (_MDS), Oracle Platform Security Services(_OPSS), and User Messaging Services (_UMS) schemas will be included in the upgrade.

    When Managed File Transfer is selected, Audit Services (_IAU), Enterprise Scheduler (_ESS) and Platform Security Services (OPSS) will be included in the upgrade.

  4. The Domain Directory screen appears when Oracle Platform Security Services or Oracle Audit Services is selected on the Available Components screen. Enter the absolute path to the existing WebLogic domain directory, or click Browse to navigate to and select the domain directory you are upgrading
  5. On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

    Note:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  6. On the Schema Credentials screen(s), specify the database connection details for each schema you are upgrading (the screen name changes based on the schema selected):
    Element Description

    Database Type

    The database type chosen for upgrade must be identical to the database type that was selected when RCU originally created the schema.

    If you select Oracle Edition-Based Redefinition (EBR) as the database type, the schema that you are upgrading also must have been created by RCU as the EBR database type. In particular, Upgrade Assistant never converts schemas from one database type to another.

    The options include:

    • Oracle Database

    • Microsoft SQL Server

    • IDM DB2

    • MySQL

    • Java DB

    • Oracle Database enabled for edition-based redefinition

    Edition Name

    For database type "Oracle Database enabled for edition-based redefinition" (EBR database) you will need to enter the name of an existing Edition in the Edition Name element field. The database schema upgrade will occur in the edition you have chosen.

    Database Connect String

    Enter the location of the database.

    For example, if you are selecting an Oracle database, the following URL format could be used:

    host:port/db_service_name

    If you are using a Microsoft SQL Server or IBM DB2 database, select the database type from the drop-down menu to see an example of the syntax that can be used for each database type.

    DBA User Name

    Enter the database user name used to connect to the database.

    Oracle Database Users Only: If SSL authentication is used, then the DBA User Name field may be optional. If you do provide a DBA User Name, then the information will be used during the database authentication.

    For Oracle database users, if you are not running as SYS or SYSDBA, then user of Upgrade Assistant must have all of the privileges granted in the FMW user account.

    Refer to your component-specific upgrade documentation for more information on creating a non-sysdba user to run Upgrade Assistant.

    DBA Password

    Enter the password associated with the specified DBA database user.

    Oracle Database Users Only: If SSL authentication is used, then the DBA Password field may be optional. If you do provide a DBA user name and password, then the information will be used during the database authentication.

    Schema User Name

    Select the schema you want to upgrade from the Schema User Name drop-down menu, and then enter the password for the schema. Be sure to use the correct schema prefix for the schemas you are upgrading.

    Upgrading from a Previous 12c Release:

    As of release 12.1.2.0.0 the schema name for UCSUMS schema changed. The new name can be either prefix_ORASDPM or prefix_UMS, depending on the starting point for the upgrade. If Upgrade Assistant does not automatically recognize the possible schemas and cannot display them in a drop-down list, then you must manually enter the name in a text field.

    11g to 12c Upgrades Only: The UCSUMS schema is not auto-populated. Enter prefix_ORASDPM as the user. The upgrade environment uses prefix_ORASDPM as the schema name, whereas in the 12c environment it is referred to as _UMS.

    Schema Password

    Enter the password associated with the specified schema user name.

  7. On the Create Schemas screen, specify if you want the Upgrade Assistant to create the missing schemas. By default the Create missing schemas for the specified domain option is enabled. The Upgrade Assistant will attempt to create the missing schemas for the domain using the database connection details and schema owner name provided. The Upgrade Assistant creates the schemas using the default tablespace settings.
    Select Use same passwords for all schemas if the same password is used for all schemas. Enter and confirm the password in the table. You only have to supply the password once.

    Note:

    Do not allow the Upgrade Assistant to create schemas for you if you require customized options for your schemas. The schemas are created using the default Repository Creation Utility (RCU) settings. For example, if your schemas require additional tablespace, you must use the RCU to create the schemas.

    If you do not want the Upgrade Assistant to create these schemas for you, deselect the Create missing schemas for the specified domain option and click Next. You will have to run the Repository Creation Utility to create the schemas.

  8. The Create Schema Defaults screen appears if you selected the Create missing schemas for the specified domain option. The default datafile size is listed for each component schema and auxiliary schema. If you need to modify the size of the tablespace datafile ,or make any other changes to the default schema settings, use the Repository Creation Utility to create the schemas. You cannot modify the tablespace settings from the Upgrade Assistant.
  9. On the Examine screen, review the status of the Upgrade Assistant as it examines each schema, verifying that the schema is ready for upgrade. If the status is Examine finished, click Next.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the schemas or configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  10. On the Upgrade Summary screen, review the summary of the schemas that will be upgraded and/or created.
    Verify that the correct Source and Target Versions are listed for each schema you intend to upgrade.
    If you want to save these options to a response file to run the Upgrade Assistant again later in response (or silent) mode, click Save Response File and provide the location and name of the response file. A silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again.
    Click Next .
  11. On the Upgrade Progress screen, monitor the status of the upgrade.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any schemas are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

    Note:

    The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

    Click Next.

  12. If the upgrade is successful: On the Upgrade Success screen, click Close to complete the upgrade and close the wizard.

    If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at NEW_ORACLE_HOME/oracle_common/upgrade/logs.

    Note:

    If the upgrade fails, you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.
Verifying the Schema Upgrade

After completing all the upgrade steps, verify that the upgrade was successful by checking that the schema version in schema_version_registry has been properly updated.

If you are using an Oracle database, connect to the database as a user having Oracle DBA privileges, and run the following from SQL*Plus to get the current version numbers:

SET LINE 120
COLUMN MRC_NAME FORMAT A14
COLUMN COMP_ID FORMAT A20
COLUMN VERSION FORMAT A12
COLUMN STATUS FORMAT A9
COLUMN UPGRADED FORMAT A8
SELECT MRC_NAME, COMP_ID, OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY ORDER BY MRC_NAME, COMP_ID ;

In the query result:

  • Check that the number in the VERSION column matches the latest version number for that schema. For example, verify that the schema version number is 12.2.1.4.0.

    Note:

    However, that not all schema versions will be updated. Some schemas do not require an upgrade to this release and will retain their pre-upgrade version number.

  • The STATUS field will be either UPGRADING or UPGRADED during the schema patching operation, and will become VALID when the operation is completed.

  • If the status appears as INVALID, the schema update failed. You should examine the logs files to determine the reason for the failure.

  • Synonym objects owned by IAU_APPEND and IAU_VIEWER will appear as INVALID, but that does not indicate a failure.

    They become invalid because the target object changes after the creation of the synonym. The synonyms objects will become valid when they are accessed. You can safely ignore these INVALID objects.

Reconfiguring the 11g Domain with the Reconfiguration Wizard

After you have renamed the Oracle BAM reconfiguration templates, start the Reconfiguration Wizard and follow the steps as described

The Reconfiguration Wizard will remove the Oracle BAM 11g application, library, BAMDataSource, BAMJMSSserver and BAMJmsSystemResource from the domain.

NOTE: After the upgrade, you must manually remove the Oracle BAM server and cluster after the upgrade as described in the post configuration taskRemoving the Oracle BAM Servers and Clusters from the Domain.

About Reconfiguring the Domain

Run the Reconfiguration Wizard to reconfigure your domain component configurations to 12c (12.2.1.4.0).

When you reconfigure a WebLogic Server domain, the following items are automatically updated, depending on the applications in the domain:

  • WebLogic Server core infrastructure

  • Domain version

Note:

Before you begin the domain reconfiguration, note the following limitations:

  • The Reconfiguration Wizard does not update any of your own applications that are included in the domain.

  • Transforming a non-dynamic cluster domain to a dynamic cluster domain during the upgrade process is not supported.

    The dynamic cluster feature is available when running the Reconfiguration Wizard, but Oracle only supports upgrading a non-dynamic cluster upgrade and then adding dynamic clusters. You cannot add dynamic cluster during the upgrade process.

  • If the installation that you’re upgrading does not use Oracle Access Management (OAM), then you must edit two files to prevent the Reconfiguration Wizard from attempting to update the nonexistent OAM Infrastructure schema, which causes the upgrade to fail.

    Comment out the lines in your $DOMAIN/init-info/domain-info.xml that are similar to this example:

    <!--extention-template-ref name="Oracle Identity Navigator" 
      version="11.1.1.3.0" 
      location="/u01/app/oracle/product/fmw/iam111130/common/templates/applications/yourcomany.oinav_11.1.1.3.0_template.jar" 
      symbol=""/-->
    
    <!--install-comp-ref name="oracle.idm.oinav" version="11.1.1.3.0" 
      symbol="yourcompany.idm.oinav_11.1.1.3.0_iam111130_ORACLE_HOME" 
      product_home="/u01/app/oracle/product/fmw/iam111130"/-->

    and similarly comment out the lines in $DOMAIN/config/config.xml that are similar to this example:

    <!--app-deployment> 
      <name>oinav#11.1.1.3.0</name>
      <target>AdminServer</target>
      <module-type>ear</module-type>
    
      <source-path>/u01/app/oracle/product/fmw/iam111130/oinav/modules/oinav.ear_11.1.1.3.0/oinav.ear</source-path>
      <deployment-order>500</deployment-order>
      <security-dd-model>DDOnly</security-dd-model>
      <staging-mode>nostage</staging-mode>
    </app-deployment-->
    
Specifically, when you reconfigure a domain, the following occurs:
  • The domain version number in the config.xml file for the domain is updated to the Administration Server's installed WebLogic Server version.

  • Reconfiguration templates for all installed Oracle products are automatically selected and applied to the domain. These templates define any reconfiguration tasks that are required to make the WebLogic domain compatible with the current WebLogic Server version.

  • Start scripts are updated.

    If you want to preserve your modified start scripts, be sure to back them up before starting the Reconfiguration Wizard.

Note:

When the domain reconfiguration process starts, you can’t undo the changes that it makes. Before running the Reconfiguration Wizard, ensure that you have backed up the domain as covered in the pre-upgrade checklist. If an error or other interruption occurs while running the Reconfiguration Wizard, you must restore the domain by copying the files and directories from the backup location to the original domain directory. This is the only way to ensure that the domain has been returned to its original state before reconfiguration.

Follow these instructions to reconfigure the existing domain using the Reconfiguration Wizard. See Reconfiguring WebLogic Domains in Upgrading Oracle WebLogic Server.
Backing Up the Domain

Before running the Reconfiguration Wizard, create a backup copy of the domain directory.

To create a backup of the domain directory:

  1. Copy the source domain to a separate location to preserve the contents.
    (Windows) copy C:\domains\mydomain to C:\domains\mydomain_backup.
    (UNIX) cp mydomain /domains/mydomain_backup
  2. Before updating the domain on each remote Managed Server, create a backup copy of the domain directory on each remote machine.
  3. Verify that the backed up versions of the domain are complete.
If domain reconfiguration fails for any reason, you must copy all files and directories from the backup directory into the original domain directory to ensure that the domain is returned entirely to its original state before reconfiguration.
Starting the Reconfiguration Wizard

Note:

Shut down the administration server and all collocated managed servers before starting the reconfiguration process. See Stopping Servers and Processes.

To start the Reconfiguration Wizard in graphical mode:

  1. Sign in to the system on which the domain resides.
  2. Open the command shell (on UNIX operating systems) or open a command prompt window (on Windows operating systems).
  3. Edition Based Database Users Only: If your schemas are configured with EBR database, a default edition name must be manually supplied before you run the Reconfiguration Wizard.
    Run the following SQL command to set the default edition:

    ALTER DATABASE DEFAULT EDITION = edition_name;

    where edition_name is the child edition name.

  4. Go to the oracle_common/common/bin directory:
    • (UNIX) NEW_ORACLE_HOME/oracle_common/common/bin
    • (Windows) NEW_ORACLE_HOME\oracle_common\commom\bin
  5. Start the Reconfiguration Wizard with the following logging options:
    • (UNIX) ./reconfig.sh -log=log_file -log_priority=ALL
    • (Windows) reconfig.cmd -log=log_file -log_priority=ALL

    where log_file is the absolute path of the log file you'd like to create for the domain reconfiguration session. This can be helpful if you need to troubleshoot the reconfiguration process.

    The parameter -log_priority=ALL ensures that logs are logged in fine mode.

    Note:

    When you run this command, the following error message might appear to indicate that the default cache directory is not valid:

    *sys-package-mgr*: can't create package cache dir
    

    You can change the cache directory by setting the environment variable CONFIG_JVM_ARGS. For example:

    CONFIG_JVM_ARGS=-Dpython.cachedir=valid_directory

Reconfiguring the SOA Domain with the Reconfiguration Wizard

You must first reconfigure your existing domain using the Reconfiguration Wizard before running the Upgrade Assistant.

Note:

If the source is a clustered environment, run the Reconfiguration Wizard on the primary node only. Use the pack/unpack utility to apply the changes to other cluster members in the domain.
To reconfigure the domain:
  1. On the Select Domain screen, specify the location of the domain you want to upgrade or click Browse to navigate and select the domain directory. Click Next.
  2. On the Reconfiguration Setup Progress screen, view the progress of the setup process. When complete, click Next.
    During this process:
    • The reconfiguration templates for your installed products, including Fusion Middleware products, are automatically applied. This updates various domain configuration files such as config.xmlconfig-groups.xml, and security.xml (among others).

    • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

    • The domain upgrade is validated.

  3. On the Domain Mode and JDK screen, select the JDK to use in the domain or click Browse to navigate to the JDK you want to use. The supported JDK version for 12c (12.2.1.4.0) is 1.8.0_211 and later. Click Next.

    Note:

    You cannot change the Domain Mode at this stage.
    For a list of JDKs that are supported for a specific platform, see Oracle Fusion Middleware Supported System Configurations.
  4. On the Database Configuration Type screen, select RCU Data to connect to the Server Table (_STB) schema.
    Enter the database connection details using the RCU service table (_STB) schema credentials and click Get RCU Configuration.
    The Reconfiguration Wizard uses this connection to automatically configure the data sources required for components in your domain.

    Note:

    By default Oracle’s Driver (Thin) for Service connections; Versions: Any is the selected driver. If you specified an instance name in your connection details — instead of the service name — you must select Oracle’s Driver (Thin) for pooled instance connections; Versions: Any If you do not change the driver type, then the connection will fail.

    Note:

    For any existing 12c (12.2.1.3.0) datasource, the reconfiguration will preserve the existing values. For new datasources where the schema was created for 12c (12.2.1.4.0) by the RCU, the default connection data will be retrieved from the _STB schema. If no connection data for a given schema is found in the _STB schema, then the default connection data is used.
    If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.

    Note:

    If you are upgrading from 12c (12.2.1.3.0), and your database has _OPSS or _IAU 12c (12.2.1.3.0) database schemas, you must manually enter database connection details for those schemas. These schemas were not required in 12c and had to be created manually. Users could assign any name to these schemas, therefore the Reconfiguration Wizard does not recognize them. When providing connection information for _IAU, use the IAU_APPEND user information.
  5. On the JDBC Component Schema screen, verify that the DBMS/Service and the Host name is correct for each component schema and click Next.
  6. On the JDBC Component Schema Test screen, select all the component schemas and click Test Selected Connections to test the connection for each schema. The result of the test is indicated in the Status column.
    When the check is complete, click Next.
  7. On the Advanced Configuration screen, you can select all categories for which you want to perform advanced configuration. For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration.

    Note:

    The optional categories that are listed on the Advanced Configuration screen depend on the resources defined in the templates you selected for the domain. Some common categories are described below.
    Advanced Configuration > Managed Servers:

    You must specify the actual hostname for the Listen Address for each managed server in your domain.

    Do not use the default localhost or All Local Addresses option.

    You must specify the actual hostname as hostname.yourcompany.com

    Managed Servers >Targeting Server Groups

    Note:

    • If you are upgrading from 11g to a 12c release, choose the following server groups for targeting the OSB managed servers.
      • OSB-MGD-SVRS-ONLY – Select this server group if you want to target Oracle Service Bus and Oracle Web Services Manager (OWSM) services to different managed servers.
      • OSB-MGD-SVRS - Select this server group if you want to target OSB and OWSM services to the same managed server. This option does not target CloudSDK to OSB Managed Servers. You can target CloudSDK manually, if needed, or additionally, choose OSB-MGD-SVRS-COMBINED server group as well to target the OSB Managed Servers.
    • If you are upgrading a domain that was created in a previous 12c release (such as 12.1.3), you MUST target your servers to the correct Server Groups during the domain reconfiguration phase of the upgrade. Failure to target these servers may result in a failed upgrade and excess downtime.
    1. On the Managed Servers screen, target each server to the correct Server Group by selecting the correct group name from the Server Groups drop-down menu.

    2. Verify that Each of the servers is targeted to the correct server group and should not show as Unspecified.
      Component and Server Server Group
      SOA (soa_server1) SOA-MGD-SVRS-ONLY
      Oracle Service Bus - OSB (osb_server1) OSB-MGD-SVRS-ONLY
      Business Activity Monitoring - BAM (bam_server1) BAM-MGD-SVRS-ONLY
      Managed File Transfer - MFT (mft_server1) MFT-MGD-SVRS-ONLY
    Advanced Configuration > Assign Servers to Machines

    If you have created servers as part of the upgrade process, then select the server name in the Servers list box and target them to the correct Node Manager Machine.

    Otherwise, no action is required on this screen when you are upgrading or reconfiguring the domain.

    Advanced Configuration > Assign Servers to Clusters

    Cluster Upgrades Only: If you are upgrading clusters, use this screen to assign Managed Servers to clusters.

    Note that only Managed Servers are displayed in the Server list box. The Administration Server is not listed because it cannot be assigned to a cluster.

    Note:

    When OWSMPM is in its own cluster and not part of SOA or OSB clusters:

    • Target only SOA-MGD-SVRS-ONLY user extensible server group to the SOA cluster
    • Target only OSB-MGD-SVRS-ONLY to the OSB cluster
    • Target WSMPM-MAN-SVER server group to OWSM
    • When upgrading 12.1.3.0 to 12.2.1.4.0, you also need to target BAM-MGD-SVRS-ONLY to BAM cluster.
  8. On the Configuration Summary screen, review the detailed configuration settings of the domain before continuing.
    You can limit the items that are displayed in the right-most panel by selecting a filter option from the View drop-down list.
    To change the configuration, click Back to return to the appropriate screen. To reconfigure the domain, click Reconfig.

    Note:

    The location of the domain does not change when you reconfigure it.
  9. The Reconfiguration Progress screen displays the progress of the reconfiguration process.
    During this process:
    • Domain information is extracted, saved, and updated.

    • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

    When the progress bar shows 100%, click Next.
  10. The End of Configuration screen indicates whether the reconfiguration process completed successfully or failed. It also displays the location of the domain that was reconfigured as well as the Administration Server URL (including the listen port). If the reconfiguration is successful, it displays Oracle WebLogic Server Reconfiguration Succeeded.
    If the reconfiguration process did not complete successfully, an error message is displayed indicates the reason. Take appropriate action to resolve the issue. If you cannot resolve the issue, contact My Oracle Support.
    Note the Domain Location and the Admin Server URL for further operations.

Running the Upgrade Assistant to Upgrade Component Configurations

After the domain reconfiguration, run the Upgrade Assistant (again) to upgrade any remaining component configurations.

Upgrading Domain Component Configurations

After reconfiguring the domain, use the Upgrade Assistant to upgrade the domain component configurations inside the domain to match the updated domain configuration.

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.4.0). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.

To start the Upgrade Assistant:

Note:

Before you start the Upgrade Assistant, make sure that the JVM character encoding is set to UTF-8 for the platform on which the Upgrade Assistant is running. If the character encoding is not set to UTF-8, then you will not be able to download files containing Unicode characters in their names. This can cause the upgrade to fail.

  1. Go to the oracle_common/upgrade/bin directory:
    • (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
    • (Windows) ORACLE_HOME\oracle_common\upgrade\bin
  2. Start the Upgrade Assistant:
    • (UNIX) ./ua
    • (Windows) ua.bat

For information about other parameters that you can specify on the command line, such as logging parameters, see:

Upgrade Assistant Parameters

When you start the Upgrade Assistant from the command line, you can specify additional parameters.

Table 5-6 Upgrade Assistant Command-Line Parameters

Parameter Required or Optional Description

-readiness

Required for readiness checks

Note: Readiness checks cannot be performed on standalone installations (those not managed by the WebLogic Server).

Performs the upgrade readiness check without performing an actual upgrade.

Schemas and configurations are checked.

Do not use this parameter if you have specified the -examine parameter.

-threads

Optional

Identifies the number of threads available for concurrent schema upgrades or readiness checks of the schemas.

The value must be a positive integer in the range 1 to 8. The default is 4.

-response

Required for silent upgrades or silent readiness checks

Runs the Upgrade Assistant using inputs saved to a response file generated from the data that is entered when the Upgrade Assistant is run in GUI mode. Using this parameter runs the Upgrade Assistant in silent mode (without displaying Upgrade Assistant screens).

-examine

Optional

Performs the examine phase but does not perform an actual upgrade.

Do not specify this parameter if you have specified the -readiness parameter.

-logLevel attribute

Optional

Sets the logging level, specifying one of the following attributes:

  • TRACE

  • NOTIFICATION

  • WARNING

  • ERROR

  • INCIDENT_ERROR

The default logging level is NOTIFICATION.

Consider setting the -logLevel TRACE attribute to so that more information is logged. This is useful when troubleshooting a failed upgrade. The Upgrade Assistant's log files can become very large if -logLevel TRACE is used.

-logDir location

Optional

Sets the default location of upgrade log files and temporary files. You must specify an existing, writable directory where the Upgrade Assistant creates log files and temporary files.

The default locations are:

(UNIX)

ORACLE_HOME/oracle_common/upgrade/logs
ORACLE_HOME/oracle_common/upgrade/temp

(Windows)

ORACLE_HOME\oracle_common\upgrade\logs
ORACLE_HOME\oracle_common\upgrade\temp

-help

Optional

Displays all of the command-line options.

Upgrading Domain Components Using the Upgrade Assistant

Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.

After running the Reconfiguration Wizard to reconfigure the WebLogic domain to 12c (12.2.1.4.0), you must run the Upgrade Assistant to upgrade the domain component configurations to match the updated domain configuration.

To upgrade domain component configurations with the Upgrade Assistant:
  1. On the Welcome screen, review an introduction to the Upgrade Assistant and information about important pre-upgrade tasks. Click Next.

    Note:

    For more information about any Upgrade Assistant screen, click Help on the screen.
  2. On the next screen:
    • Select All Configurations Used By a Domain. The screen name changes to WebLogic Components.

    • In the Domain Directory field, enter the WebLogic domain directory path.

    Click Next.

  3. If your pre-upgrade environment has multiple WebLogic domains, but the Oracle Web Services Manager (OWSM) Policy Manager is in only one domain, and OWSM agents are in the other domains: On the OWSM Policy Manager screen, provide the credentials for the WebLogic Administration Server domain where the Oracle Web Services Manager (OWSM) Policy Manager is deployed.
  4. On the Component List screen, verify that the list includes all the components for which you want to upgrade configurations and click Next.
    If you do not see the components you want to upgrade, click Back to go to the previous screen and specify a different domain.
  5. On the Prerequisites screen, acknowledge that the prerequisites have been met by selecting all the check boxes. Click Next.

    Note:

    The Upgrade Assistant does not verify whether the prerequisites have been met.
  6.  If there are remote managed servers hosting User Messaging Services (UMS) configuration files: On the UMS Configuration screen, provide the credentials to these servers so that the Upgrade Assistant can access the configuration files.

    Note:

    You may need to manually copy the UMS configuration files if the Upgrade Assistant is unable to locate them. See Error while Copying User Messaging Service (UMS) Configuration Files.
  7. On the Examine screen, review the status of the Upgrade Assistant as it examines each component, verifying that the component configuration is ready for upgrade. If the status is Examine finished, click Next.
    If the examine phase fails, Oracle recommends that you cancel the upgrade by clicking No in the Examination Failure dialog. Click View Log to see what caused the error and refer to Troubleshooting Your Upgrade in Upgrading with the Upgrade Assistant for information on resolving common upgrade errors.

    Note:

    • If you resolve any issues detected during the examine phase without proceeding with the upgrade, you can start the Upgrade Assistant again without restoring from backup. However, if you proceed by clicking Yes in the Examination Failure dialog box, you need to restore your pre-upgrade environment from backup before starting the Upgrade Assistant again.

    • Canceling the examination process has no effect on the configuration data; the only consequence is that the information the Upgrade Assistant has collected must be collected again in a future upgrade session.

  8. On the Upgrade Summary screen, review the summary of the options you have selected for component configuration upgrade.
    The response file collects and stores all the information that you have entered, and enables you to perform a silent upgrade at a later time. The silent upgrade performs exactly the same function that the Upgrade Assistant performs, but you do not have to manually enter the data again. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file.
    Click Upgrade to start the upgrade process.
  9. On the Upgrade Progress screen, monitor the status of the upgrade.

    Caution:

    Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary. Doing so may result in an unstable environment.
    If any components are not upgraded successfully, refer to the Upgrade Assistant log files for more information.

    Note:

    The progress bar on this screen displays the progress of the current upgrade procedure. It does not indicate the time remaining for the upgrade.

    Click Next.

  10. If the upgrade is successful: On the Upgrade Success screen, click Close to complete the upgrade and close the wizard. The Post-Upgrade Actions window describes the manual tasks you must perform to make components functional in the new installation. This window appears only if a component has post-upgrade steps.
    If the upgrade fails: On the Upgrade Failure screen, click View Log to view and troubleshoot the errors. The logs are available at NEW_ORACLE_HOME/oracle_common/upgrade/logs.

    Note:

    If the upgrade fails you must restore your pre-upgrade environment from backup, fix the issues, then restart the Upgrade Assistant.

Performing Post Upgrade Configuration Tasks for Oracle SOA with Oracle BAM 12c

To run the SOA 12c domain that will eventually include Oracle BAM 12c, you must perform additional configuration tasks after the upgrade.

Note:

Oracle recommends that you first run the 12c SOA environment with Oracle BAM 11g. Once you have verified that the environment is functioning as expected, you can extend the domain with Oracle BAM 12c as described in Extending the SOA Domain with Oracle BAM 12c.

Starting the Admininstration (Admin) Server

To start the Oracle WebLogic Administration Server, use the following script:

(UNIX) DOMAIN_HOME/bin/startWebLogic.sh

(Windows) DOMAIN_HOME\bin\startWebLogic.cmd

Launching the WebLogic Server Administration 12c Console

To display the Administration Console:

  1. Enter the following URL in a browser:
    http://hostname:port_number/console
    

    The port number is the port number of the Administration Server. By default, the port number is 7001.

    The login page is displayed.

  2. Log in using the user name and password supplied during installation or another administrative user that you created.

    Alternatively, you can access the Administration Console from Fusion Middleware Control, from the home pages of targets such as the Administration Server or Managed Servers.

Deleting the UMS JMS Resources Running on the Oracle BAM Server or Oracle BAM Cluster

These steps can be used to remove the UMS JMS resources for standalone or clustered environments. Note the additional steps needed for Oracle BAM cluster.

  1. Determine which JMS Server name is targeted to the Oracle BAM server or Oracle BAM cluster. You may have multiple JMS servers, and it is important to note which server is targeted to the Oracle BAM server or cluster before you continue. If you have only one UMS JMS Server, the default name is UMSJMSServer_auto_1. Always validate that the target of the selected UMS JMS Server is the Oracle BAM server or Oracle BAM cluster.

    Navigate to the Summary of JMS Servers screen (shown below). From the Domain Structure menu, expand Services, select Messaging and then select JMS Servers. Locate the UMSJMSServer that is targeted to the Oracle BAM server.

    In the example below, UMSJMSServer_auto_3 is the server targeted to the Oracle BAM server.

  2. Delete the local queues for the UMS JMS Server targeted to Oracle BAM (UMSJMSServer_auto_3 in this example).

    Navigate to the Summary of JMS Modules screen (shown below). From the Domain Structure menu, expand Services, select JMS Modules. Locate UMSJMSSystemResource and click to display the local (and distributed) queues in the Settings for UMSJMSSystemResource screen. You can filter the results to show only those queues targeted to your UMS JMS Server.

  3. Oracle BAM Cluster Only: Select all Uniform Distributed Queues targeted only to the Oracle BAM server or cluster (UMSJMSServer_auto_3 in this example). (You can filter by type Uniform Distributed Queues). Click Delete.

    CAUTION: Do not delete distributed queues that include server targets other than Oracle BAM. If there are other targeted servers, you must first remove (untarget) the Oracle BAM server from the distributed queue as shown in Step 4.

  4. Untarget the Oracle BAM server from the distributed queue (if necessary).

    To untarget the Oracle BAM server from the distributed queue, click the Targets tab from the Settings for UMSJMSSystemResource screen. Remove the checkmark next to the Oracle BAM server and click Save. Now you can safely delete the distributed queues as described in Step 3.

  5. Delete the local queues that are targeted to the UMS JMS Server.

    Select all local queues that are targeted to the UMS JMS Server targeted to Oracle BAM (UMSJMSServer_auto_3) from the Settings for UMSJMSSystemResource screen (as shown below):

  6. Click Delete.

Deleting Subdeployment Resources Targeted to UMS JMS Server Targeted to Oracle BAM

Delete the subdeployment resources targeted to UMS JMS server targeted to Oracle BAM.

  1. Delete the subdeployment resources from the UMS JMS Server.

    From the Settings for UMSJMSSystemResource screen, click the Subdeployments tab.

  2. Select the UMS JMS Server targeted to Oracle BAM (in the example below its UMSJMSServer_auto_3).
  3. Click Delete.

Removing the Oracle BAM Servers and Clusters from the Domain

While the Admin Server is running, use Weblogic Console to complete the following tasks.

Note:

For more information on navigating through the Fusion Middleware Control Console, see Getting Started with Administering Oracle SOA Suite and Oracle BPM Suite.

  1. Navigate to the Summary of JMS Servers screen (shown below). From the Domain Structure menu, expand Services, select Messaging and then select JMS Servers.
  2. Select the UMSJMSServer_auto_x from the list. Make sure the Current Target is the Oracle BAM server.
  3. Click Delete.
  4. Navigate to the Summary of Persisted Stores screen (shown below).
  5. Select UMSJMSFileStore_auto_x from the list. (Make sure the Target is the Oracle BAM server.)
  6. Click Delete.

  7. Navigate to the Summary of Clusters screen (shown below). From the Domain Structure menu, expand Environment and select Clusters.
  8. Select bam_cluster from the list of clusters.
  9. Click Delete.

  10. Navigate to the Summary of Servers screen (shown below). From the Domain Structure menu, expand Environment and select Servers.
  11. Select the Oracle BAM server(s) from the list.
  12. Click Delete.

Removing Unnecessary Oracle BAM 11g Files from the Upgraded Domain

Use the domainupdater script to remove any unnecessary 11g files from the upgraded domain.

  1. Stop the 12c Admin Server:
    DOMAIN_HOME/bin/stopWebLogic.sh 
           username password [admin_url]
    
  2. Run the domainupdater script from the SOA 12c home to remove any unnecessary legacy 11g files from the upgraded domain.
    (UNIX) cd ORACLE_HOME/soa/bam/bin
    ./domainupdater.sh
    Enter the 11g domain path: (ex:)/soa11g/user_projects/domains/soa_domain 
    
    (Windows) cd ORACLE_HOME\soa\bam\bin
    domainupdater.cmd
    Enter the 11g domain path: (ex:)\soa11g\user_projects\domains\soa_domain 
    
  3. Restart the 12c Admin Server.
    (UNIX) DOMAIN_HOME/bin/startWebLogic.sh
    
    (Windows) DOMAIN_HOME\bin\startWebLogic.cmd
    

For Cluster Upgrades Only: Stop the Admin and Managed Servers

If you are upgrading a cluster, you must stop the Admin and Managed Servers before you execute the pack and unpack commands.

To stop the WebLogic Server:

DOMAIN_HOME/bin/stopWebLogic.sh 
       username password [admin_url]

To stop the SOA server:

(UNIX) DOMAIN_HOME/bin/stopManagedWebLogic.sh
           soa_server_name admin_url 
(Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd
           soa_server_name admin_url

Managed servers must be stopped in the order described in the following:

Stop the Admin Server and SOA Managed Server(s)

Stop the Managed Servers

Stop all of the 12c servers and processes that are currently running before you begin extending the domain.

Stop the SOA Managed Servers with following script:

  • (UNIX)

    DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url
  • (Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Note:

Stop the SOA servers and processes in this order:
  1. Business Activity Monitoring (BAM) Managed Server

  2. Oracle Service Bus (OSB) Managed Server

  3. Service-Oriented Architecture (SOA) Managed Server

  4. Oracle Web Services Manager (OWSM) Managed Server

Stop the Administration Server

When you stop the Administration Server, you also stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To stop an Administration Server, use the following script:

DOMAIN_HOME/bin/stopWebLogic.sh       

When prompted, enter your user name, password and the URL of the administration server

For Cluster Upgrades Only: Run the Pack Command where the Admin Server and Managed Servers are Installed

To get the reconfigured domain, including NodeManager, onto the other node in the cluster, execute a managed pack from the Admin Server machine, and then unpack on the remote nodes.

The pack command creates a template archive (.jar) file that contains a snapshot of either an entire domain or a subset of a domain. You can use a template that contains a subset of a domain to create a Managed Server domain directory hierarchy on a remote machine.

NOTE: The pack and unpack command utility must be run from 12c install directory pointing to the upgraded 11g domain.

Execute the pack command on the server where the Admin Server and one of the Managed Servers is installed.

In our example, you would execute the following on SOAHOST1:

cd /12c_ORACLE_HOME/oracle_common/common/bin

./pack.sh -domain=/11g_DOMAIN_HOME -template=domainupgradetemplate.jar -template_name=domainupgradetemplate -managed=true

In this example:

  • 12c_ORACLE_HOME refers the actual path to the 12c Oracle Home directory (the installation directory for the 12.2.1 bits).

  • Replace 11g_DOMAIN_HOME with the actual path to the upgraded domain directory.

  • domainupgradetemplate.jar is a sample name for the jar file you are creating, which will contain the domain configuration files.

  • domainupgradetemplate is the name assigned to the domain template file.

  • By default, the domainupgradetemplate is created in the current directory where you ran the pack command. In this example, it would be created in the following directory, but you can specify a full path for the template jar file as part of the -template argument to the pack command:

    ORACLE_COMMON_HOME/common/bin/
    

The pack command creates a template archive (.jar) file that contains a snapshot of either an entire domain or a subset of a domain. You can use a template that contains a subset of a domain to create a Managed Server domain directory hierarchy on a remote machine.

For more information on using the pack command, see "Overview of the Pack and Unpack Commands" in Creating Templates and Domains Using the Pack and Unpack Commands.

For Cluster Upgrades Only: Run the Unpack Command to Replicate the Domain Configuration of SOAHOST1 on SOAHOST2.

Make sure that the Admin and Managed Servers are still stopped and then execute the following unpack command to create a full domain or a subset of a domain

You can create a full domain or a subset of a domain used for a Managed Server domain directory on the remote machine. You may use unpack only with a template compatible with your current installation.

A sample unpack command code snippet is shown below. Use this as an example only. Note that you must specify the "-overwrite_domain=true" flag on unpack.

For more information on using the pack command, see "Overview of the Pack and Unpack Commands" in Creating Templates and Domains Using the Pack and Unpack Commands.

cd /12c_ORACLE_HOME/oracle_common/common/bin

./unpack.sh -template=domainupgradetemplate.jar - domain=11g_DOMAIN_HOME -overwrite_domain=true

In this example:

  • 12c_ORACLE_HOME refers the actual path to the 12c Oracle Home directory (the installation directory for the 12.2.1 bits).

  • Replace 11g_DOMAIN_HOME with the actual path to the upgraded domain directory.

  • domainupgradetemplate.jar is a sample name for the jar file you are creating, which will contain the domain configuration files.

  • domainupgradetemplate is the name assigned to the domain template file.

Restarting the Admin Server

You must restart the 12c Administration Server before you execute the remaining configuration tasks.

When you start the Administration Server, you also start the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To start an Administration Server, use the following script:

(UNIX) DOMAIN_HOME/bin/startWebLogic.sh
(Windows)DOMAIN_HOME\bin\startWebLogic.cmd    

When prompted, enter your user name, password and the URL of the administration server

Configuring 11g Oracle BAM Adapter to Work With SOA 12c Domain

Once the SOA 12c domain has been upgraded, you must configure the SOA 12c domain to use the Oracle BAM 11g domain.

Use the Oracle BAM 11g domain you created in Creating a New Oracle BAM 11g Domain Before You Upgrade.

For more information on how to configure this setup, see "Configuring Oracle BAM Adapter" in the 11g version of the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite.

Restarting the SOA Managed Servers

You must restart the SOA Managed Servers to complete the post configuration tasks.

Start the WebLogic Server Managed Server with following script:

  • (UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url

  • (Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Start SOA servers and processes in this order:

  1. Oracle Web Services Manager (OWSM) Managed Server
  2. Service-Oriented Architecture (SOA) Managed Server

  3. Oracle Service Bus (OSB) Managed Server

  4. Business Activity Monitoring (BAM) Managed Server

Note:

The startup of a Managed Server will typically start the applications which are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.

Deleting the Existing UMS Email Driver from the SOA Domain

Due to incompatibility issues with the mail patterns, you must delete the UMS driver in Oracle Enterprise Manager.

Note that you will create a new driver after you have extended the SOA 12c domain with the Oracle BAM 12c templates.

  1. While the Admin Server and all the managed servers are running in the SOA domain, navigate to User Messaging Service, select the usermessagingdriver-mail service targeted to the soa_server.

    From the User Messaging Email Driver drop-down menu, select Email Driver Properties as shown below.

  2. Select the User Messaging Service Email driver name from the Target Navigation pane.
  3. Click Delete.
  4. Repeat the process for any other cluster present in the domain.

Extending the SOA Domain with Oracle BAM 12c

When you are ready to use Oracle BAM 12c with your upgraded SOA 12c environment, you must extend the domain to include the BAM 12c templates.

Complete the following tasks. Note that some tasks are optional.

Stop the Admin Server and SOA Managed Server(s)

Stop the Managed Servers

Stop all of the 12c servers and processes that are currently running before you begin extending the domain.

Stop the SOA Managed Servers with following script:

  • (UNIX)

    DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url
  • (Windows) DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Note:

Stop the SOA servers and processes in this order:
  1. Business Activity Monitoring (BAM) Managed Server

  2. Oracle Service Bus (OSB) Managed Server

  3. Service-Oriented Architecture (SOA) Managed Server

  4. Oracle Web Services Manager (OWSM) Managed Server

Stop the Administration Server

When you stop the Administration Server, you also stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

To stop an Administration Server, use the following script:

DOMAIN_HOME/bin/stopWebLogic.sh       

When prompted, enter your user name, password and the URL of the administration server

Extend the SOA 12c Domain with Oracle BAM 12c Domain Template

Use the Configuration Wizard to extend the existing SOA domain with Oracle BAM 12c.

  1. Launch the Configuration Wizard.
    (UNIX) ORACLE_HOME/oracle_common/common/bin
    ./config.sh
    
    (Windows) ORACLE_HOME\oracle_common\common\bin
    config.cmd
     
  2. Select Extend Existing Domain when prompted:
  3. Select the following templates on the Templates screen:
    • Oracle WSM Policy Manager - 12.2.1.0

    • Oracle User Messaging Service - 12.2.1.0

    • Oracle BAM Client - 12.2.1.0

    • Oracle Enterprise Manager Plugin for BAM - 12.2.1.0

  4. Complete the remaining Configuration Wizard screens as described in Configuring the Oracle Business Activity Monitoring Domain in Installing and Configuring Oracle SOA Suite and Business Process Management.

Certain Fusing Middleware components such as SOA, OSB and BAM have a dependency on UMS in 12c. If you configure more than one of these components within a single 12.2.1 domain, then each of these components must run within its own cluster — even if there is only one server that runs that component. See Figure 8-1 in Upgrading a Clustered SOA Environment.

When you reach the Advanced Configuration screen of the Configuration Wizard, select Managed Servers, Clusters, and Coherence to create a BAM cluster as described in "Clusters" in Creating WebLogic Domains Using the Configuration Wizard.

Create the New UMS Email Driver for the Oracle BAM Server

While the Oracle BAM server is running in the cluster, use Fusion Middleware Control Console to complete the following tasks:

  1. Navigate to the Email Driver Properties screen.

    From the Target Navigation pane, select User Messaging Service and from the User Messaging Email Driver drop-down menu, select Email Driver Properties (as shown below).

  2. Click Create to add a new UMS Email driver.
  3. Provide a unique name for the new Email driver in the Name field as shown below. Note that UMS needs to be configured on each cluster in a 12c domain. Therefore maintain the default selection for Configuration Level as Cluster as shown in the image.
  4. Select Use Default Sender Address. Note that the EMAIL: prefix is mandatory in this field.
  5. Click OK to create the new driver with the given properties.

Import the Oracle BAM 11g data objects and EMS data to the BAM 12c server.

Once you have extended the domain to include BAM 12c, you must export the data objects and EMS data from the BAM 11g environment you have been using with SOA 12c. You will then import this data to the SOA with BAM 12c environment.

  1. Export the data objects and EMS data from the 11g BAM domain using the 11g ICommand command-line utility. (Note that the EMS definitions were upgraded as part of the standard upgrade process and do not need to be imported.)

    The following example shows how to use ICommand 11g to export information about one or more objects in the Oracle BAM server to a XML file:

    $11g_ORACLE_HOME/soa/bam/bin/icommand -cmd export -name "/Samples/Call Center" -type dataobject -file C:\CallCenter.xml
    

    NOTE: You may need to modify the ICommand configuration file before you run the script. Specifically, verify that the correct usernames and passwords have been entered. The BAMICommandConfig.xml file is located in WLS_HOME/user_projects/domains/base_domain/config/fmwconfig/servers/bam_server1/applications/oracle-bam_11.1.1/config/.

    The following is an example configuration file.

    <host>www.example.com</host>
    <port>7001</port>
    <username>weblogic</username>
    <password>your_password</password>
    <dbusername>SOAINFRA</dbusername>
    <dbpassword>your_dbpassword</dbpassword>
    <dburl>jdbc:oracle:thin:@localhost:1521:example</dburl>
    

  2. Import the XML file (created in the previous step) using the 12c BAMCommand command-line utility.

    The following example shows how to use 12c BAMCommand to import the information:

    $12c_ORACLE_HOME/soa/bam/bin/bamcommand -cmd import -file BPELOrderBookingDataObject.xml -upgrade 1 -username weblogic -port 7001 -host server.yourcompany.com 
    

Note:

When you use the import command with the -upgrade parameter to bring Oracle BAM 11g artifacts into Oracle BAM 12c, some information is modified.

Manually recreate the 11g BAM dashboards, alerts, and other artifacts for use in the BAM 12c domain.

The dashboards, alerts, views, etc. you used in your BAM 11g domain must be recreated for the BAM 12c domain.

See the following sections of the BAM user guide, Monitoring Business Activity with Oracle BAM:

Migrate 11g Process Cubes to BAM 12c Process Star Schema (BPM Users Only).

Oracle strongly recommends that you perform the process cubes migration after extending an upgraded BPM 12c domain with BAM 12c. This migration will ensure that all of the necessary 12c data objects are created for BPM entities. This will also ensure the BPM process analytics data has been migrated from the 11g Process cubes (applicable only if cube tables are populated with run-time data).

While exporting and importing each archive, you will be required to provide the server admininstrator (admin) username and password, as well as the SOAINFRA schema username and password.

Note:

The process cubes migration is a required prerequisite before proceeding with the Monitor Express migration described in Migrate the 11g Monitor Express data to BAM 12c Process Star schema. (Optional).

This step is required even if you did not use Oracle BAM 11g Monitor Express with BPM 11g.

Task 1: Disable the Process Metrics.
  1. Log in to the Fusion Middleware Control console.
  2. In the Target Navigation pane, expand the Weblogic Domain node.
  3. Select the domain in which Oracle SOA 12c server is installed.

    For example, the domain might be soainfra or base_domain.

  4. Right-click on the domain and select System MBean Browser.

    The System MBean Browser page appears.

  5. In the System MBean Browser, expand the Application Defined MBeans node.
  6. Under Application Defined MBeans, expand the oracle.as.soainfra.config node.
  7. Under oracle.as.soainfra.config, expand the Server: server_name node.
  8. Under Server: server_name, expand the AnalyticsConfig node.
  9. Under AnalyticsConfig, click analytics.

    The analytics attributes are listed.

  10. If not already set to true, change the value of the DisableProcessMetrics attribute to true.
  11. Click Apply.
Task 2: Determing the exportType to be used for the migration.

The exportType must be decided before migration because once the active instance migration is complete, and process analytics are enabled, you will not be able to go back and migrate the Completed instance data.

The valid exportType values are:

  • INFLIGHT_WITH_DIMENSION_AND_DEFINITION (default): Migrates only Active instance fact data archives

  • ALL: Migrates all Active and Completed instance fact data archives

Task 3: (UNIX Only) Run migrateBPMProcessCubes script from the 12c SOA home.

The migrateBPMProcessCubes shell script performs migration in two phases: export and import. The first phase exports the following archives from BPM Process Cubes, and then the second phase imports them to BAM 12c.

  • DefinitionExport.zip

  • DimensionExport.zip

  • ActiveFactDataExport.zip

  • CompletedFactDataExport.zip (if running with -exportType = ALL option)

Before running the migrateBPMProcessCubes script, you must set the following environment variables:
Environment Variable Description Sample Location
JAVA_HOME The location where you install the supported Java Development Kit (JDK). /u01/oracle/products/jdk_version
ORACLE_HOME The Oracle home that is created for all the Oracle Fusion Middleware products on a host computer. This read-only directory contains binary and library files, the Oracle Common home directory, and the individual product directories for each Oracle Fusion Middleware product you install.

NOTE: This was known at the Middleware Home in 11g.

/install_location/Oracle_Home
PROD_DIR The directory within the Oracle home, which contains the binary files associated with a logical product or feature set. The name of each product directory within the Oracle home is predefined by the installer and cannot be changed. install_location/Oracle_Home/SOA

On UNIX Operating Systems:

cd $ORACLE_HOME/bam/bin
./migrateBPMProcessCubes.sh -serverUrl <BAM 12c server url> -serverPort <BAM 12c server port> -serverUserName <BAM 12c server user> -dbUrl <soa db jdbc url> -dbUserName <soainfra schema username> -exportDir <export dir> [-exportType ALL] [-importOnly]

Where:

 serverUrl      (mandatory) : BAM 12c Server URL
 serverPort     (mandatory) : BAM 12c Server Port
 serverUserName (mandatory) : BAM 12c Server  admin user
 dbUrl          (mandatory) : SOA DB jdbc URL
 dbUserName     (mandatory) : SOAINFRA schema username
 exportDir      (mandatory) : A writable Directory where exported archives will be written
 exportType     (optional ) : Export Type.  Valid values are
                                a)INFLIGHT_WITH_DIMENSION_AND_DEFINITION (default):  Migrates only Active instance fact data archives
                                b)ALL                                             :  Migrates all Active and Completed instance fact data archives
 importOnly     (optional ) : If specified, data object definition and data archive export phase is skipped and only import is performed. It is assumed that archives are already present under "exportDir"

Note:

If there were errors during the migration, you may need to manually correct the issues and start the script again. For more information, see Error Handling: 11g Process Cubes to BAM 12c Star Schema Migration.

Task 4: (Windows Only) Export data object definitions and data from 11g BPM Process Cubes and then import them to 12c.

The data object definitions migration is performed in two steps. Step one involves exporting the data from 11g process cubes and step 2 imports the data into 12c.

The first phase exports the following archives from BPM Process Cubes, and then the second phase imports them to BAM 12c.The export command shown below will generate the following archive files under the <exportDir> directory:

  • DefinitionExport.zip

  • DimensionExport.zip

  • ActiveFactDataExport.zip

  • CompletedFactDataExport.zip (if running with -exportType = ALL option)

  1. Export the data objects and definitions using the following code example: (make sure that you provide your actual directory names)
    java -cp
    
    %ORACLE_HOME%\soa\modules\oracle.bpm.runtime_11.1.1\oracle.bpm.analytics.metrics.interface.jar;
    %ORACLE_HOME%\soa\modules\oracle.bpm.runtime_11.1.1\oracle.bpm.analytics.metrics.model.jar;
    %ORACLE_HOME%\oracle_common\modules\oracle.jdbc_12.1.0\ojdbc6.jar;
    %ORACLE_HOME%\bam\modules\oracle.bam.client\bam-client.jar;%ORACLEHOME%\bam\lib\bam-schema.jar;
    %ORACLE_HOME%\soa\modules\oracle.bpm.runtime_11.1.1\oracle.bpm.analytics.metrics.dataobject.jar;
    %ORACLE_HOME%\soa\modules\oracle.bpm.runtime_11.1.1\oracle.bpm.hwfanalytics.dataobject.jar
    
    oracle.bpm.metrics.dataobject.migration.application.Migrate11gProcessCubesto12cDO -url <soa db jdbc url> -userName <soa schema user name> -exportDir <export directory path> [-exportType ALL]
    
  2. Import the data object definitions(DefinitionExport.zip) into the BAM server.
    cd %ORACLE_HOME%\bam\bin\
    
    bamcommand.cmd  -host <bam server host> -protocol t3 -port <bam server port> -username <bam server admin user> -dburl <bam database jdbc url>
    -dbusername <bam database db user>  -cmd import -file <Path to  DefinitionExport.zip> -mode update
    
    

    NOTE: After importing the archive for BAM 12c, review the bamcommand.log.* files under ORACLE_HOME/bam/bin directory to make sure no errors occurred. If error conditions do exist, see Error Handling: 11g Process Cubes to BAM 12c Star Schema Migration.

Task 5: (Windows Only) Import dimension data (DimensionExport.zip) into the BAM server.

This command uses -datamode and -migrate parameters.

Use the following code example to import the dimension data:

cd %ORACLE_HOME%\bam\bin\

bamcommand.cmd  -host <bam server host> -protocol t3 -port <bam server port> -username <bam server admin user> -dburl <bam database jdbc url>
-dbusername <bam database db user>  -cmd import -file <Path to  DimensionExport.zip>  -datamode update -migrate 1

NOTE: After importing the archive for BAM 12c, review the bamcommand.log.* files under ORACLE_HOME/bam/bin directory to make sure no errors occurred. If error conditions do exist, see Error Handling: 11g Process Cubes to BAM 12c Star Schema Migration.

Task 6: (Windows Only) Import active fact data (ActiveFactDataExport.zip) into the BAM server.

This command uses -datamode and -migrate parameters.

cd %ORACLE_HOME%\bam\bin\

bamcommand.cmd  -host <bam server host> -protocol t3 -port <bam server port> -username <bam server admin user> -dburl <bam database jdbc url>
-dbusername <bam database db user>  -cmd import -file <Path to  ActiveFactDataExport.zip>  -datamode update -migrate 1
 
Task 7: (Windows Only - if exportType=ALL) Import completed fact data (CompletedFactDataExport.zip) into the BAM server.

This command uses -datamode and -migrate parameters.

Use this command only if you used the exportType ALL when you migrated the data objects definitions for the BAM 11g process cubes.

cd %ORACLE_HOME%\bam\bin\

run the following command
bamcommand.cmd  -host <bam server host> -protocol t3 -port <bam server port> -username <bam server admin user> -dburl <bam database jdbc url>
-dbusername <bam database db user>  -cmd import -file <Path to  ActiveFactDataExport.zip>  -datamode update -migrate 1
 

NOTE: After importing the archive for BAM 12c, review the bamcommand.log.* files under ORACLE_HOME/bam/bin directory to make sure no errors occurred. If error conditions do exist, see Error Handling: 11g Process Cubes to BAM 12c Star Schema Migration.

Task 8: Restart the Oracle BAM server once the migration has completed successfully.
(UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh
           bam_server_name admin_url
 
(Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd
           bam_server_name admin_url

When prompted, enter your user name and password.

Task 9: Enable the process metrics while the Oracle BAM server is running.
  1. Log in to the Fusion Middleware Control console.
  2. In the Target Navigation pane, expand the Weblogic Domain node.
  3. Select the domain in which the Oracle BAM server is installed.

    For example, the domain might be soainfra or base_domain.

  4. Right-click on the domain and select System MBean Browser.

    The System MBean Browser page appears.

  5. In the System MBean Browser, expand the Application Defined MBeans node.
  6. Under Application Defined MBeans, expand the oracle.as.soainfra.config node.
  7. Under oracle.as.soainfra.config, expand the Server: server_name node.
  8. Under Server: server_name, expand the AnalyticsConfig node.
  9. Under AnalyticsConfig, click analytics.

    The analytics attributes are listed.

  10. Change the value of the DisableProcessMetrics attribute to false.
  11. Click Apply.

Migrate the 11g Monitor Express data to BAM 12c Process Star schema. (Optional)

Prerequisite: Perform the steps in Migrate 11g Process Cubes to BAM 12c Process Star Schema (BPM Users Only)..

Complete this optional task only if want to be able to analyze historical data from BAM 11g through the BAM 12c process analytics dashboards. To do this, you must migrate the 11g process analytics data from BAM 11g the Monitor Express data objects to the BAM 12c Process star schema data objects.

Before you can upgrade the 11g Monitor Express data to BAM 12c Process Star schema, you must migrate 11g process cubes to the BAM 12c star schema to ensure that all of the necessary 12c data objects are created for BPM entities. This will also ensure the BPM process analytics data has been migrated from the 11g Process cubes (applicable only if cube tables are populated with run-time data).

Note:

If there are any errors while importing the archive files, you can roll back all of the imported data in the BAM 12c process star schema data objects by running the rollback SQL file.

From a BAM 12c database SQL prompt, log in as the SOAINFRA schema user, navigate to the <PATH> directory and execute the following command:

sql> @rollbackMonitorExpressMigration.sql

For additional error handling procedures, see Error Handling: 11g Process Cubes to BAM 12c Star Schema Migration.

Disable the Process Metrics.
  1. Log in to the Fusion Middleware Control console.
  2. In the Target Navigation pane, expand the Weblogic Domain node.
  3. Select the domain in which the Oracle BAM server is installed.

    For example, the domain might be soainfra or base_domain.

  4. Right-click on the domain and select System MBean Browser.

    The System MBean Browser page appears.

  5. In the System MBean Browser, expand the Application Defined MBeans node.
  6. Under Application Defined MBeans, expand the oracle.as.soainfra.config node.
  7. Under oracle.as.soainfra.config, expand the Server: server_name node.
  8. Under Server: server_name, expand the AnalyticsConfig node.
  9. Under AnalyticsConfig, click analytics.

    The analytics attributes are listed.

  10. Change the value of the DisableProcessMetrics attribute to true.
  11. Click Apply.
Run the Oracle BAM migration utility to migrate the Monitor Express data.

Data objects and data object definitions were migrated in Migrate 11g Process Cubes to BAM 12c Process Star Schema (BPM Users Only).

The following command will generate the data export for BPM data in zipped CSV files:

java -cp
$DOMAIN_HOME/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.analytics.metrics.interface.jar:
$ORACLE_HOME/oracle_common/modules/oracle.jdbc_12.1.0/ojdbc6.jar:
$ORACLE_HOME/bam/modules/oracle.bam.client/bam-client.jar:
$ORACLE_HOME/bam/lib/bam-schema.jar:
$ORACLE_HOME/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.analytics.metrics.dataobject.jar:
$ORACLE_HOME/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.hwfanalytics.dataobject.jar:
$ORACLE_HOME/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.analytics.metrics.model.jar    oracle.bpm.metrics.dataobject.migration.application.Migrate11gBAMBPMTo12cDO  PropertyFiles

This command will generate "FactDataExport.zip" file under <PATH> directory.

NOTE: You can specify the composite name in the property file. If a composite name is specified, then data for only those composites will be migrated. If a composite name is not defined in the property file, then all the composite data will be migrated.

#*************************************
#Mandatory Fields
#*************************************
#11g User Name
BAM_11g_USER_NAME= <<11gUserName>>
#12c User Name
BAM_12c_SOURCE_NAME = <<12cUserName>>
 
#11g URL
BAM_11g_URL=jdbc:oracle:thin:@<<11gBAMSchemaDatabaseIP>>:<<Port>>:<<SID>>
#12c URL
BAM_12c_URL=jdbc:oracle:thin:@<<12cDatabaseIP>>:<<Port>>:<<SID>>
 
#Path where data to be exported
PATH = <<Path where data need to be exported>>
#*************************************
#Optional Fields
#************************************
 
COMPOSITE_LIST = <<List of Composite for which data needs to be exported. This is ':' separated>>
#If above mention configurable is missing then all the composite data will be migrated.
DATAOBJECT_FOLDER_PATH = <<DataObject Path If this field is absent then default path will taken as Samples/Monitor Express/BI_>>
#************************************

Import the BPM data to Oracle BAM 12c.

This step will ensure that the previously exported BPM Monitor Express data is imported to BAM 12c.

cd $DOMAIN_HOME/bam/bin
 
./bamcommand -host <<host>> -protocol t3 -dbusername <<DbUserName>>  -dburl jdbc:oracle:thin:@<<DBIP>>:<<Port>><<SID>> -username  <<weblogicUserName>> -cmd import  -file <<Path of BPM FactDataExport zip file >> -mode update -migrate 1
Enable publishing to BAM 12c.

Once the migration is complete, enable publishing to BAM 12c by setting the DisableProcessMetrics parameter to false.

  1. Log in to the Fusion Middleware Control console.
  2. In the Target Navigation pane, expand the Weblogic Domain node.
  3. Select the domain in which the Oracle BAM server is installed.

    For example, the domain might be soainfra or base_domain.

  4. Right-click on the domain and select System MBean Browser.

    The System MBean Browser page appears.

  5. In the System MBean Browser, expand the Application Defined MBeans node.
  6. Under Application Defined MBeans, expand the oracle.as.soainfra.config node.
  7. Under oracle.as.soainfra.config, expand the Server: server_name node.
  8. Under Server: server_name, expand the AnalyticsConfig node.
  9. Under AnalyticsConfig, click analytics.

    The analytics attributes are listed.

  10. Change the value of the DisableProcessMetrics attribute to false.
  11. Click Apply.

Note:

If there are any errors while importing the archive files, you can roll back all of the imported data in the BAM 12c process star schema data objects by running the rollback SQL file.

From a BAM 12c database SQL prompt, log in as the SOAINFRA schema user, navigate to the <PATH> directory and execute the following command:

sql> @rollbackMonitorExpressMigration.sql

For additional error handling procedures, see Error Handling: 11g Process Cubes to BAM 12c Star Schema Migration.

Generating 11g Compatible Process Star Schema Data Views in 12c (Optional)

If you have an Oracle Fusion Middleware 11g application built on top of 11g process star schema views, and you want to continue to use the application in 12c, then you will need to recreate the views after the upgrade. The Star schema database views in 12c are different from the 11g views and cannot be automatically upgraded.

Specifically, the star schema database views in 12c have different names, are based on top of Oracle BAM data objects (and not on process cube tables), and are created at the composite level (instead of process level as in 11g). An automated utility is provided to assist you in recreating your views - both standard and process-specific - for use in your Oracle 12c environment.

Task 1: Update the classpath to include the interface JAR file.

You must updated the CLASSPATH to include the location of the oracle.bpm.analytics.interface.jar file located in the SOA Home.

For example:

DOMAIN_HOME/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.analytics.interface.jar

Task 2: Recreate Standard Views

Use the Standard View 11g Migration Utility to create 12c compatible versions of the following 11g standard views:

  • BPM_ACTIVITY_DEFINITION_V
  • BPM_ACTIVITY_INSTANCE_V
  • BPM_ACTIVITY_PERFORMANCE_V
  • BPM_PROCESS_DEFINITION_V
  • BPM_PROCESS_INSTANCE_V
  • BPM_PROCESS_PERFORMANCE_V
  • BPM_ROLE_DEFINITION_V

Use the following command to run the utility:

java -cp $DOMAIN_HOME/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.analytics.interface.jar oracle.bpm.analytics.cube.persistence.util.StandardView11gMigrationUtil <initialContextFactory> <protocol> <hostname> <soa-port> <username>[]

Where:

  • initialContextFactory is the JNDI Initial Context Factory such as weblogic.jndi.WLInitialContextFactory

  • protocol is the RMI / JNDI protocol configured for the target server. Specify t3, IIOP, HTTP, T3s, IIOPS, or HTTPS.

  • hostname is the full name of the host such as soa.mycompany.com

  • soa-port is the SOA listening port such as 7001

  • username is the server login name such as weblogic.

Task 3: Recreate Process-Specific Views

Use the Process Specific View 11g Migration Utility to create 12c compatible versions of the following 11g process-specific views:

  • BPM_ACTV_INST_<viewIdentifier>_V
  • BPM_ACTV_PERF_<viewIdentifier>_V
  • BPM_PRCS_INST_<viewIdentifier>_V
  • BPM_PRCS_PERF_viewIdentifier>_V

Use the following command to run the utility:

java -cp $DOMAIN_HOME/soa/modules/oracle.bpm.runtime_11.1.1/oracle.bpm.analytics.interface.jar oracle.bpm.analytics.cube.persistence.utill.ProcessSpecificView11gMigrationUtil <initialContextFactory> <protocol> <hostname> <soa-port> <username > [<composite-name>]

Where:

  • initialContextFactory is the JNDI Initial Context Factory such as weblogic.jndi.WLInitialContextFactory

  • protocol is the RMI / JNDI protocol configured for the target server. Specify t3, IIOP, HTTP, T3s, IIOPS, or HTTPS.

  • hostname is the full name of the host such as soa.mycompany.com

  • soa-port is the SOA listening port such as 7001

  • username is the server login name such as weblogic.

  • composite-name (optional) is the name of a single composite you want to create views

Recovering from a Failed Oracle BAM Upgrade

This section applies only when there are BAM servers in the domain. As part of BAM Upgrade, you can export BAM archives from 11g and import them into BAM 12c. If you receive any errors during this process, use this section to try to resolve the issues.

Resolving the CFGFWK-60950 Error

If you received the CFGFWK-60950 error, rename the BAM templates as described in "Renaming the Oracle BAM Templates Before Upgrading the 11g Schemas" and launch the Reconfiguration Wizard again.

If you received this error, you will need restore your entire pre-upgrade environment, perform the necessary pre-upgrade tasks and then perform the steps in the section listed above before you can attempt the reconfiguration process again.

Error Handling: 11g Process Cubes to BAM 12c Star Schema Migration

You may be able to resolve common errors by rolling back the data changes and rerunning the scripts with modified options.

Rollback All Data Changes:

  1. Open a SQL session on the SOA database.
  2. Log in as the SOAINFRA schema user and run the following script to roll back any data changes:
    "<exportDir>/rollBackBPMProcessCubesMigration.sql"
    

Review the recommendations for your operating system:

Error Handling for UNIX Operating Systems

If any unexpected errors occurred during migration, you can try the following steps to correct the issues:

For Errors that Occurred During the Import Phase:

If the error occurred while importing archives to BAM 12c, rerun the shell script "migrateBPMProcessCubes.sh" as described in Migrate 11g Process Cubes to BAM 12c Process Star Schema (BPM Users Only)., but add the "-importOnly" option. This can save time by skipping the export step.

For example:

cd $ORACLE_HOME/bam/bin
./migrateBPMProcessCubes.sh -serverUrl <BAM 12c server url> -serverPort <BAM 12c server port> -serverUserName <BAM 12c server user> -dbUrl <soa db jdbc url> -dbUserName <soainfra schema username> -exportDir <export dir> [-exportType ALL] [-importOnly]

For Errors that Occurred During the Export Phase:

If the error occurred while exporting archives from BPM Process cubes, perform the following tasks:

  1. Create a backup copy of the export directory defined as (<exportDir>)
  2. Delete the contents of the <exportDir>.
  3. Rerun the shell script "migrateBPMProcessCubes.sh" as described in Migrate 11g Process Cubes to BAM 12c Process Star Schema (BPM Users Only)., but remove the "-importOnly" option.

    For example:

    cd $ORACLE_HOME/bam/bin
    ./migrateBPMProcessCubes.sh -serverUrl <BAM 12c server url> -serverPort <BAM 12c server port> -serverUserName <BAM 12c server user> -dbUrl <soa db jdbc url> -dbUserName <soainfra schema username> -exportDir <export dir> [-exportType ALL]
    

Additional Information:

You can also try the following to help resolve any issues:

  • After importing each archive to BAM 12c, review the bamcommond.log.* files located in the $ORACLE_HOME/bam/bin directory to make sure no errors occurred.

  • Review the migration logs located in the <exportDir>/MigrationLogs.* :

Error Handling for Windows Operating Systems

Roll back all of the data changes as described above, and then try the following:

For Errors that Occurred During the Import Phase:

Reimport the archives as described in the following sections:

  1. Create a backup copy of the export directory defined as (<exportDir>)
  2. Delete the contents of the <exportDir>.
  3. Rerun the shell script "migrateBPMProcessCubes.sh" as described in Migrate 11g Process Cubes to BAM 12c Process Star Schema (BPM Users Only)., but remove the "-importOnly" option.

    For example:

    java -cp
    
    %ORACLE_HOME%\soa\modules\oracle.bpm.runtime_11.1.1\oracle.bpm.analytics.metrics.interface.jar;
    %ORACLE_HOME%\soa\modules\oracle.bpm.runtime_11.1.1\oracle.bpm.analytics.metrics.model.jar;
    %ORACLE_HOME%\oracle_common\modules\oracle.jdbc_12.1.0\ojdbc6.jar;
    %ORACLE_HOME%\bam\modules\oracle.bam.client\bam-client.jar;%ORACLEHOME%\bam\lib\bam-schema.jar;
    %ORACLE_HOME%\soa\modules\oracle.bpm.runtime_11.1.1\oracle.bpm.analytics.metrics.dataobject.jar;
    %ORACLE_HOME%\soa\modules\oracle.bpm.runtime_11.1.1\oracle.bpm.hwfanalytics.dataobject.jar
    
    oracle.bpm.metrics.dataobject.migration.application.Migrate11gProcessCubesto12cDO -url <soa db jdbc url> -userName <soa schema user name> -exportDir <export directory path> [-exportType ALL]
    
  4. Repeat the remaining migration steps in Migrate the 11g Monitor Express data to BAM 12c Process Star schema. (Optional).