4 Upgrading Oracle Service Bus (without Oracle SOA Suite) from 11g

Describes the upgrade-specific tasks for upgrading Oracle Service Bus 11g without Oracle SOA Suite and Business Process Management.

Note:

If Oracle Service Bus is part of your SOA 11g or a previous 12c domain, and you will be upgrading Oracle Service Bus as part of your Oracle SOA Suite upgrade to 12c (12.2.1.2), follow the standard upgrade process described in Upgrading SOA Suite and Business Process Management from 11g or Upgrading Oracle SOA Suite and Business Process Management from a Previous 12c Release.

• Understanding the Oracle Service Bus Standalone Upgrade to 12c
  Follow this process flow to upgrade an Oracle Service Bus 11g deployment that does not include Oracle SOA Suite.
• Upgrade Limitations for Oracle Service Bus 12c (12.2.1.2)
  If your Oracle Service Bus 11g topology is configured with more than one component within a single domain, then you will not be able to upgrade to 12c (12.2.1.2)
• Performing Pre-Upgrade Tasks for Oracle Service Bus (OSB)
  
• Installing Oracle Service Bus
  Before beginning your upgrade, use the Oracle Universal Installer to install the required product distribution on the target system. You can install and upgrade Oracle Service Bus without Oracle SOA Suite and Business Process Management, but you must still install the Oracle Fusion Middleware Infrastructure 12c (12.2.1.2) before upgrading Oracle Service Bus.
• Creating the Required 12c Schemas with the RCU
  When upgrading from 11g, you must use the Repository Creation Utility (RCU) to create the required 12c schemas before you begin the upgrade.
• Stopping Servers and Processes
  Before running the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all processes and servers, including the Administration server and any managed servers.
• Upgrading an Oracle Service Bus Domain (without SOA)
  
• Reconfiguring the Domain
  Run the Reconfiguration Wizard to reconfigure your domain component configurations to 12c (12.2.1.2).
• 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.
• Performing Post Upgrade Tasks for Oracle Service Bus
  
• Troubleshooting Oracle Service Bus Upgrade
  

4.1 Understanding the Oracle Service Bus Standalone Upgrade to 12c

Follow this process flow to upgrade an Oracle Service Bus 11g deployment that does not include Oracle SOA Suite.

Oracle Service Bus (OSB) can be upgraded to 12c (12.2.1.2) with or without Oracle SOA Suite and Business Process Management. The upgrade steps in this topic describe how to upgrade Oracle Service Bus without SOA.

If Oracle Service Bus is part of your SOA 11g or a previous 12c domain, and you will be upgrading Oracle Service Bus as part of your Oracle SOA Suite upgrade to 12c (12.2.1.2), follow the standard upgrade process described in Upgrading SOA Suite and Business Process Management from 11g.

Note:

Even though your domain does not include SOA, you will still have to upgrade the _SOAINFRA schema to upgrade Oracle Service Bus metadata. Oracle Service Bus does not have a separate schema.

Description of the illustration GUID-BC505C48-EFBB-456B-9256-9979A9C6B2C9-default.png

Task	Description
Required if Oracle Web Services Manager is not already deployed. Deploy Oracle Web Services Manager Policy Manager in your existing 11g environment.	If Oracle Web Services Manager (OWSM) Policy Manager is not already deployed in your Oracle Service Bus 11g environment, then you must manually deploy it before you upgrade to 12c.
Required Export services, projects and resources when upgrading Oracle Service Bus	You must export services, projects and resources into a configuration JAR file before you can upgrade to Oracle Service Bus 12c (12.2.1.2). After the upgrade, you will import the JAR file to the new 12c environment.
Required Delete all services, projects and resources from the existing environment.	After the export, you must delete all user-created services, projects and resources before the upgrade.
Required Install the 12c Oracle Fusion Middleware Infrastructure distribution into a new Oracle home.	You must install the 12c Infrastructure (which includes Oracle WebLogic Server and JRF components).
Required Install Oracle Service Bus into a new Oracle home.	Obtain the Oracle Service Bus distribution and install the content to a new Oracle home.
Required Run the Repository Creation Utility (RCU) to create the new required schema.	The Service Table schema (_STB) is a new required schema for all domains. If you are upgrading from 11g, you will have to create this schema before you can upgrade to 12c. Oracle Service Bus also requires the SOA schema (_SOAINFRA) even when SOA is not part of your domain. If you are upgrading from a previous 12c release, do not create another Service Table schema.
Required Stop all servers and processes.	You must stop all servers and processes before starting the upgrade.
Required Run the Upgrade Assistant to upgrade the required schemas.	If you are upgrading from a previous 12c release, the _SOAINFRA schema must be upgraded to 12c (12.2.1.2).
Required Run the Reconfiguration Wizard to reconfigure the existing domain.	You will continue to use the existing domain after the upgrade, so it must be reconfigured to work with the new components.
Required Run the Upgrade Assistant to configure the component configurations.	You will run the Upgrade Assistant a second time to update the component configuration to work in the new domain.
Required Perform all post-upgrade tasks.	Perform the standard 12c post-upgrade tasks, as well as any post-upgrade OSB-specific tasks, that apply to your deployment.

