Upgrading Oracle Traffic Director from a Previous 12c Release

4 Upgrading Oracle Traffic Director from a Previous 12c Release

You can upgrade Oracle Traffic Director from an earlier 12c release version to the latest 12c (12.2.1.4.0) release version.

Oracle Fusion Middleware Upgrade Assistant supports an in-place upgrade to 12c (12.2.1.4.0) for the following Oracle Traffic Director release versions:

Oracle Traffic Director FMW 12c Release 2, Version: 12.2.1.2.0
Oracle Traffic Director FMW 12c Release 2, Version: 12.2.1.3.0

Note:

As of 12.2.1.4.0, Oracle Traffic Director is deprecated. In the future, use Oracle HTTP Server or Kubernetes Load Balancer for equivalent functionality.

The following topics describe how to upgrade Oracle Traffic Director to 12c (12.2.1.4.0):

About Oracle Traffic Director Upgrade Process from an Earlier or a Previous 12c Release

Review the roadmap for an overview of the upgrade process for Oracle Traffic Director from a previous 12c release.

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 4-1 Tasks for Upgrading Oracle Traffic Director from a Previous 12c Release

Task	Description
Required If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks.	See: Introduction to Upgrading Oracle Traffic Director to 12c (12.2.1.4.0) Pre-Upgrade Requirements Pre-Upgrade Checklist
Required Download and install the Oracle Fusion Middleware Infrastructure and Oracle Traffic Director 12c (12.2.1.4.0) distributions into a new Oracle home.	See Installing the Product Distributions. Tip: See the following documents for more information on the installation and configuration of Oracle Fusion Middleware Infrastructure and Oracle Traffic Director: Installing and Configuring the Oracle Fusion Middleware Infrastructure Installing Oracle Traffic Director
Required Shut down the source and target environments (stop all the Administration and Managed Servers).	WARNING: Failure to shut down your servers during an upgrade may lead to data corruption. See Stopping Servers and Processes.
Required Reconfigure the existing domain.	Run the reconfiguration wizard targeting the existing domain to update WebLogic Server core infrastructure and the domain to 12c (12.2.1.4.0) version.
Required Start the Upgrade Assistant to upgrade domain component configurations.	The Upgrade Assistant is used to update the domain’s component configurations on the node that hosts the Administration Server. See Starting the Upgrade Assistant for Oracle Traffic Director 12c Specific Upgrade.
Required Create Oracle Traffic Director instances.	The Upgrade Assistant does not create Oracle Traffic Director instances. These instances must be created post upgrade by targeting Oracle Traffic Director configurations to machines, using Fusion Middleware Control UI or Oracle WebLogic Scripting Tool (WLST). See Post-Upgrade Tasks. Note: This is not applicable for upgrading standalone domain.
Optional Upgrade remote managed domains.	For the collocated domain managed remote nodes, we need to upgrade the managed domains on the remote nodes by packing the upgraded collocated domain and recopying the same on to the remote nodes. Note: This is not applicable for upgrading standalone domain.
Optional Setup failover.	If your source Oracle Traffic Director installation is part of a failover setup with remote nodes managed by the administration server, you must recreate the similar topology as specified in Configuring Failover. Note: This is not applicable for upgrading standalone domain.
Required Start Upgrade Assistant to upgrade standalone system component configurations.	Upgrade Assistant updates the standalone agent’s component configurations. See Starting the Upgrade Assistant for Oracle Traffic Director 12c Specific Upgrade.
Required Start all process and servers. Restart the servers and Oracle Traffic Director 12c (12.2.1.4.0) instance.	When the upgrade process is complete, restart Oracle Traffic Director 12c (12.2.1.4.0) instance. Once the upgrade process is complete, start all processes and servers including the Admin Server, Managed Servers and Oracle Traffic Director instances. See Starting Servers and Processes.
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. Important: Oracle recommends that you ensure all of the upgraded components are working as expected before deleting your backups. See Verifying the Component Configurations.

Task

Description

Required

If you have not done so already, review the introductory topics in this guide and complete the required pre-upgrade tasks.

See:

Required

