Sun GlassFish Enterprise Server 2.1 High Availability Administration Guide

Deploying Node Agents

You configure and deploy node agents in two ways:

ProcedureTo Deploy Node Agents Online

Use online deployment if you already know the domain topology and have the hardware for your domain.

The following figure summarizes the online deployment of node agents:

Node Agent Online Deployment
Before You Begin

Install and start the Domain Administration Server. Once the Domain Administration Server is up and running, begin either online or offline deployment.

  1. Install a node agent on every machine that will host a server instance.

    Use the installer or the asadmin create-node-agent command . If a machine requires more than one node agent, use the asadmin create-node-agent command to create them.

    See Creating a Node Agent for more information.

  2. Start the node agents using the asadmin start-node-agent command .

    When started, a node agent communicates with the Domain Administration Server (DAS). When it reaches the DAS, a configuration for the node agent is created on the DAS. Once the configuration exists, the node agent is viewable in the Admin Console.

    See Starting a Node Agent for more information.

  3. Configure the domain: create server instances, create clusters, and deploying applications.

ProcedureTo Deploy Node Agents Offline

Use offline deployment to deploy node agents in the domain before configuring the individual local machines.

The following figure summarizes the offline deployment.

Node Agent Offline Deployment
Before You Begin

Install and start the Domain Administration Server. Once the Domain Administration Server is up and running, begin either online or offline deployment.

  1. Create placeholder node agents in the Domain Administration Server.

    See To Create a Node Agent Placeholder for more information.

  2. Create server instances and clusters, and deploy applications.

    When creating a server instance, make sure to assign port numbers that are not already in use. Because the configuration is being done offline, the domain cannot check for port conflicts at creation time.

  3. Install a node agent on every machine that will host a server instance.

    Use the installer or the asadmin create-node-agent command . The node agents must have the same names as the placeholder node agents previously created.

    See Creating a Node Agent for more information.

  4. Start the node agents using the asadmin start-node-agent command .

    When a node agent is started, it binds to the Domain Administration Server and creates any server instances previously associated with the node agent.

    See Starting a Node Agent for more information.