4.2 Upgrade Limitations for Oracle Service Bus 12c (12.2.1.2)

If your Oracle Service Bus 11g topology is configured with more than one component within a single domain, then you will not be able to upgrade to 12c (12.2.1.2)

Upgrading Multiple Components that use UMS in a Single OSB Domain (Not Supported)

Certain Fusion Middleware components such as Oracle SOA, Oracle Service Bus (OSB) and Business Activity Monitoring (BAM) have a dependency on User Messaging Service (UMS) in 12c. If you configure more than one of these components within a single 12c (12.2.1.2) domain, then each of these components must run within its own cluster — even if there is only one server that runs that component.

In order to upgrade these components, you must create a separate cluster for each component during the domain reconfiguration as described in Clusters.

The supported upgrade topology for these components is described in Upgrading a Clustered Topology.

4.3 Performing Pre-Upgrade Tasks for Oracle Service Bus (OSB)

If you are upgrading Oracle Service Bus, you must perform the following tasks before you begin the upgrade. Review your own use case scenarios and existing deployment to determine if the following tasks apply to your environment.

1. Deploying Oracle Web Services Manager Policy Manager in Your 11g Environment
   
2. Exporting Services, Projects and Resources when Upgrading Oracle Service Bus
   
3. Deleting All Services, Projects and Resources
   
4. Migrating Oracle Service Bus Resources from Previous Releases
   

4.3.1 Deploying Oracle Web Services Manager Policy Manager in Your 11g Environment

If Oracle Web Services Manager (OWSM) Policy Manager is not already deployed in your Oracle Service Bus 11g environment, then you must manually deploy it before you upgrade to 12c.

In 11g, both WebLogic security policies and OWSM policies were supported on Oracle Service Bus. As of 11g (11.1.1.7), WebLogic Security policies were deprecated, and are not supported in 12c (12.2.1.2). Because WebLogic security policies were available in 11g, deployment of the OWSM Policy Manager and use of the OWSM policies was optional. Since only OWSM policies are supported in 12c, OWSM Policy Manager deployment is mandatory.

For information on manually deploying the OWSM Policy Manager in your 11g environment, see Installing OWSM with WebLogic Server in Securing Web Services and Managing Policies with Oracle Web Services Manager.

4.3.2 Exporting Services, Projects and Resources when Upgrading Oracle Service Bus

You must export services, projects and resources into a configuration JAR file before you can upgrade to Oracle Service Bus 12c (12.2.1.2). After the upgrade, you will import the JAR file to the new 12c environment.

Note that you can manually export resources and services from older, supported releases. See Migrating Oracle Service Bus Resources from Previous Releases.

For more information, see Importing and Exporting Resources and Configurations in Developing Services with Oracle Service Bus.

4.3.3 Deleting All Services, Projects and Resources

After the export, you must delete all user-created services, projects and resources before the upgrade.

For information on using the Oracle Service Bus Console to delete resources, see How to Delete Projects, Folders, and Resources.

For information on using JDeveloper to delete resources, see How to Delete a Project or Resource.

4.3.4 Migrating Oracle Service Bus Resources from Previous Releases

You can manually export resources and services from the following releases and use them with Oracle Service Bus 12c (12.2.1.2):

• Oracle Service Bus 12c Release 12.1.3.0, 12.2.1.0, and 12.2.1.1

• Oracle Service Bus 11g Release: 11.1.1.7.0

• Oracle Service Bus 10.3 Releases: 10.3.1 and 10.3.0

• AquaLogic® Service Bus Releases 3.0 and later

For more information, see Importing and Exporting Resources and Configurations in Developing Services with Oracle Service Bus.

4.4 Installing Oracle Service Bus

Before beginning your upgrade, use the Oracle Universal Installer to install the required product distribution on the target system. You can install and upgrade Oracle Service Bus without Oracle SOA Suite and Business Process Management, but you must still install the Oracle Fusion Middleware Infrastructure 12c (12.2.1.2) before upgrading Oracle Service Bus.

Note:

You must install the Oracle Fusion Middleware Infrastructure distribution first before installing other Fusion Middleware products, when Infrastructure is required for the upgrade.

Before you begin, note the following:

• Oracle Service Bus requires the Oracle Fusion Middleware Infrastructure (Oracle WebLogic Server and JRF).

