test

Sun Java System Application Server 9.1 Upgrade and Migration Guide

Upgrading your Application Server

For upgrading your Application Server installation you can choose:

Use the following procedures to upgrade your existing clusters and node agents:

To Upgrade from the Command Line

You can run the upgrade utility from the command line using the following syntax:

asupgrade 
[--console ] 
[--version ] 
[--help ] 
[--source applicationserver_8.x_installation_domaindirectory] 
[--target applicationserver_9.1_installation] 
[--passwordfile passwords.txt]

The following table describes the command options in greater detail, including the short form, the long form, and a description.

Table 2–2 asupgrade Utility Command Options

Short Form  

Long Form  

Description  

-c 

--console 

Launches the upgrade command line utility. 

-v or -V 

--version 

The version of the Upgrade Tool. 

-h 

--help 

Displays the arguments for launching the upgrade utility. 

-t 

--target 

The domains directory of the Application Server 9.1 installation. 

-s 

--source 

The installation directory of the older Application Server installation. 

-a  

--adminuser 

The admin user for the source server.  

-f 

--passwordfile 

The file containing the admin password and the master password. 

Note –

For a more detailed usage summary of the asupgrade command, see asupgrade(1M).

The following examples show how to use the asupgrade command-line utility to upgrade an existing application server installation to Application Server 9.1.

This example shows how to perform a side-by-side upgrade of a Sun Java SystemApplication Server 8.x installation to Sun Java System Application Server 9.1. 

asupgrade --source /home/sunas8.2/domains/domain1 --target /home/sjsas9.1/domains

After upgrade, node agents for all remote instances are created on the target DAS. These node agents have to be copied to the respective host systems and started.

ProcedureTo Upgrade using the Upgrade Tool Wizard

To start the wizard,

- On UNIX, change to the <install_dir>/bin directory and type asupgrade.

- On Windows, double click the asupgrade icon in the <install_dir>/bin directory.

If the Upgrade checkbox was selected during the Application Server installation process, the Upgrade Wizard screen automatically displays after the installation completes.

  1. In the Source Installation Directory field, enter the location of the existing installation from which to import the configuration. Enter the domain directory.

    For example, <install-root>/domains/domain1

  2. In the Target Installation Directory field, enter the location of the Application Server installation to which to transfer the configuration. Provide the domains root directory of the target Application Server installation as the input to this field.

  3. Provide the admin user name, the admin password, and master password of the source application server. The target domain is created with these credentials.

  4. The Upgrade Results panel is displayed showing the status of the upgrade operation.

  5. Click the Finish button to close the Upgrade Tool when the upgrade process is complete.

To Upgrade a Cluster

When you are upgrading Application Server 8.x EE to Application Server 9.1, the upgrade tool automatically detects clusters, if any, on the source installation.

ProcedureTo Upgrade a Node Agent

If you are performing an upgrade from Application Server 8.x EE to Application Server 9.1, in which all the node agents run on a single machine, the upgrade tool automatically detects node agents, if any, on the source installation. The user need not take any special action. If you are performing an upgrade from Application Server 8.x EE to Application Server 9.1, in which remote node agents are running on other machines use the following steps to perform the upgrade.

  1. Install Application Server 9.1 on Machine A.

  2. Perform the upgrade from Application Server 8.x EE to Application Server 9.1.

  3. Install Application Server 9.1 on Machine B without the DAS but with the Node Agent feature.

    Note –

    Machine A is the primary machine. It runs the DAS. Machine B is a secondary machine, which is not running the DAS. Machine B runs remote node agents that are configured to communicate with Machine A.

  4. If you are performing an in-place upgrade:

    1. On Machine A, start each node agent using the start-node-agent command with the --syncinstances option. This option resynchronizes all associated instances. Example: asadmin start-node-agent --user admin --syncinstances nodeagent1

    2. On Machine B, start each node agent using the start-node-agent command with the --syncinstances option. This option resynchronizes all associated instances

  5. If you are performing an side—by—side upgrade:

    1. Check the value of the agent.adminPort property in thenodeagent.properties file before starting the node agent for the first time. Perform this check on the nodeagent.properties files on both Machine A and Machine B. The value of agent.adminPort property must reflect the same value as the jmx-connector port defined in the domain.xml file on Machine A. Edit the agent.adminPort property in the nodeagent.properties files on Machine A and Machine B, as required.

    2. If you are using non-default ports, you must check the value of the agent.bind.status property in nodeagent.properties file on Machine B, before starting the node agent for the first time. If the agent.bind.status property in nodeagent.properties file is BOUND, change it to UNBOUND.

    3. On Machine A, start each node agent using the start-node-agent command. Do not use the --syncinstances option.

    4. On Machine B, start each node agent using the start-node-agent command. Do not use the --syncinstances option.

Starting the Upgraded Node Agent

For information on how to resolve problems with starting the upgraded node agent, see Node Agent Startup Failure.