Fusion Middleware Documentation
Advanced Search


Upgrading to the Oracle Fusion Middleware Infrastructure
Close Window

Table of Contents

Show All | Collapse

2 Performing the Infrastructure Upgrade

This chapter provides the end-to-end procedure for upgrading an Oracle Fusion Middleware 11g Application Developer installation to Oracle Fusion Middleware 12c (12.1.3) Infrastructure.

This chapter includes the following sections:

2.1 Backing Up Your Existing Oracle Fusion Middleware 11g Environment

Before you upgrade Oracle Fusion Middleware 11g Application Developer installation to Oracle Fusion Middleware 12.1.3 Infrastructure, you must back up your existing 11g environment. If the upgrade fails for any reason, you will have to restart the upgrade process from the source backup.

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

Caution:

After you upgrade, any custom changes that you made to your setDomainEnv script will be lost. Make sure that you have a backup copy of the script before you upgrade.

For more information on retaining your settings after an upgrade, see Maintaining Your Custom setDomainEnv Settings (Optional).

2.2 Upgrading the Oracle Database

The database that will be used to host your new 12c environment must be supported. It is important that you understand the Oracle Database requirements for Oracle Fusion Middleware 12c (12.1.3) Infrastructure, and, if necessary, upgrade the Oracle Fusion Middleware Database before you begin the Fusion Middleware upgrade.

For more information about upgrading and preparing your Oracle Database for 12c, see "Upgrading and Preparing Your Oracle Databases for 12c (12.1.3)" in the Oracle Fusion Middleware Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.

2.3 Maintaining Your Custom setDomainEnv Settings (Optional)

Every domain includes dynamically generated domain and server startup scripts, such as setDomainEnv. Oracle recommends that you do not modify these startup scripts, as any changes you make to them will be overwritten during subsequent domain upgrade operations.

Caution:

Changes made to the setDomainEnv script - or any other startup script - before an upgrade will be overwritten by new, regenerated scripts during the domain reconfiguration process. Consider creating a separate file to store your customized domain settings before you upgrade.

If you want to customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverrides.cmd (Windows) or setUserOverrides.sh (UNIX) and configure it to, for example, add custom libraries to the WebLogic Server classpath, specify additional java command line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when using the pack and unpack commands.

During server startup, if this file exists, it is included in the startup sequence and any overrides it defines take effect. The file must be stored in the domain_home/bin directory.

For more information on creating the setUserOverrides file to maintain your customized domain wide parameters after an upgrade, see "Customizing Domain Wide Server Parameters".

Note:

If you are unable to create the setUserOverrides script before an upgrade, you will need to reapply your settings as described in Section 4.4, "Reapplying Customizations to setDomainEnv".

2.4 Reassociating a File-Based Security Store Before Upgrade

If you are using a file-based security store in your existing 11g environment, you must perform the following tasks before you begin the upgrade process.

Refer to the following tasks for more information:

Task 1   Creating 11g OPSS and IAU Schemas

Create new 11g Oracle Platform Security Services (OPSS) schema in a supported database using the 11g Repository Creation Utility. Once you have successfully reassociated OPSS to database-based store using OPSS during upgrade, you can create the 12.1.3 Audit (IAU) schema using 12.1.3 RCU.

For more information about creating 11g schemas, see "Obtaining and Running Repository Creation Utility" in the Oracle Fusion Middleware Repository Creation Utility User's Guide for 11g Release 1 (11.1.1.7.0).

You might be required to create the IAU 12c (12.1.3) schema, depending on whether or not you are using an Audit Data Store in 11g and the type of Audit Data Store you are using. For more information, see Section 1.1.2.2, "Infrastructure 12c Requires Specific Database Schemas".

Task 2   Reassociating the 11g Security Store with the Database-Based Security Store and OPSS Schema

If you are using a file-based security store in your 11g environment, then reassociate the file-based store with the database-based repository and OPSS schema.

If the Create New Domain box is not checked, after the reassociate the WebLogic server will not start.