• If you want to use Oracle Web Services Manager policies with Oracle Service Bus, then you must select the Oracle Web Services Manager extension template after selecting one of the Oracle Service Bus domain templates when configuring the Oracle WebLogic domain.

To install the required distributions for Oracle Service Bus:

1. Sign in to the target system where you want to install the 12c (12.2.1.2) product distribution.
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.2.0_infrastructure_generic.jar)
   • Oracle Service Bus (fmw_12.2.1.2_osb_generic.jar)
3. Change to the directory where you downloaded the 12c (12.2.1.2) product distribution.
4. Start the installation program for Oracle Fusion Middleware Infrastructure:
   • (UNIX) JDK_HOME/bin/java -jar fmw_12.2.1.2.0_infrastructure_generic.jar
   • (Windows) JDK_HOME\bin\java -jar fmw_12.2.1.2.0_infrastructure_generic.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 Skip Auto Updates. Options are:

   • 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 gets 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 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 11 to install the Oracle Service Bus distribution.

4.5 Creating the Required 12c Schemas with the RCU

When upgrading from 11g, you must use the Repository Creation Utility (RCU) to create the required 12c schemas before you begin the upgrade.

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.

In Oracle Fusion Middleware 11g releases it was possible to run Oracle Service Bus (OSB) 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 Oracle Service Bus 12c (12.2.1.2).

If you are upgrading from 11g, refer to the Pre-Upgrade Checklist to identify the existing schemas in your domain. The following schemas must exist before you upgrade to 12c:

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

• SOA Infrastructure schema (prefix_SOAINFRA).
• Oracle User Messaging Service schema (prefix_UMS ).

To create the 12c schemas with the RCU:

1. (Optional) If you are upgrading from 11g, and you would like to confirm which schemas are in your existing domain, 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.2), the certified JDK is 1.8.0_101 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_101
   • (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_101
   Add $JAVA_HOME/bin to $PATH.
3. Go to the oracle_common/bin directory:
   • (UNIX) ORACLE_HOME/oracle_common/bin
   • (Windows) 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 4-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 4-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 4-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 plus 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 4-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 page. 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 Service Bus.
   Note: The Common Infrastructure Services Service Table (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 desired 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. You can 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.

4.6 Stopping Servers and Processes

Before running the Upgrade Assistant to upgrade your schemas and configurations, you must shut down all 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 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 in Administering Oracle Fusion Middleware.

To stop your Fusion Middleware environment, follow the steps below.

Step 1: Stop System Components

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

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

• (Windows) 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) 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.

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, that form part of your environment:

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

• (Windows) 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) DOMAIN_HOME/bin/stopWebLogic.sh

• (Windows) 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 having set the nodemanager.properties attribute QuitEnabled to true (the default is false), you can use WLST to connect to Node Manager and shut it down. For more information, see stopNodeManager in WLST Command Reference for WebLogic Server.

4.7 Upgrading an Oracle Service Bus Domain (without SOA)

Although there is no Oracle Service Bus schema, the database schema data for Oracle Service Bus is incorporated in the SOAINFRA schema. Therefore, to upgrade Oracle Service Bus, you must upgrade the SOAINFRA schema.

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

4.7.1 Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.2). 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:

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
  

4.7.1.1 Upgrade Assistant Parameters

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

Table 4-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 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 will create 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.

4.8 Reconfiguring the Domain

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

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.

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:

Once the domain reconfiguration process starts, it is irreversible. 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. For general information about how the domain is reconfigured, see Reconfiguring WebLogic Domains in Upgrading Oracle WebLogic Server.

• Backing Up the Domain
  
• Starting the Reconfiguration Wizard
  
• Reconfiguring the SOA Domain with the Reconfiguration Wizard
  You must first reconfigure your existing domain using the Reconfiguration Wizard before running the Upgrade Assistant.

4.8.1 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.
   For example, copy C:\domains\mydomain to C:\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.

4.8.2 Starting the Reconfiguration Wizard

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) ORACLE_HOME/oracle_common/common/bin
   • (Windows) 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

4.8.3 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.xml, config-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.2) is 1.8.0_101 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: For any existing 11g datasource, the reconfiguration will preserve the existing values. For new datasources where the schema was created for 12c 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.
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.company.com

   Managed Servers >Targeting Server Groups

   Note:

   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.
      
      Description of the illustration GUID-E96F27A4-74D8-4A33-83E3-1829BDBD98B4-default.png
      

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

4.9 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.2). Oracle recommends that you run the Upgrade Assistant as a non-SYSDBA user, completing the upgrade for one domain at a time.
• Upgrading Domain Components Using the Upgrade Assistant
  Navigate through the screens in the Upgrade Assistant to upgrade component configurations in the WebLogic domain.

4.9.1 Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 12c (12.2.1.2). 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:

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
  

