test

Sun Java System Application Server 9.1 Upgrade and Migration Guide

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.