Do the following to re-associate 11g OPSS and IAU (Audit) Schema to make it database based before it can be upgraded:

  1. Configure a JDBC Data Source in the Console:

    • Login to the Console and navigate to Services and then DataSources.

    • Select New, then Generic data source from the dropdown menu.

    • Give the new data source a name.

    • Enter the JNDI Name.

      Note: This name is used when configuring a DB-Based store in the file jps-config.xml, and the value used in the re-associate command. An example value for OPSS is jdbc/opssDataSource and for IAU is jdbc/AuditDB.

    • Select the appropriate DB type in the DataBase Type dropdown menu.

    • In the Database Driver pull-down, select Oracle's Driver (Thin) for Instance connections; Versions: 9.0.1 and later (this is a Non-XA JDBC driver).

    • Make sure that Supports Global Transactions is deselected.

    • In the area Connection Properties, enter data for Database Name, Host Name, Port, Database User Name, and Password. Verify and test the settings.

    • In the Targets section, this Data Source must be targeted to all servers in the domain. Click Finish.

  2. Re-associate data file:

    1. Re-associate data file with OPSS for the OPSS schema:

      $cd $11g_MW_Home/oracle_common/common/bin
      $./wlst.sh
      connect()
      wls:/jrf_domain/serverConfig> reassociateSecurityStore(domain="jpsconfig",    servertype="DB_ORACLE", jpsroot="cn=jpsroot", datasourcename="jdbc/opssDataSource")
      
    2. Re-associate data file with IAU for the IAU schema:

      $cd $11g_MW_Home/oracle_common/common/bin
      $./wlst.sh
      connect()
      wls:/base_domain/serverConfig> setAuditRepository(switchToDB="true",dataSourceName="jdbc/AuditDB")
      
  3. Restart all servers.

  4. Validate re-association via Enterprise Manager Fusion Middleware Control.

    1. Validating OPSS Re-Association via Enterprise Manager Fusion Middleware Control:

      -Log in to Enterprise Manager Fusion Middleware Control and navigate to Domain > Security > Security Provider Configuration.

      - Confirm that the configuration no longer shows File as the Provider Type.

      - The table should now display the entry Oracle Database in the above Provider Type field.

    2. Validate Audit DB Configuration via Enterprise Manager Fusion Middleware Control:

      - Log in to Enterprise Manager Fusion Middleware Control and navigate to Domain > Security > Security Provider Configuration.

      - Click the Configure under the Audit Service section of the screen to access the OHS11GPS61STdomain screen.

      - Validate that the JNDI DataSource name is correct and is as previously specified, and confirm the Database connection is specified in the URL field.

      - If the DB Based Audit Data source is not specified, then click the Magnifying Glass Icon next to the Data Source JNDI Name, and select the Audit Data Source previous created.

      - Confirm the details in this screen to match what was previously specified in the prior steps above, and then click Apply.

Note:

The database user that will access the datasource and database store configuration should be the same as the OPSS schema owner.

IAU Schema upgrade should be optional. In 11g by default Audit Store is not configured. If Audit Store is not configured, we should be able to skip the audit store association.

2.5 Using No-Auth SSL Mode in OID Security Store

If you are upgrading to 12c and using OID for the security policy store with WLS, then you may need to modify the default SSL mode. In Oracle Internet Directory 11g, SSL interoperability mode is enabled by default. But Oracle Internet Directory is fully compliant with the JDK's SSL, provided SSL interoperability mode is disabled.

The default use of No-Auth SSL mode in Oracle Internet Directory (OID) is discouraged for production environments due to the susceptibility to Man-in-the-Middle (MITM) attacks.

However, if No-Auth SSL is required, and WebLogic Server is the client, the following system properties must be applied to the weblogic.properties file before you upgrade:

  • -Dweblogic.security.SSL.AllowAnonymousCipher=true

  • -Dweblogic.security.SSL.ignoreHostnameVerification=true

Note:

Setting these properties will consequently make WLS susceptible to MITM attacks, since anonymous cipher suites will be enabled, and client connections will be made without Hostname Verification checking.

ORACLE STRONGLY RECOMMENDS the use of either server or client/server SSL authentication when using OID with WLS 12c.

