Upgrading Oracle Service Bus (without Oracle SOA Suite)

4 Upgrading Oracle Service Bus (without Oracle SOA Suite)

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

Note:

If Oracle Service Bus is part of your existing 12c domain, and you will be upgrading Oracle Service Bus as part of your Oracle SOA Suite upgrade to 14c (14.1.2.0.0), follow the standard upgrade process described in Upgrading SOA Suite and Business Process Management.

Understanding the Oracle Service Bus Standalone Upgrade

Follow this process flow to upgrade an Oracle Service Bus 12c (12.2.1.4.0) deployment that does not include Oracle SOA Suite.

Oracle Service Bus (OSB) can be upgraded to 14c (14.1.2.0.0) 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 existing SOA 12c domain, and you will be upgrading Oracle Service Bus as part of your Oracle SOA Suite upgrade to 14c (14.1.2.0.0), follow the standard upgrade process described in Upgrading SOA Suite and Business Process Management.

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.

Task	Description
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 14c (14.1.2.0.0). After the upgrade, you will import the JAR file to the new 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 14c (14.1.2.0.0) Oracle Fusion Middleware Infrastructure distribution into a new Oracle home.	You must install the 14c (14.1.2.0.0) 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 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.	The `_SOAINFRA` schema must be upgraded to 14c (14.1.2.0.0).
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 post-upgrade tasks, as well as any post-upgrade OSB-specific tasks, that apply to your deployment.

Upgrade Limitations for Oracle Service Bus

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

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). If you configure more than one of these components within a single 14c (14.1.2.0.0) 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.

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.

Exporting Services, Projects and Resources when Upgrading Oracle Service Bus

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

Note:

While WebLogic Server allows forward slashes in JNDI names, such as "myqueues/myqueue", JNDI names with forward slashes interfere with the URI format required by Service Bus, and you cannot use those names. To work around this issue, define a JMS foreign server and reference that foreign server in the URI.

See Configure foreign servers in the Oracle WebLogic Server Administration Console Online Help.

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.

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.

Migrating Oracle Service Bus Resources from Previous Releases

You can manually export resources and services and use them with Oracle Service Bus 14c (14.1.2.0.0):

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

Installing Oracle Service Bus

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 14c (14.1.2.0.0) before upgrading Oracle Service Bus.

Note:

When Infrastructure is required for the upgrade, you must install the Oracle Fusion Middleware Infrastructure distribution first before you install other Fusion Middleware products. If your JDK is not supported, or you do not have a JDK installed, you must download the required Java SE JDK before you begin

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:

Sign in to the target system.
Download the Oracle Fusion Middleware Infrastructure (fmw_14.1.2.0.0_infrastructure.jar) from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
- Fusion Middleware Infrastructure distribution (fmw_14.1.2.0.0_infrastructure.jar)
- Oracle Service Bus (fmw_14.1.2.0.0_osb.jar)
Change to the directory where you downloaded the 14c (14.1.2.0.0) product distribution.
Start the installation program for Oracle Fusion Middleware Infrastructure:
- (UNIX) JDK_HOME/bin/java -jar fmw_14.1.2.0.0_infrastructure_generic.jar
- (Windows) JDK_HOME\bin\java -jar fmw_14.1.2.0.0_infrastructure_generic.jar
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.
On the Welcome screen, review the information to make sure that you have met all the prerequisites. Click Next.
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.
On the Installation Type screen, select the product(s) to install. Product dependencies will be automatically selected and click Next.
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).
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.
On the Installation Progress screen, when the progress bar displays 100%, click Finish to dismiss the installer, or click Next to see a summary.
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.
After you have installed the Infrastructure, repeat steps 3 through 11 to install the Oracle Service Bus distribution.

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, 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 Remote Console. See Starting and Stopping Administration and Managed Servers and Node Manager.

As of release 14c (14.1.2.0.0), the WebLogic Server Administration Console has been removed. For comparable functionality, you should use the WebLogic Remote Console. For more information, see Oracle WebLogic Remote Console.

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

Note:

It is important that you stop the following servers in the correct order.

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

Business Activity Monitoring (BAM) Managed Server
Oracle Service Bus (OSB) Managed Server
Service-Oriented Architecture (SOA) Managed Server
Oracle Web Services Manager (OWSM) Managed Server

Step 3: Stop the Administration Server

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 4: 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 Oracle WebLogic Server.

Upgrading Schemas with the Upgrade Assistant

Note:

For Service Bus this step is only required if there are schemas in the domain that must be upgraded. If you just created the required schemas using the RCU, and there are no other schemas in the domain, you can skip this step and move to the Reconfiguration Wizard step.

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 — if it exists.

Starting the Upgrade Assistant

Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to 14c (14.1.2.0.0).

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. To set the character encoding, run the following:

UNIX operating systems:

export UA_PROPERTIES="-Dfile.encoding=UTF-8 ${UA_PROPERTIES}"

Windows operating systems:

set UA_PROPERTIES=-Dfile.encoding=UTF-8 %UA_PROPERTIES%

Go to the oracle_common/upgrade/bin directory:
- (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
- (Windows) ORACLE_HOME\oracle_common\upgrade\bin
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 4-1 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.

Run the Upgrade Assistant to upgrade any product schemas in the Service Bus domain. The Upgrade Assistant can also detect which schemas are required and will create them for you (if you did not use the RCU to create them in the previous step).

To upgrade product schemas with the Upgrade Assistant:

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.
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 14c (14.1.2.0.0) components. Do not upgrade schemas that are currently being used to support components that are not included in Oracle Fusion Middleware 14c (14.1.2.0.0).
Click Next.
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.
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
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.
On the Schema Credentials screen, specify the database connection details for each schema you are upgrading (the screen name changes based on the schema selected):
- Select the database type from the Database Type drop-down menu.
- Enter the database connection details, and click Connect.
- 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.
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 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 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 this option and click Next. You will have to run the Repository Creation Utility to create the schemas.
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.
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 .
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.
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.

About Reconfiguring the Domain

Run the Reconfiguration Wizard to reconfigure your domain component configurations to 14c (14.1.2.0.0).

Note:

If the source is a clustered environment, run the Reconfiguration Wizard on the primary node only.

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="14.1.2.0.0" 
  location="/u01/app/oracle/product/fmw/iam111130/common/templates/applications/yourcomany.oinav_14.1.2.0.0_template.jar" 
  symbol=""/-->

<!--install-comp-ref name="oracle.idm.oinav" version="14.1.2.0.0" 
  symbol="yourcompany.idm.oinav_14.1.2.0.0_iam141200_ORACLE_HOME" 
  product_home="/u01/app/oracle/product/fmw/iam141200"/-->

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

<!--app-deployment> 
  <name>oinav#14.1.2.0.0</name>
  <target>AdminServer</target>
  <module-type>ear</module-type>

  <source-path>/u01/app/oracle/product/fmw/iam141200/oinav/modules/oinav.ear_14.1.2.0.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.

Backing Up the Domain

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

Create a backup of the domain directory.
Before updating the domain on each remote Managed Server, create a backup copy of the domain directory on each remote machine.
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:

Sign in to the system on which the domain resides.
Open the command shell (on UNIX operating systems) or open a command prompt window (on Windows operating systems).
Go to the oracle_common/common/bin directory:
- (UNIX) NEW_ORACLE_HOME/oracle_common/common/bin
- (Windows) NEW_ORACLE_HOME\oracle_common\commom\bin
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 to configure domain component configurations.

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:

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.
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).
- Scripts and other files that support your Fusion Middleware products are updated.
- The domain upgrade is validated.
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 14c (14.1.2.0.0) is 17.0.12 and later. Click Next.

Note:
You cannot change the Domain Mode at this stage. Your domain will retain its pre-upgrade domain mode. If you want to change the domain to secure mode, then after the upgrade see Changing Domain Mode Post Upgrade.

For a list of JDKs that are supported for a specific platform, see Oracle Fusion Middleware Supported System Configurations.
On the Database Configuration Type screen, select RCU Data to connect to the Server Table (<PREFIX>_STB) schema.
Note: <PREFIX> is the RCU schema prefix of the 12.2.1.4 domain that is being upgraded.

Enter the database connection details using the RCU service table (<PREFIX>_STB) schema credentials and click Get RCU Configuration.

The Reconfiguration Wizard uses this connection to automatically update 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.

If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.
On the JDBC Component Schema screen, verify that the DBMS/Service and the Host name is correct for each component schema and click Next.
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.

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

If you are upgrading a domain that was created in 12c (12.2.1.4.0), 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.

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.

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

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

Upgrading Domain Component Configurations

After reconfiguring the domain, use the Upgrade Assistant again 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 14c (14.1.2.0.0).

To start the Upgrade Assistant:

Note:

UNIX operating systems:

export UA_PROPERTIES="-Dfile.encoding=UTF-8 ${UA_PROPERTIES}"

Windows operating systems:

set UA_PROPERTIES=-Dfile.encoding=UTF-8 %UA_PROPERTIES%

Go to the oracle_common/upgrade/bin directory:
- (UNIX) ORACLE_HOME/oracle_common/upgrade/bin
- (Windows) ORACLE_HOME\oracle_common\upgrade\bin
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 4-2 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 Oracle Analytics server, 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:

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

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

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.

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.

Note:

See Configure foreign servers in the Oracle WebLogic Remote Console Online Help.

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

Importing Security Configurations

Use the Oracle WebLogic Remote 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 Remote Console Online Help.

Note:

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

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

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>