Upgrade Scenarios
The upgrade scenarios are as follows:
Side-by-Side Upgrade
The source server and the target server are installed on the same machine , but under different install locations. You can choose to perform this type of upgrade if you wish to have the configuration corresponding to these installations on the same machine in different locations.
A side-by-side upgrade involves the following sequence of tasks
-
Upgrading Configuration, Deployed Applications, and Certificate Databases.
-
To Upgrade Remote Node Agents (Side-by-side) (only if you have remote agents in the source application server).
If all existing node agents (from the source application server installation) run on a single machine, the upgrade tool automatically detects node agents, if any, on the source installation.
In-Place Upgrade
The target server is installed in the same installation location as the source server. You can choose to perform this type of upgrade if you wish to install the configuration (that is, the domains) in the same location as before. In this scenario, you install the binaries in the same location as the existing binaries using the installer.
Note –
For an in-place upgrade from Sun Java System Application Server 9.1, 9.1 Update1, 9.1 Update 2 to Enterprise Server 2.1, do not use the asupgrade utility. It is sufficient to upgrade the runtime binaries by using the installer. After upgrading the binaries to Enterprise Server 2.1, start the domain with the asadmin start-domain command.
An in-place upgrade involves the following sequence of tasks:
-
Upgrading Configuration, Deployed Applications, and Certificate Databases.
-
To Upgrade Remote Node Agents (In-place) (only if you have remote agents in the source application server).
If all existing node agents (from the source application server installation) run on a single machine, the upgrade tool automatically detects node agents, if any, on the source installation.
- © 2010, Oracle Corporation and/or its affiliates