2.6 Removing the Server Instance Scope from OWSM Policy Sets

Using the Server Instance scope in policy sets was not recommended in 11g (11.1.1.7.0) and it is not supported in 12c. If, however, you have policy sets that use the Server scope, they will be disabled during the upgrade to 12c. Therefore, before you upgrade to 12c, you must remove the server instance scope from all 11g policy sets.

For instructions, see "Editing a Policy Set" in Security and Administrator's Guide for Web Services in the Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0) documentation library.

2.7 Cloning Predefined Documents and Migrating OWSM Policy Attachments

When upgrading, it is important to note that any predefined documents that have not been customized for your environment are replaced with read-only versions, and new, predefined, read-only documents are added. Note, however, that any existing predefined documents that have been customized, as well as any user-created custom policies in the repository, will not be overwritten.

To ensure that you always get all of the latest policies, Oracle recommends that you clone any predefined documents that you have modified and migrate any policy attachments. For details, see "Upgrading the OWSM Repository" in Securing Web Services and Managing Policies with Oracle Web Services Manager.

2.8 Installing Oracle Fusion Middleware Infrastructure 12.1.3 on APPHOST

Install 12.1.3 Infrastructure in a new Oracle home on the same host as that of 11g.

Note:

Do not use the Configuration Wizard to configure Oracle Fusion Middleware Infrastructure 12.1.3.

Follow the instructions described in Table 2-1 to install Oracle Fusion Middleware Infrastructure 12.1.3.

Table 2-1 Oracle Fusion Middleware Infrastructure Installation Roadmap

Task Description More Information

Prepare your system for the 12.1.3 install.

Before you install Infrastructure 12.1.3, verify that the minimum system and network requirements are met.

"Roadmap for Verifying Your System Environment" in Oracle Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure.

Obtain the Infrastructure distribution.

Obtain the Oracle Fusion Middleware Infrastructure distribution (wls_jrf_generic.jar).

"Understanding and Obtaining the Oracle Fusion Middleware Infrastructure Distribution" in Oracle Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure.

Start the Infrastructure 12.1.3 installer.

Start the Infrastructure installer from the location where you downloaded it.

"Starting the Installation Program" in Oracle Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure.

Navigate the installer screens.

Use the installer to install Infrastructure 12.1.3.

"Navigating the Installation Screens" in Oracle Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure.


2.9 Installing Oracle HTTP Server 12.1.3 on APPHOST

If your 11g domain includes Oracle HTTP Server instances that are associated with the domain, you must install Oracle HTTP Server 12.1.3 on the following machines:

  • On machines where 11g Oracle HTTP Server instances are running

  • On the machine where Administration Server is running

For more information about installing Oracle HTTP Server 12.1.3, see "Installing the Oracle HTTP Server Software" in the Oracle Fusion Middleware Oracle Fusion Middleware Installing and Configuring Oracle HTTP Server.

Note:

Do not configure Oracle HTTP Server 12.1.3.

2.10 Stopping Servers and Processes

Before running Upgrade Assistant, shut down all Oracle Fusion Middleware Managed Servers, Administration Servers, and system components (such as OHS) that may be using the schemas or configurations you want to update. Failure to do so may result in an incomplete or failed upgrade.

If you are running Node Manager, you should also stop Node Manager. You can do this by closing the console window in which Node Manager is running, or by using the stopNodeManager WLST command.

Instructions for stopping an Oracle Fusion Middleware environment are provided in "Stopping an Oracle Fusion Middleware Environment" in Oracle Fusion Middleware Administering Oracle Fusion Middleware.

2.11 Using the Schema Version Registry to Identify Existing 11g Schemas

The Upgrade Assistant identifies schemas for which an upgrade is available. You can upgrade multiple schemas in a single session of running the Upgrade Assistant.

When the schemas are created in your database, RCU creates and maintains a table called schema_version_registry. This table contains schema information such as version number, component name and ID, date of creation and modification, and custom prefix.