Download and install the Oracle Fusion Middleware Infrastructure and Oracle Traffic Director 12c (12.2.1.4.0) distributions into a new Oracle home.

See Installing the Product Distributions.

Tip:

See the following documents for more information on the installation and configuration of Oracle Fusion Middleware Infrastructure and Oracle Traffic Director:

Required

Shut down the source and target environments (stop all the Administration and Managed Servers).

WARNING:

Failure to shut down your servers during an upgrade may lead to data corruption.

See Stopping Servers and Processes.

Required

Reconfigure the existing domain.

Run the reconfiguration wizard targeting the existing domain to update WebLogic Server core infrastructure and the domain to 12c (12.2.1.4.0) version.

Required

Start the Upgrade Assistant to upgrade domain component configurations.

The Upgrade Assistant is used to update the domain’s component configurations on the node that hosts the Administration Server.

See Starting the Upgrade Assistant for Oracle Traffic Director 12c Specific Upgrade.

Required

Create Oracle Traffic Director instances.

The Upgrade Assistant does not create Oracle Traffic Director instances. These instances must be created post upgrade by targeting Oracle Traffic Director configurations to machines, using Fusion Middleware Control UI or Oracle WebLogic Scripting Tool (WLST).

See Post-Upgrade Tasks.

Note:

This is not applicable for upgrading standalone domain.

Optional

Upgrade remote managed domains.

For the collocated domain managed remote nodes, we need to upgrade the managed domains on the remote nodes by packing the upgraded collocated domain and recopying the same on to the remote nodes.

Note:

This is not applicable for upgrading standalone domain.

Optional

Setup failover.

If your source Oracle Traffic Director installation is part of a failover setup with remote nodes managed by the administration server, you must recreate the similar topology as specified in Configuring Failover.

Note:

This is not applicable for upgrading standalone domain.

Required

Start Upgrade Assistant to upgrade standalone system component configurations.

Upgrade Assistant updates the standalone agent’s component configurations.

See Starting the Upgrade Assistant for Oracle Traffic Director 12c Specific Upgrade.

Required

Start all process and servers.

Restart the servers and Oracle Traffic Director 12c (12.2.1.4.0) instance.

When the upgrade process is complete, restart Oracle Traffic Director 12c (12.2.1.4.0) instance.

Once the upgrade process is complete, start all processes and servers including the Admin Server, Managed Servers and Oracle Traffic Director instances.

See Starting Servers and Processes.

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.

Important:

Oracle recommends that you ensure all of the upgraded components are working as expected before deleting your backups.

See Verifying the Component Configurations.

Preparing to Upgrade Oracle Traffic Director from an Earlier or a Previous 12c to the Latest 12c

This section describes preparing the upgrade Oracle Traffic Director from an earlier or previous 12c version to the latest 12c (12.2.1.4.0) release version.

Important:

Before you upgrade to Oracle Traffic Director 12c (12.2.1.4.0), you must ensure that 12c (12.2.1.4.0) binaries are installed in a new FMW_HOME.

Note:

Upgrading across different platforms is not supported. For example, you cannot upgrade Oracle Traffic Director from a Linux to Solaris environment.

For more information on installing 12c (12.2.1.4.0) binaries in a new FMW_HOME, see the following topic with more details on the procedure and processes.

Installing the Product Distributions

Before beginning your upgrade, download Oracle Fusion Middleware Infrastructure and Oracle Traffic Director 12c (12.2.1.4.0) distributions on the target system and install them using Oracle Universal Installer.

Note:

When Infrastructure is required for the upgrade, you must install the Oracle Fusion Middleware distribution first before you install other Fusion Middleware products.

The following install instructions are for the standard Oracle Fusion Middleware installation topology. Refer to the Oracle Traffic Director Installation Guide for more information about installing the other supported topologies.

To install 12c (12.2.1.4.0) distributions:

Sign in to the target system.
Download the following from Oracle Technology Network or Oracle Software Delivery Cloud to your target system:
- Oracle Fusion Middleware Infrastructure (fmw_12.2.1.4.0_infrastructure_generic.jar)
- Oracle Traffic Director (UNIX: distribution_name_12.2.1.3.0_otd_linux64.bin), (Windows: distribution_name_12.2.1.3.0_otd_win64.exe)
Change to the directory where you downloaded the 12c (12.2.1.4.0) product distribution.
Start the installation program for Oracle Fusion Middleware Infrastructure:
- (UNIX) JDK_HOME/bin/java -jar fmw_12.2.1.4.0_infrastructure.jar
- (Windows) JDK_HOME\bin\java -jar fmw_12.2.1.4.0_infrastructure.jar
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 Auto Updates screen, select an option:
- Skip Auto Updates: If you do not want your system to check for software updates at this time.
- Select patches from directory: To navigate to a local directory if you downloaded patch files.
- Search My Oracle Support for Updates: To automatically download software updates if you have a My Oracle Support account. You must enter Oracle Support credentials then click Search. To configure a proxy server for the installer to access My Oracle Support, click Proxy Settings. Click Test Connection to test the connection.
Click Next.
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 following:
1. For Infrastructure, select Fusion Middleware Infrastructure
2. For Oracle Traffic Director, select Oracle Traffic Director
Select the type of installation and consequently, the products and feature sets you want to install.
- Select Standalone OTD (Managed independently of WebLogic server) if you are installing Oracle Traffic Director in a Standalone domain or installing Oracle Traffic Director in a remote node of a collocated domain.
- Select Collocated OTD (Managed through WebLogic server) if you are installing Oracle Traffic Director in a WebLogic Server domain on the administration server node.
Important:
You can only upgrade earlier versions of Oracle Traffic Director 12c in the standalone OTD. Upgrading Oracle Traffic Director from 11g to 12c standalone is not supported.
Click Next.
See Installing Oracle Traffic Director for more information.
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 Oracle Fusion Middleware Infrastructure, enter the following command to start the installer for your product distribution and repeat the steps above to navigate through the installer screens:
(UNIX) ./distribution_name_12.2.1.3.0_otd_linux64.bin

(Windows) distribution_name_12.2.1.3.0_otd_win64.exe

Performing Pre-Upgrade Tasks on Oracle Traffic Director Domain to be Upgraded

You must perform the tasks as in this section, before you begin any upgrade from an earlier or previous Oracle Traffic Director 12c domain to the latest 12c (12.2.1.4.0). These tasks ensure you have a successful upgrade and a limited amount of downtime.

Before you upgrade your earlier or previous Oracle Traffic Director 12c version to the latest Oracle Traffic Director 12c (12.2.1.4.0) environment, you must follow these steps:

If you have configured webgate plug-in on Oracle Traffic Director instance, then you must ensure that the related changes are pulled into the corresponding Oracle Traffic Director configuration before you run the upgrade.

Tip:

See pullComponentChanges in WebLogic Scripting Tool Command Reference for Oracle Traffic Director.
Shut down all of the pre-upgrade processes and servers, including the Administration Server and any managed servers.

Tip:

To stop Oracle Traffic Director instances in 12c environment, see Managing Oracle Traffic Director Instances in 12c Environment.

For more information on stopping Administration and Managed Servers and Node Manager, see the following topic with more details on the procedure, processes, and servers.

Stopping Servers and Processes

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

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

Note:

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

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

Step 1: Stop System Components

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

(UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name
(Windows) EXISTING_DOMAIN_HOME\bin\stopComponent.cmd component_name

You can stop system components in any order.

Step 2: Stop the Managed Servers

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

(UNIX) EXISTING_DOMAIN_HOME/bin/stopManagedWebLogic.sh managed_server_name admin_url
(Windows) EXISTING_DOMAIN_HOME\bin\stopManagedWebLogic.cmd managed_server_name admin_url

When prompted, enter your user name and password.

Step 3: Stop Oracle Identity Management Components

Stop any Oracle Identity Management components, such as Oracle Internet Directory:

(UNIX) EXISTING_DOMAIN_HOME/bin/stopComponent.sh component_name
(Windows) EXISTING_DOMAIN_HOME\bin\stopComponent.cmd component_name

Step 4: Stop the Administration Server

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

To stop the Administration Server, use the stopWebLogic script:

(UNIX) EXISTING_DOMAIN_HOME/bin/stopWebLogic.sh
(Windows) EXISTING_DOMAIN_HOME\bin\stopWebLogic.cmd

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

Step 5: Stop Node Manager

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

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

Managing Oracle Traffic Director Instances in 12c Environment

Before you start upgrading your domain, you must stop all the instances of Oracle Traffic Director.

For more information on how you can configure in multiple modes, see the following topics:

Starting, Stopping, and Restarting 12c Oracle Traffic Director Instances Using Fusion Middleware Control

Learn more about starting, stopping, or restarting one or more 12c Oracle Traffic Director instances in the graphical mode.

To start, stop, or restart 12c Oracle Traffic Director instances by using Fusion Middleware Control, you must perform the following:

Sign in to Fusion Middleware Control for Oracle Traffic Director.

Tip:

For more details, see Displaying Fusion Middleware Control in Administering Oracle Traffic Director.
Click WebLogic Domain button at the upper left corner of the page.
Select Administration > OTD Configurations.
A list of the available configurations is displayed.
Select the configuration for which you want to start, stop, or restart instances.
Click Oracle Traffic Director Configuration, in the Common Tasks pane.
Select Administration > Instances.
The Instances page is displayed.
Select on the list of instances available.
Click Start Instances, or Stop Instances, or Restart Instances button, as required, for the instance that you want to start, stop, or restart.

Starting, Stopping, and Restarting Oracle Traffic Director 12c Instances Using Oracle WebLogic Scripting Tool (WLST)

Learn more about starting, stopping, or restarting one or more Oracle Traffic Director 12c instances in the command line mode.

To start, stop, or restart one or more Oracle Traffic Director 12c instances, you must run the following commands:

Table 4-2 Configuration Commands for 12c Oracle Traffic Director Instances

Action	Commands
To Start	`start`
To Stop	`shutdown`
To Restart	`softRestart`

The following examples are for your reference and requirement.

The three commands start, shutdown, and softRestart the instance on the machine otd_foo_machine1.

start('otd_foo_machine1')

shutdown('otd_foo_machine1')

softRestart('otd_foo_machine1')

Tip:

For more information on Oracle WebLogic Scripting Tool (WLST) commands mentioned in this section, see WebLogic Scripting Tool Command Reference for Oracle Traffic Director.

Reconfiguring the Existing Domain in Oracle Traffic Director

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

Follow the process to reconfigure the source Oracle Traffic Director domain on the machine that hosts the Administration Server or the Standalone Domain.

WARNING:

Before you start your reconfiguration process for an existing collocated domain, you must ensure that the Administration Server is not running.

You can run the Reconfiguration Wizard in the following modes:

Reconfiguring the Existing Oracle Traffic Director Domain in Graphical Mode

To reconfigure your existing Oracle Traffic Director domain using the graphical mode, run the Reconfiguration Wizard.

Navigate through the screens in the Reconfiguration Wizard to reconfigure your existing domain.

Launch <12.2.1.4.0 oracle home>/oracle_common/common/bin/reconfig.sh from 12.2.1.4.0 installation location.

While the steps described are for collocated domain, the screens are very similar for standalone domain as well.

In the Select Domain screen, provide the domain path of the previous 12c release in the Existing Domain Location field.
The setup progress screen is displayed.

Click Next to continue.
The Reconfig Summary screen is displayed.

Click Next to continue.
Click Next to continue in the Domain mode and the JDK screen.
The Advanced Configuration screen is displayed.

Click Next to continue.
Click Reconfig on the Configuration Summary screen to continue.
The Reconfiguration Progress screen is displayed.

Click Next to continue once the progress is completed and shows 100%.
Click Close in the End of Configuration screen to finish the Reconfiguration.

Reconfiguring the Existing Oracle Traffic Director Domain Using Oracle WebLogic Scripting Tool

Learn about how you can reconfigure your existing Oracle Traffic Director domain in the command line mode.

You can also reconfigure the domain using Oracle WebLogic Scripting Tool in the offline mode using the readDomainForUpgrade command.

Tip:

For more information, see Reconfiguring a WebLogic Domain Using WebLogic Scripting Tool.

Starting the Upgrade Assistant for Oracle Traffic Director 12c Specific Upgrade

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

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 start the Upgrade Assistant

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 the following topic.

Upgrade Assistant Parameters Specific to Oracle Traffic Director

You can start the Upgrade Assistant, using the specific command line parameters for Oracle Traffic Director.

When you start the Upgrade Assistant from the command line, you can specify additional parameters. The Table 3-3 shows the specific Command-Line Parameters for Oracle Traffic Director upgrade in Upgrade Assistant.

Table 4-3 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 will create log files and temporary files. The default locations are: (UNIX) `NEW_ORACLE_HOME/oracle_common/upgrade/logs` `NEW_ORACLE_HOME/oracle_common/upgrade/temp` (Windows) `NEW_ORACLE_HOME\oracle_common\upgrade\logs` `NEW_ORACLE_HOME\oracle_common\upgrade\temp`
`-help`	Optional	Displays all of the command-line options.

Upgrading a Collocated Domain

Run the Upgrade Assistant to upgrade Oracle Traffic Director component configurations on the collocated domain. You can upgrade a collocated Oracle Traffic Director, from an earlier or a previous 12c domain to the latest 12c ( 12.2.1.3.0 ) version.

You can run the Upgrade Assistant in the following modes:

Note:

The Upgrade Assistant must only be running on the domain where Oracle Traffic Director is collocated with WebLogic Administration Server within an Oracle Fusion Middleware Infrastructure Oracle home.

For more information on upgrading remote nodes managed by the administration server, see Upgrading Remote Managed Domains.

You can run the Upgrade Assistant in the following modes to upgrade a collocated domain:

Upgrading Collocated Oracle Traffic Director in Graphical Mode

To upgrade your collocated Oracle Traffic Director using the graphical mode, run the upgrade wizard.

Launch the Upgrade Assistant and follow the steps below:

The Welcome screen displays the pre-upgrade tasks that need to be performed.

Ensure you perform these tasks and Click Next to continue.
In the Upgrade Type screen, select All Configurations Used By a Domain and provide the path of the reconfigured domain of an earlier or a previous 12c release in the Domain Directory field.

Click Next to continue.
In the Component List screen, the list of components that will be upgraded are displayed.

Click Next to continue.
In the Prerequisites screen, make sure you have met all the prerequisites mentioned in the screen.

Select all the check boxes.

Then click Next to continue.
In the Oracle Traffic Director Upgrade Path screen, select the source version for the upgrade as 12c source.
The Examine screen shows the status of the examination process where it is checked if the components are ready to be upgraded.

Once the process is complete, Click Next to continue.
The Upgrade Summary screen is displayed.

Click the Save Response File.. button to create a response file.

A response file is a text file the Upgrade Assistant can write out that saves all of your inputs to the various screens.

This file can be used later as an input for Command Line upgrade bypassing the GUI.

Click Upgrade to continue.
The Upgrade Progress screen displays the upgrade progress.

Once upgrade is done, Click Next to continue.
In the Upgrade Success screen, check the log file in case of any errors during the upgrade.

Click Close to complete the upgrade.

Upgrading Collocated Oracle Traffic Director in Silent Mode

You can upgrade your collocated Oracle Traffic Director in silent mode (command line mode).

To upgrade collocated Oracle Traffic Director using silent mode, run the upgrade assistant command with the response file generated using the upgrade wizard.

After a successful upgrade, a success message is displayed on the console.
Log file for the upgrade will be saved in the following path:
```
<12.2.1.4.0 oracle home>/oracle_common/upgrade/logs
```

Command Line for silent upgrade (on UNIX):

<12.2.1.4.0 oracle home>/oracle_common/upgrade/bin/ua 
-response <response-file> 
-logLevel <Log-verbosity>

Syntax

After a successful upgrade, a success message is displayed on the console. Log file is available under the following path:

<12.2.1.4.0 oracle home>/oracle_common/upgrade/logs

Command Line for Silent Upgrade (on UNIX)

<12.2.1.4.0 oracle home>/oracle_common/upgrade/bin/ua -response <response-file> -logLevel <Log-verbosity>

Sample Response File

The following is a sample response file as an example for your requirement.

# This is a response file for the Fusion Middleware Upgrade Assistant.
# Individual component upgrades are performed in the order they are described here.
# Each upgrade is introduced by a section header containing the name of the
# component and name of the upgrade plugin. The form of the section header is
# [ComponentName.PluginName]
 
# These names can be found in the Upgrade Descriptor files for the components.
# Individual input lines consist of a name, an equal sign, and a value.
# The name is in two parts separated by a period. The first part is the "name" attribute from the Descriptor File XML tag by which the plugin refers to the value.
# The second part of the name identifies a field within that value. Some input types have only one field, while other types can have half a dozen.
# Do not intermix input lines that apply to different XML tags.
 
[GENERAL]
# This is the file format version number. Do not change the next line.
fileFormatVersion = 3
 
# The next section contains information for accessing a WebLogic Server domain.
[UAWLSINTERNAL.UAWLS]
 
# The following number uniquely identifies this instance of an upgrade plugin. Do not change it.
pluginInstance = 1
 
# Specifies the WebLogic Server domain directory:
UASVR.path = /export/orahome/domains/otd_domain
 
# The next section contains the information for performing a mid-tier upgrade on Oracle JRF, as described in the Upgrade Descriptor file located at
# /export/orahome/oracle_common/plugins/upgrade/jrfua.xml
# Do not change the next line.
[JRF.JRF_CONFIG_PLUGIN]
 
# The following number uniquely identifies this instance of an upgrade plugin. Do not change it.
pluginInstance = 8
 
# The next section contains the information for performing a mid-tier upgrade on System Components Infrastructure, as described in the Upgrade Descriptor file located at
# /export/orahome/oracle_common/plugins/upgrade/syscomp.xml
# Do not change the next line.
[CAM.SYSCOMP]
 
# The following number uniquely identifies this instance of an upgrade plugin. Do not change it.
pluginInstance = 4
 
# The next section contains the information for performing a mid-tier upgrade on Oracle Traffic Director, as described in the Upgrade Descriptor file located at
# /export/orahome/otd/plugins/upgrade/otd-upgrade.xml
# Do not change the next line.
[OTD.CONFIG_UPGRADE]
 
# The following number uniquely identifies this instance of an upgrade plugin. Do not change it.
pluginInstance = 12
 
# Specifies a choice from a collection of values,
# "Select the source version for the upgrade"
UPGRADE_CHOICE.choose = 12-12
 
# Specifies the choice for a yes/no option:
# "Remote directory"
REMOTE_INSTANCE_HOME.option = no

Upgrading Remote Managed Domains

Follow the process as in this topic to upgrade Oracle Traffic Director remotely managed domains.

If the Administration server in the upgraded domain manages multiple remote domains, the following procedure must be followed to upgrade each of these.

Note:

Note that domains managed by a remote Administration Server are not directly upgradable. Instead, the collocated domain on which the Administration Server is running must be packed and unpacked on the remote node.

Learn more about processes and steps on how you can upgrade remotely managed domains as in the following modes:

Installing Product Binaries

You must install the product binaries to begin your Oracle Traffic Director upgrade in remote managed domains.

Install Oracle Traffic Director in standalone mode on each node that hosts remote managed domain.

Tip:

For more information on installing Oracle Traffic Director in a standalone mode, see Installation Procedure in Installing Oracle Traffic Director.

Packing the Upgraded Collocated Domain

Follow the steps to pack your upgraded collocated domain in Oracle Traffic Director upgrade.

Pack the upgraded domain in the node that hosts the Administration Server using the pack command.

This command creates a template jar file that contains a subset of the domain that can be used to create an Oracle Traffic Director managed domain on the remote machine.
Copy the template jar created by pack command to the node that needs to host remote managed domain or keep the jar in a file system location which can be accessed from that node.

Syntax

<12.2.1.4.0 Oracle Home>/oracle_common/common/bin/pack.sh 
-domain=<full path to the domain that needs to be packed> 
-template=<full path to a template jar file to be created> 
-template_name=<description> 
-managed=true

Sample Response File

The following is a sample response file as an example for your requirement.

<12.2.1.4.0 Oracle Home>/oracle_common/common/bin/pack.sh 
-domain=<domain home> 
-template=/share/files/upgraded_domain.jar 
-template_name=test_after_upgrade 
-managed=true

Unpacking the Upgraded Collocated Domain on the Remote Nodes

Follow the steps to unpack your upgraded collocated domain in Oracle Traffic Director upgrade on the remote nodes.

To unpack your upgraded collocated domain, run the unpack command on the standalone node that needs to host remote managed domain.

Syntax

<12.2.1.4.0 Oracle Home>/oracle_common/common/bin/unpack.sh 
-domain=<full path to the domain that needs to be created> 
-template=<full path to the template jar file created using pack>

Sample Response File

The following is a sample response file as an example for your requirement.

<12.2.1.4.0 Oracle Home>/oracle_common/common/bin/unpack.sh 
-domain=<domain home> 
-template=/share/files/upgraded_domain.jar

Upgrading a Standalone Domain

Run the Upgrade Assistant to upgrade Oracle Traffic Director component configurations on the standalone domain. You can upgrade a standalone Oracle Traffic Director, from an earlier or a previous 12c domain to the latest 12c (12.2.1.4.0) version.

You can run the Upgrade Assistant in the following modes:

Upgrading Standalone Oracle Traffic Director in Graphical Mode

To upgrade your standalone Oracle Traffic Director using the graphical mode, run the upgrade wizard.

Launch the Upgrade Assistant and follow the steps below:

The Welcome screen displays the pre-upgrade tasks that need to be performed.

Ensure you perform these tasks and Click Next to continue.
In the Upgrade Type screen, Select Standalone System Component Configurations.

In the Standalone Components screen, Select Update an Existing Domain and provide the path of the reconfigured standalone domain of previous 12c release in the Domain Directory field.

Click Next to continue.

Note:

The Create a new Domain option is not supported in Oracle Traffic Director Standalone Domain.
In the Component List screen, the list of components that will be upgraded are displayed.

Click Next to continue.
In the Prerequisites screen, ensure you have met all the prerequisites mentioned in the screen.

Select all the check boxes, then Click Next to continue.
In Oracle Traffic Director Upgrade Path screen, Select the source version for the upgrade as 12c source.
The Examine screen shows the status of the examination process where it is checked if the components are ready to be upgraded.

Once the process is complete, Click Next to continue.
The Upgrade Summary screen is displayed.

Click the Save Response File... button to create a response file.

This file can be used as an input for Command Line upgrade.

Click Upgrade to continue.
The Upgrade Progress screen displays the upgrade progress.

Once the upgrade is completed, Click Next to continue.
In the Upgrade Success screen, check the log file in case of any errors during the upgrade.

Click Close to complete this upgrade.

Upgrading Standalone Oracle Traffic Director in Silent Mode

You can upgrade your standalone Oracle Traffic Director in silent mode (command line mode).

To upgrade standalone Oracle Traffic Director using silent mode, run the Upgrade Assistant command with the response file generated using the upgrade wizard.

Syntax

After a successful upgrade, a success message is displayed on the console. Log file is available under the following path:

<12.2.1.4.0 oracle home>/oracle_common/upgrade/logs

Command Line for Silent Upgrade (on UNIX)

<12.2.1.4.0 oracle home>/oracle_common/upgrade/bin/ua 
-response <response-file> 
-logLevel <Log-verbosity>

Sample Response File

The following is a sample response file as an example for your requirement.

# This is a response file for the Fusion Middleware Upgrade Assistant.
# Individual component upgrades are performed in the order they are described here.
# Each upgrade is introduced by a section header containing the name of the component and name of the upgrade plugin. The form of the section header is
# [ComponentName.PluginName]
 
# These names can be found in the Upgrade Descriptor files for the components.
# Individual input lines consist of a name, an equal sign, and a value.
# The name is in two parts separated by a period.  The first part is the "name" attribute from the Descriptor File XML tag by which the plugin refers to the value.
# The second part of the name identifies a field within that value. Some input types have only one field, while other types can have half a dozen.
# Do not intermix input lines that apply to different XML tags.
 
[GENERAL]
 
# This is the file format version number.  Do not change the next line.
fileFormatVersion = 3
 
# The next section contains information for accessing a WebLogic Server domain.
[UAWLSINTERNAL.UAWLS]
 
# The following number uniquely identifies this instance of an upgrade plugin. Do not change it.
pluginInstance = 1
 
# Specifies the WebLogic Server domain directory:
UASVR.path = /export/12212/orahome/otd_domain
 
# The next section contains the information for performing a mid-tier upgrade on Oracle Traffic Director, as described in the Upgrade Descriptor file located at
#   /export/12213/orahome/otd/plugins/upgrade/otd-upgrade.xml
# Do not change the next line.
[OTD.CONFIG_UPGRADE]
 
# The following number uniquely identifies this instance of an upgrade plugin. Do not change it.
pluginInstance = 5
 
# The next section contains the information for performing a mid-tier upgrade on System Components Infrastructure, as described in the Upgrade
# Descriptor file located at
#   /export/12213/orahome/oracle_common/plugins/upgrade/syscomp.xml
# Do not change the next line.
[CAM.SYSCOMP]
 
# The following number uniquely identifies this instance of an upgrade plugin. Do not change it.
pluginInstance = 2
 
# The next few lines describe an Oracle Instance:
#  "Enter the location of one or more 11g Oracle instance directories to be upgraded."
# Specifies whether source of the upgrade is 12c or not
INSTANCES.sourceIs12 = yes

Verifying the Component Configurations for a Successful Upgrade

After completing all the component configurations upgrade steps, verify whether it is successful by checking your upgraded configuration for Oracle Traffic Director domain.

This section describes the steps to verify the component configurations upgrade for Oracle Traffic Director domain.

For Oracle Traffic Director 12c Configuration:

The version in server.xml is modified to 12c (12.2.1.4.0).
The value of ORACLE_HOME in the scripts and in the obj.conf file are updated as the new ORACLE_HOME for local Oracle Traffic Director instances.

Post-Upgrade Tasks

Follow the process to complete post-upgrade tasks for Oracle Traffic Director from an earlier/previous 12c to the latest 12c (12.2.1.4.0) version.

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.4.0):