4.9.1.1 Upgrade Assistant Parameters

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

Table 4-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 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 will create 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.

4.9.2 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.2), 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 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.

4.10 Performing Post Upgrade Tasks for Oracle Service Bus

After a successful upgrade, you may need to perform one or more of the following tasks. Review your own use case scenarios and existing deployment to determine if the following tasks apply to your environment.

Note:

If you experience any post-upgrade issues with Oracle Service Bus, refer to Troubleshooting Oracle Service Bus for a list of common solutions.

• Configuring Oracle HTTP Server for the WLS_OSB Managed Servers
  
• Importing Domain Configuration Data
  
• Importing Security Configurations
  
• Upgrading Your XQuery Resources
  
• Understanding 12c Split-Joins
  

4.10.1 Configuring Oracle HTTP Server for the WLS_OSB Managed Servers

To enable Oracle HTTP Server to route to Oracle Service Bus console and Oracle Service Bus service, set the WebLogicCluster parameter to the list of nodes in the cluster.

For more information, see Configuring Oracle HTTP Server for the Oracle Service Bus in the Enterprise Deployment Guide for Oracle SOA Suite.

4.10.2 Importing Domain Configuration Data

After the upgrade you will need to import the domain configuration data that you exported in Exporting Services, Projects and Resources when Upgrading Oracle Service Bus.

For more information, see How to Import Resources from a Configuration JAR File in the Console and Executing a Configuration File.

4.10.3 Importing Security Configurations

Use the Oracle WebLogic Administration Console to import the security data that you exported pre-upgrade into the new Oracle Service Bus domain.

For more information, see the "Import data into a security provider" section of the Oracle WebLogic Server Administration Console Online Help.

Note:

You must import the security information for each security provider separately.

4.10.4 Upgrading Your XQuery Resources

Oracle Service Bus supports XQuery 1.0. The older XQuery 2004 is also supported. Any new XQuery resource created in Service Bus uses the XQuery 1.0 version, by default.

If you have upgraded from a pre-12c Service Bus project, all XQuery resources in the project are configured to use the XQuery 2004 version.

For more information on upgrading XQuery Resources, see How to Upgrade Your XQuery Resources to use XQuery 1.0.

4.10.5 Understanding 12c Split-Joins

The Fusion Middleware 11g split-join business service will no longer exist in 12c because in 12c there is a direct way to invoke a split-join component from a pipeline or a proxy service. The upgrade process will automatically change all statically configured invoke references to a split-join business service as follows:

• The flow business service is removed. This means the Timeout property configured for the Flow business service is also removed.

• If the business service is located in the same project as the proxy service that invokes it, then the pipeline associated with that proxy service invokes the split-join directly.

• If the business service is located in a different project from the proxy service that invokes it, then a local proxy service is created to invoke the split-join. The local proxy service is invoked by the original proxy service.

4.11 Troubleshooting Oracle Service Bus Upgrade

If you experience post-upgrade issues with Oracle Service Bus, review the following and apply any relevant solutions.

• Resolving the HTTP 404 Error After OSB Upgrade with OHS as Cluster Frontend Host
  
• Resolving the HTTP 404 Error When Accessing OSB Console
  

4.11.1 Resolving the HTTP 404 Error After OSB Upgrade with OHS as Cluster Frontend Host

If you configure Oracle HTTP Server (OHS) as a cluster domain frontend host, then you must add the following code to the OHS configuration file (ohs.confg):

 <Location /sbconsole>
  SetHandler weblogic-handler
  WebLogicCluster [ADMIN_SERVER_HOST]:[ADMIN.SERVER:PORT]
</Location>
<Location /servicebus>
  SetHandler weblogic-handler
  WebLogicCluster [ADMIN_SERVER_HOST]:[ADMIN.SERVER:PORT]
</Location>

Where ADMIN.SERVER:PORT is the machine name, server name and port number used for the OHS.

mymachine.us.mycompany.com:7001 as shown in this sample code example:

<Location /sbconsole>
  SetHandler weblogic-handler
  WebLogicCluster mymachine.us.mycompany.com:7001
</Location>
<Location /servicebus>
  SetHandler weblogic-handler
  WebLogicCluster mymachine.us.mycompany.com:7001
</Location>

4.11.2 Resolving the HTTP 404 Error When Accessing OSB Console

Prior to 12c, the OSB console was accessed using the following URL: http://[HOST]:[PORT]/sbconsole

In 12c, the OSB Console URL has changed to: http://[HOST]:[PORT]/servicebus.

After the upgrade, if you enter http://[HOST]:[PORT]/sbconsole, it should redirect to http://[HOST]:[PORT]/servicebus.

If the redirect fails, and you receive a HTTP 404 error, try direclty entering the 12c URL: http://[HOST]:[PORT]/servicebus.