To determine which of your 11g or 12.1.2 schemas can be upgraded to 12.1.3.0.0, see "Identifying Schemas that Can be Upgraded with the Upgrade Assistant" in Oracle Fusion Middleware Upgrading with the Upgrade Assistant.

2.12 Creating the Required 12.1.3 Schemas Before You Upgrade

Before you upgrade, you must install one or more schemas in a supported database:

2.12.1 Determining Which Schemas to Create

Consider the following scenarios:

  • If you did not use a database in 11g, then you must install and configure a supported database, and you must create one or more of the database schemas as described in Section 1.1.2.2, "Infrastructure 12c Requires Specific Database Schemas".

  • If you were already using a database to host the schemas for your Application Developer 11g domain, then use the schema version registry to list the Oracle Fusion Middleware 11g schemas that are already available in your database, as described in Section 2.11.

    Do not create any of the schemas listed in the Schema Version Registry; instead, you can use the Oracle Fusion Middleware Upgrade Assistant later in the upgrade process to upgrade the 11g schemas to 12.1.3.

    Note, however, that you must still create the required schemas, as described in Section 1.1.2.2, "Infrastructure 12c Requires Specific Database Schemas".

Note:

As of release 12c (12.1.2.0), the Service Table (_STB) schema is required for all Infrastructure installations. The Service Table schema must be upgraded each time the infrastructure is upgraded. You cannot use an older version schema with a new Infrastructure installation.

2.12.2 Creating the Required Schemas with the Repository Creation Utility

Complete the following steps to create necessary schemas:

Note:

When you create the new 12.1.3 schemas, be sure to use a unique schema prefix. This prefix enables you to differentiate between any schemas previously installed or upgraded in the database, as opposed to those that you have created specifically for Oracle Fusion Middleware 12.1.3.

  1. Starting the Repository Creation Utility (RCU) by doing the following:

    1. If you have not done so already, set the JAVA_HOME variable and add JAVA_HOME/bin to $PATH.

    2. Navigate to the ORACLE_HOME/oracle_common/bin directory on your system.

    3. Start RCU:

      (UNIX) ./rcu

      (Windows) .\rcu.bat

  2. Navigate the RCU screens to create required schemas for Infrastructure upgrade.

    For more information, see "Navigating the RCU Screens to Create the Schemas" in Oracle Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure.

Note:

Edition-based redefinition (EBR) enables you to support multiple versions of a database schema on the same database and at the same time. For more information on creating an edition on the server for redefinition, see "Creating an Edition on the Server for Editions-Based Redefinition" in Oracle Fusion Middleware Planning an Upgrade of Oracle Fusion Middleware.

2.13 Upgrading 11g Schemas Using the Upgrade Assistant

Follow the instructions in this section to upgrade Infrastructure schemas using the Upgrade Assistant.

Task 1   Determine Which Schemas to Upgrade

Before you start the Oracle Fusion Middleware Upgrade Assistant, view the list of existing 11g schemas in the schema version registry using the instructions in "Identifying Schemas that Can be Upgraded with the Upgrade Assistant" in Oracle Fusion Middleware Upgrading with the Upgrade Assistant.

The schemas listed in the Oracle Fusion Middleware Upgrading with the Upgrade Assistant guide are the component schemas that can be used to support your 12.1.3 components. From this list, identify the schemas that are used by the domain that is being upgraded.

Caution:

If your domain is using schemas that are not supported by this upgrade, do not attempt to upgrade the domain. Review the Oracle Fusion Middleware Understanding Interoperability and Compatibility guide for more information on supported domain configurations.

Task 2   Start the Upgrade Assistant

Complete the following steps to start the Upgrade Assistant:

  1. Change directory to ORACLE_HOME/oracle_common/upgrade/bin (on Unix operating systems) or ORACLE_HOME\oracle_common\upgrade\bin (on Windows operating systems).

  2. Enter the following command to start the Upgrade Assistant.

    (UNIX) ./ua

    (Windows) ua.bat

Task 3   Upgrade the Schemas

The Upgrade Assistant displays a sequence of screens listed in Table 2-2 when upgrading schemas. Perform the respective action(s) for each of the screens.