Oracle Traffic Director instances must be created post-upgrade, by targeting Oracle Traffic Director configurations to the machines using Fusion Middleware Control or Oracle WebLogic Scripting Tool (WLST).

Tip:

See Managing Instances in Administering Oracle Traffic Director.
Setting up failover is a deployment task.

These steps are best handled outside the upgrade as post-upgrade steps.

Tip:

For more information on deployment topology and configuring failover groups, see Configuring Oracle Traffic Director for High Availability in Administering Oracle Traffic Director.
Any references in Oracle Traffic Director configuration files to the paths outside of INSTANCE_HOME and ORACLE_HOME may not be accessible post upgrade.

This must be configured manually.

Starting Servers and Processes

After a successful upgrade from an earlier/previous 12c to the latest 12c (12.2.1.4.0) version, start all the processes and servers, including the Administration Server and any Managed Servers and system components.

The components may be dependent on each other and hence, they must be started in the correct order.

Tip:

To start Oracle Traffic Director instances in 12c environment, see Managing Instances.

For more information on starting and stopping Administration and Managed Servers and Node Manager, see the following topic with complete details on the procedure and how to run all these processes and servers.

Starting Servers and Processes

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) NEW_DOMAIN_HOME/bin/startWebLogic.sh
(Windows) NEW_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) NEW_DOMAIN_HOME/bin/startNodeManager.sh
(Windows) NEW_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) NEW_DOMAIN_HOME/bin/startComponent.sh component_name
(Windows) NEW_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) NEW_DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name admin_url
(Windows) NEW_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) NEW_DOMAIN_HOME/bin/startComponent.sh component_name
(Windows) NEW_DOMAIN_HOME\bin\startComponent.cmd component_name

You can start system components in any order.