You can upgrade Oracle Traffic Director from Oracle Fusion Middleware Release 11g to 12c (12.2.1.2) .
Complete the steps in the following topics to perform the upgrade:
Review the roadmap for an overview of the upgrade process for Oracle Traffic Director.
The steps you take to upgrade your existing domain will vary depending on how your domain is configured and which components are being upgraded. Follow only those steps that are applicable to your deployment.
Table 3-1 Tasks for Upgrading Oracle Traffic Director
| Task | Description |
|---|---|
|
Required If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks. |
|
|
Required Download and install the Oracle Fusion Middleware Infrastructure and Oracle Traffic Director 12c (12.2.1.2) distributions into a new Oracle home. |
See |
|
Required Shut down the 11g environment (stop all Administration and Managed Servers). |
WARNING: Failure to shut down your servers during an upgrade may lead to data corruption. |
|
Required Start the Upgrade Assistant (again) to upgrade domain component configurations. |
The Upgrade Assistant is used to update the domain’s component configurations. For 11g to 12c upgrades see Upgrading the Component Configurations |
|
Required Start the Upgrade Assistant (again) to upgrade standalone system component configurations. |
The Upgrade Assistant updates the standalone agent’s component configurations. |
|
Required Complete and verify the upgrade. |
Perform the required post-upgrade configuration tasks (if needed), including starting the new Administration and Managed Servers and node manager to ensure there are no issues. Oracle recommends that you ensure all of the upgraded components are working as expected before deleting your backups. |
This section describes the steps to prepare the upgrade Oracle Traffic Director to 12c (12.2.1.2)
Oracle Fusion Middleware Upgrade Assistant supports an out-of-place upgrade to 12c (12.2.1.2.0) for the following Oracle Traffic Director 11g releases:
Oracle Traffic Director FMW 11g Release 1 (11.1.1.7.0)
Oracle Traffic Director FMW 11g Release 1 (11.1.1.9.0)
Before you upgrade to Oracle Traffic Director 12c (12.2.1.2), follow these steps:
If Oracle Traffic Director 11g and 12c installations are on different hosts/machines (for example 11g on OEL5 and 12c on OEL6), then the user has to do one of the following:
In the Upgrade Assistant, when you select '11g source' as the source version for the upgrade, specify the remote directory path for Oracle Traffic Director 11g instances. See Section 4.1.3, "Upgrading the Component Configurations".
Remotely copy ORACLE_HOME and INSTANCE_HOME directories from 11g host to 12c preserving the same path as it was on 11g host.
For example, on 12c host:
# scp -r <11g host>:/otd/oracle_home /otd/oracle_home # scp -r <11g host>:/otd/oracle_home /otd/oracle_home
Mount 11g ORACLE_HOME and INSTANCE_HOME paths on 12c host preserving the same path as it was on 11g host.
For example, on 12c host:
# mount <11g host>:/otd/oracle_home on /otd/oracle_home # mount <11g host>:/otd/instance_home on /otd/instance_home
Oracle Traffic Director 11g INSTANCE_HOME must have read permissions for the user running Upgrade Assistant to access the configurations within 11g Administration Server config-store.
Upgrading across different platforms is not supported. For example, you cannot upgrade Oracle Traffic Director from a Linux to Solaris environment.
Before beginning your upgrade, download Oracle Fusion Middleware Infrastructure and Oracle Traffic Director 12c (12.2.1.2) distributions on the target system and install them using Oracle Universal Installer.
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 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.
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.
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.
oracle_common/upgrade/bin directory:
ORACLE_HOME/oracle_common/upgrade/binORACLE_HOME\oracle_common\upgrade\binFor information about other parameters that you can specify on the command line, such as logging parameters, see:
When you start the Upgrade Assistant from the command-line, you can specify additional parameters.
Table 3-2 Upgrade Assistant Command Line Parameters
| Parameter | Required or Optional | Description |
|---|---|---|
|
|
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 |
|
|
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. |
|
|
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). |
|
|
Optional |
Performs the examine phase but does not perform an actual upgrade. Do not specify this parameter if you have specified the |
|
|
Optional |
Sets the logging level, specifying one of the following attributes:
The default logging level is Consider setting the |
|
|
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) (Windows) |
|
|
Optional |
Displays all of the command-line options. |
When you run the Upgrade Assistant to upgrade the Oracle Traffic Director component configurations, consider the following points based on the Oracle Traffic Director domain.
Collocated domain upgrade:
Specify the starting point for an upgrade. The options are 12c source and 11g source.
Specify the 11g Oracle Traffic Director Instance Home where instances are located.
For each Oracle Traffic Director configuration, specify the NSS DB password for internal token, if one exists.
You can run the Upgrade Assistant in the following ways:
Launch the upgrade assistance and follow the steps below:
The Welcome screen displays list of tasks to be performed. Click Next to continue.
In the All Configurations screen, select All Configurations Used By a Domain and provide the correct domain path in the Domain Directory field.
Click Next to continue.
In the Component List screen, click Next to continue.
In the Prerequisites screen, select all the check boxes, then click Next to continue.
In the OTD 11g Instance Home screen, provide the path to 11g OTD Instance Home, then click Next to continue.
The Examine screen displays the list of tasks done. Click Next to continue.
The Upgrade Summary screen is displayed.
Note:
Click the Save Response File.. button to create a response file, which can be used as an input for Command Line upgrade.
Click Next to continue.
In the Upgrade Progress screen, click Next to continue.
In the Upgrade Success screen, click Close to complete the upgrade.
To upgrade using silent mode, run the upgrade UA command with the response file option.
This response file is generated using the upgrade wizard. Click the Save Response File button in the Upgrade Summary screen.
After successful upgrade, a success message is displayed on the console. Log file is available under the following path:
<FMW_HOME>\oracle_common\upgrade\logs
Command Line for silent upgrade (on unix):
Syntax
<MW_HOME>/oracle_common/upgrade/bin/ua -response <response-file> -logLevel <Log-verbosity>
Sample response file:
[GENERAL] fileFormatVersion = 3 [UAWLSINTERNAL.UAWLS] pluginInstance = 1 UASVR.path = <PATH-TO-12C-OTD-DOMAIN> [JRF.JRF_CONFIG_PLUGIN] pluginInstance = 5 [CAM.SYSCOMP] pluginInstance = 2 [OTD.CONFIG_UPGRADE] pluginInstance = 12 INSTANCE_HOME.path = <PATH-TO-11g-OTD-INSTANCE-HOME> SSL_TOKEN_TABLE.CONFIG_NAME.0.string = <OTD-11G-CONFIG-NAME> SSL_TOKEN_TABLE.SSL_TOKEN_PIN.0.encryptedPassword = <ENCRYPTED-SSL-TOKEN-PIN-FOR-CONFIG-IN-11G> SSL_TOKEN_TABLE.WALLET_PSWD.0.encryptedPassword = <ENCRYPTED-WALLET-PASSWORD-FOR-UPGRADED-CONFIG-IN-12C>
Note:
The SSL_TOKEN* fields are applicable only if the 11g instance has SSL enabled config.
Verifying the Component Configurations Upgrade.
For Oracle Traffic Director 11g Configuration:
The 11g configuration files are copied to the 12.2.1.2.0 domain under DOMAIN_HOME/config/fmwconfig/components/OTD/ directory.
The configuration elements in server.xml file are modified.
The 11g server.xml elements which are not supported in 12.2.1.2.0 are removed.
The 11g obj.conf parameters which are not supported in 12.2.1.2.0 are removed.
Certificate configurations from the NSS database are moved to KSS and to Oracle wallet for Oracle Traffic Director runtime consumption.
The version in server.xml of config-store is modified to 12.2.1.2.
Review the following list of post-upgrade tasks to be performed after using the Upgrade Assistant to upgrade to Oracle Traffic Director 12c (12.2.1.2):
Oracle Traffic Director system component instances must be created post-upgrade by targeting the system component configurations to machines using Fusion Middleware Control or WLST. For more information, see Managing Instances in Administering Oracle Traffic Director.
Creation of instances and failover groups is a deployment task. These steps are best handled outside upgrade as post-upgrade steps. For more information about the deployment topology and configuring failover groups, see Configuring Oracle Traffic Director for High Availability in Administering Oracle Traffic Director.
Any references in the Oracle Traffic Director config files to the paths outside of INSTANCE_HOME and ORACLE_HOME may not be accessible post-upgrade. This should be configured manually.
After a successful upgrade, restart all processes and servers, including the Administration Server and any Managed Servers.
The components may be dependent on each other so they must be started in the correct order.
Note:
The procedures in this section describe how to start servers and process using the WLST command line 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 start your Fusion Middleware environment, follow the steps below.
Step 1: Start the Administration Server
When you start the Administration Server, you also start the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.
To start the Administration Server, use the startWebLogic script:
(UNIX) DOMAIN_HOME/bin/startWebLogic.sh
(Windows) DOMAIN_HOME\bin\startWebLogic.cmd
When prompted, enter your user name, password, and the URL of the Administration Server.
Step 2: Start Node Manager
To start Node Manager, use the startNodeManager script:
(UNIX) DOMAIN_HOME/bin/startNodeManager.sh
(Windows) DOMAIN_HOME\bin\startNodeManager.cmd
Step 3: Start Oracle Identity Management Components
Start any Oracle Identity Management components, such as Oracle Internet Directory, that form part of your environment:(UNIX) DOMAIN_HOME/bin/startComponent.sh component_name
(Windows) DOMAIN_HOME\bin\startComponent.cmd component_name
Step 4: Start the Managed Servers
To start a WebLogic Server Managed Server, use the startManagedWebLogic script:
(UNIX) DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url
(Windows) DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name admin_url
When prompted, enter your user name and password.
Note:
The startup of a Managed Server will typically start the applications that are deployed to it. Therefore, it should not be necessary to manually start applications after the Managed Server startup.Step 5: Start System Components
To start system components, such as Oracle HTTP Server, use the startComponent script:
(UNIX) DOMAIN_HOME/bin/startComponent.sh component_name
(Windows) DOMAIN_HOME\bin\startComponent.cmd component_name
You can start system components in any order.