Table 2-2 Upgrade Assistant Screens: Upgrading Schemas

Screen Description and Action Required

Welcome

This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks.

Schemas

Select Schemas.

Available Components

This screen provides a list of installed Oracle Fusion Middleware components that have schemas that can be upgraded. When you select a component, the schemas and any dependencies are automatically selected.

Domain Directory

This screen appears if you selected Oracle Platform Security Services or Oracle Audit Services on the Available Components screen.

Enter the absolute path to the existing 11g WebLogic domain directory, or click Browse to navigate to and select the 11g domain directory you are upgrading.

Prerequisites

Check if the prerequisites for schema upgrade are met.

Select Schemas

Use this screen to enter database connection details for each of the schemas you are upgrading.

  1. Select a the database type from the Database Type drop-down menu.

  2. Enter the database connection details, and click Connect. Some of the schemas might need system DBA privileges to upgrade.

  3. Select the schema you want to upgrade from the Schema User Name drop-down menu, and then enter the password for the schema. Make sure that you select the correct schema from the list. The default schema shown may not be the one you intend to upgrade.

  4. Click Next.

For more information on which schemas need to be upgraded, see Section 1.1.2.2, "Infrastructure 12c Requires Specific Database Schemas,".

Notes:

  • The title of Select Schemas screen varies, depending upon the schemas you are upgrading. For example, if you are upgrading the MDS schema, the screen title appears as "MDS Schema".

  • When upgrading the WLS schema, you cannot connect to the database first to obtain the list of available schemas; instead, you must enter the WLS schema name in the Schema User Name field, and then click Next.

  • For information on the fields required to connect to the database, click Help, or refer to "Select Schemas" in Oracle Fusion Middleware Upgrading with the Upgrade Assistant.

Examine

Review the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade.

Upgrade Summary

Review the summary of the options that you have selected for schema upgrade.

Click Upgrade to upgrade the schemas, or click Back if you wish to change the configurations.

Upgrade Progress

Review the status of the upgrade process.

The Upgrade Progress status bar represents the number of upgrade processes that have been completed. It is NOT meant to identify time remaining.

Allow the Upgrade Assistant enough time to perform the upgrade. Do not cancel the upgrade operation unless absolutely necessary.

Click Next when the upgrade is complete.

Upgrade Success

Click Close if the Upgrade was successful.

If the upgrade failed or if you canceled the upgrade before it completed successfully, you should review the log files, restore the backed up environment, and restart the Upgrade Assistant.


Task 4   Verify the Schema Upgrade

Use the following SQL command to verify that the schema version in schema_version_registry has been properly updated.

SELECT comp_id, owner, version, status, upgraded FROM schema_version_registry where version like '12.1.3.%';

Check that the number in the VERSION column matches the latest version number for that schema. See Table 1-1, "Schemas That Require an Upgrade" in Upgrading with the Upgrade Assistant to verify that the updated version number is correct for your schema(s).

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

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

Task 5   Check for Invalid Database Objects

If you are using an Oracle database, you should recompile database objects after running the Upgrade Assistant by connecting to the database as SYS and running the following from SQL*Plus:

Issue the following query to ensure there are no longer any invalid database objects:

SELECT owner, object_name FROM all_objects WHERE status='INVALID';

None of the database objects for the upgraded schema should be invalid at this point. If there are any, run the utlrp.sql command again and check again. If the problem persists, run the following script and file a service request.

SQL>@?/rdbms/admin/utlrp.sql

This will compile the database objects that were upgraded by Upgrade Assistant.

2.14 Reconfiguring the Domain Using the Reconfiguration Wizard

Follow the instructions in this section to reconfigure the existing 11g domain using the reconfiguration wizard.

Task 1   Starting the Reconfiguration Wizard

Start the Reconfiguration Wizard in graphical mode by doing the following:

  1. Log in to the system on which the domain resides.

  2. Open command shell (on UNIX operating systems) or open 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 name of the default database edition name.

  4. Go to the following directory:

    (UNIX) ORACLE_HOME/oracle_common/common/bin

    (Windows) ORACLE_HOME\oracle_common\common\bin

    where ORACLE_HOME is your Oracle home directory.

  5. Execute the following command:

    (UNIX) ./reconfig.sh -log=log_file
    (Windows) reconfig.cmd -log=log_file
    

    Replace log_file with 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.

    Notes:

    When you run the reconfig.cmd or reconfig.sh command, the following error message might be displayed 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

Task 2   Reconfiguring the Domain

The Reconfiguration Wizard displays a sequence of screens such as those listed in Table 2-3.

Depending on the options you select, you may or may not see all of the screens shown in Table 2-3. In some advanced configurations you will see additional screens. Use the online help for more information on advanced configurations.

Review the full reconfiguration process in "Reconfiguring WebLogic Domains" in Upgrading Oracle WebLogic Server.

Table 2-3 Reconfiguration Wizard Screens

Screen Description and Action Required

Select Domain

Enter the absolute path to the existing 11g domain directory, or click Browse to navigate to and select the domain directory.

Reconfiguration Setup Progress

Shows the progress of the application of reconfiguration templates.

Domain Mode and JDK

Domain mode cannot be changed.

Select the JDK to use in the domain or click Browse to navigate to the JDK you want to use.

Note that Oracle Fusion Middleware 12c requires Java SE 7. For more information, see "Verifying Certification and System Requirements" in Oracle Fusion Middleware Planning an Installation of Oracle Fusion Middleware.

JDBC Data Sources

This screen is displayed if you created custom data sources for a database-based OPSS security store or Audit Data store in 11g.

Use this screen to review the JDBC data sources defined in your domain source.

For information about the fields on this page, click Help, or refer to "JDBC Data Sources" in Upgrading Oracle WebLogic Server.

JDBC Data Sources Test

Test the data source connections you configured on the JDBC Data Sources screen.

For information about the fields on this page, click Help, or refer to "JDBC Data Sources Test" in Upgrading Oracle WebLogic Server.

Database Configuration Type

If you provided the data source connection details in the previous screen, the database connection details will be automatically entered.

If the information was not provided on this screen, select RCU Data and provide the database credentials to retrieve the schema information for all 12.1.2 schemas that are included in the domain. If you select this option, the fields on this screen are activated. Fill in each field, using the connection information that you specified for the STB component in the Repository Creation Utility (RCU).

When you have provided the connection information, click Get RCU Configuration to retrieve the schema information.

For more information, click Help, or refer to "Database Configuration Type" in Upgrading Oracle WebLogic Server.

JDBC Component Schema

By default, the schema information will be displayed if you selected Get RCU Data on the previous screen and the schema owner is the same for all schemas.

If you need to make changes to the data source settings for any of the schemas listed on the screen, select the check box adjacent to each schema name. The changes you make in the fields at the top of the screen will update the schema (or schemas) you have selected below. Make sure that you select only those schemas you want to modify.

Notes:

  • You must specify the 11g schema details for those schemas that you upgraded in Section 2.13. For the others, specify the 12.1.3 schema details.

  • For information about the fields on this page, click Help, or refer to "JDBC Component Schema" in Upgrading Oracle WebLogic Server.

JDBC Component Schema Test

Test the configurations that you specified for the data sources in the previous screen. Select the check boxes adjacent to the names of the schemas to test, and click Test Selected Connections.

The result of the test is indicated in the Status column. Click Next when the test is successful for all the schemas.

Node Manager

This screen is displayed only if the domain you are reconfiguring is currently using a Per Domain Default Location Node Manager.

Select Migrate Existing Configuration and provide the location of the per domain default location.

Enable Apply Oracle Recommended Defaults.

Provide Node Manager Credentials. This is a new User that is being created to administer the Node Manager. The password will be required during start-up, for any components now handled by the Node Manager (including the OHS).

Note: When upgrading a domain and changing from a per-host Node Manager configuration to a per-domain Node Manager configuration, if you are using custom scripts to start and stop the WebLogic Server environment, you must manually update the scripts to change the Node Manager home location to the new domain-based location.

For more information on configuring the Node Manager, see "Default Node Manager Configuration" in Administering Node Manager for Oracle WebLogic Server.

Advanced Configuration

Select all categories (if any) 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. If you do not select any items on this screen, the Configuration Summary screen is displayed next.

The screens that appear next will vary depending on which categories you select. Use the Online Help for information on each screen.

NOTE: If Node Manager is available and you do not select it, you must manually configure Node Manager as described in "Completing the Node Manager Configuration" in Upgrading Oracle WebLogic Server.

The Node Manager advanced option is available only if you are reconfiguring a domain that is currently using a per-host Node Manager configuration. It enables you to switch to a per-domain Node Manager or continue using the existing per-host Node Manager.

Configuration Summary

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.

If you need to change the configuration, click Back to return to the appropriate screen.

Click Reconfig to reconfigure the domain, or click Back if you wish to change the configurations.

Reconfiguration Progress

Review the reconfiguration progress. Click Next when the process is complete.

Reconfiguration Success

Review the final status of the reconfiguration process. Click Finish to exit the Reconfiguration Wizard.


2.15 Upgrading the Domain Component Configurations Using the Upgrade Assistant

Follow the instructions in this section to upgrade any additional domain component configurations, such as OWSM policy metadata structure and adapter configurations, using the Upgrade Assistant.

Task 1   Starting the Upgrade Assistant

Start the Upgrade Assistant on the host where Administration Server is running, by doing the following:

  1. Change directory to ORACLE_HOME/oracle_common/upgrade/bin (on Unix operating systems) or ORACLE_HOME\oracle_common\upgrade\bin (on Windows operating systems).

  2. Enter the following command to start the Upgrade Assistant.

    (UNIX) ./ua

    (Windows) .\ua.bat

Task 2   Upgrading Any Component Configurations

The Upgrade Assistant displays a sequence of screens listed in Table 2-4 when upgrading WebLogic Component Configurations. Perform the respective action(s) for each of the screens.

Table 2-4 Upgrade Assistant Screens: Upgrading WebLogic Component Configurations

Screen Description and Action Required

Welcome

This screen provides an overview of the Upgrade Assistant and some information about important pre-upgrade tasks.

Click Next to continue.

WebLogic Components

Select WebLogic Component Configurations.

Select the WebLogic Component Configurations option to upgrade component configurations for a managed WebLogic Server domain. You must enter the domain directory for the domain that you are upgrading now.

Click Next.

Component List

This screen provides a list of components that will be included in the domain component configuration upgrade.

Prerequisites

Check if the prerequisites for component configurations upgrade are met.

UMS Configuration

Use this screen to specify the login credentials of the remote managed servers hosting your UMS 11g configuration files. The Upgrade Assistant automatically copies remote configuration files if all necessary prerequisites are met and the required login information is provided.

NOTE: If the UA is unable to locate the managed servers or the configuration files, you will have to manually copy the files and then restart the Upgrade Assistant. For more information, see Section 2.16.3, "Upgrade Assistant: Copying UMS Configuration Files".

Examine

Review the status of the Upgrade Assistant as it examines each component, verifying that the component is ready for upgrade.

Upgrade Summary

Review the summary of the options that you have selected for schema upgrade.

Click Upgrade to upgrade the schemas, or click Back if you wish to change the configurations.

Upgrade Progress

Review the status of the upgrade process.

Click Next when the upgrade is complete.

Upgrade Success

Click Close if the Upgrade was successful.

If the upgrade failed or if you canceled the upgrade before it completed successfully, you should review the log files, restore the backed up environment, and restart the Upgrade Assistant.


2.16 Troubleshooting the Infrastructure Upgrade

If you an encounter an error during the Infrastructure upgrade, refer to the following sections:.

Caution:

As with most Fusion Middleware errors, errors that are detected in the Examine phase can be fixed and the Upgrade Assistant can continue to run. Errors that occur during the Upgrade phase, however, must be corrected using the restored backup files and the upgrade process must be started from the beginning. Do not attempt to rerun an upgrade that errors during the Upgrade phase. The environment should be considered unstable and will need to be restored to its pre-upgrade state.

For more information, see "General Troubleshooting Guidelines" in Oracle Fusion Middleware Upgrading with the Upgrade Assistant.

2.16.1 Reconfiguration Wizard: WebLogic Server Domain Upgrade Process

If an error occurs while reconfiguring your domain, refer to the "Important Notes About the Domain Upgrade Process" in Upgrading Oracle WebLogic Server.

2.16.2 Upgrade Assistant: Authentication Failure - JSch Exception: Auth Fail

When Running the Upgrade Assistant to upgrade Weblogic Component Configurations, if you provide incorrect login credentials for a UMS server, you will see the following exception in UA log files:

[upgrade.UCSUMS.UCSUMS_CONFIGURATION_PLUGIN] [tid: 110] [ecid:
88ab893d-a523-4a83-b5a6-f7b1cf8cb029-00000001,0] [[
com.jcraft.jsch.JSchException: Auth fail

The resolution to this error depends on when the error occurred:

If this error occurred during the Examine phase (before Upgrade phase): Verify that the username and password you entered are valid for all managed servers and directories and that the username provided has privileges for ssh. Once you have corrected the error, retry the connection.

If this error occurred during the Upgrade phase, your upgrade operation did not succeed and you will need to restore your files from backup and start the upgrade again. Make sure that you use the correct server login credentials when prompted.

Caution:

Errors that occur during the Upgrade phase are non-reentrant, meaning you cannot simply correct the error and continue through the upgrade. Once you click Upgrade, if an error occurs then the environment must be restored from backup before you start the upgrade process again.

2.16.3 Upgrade Assistant: Copying UMS Configuration Files

If the Upgrade Assistant fails to automatically copy the UMS configuration files, you must stop the upgrade and manually copy the configuration files before attempting to upgrade UMS.

Note:

This process is required only if the Upgrade Assistant fails to automatically copy the configuration files or if you prefer to copy the configuration files manually.

This section describes the location of the User Messaging Service (UMS) configuration files that are copied from the remote managed server nodes to the Admin server while upgrading UMS from 11g to 12c. Note that the Upgrade Assistant can automatically copy the remote configuration files, if all necessary prerequisites are met and the required login information is provided. For more information about using Upgrade Assistant to copy configuration files, see Oracle Fusion Middleware Upgrading with the Upgrade Assistant.

However, if the Upgrade Assistant cannot locate your files, then you must copy the configuration files from the remote managed server to the same location on the Admin server running the upgrade. The configuration files that must be copied include the UMS server configuration files (appconfig.xml), driver configuration files (driverconfig.xml), and the user preferences files (businessterms.xml). These files are located in the /applications folder for each managed server, as shown in Table 2-5.

After manually copying the configuration files from the managed server to the Admin server, you must start the Upgrade Assistant again using the procedures from Section 2.15, "Upgrading the Domain Component Configurations Using the Upgrade Assistant"

Table 2-5 Configuration File locations

Configuration file Location

UMS Server (appconfig.xml)

<DOMAIN_HOME>/config/fmwconfig/servers/<MANAGED_SERVER_NAME>/applications/usermessagingserver/configuration/appconfig.xml

Driver Configuration (driverconfig.xml)

<DOMAIN_HOME>/config/fmwconfig/servers/<MANAGED_SERVER_NAME>/applications/usermessagingdriver-<DRIVER_NAME>/configuration/driverconfig.xml

User Preferences (businessterms.xml)

<DOMAIN_HOME>/config/fmwconfig/servers/<MANAGED_SERVER_NAME>/applications/usermessagingserver/configuration/businessterms.xml


Note:

If there are multiple drivers deployed in a domain, then you must ensure that configuration files for all drivers are copied. This can be achieved by replacing the <DRIVER_NAME> with as many drivers deployed in that domain.

2.17 Performing the Post-Upgrade Tasks

After you upgrade Oracle Fusion Middleware 11g Application Developer to Oracle Fusion Middleware 12.1.3 Infrastructure, you must complete the post-upgrade tasks described in Chapter 4, "Tasks to Perform After Upgrade".