JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide
search filter icon
search icon

Document Information

Preface

1.  High Availability in GlassFish Server

2.  Setting Up SSH for Centralized Administration

3.  Administering GlassFish Server Nodes

Types of GlassFish Server Nodes

Creating, Listing, Testing, and Deleting SSH Nodes

To Create an SSH Node

To List SSH Nodes in a Domain

To Test if an SSH Node is Reachable

To Delete an SSH Node

Creating, Listing, and Deleting CONFIG Nodes

To Create a CONFIG Node

To List CONFIG Nodes in a Domain

To Delete a CONFIG Node

Updating and Changing the Type of a Node

To Update an SSH Node

To Update a CONFIG Node

To Change the Type of a Node

4.  Administering GlassFish Server Clusters

5.  Administering GlassFish Server Instances

6.  Administering Named Configurations

7.  Configuring Web Servers for HTTP Load Balancing

8.  Configuring HTTP Load Balancing

9.  Upgrading Applications Without Loss of Availability

10.  Configuring High Availability Session Persistence and Failover

11.  Configuring Java Message Service High Availability

12.  RMI-IIOP Load Balancing and Failover

Index

Updating and Changing the Type of a Node

GlassFish Server enables you to update the configuration data of any node and to change the type of a node.

The following topics are addressed here:

To Update an SSH Node

Use the update-node-ssh subcommand in remote mode to update an SSH node.

Options of this subcommand specify the new values of the node's configuration data. If you omit an option, the existing value is unchanged.

Before You Begin

Ensure that the following prerequisites are met:

  1. Ensure that the DAS is running.

    Remote subcommands require a running server.

  2. Run the update-node-ssh subcommand.
    asadmin> update-node-ssh options node-name
    options

    Options of the update-node-ssh subcommand for changing the node's configuration data. For information about these options, see the update-node-ssh(1) help page.

    node-name

    The name of the SSH node to update.

Example 3-10 Updating an SSH Node

This example updates the host that the node sj01 represents to adc01.example.com.

asadmin> update-node-ssh --nodehost adc01.example.com sj01
Command update-node-ssh executed successfully.

See Also

update-node-ssh(1)

You can also view the full syntax and options of the subcommand by typing asadmin help update-node-ssh at the command line.

To Update a CONFIG Node

Use the update-node-config subcommand in remote mode to update a CONFIG node.

Options of this subcommand specify the new values of the node's configuration data. If you omit an option, the existing value is unchanged.

Before You Begin

Ensure that the node that you are updating exists.

  1. Ensure that the DAS is running.

    Remote subcommands require a running server.

  2. Run the update-node-config subcommand.
    asadmin> uupdate-node-config options node-name
    options

    Options of the update-node-config subcommand for changing the node's configuration data. For information about these options, see the update-node-config(1) help page.

    node-name

    The name of the CONFIG node to update.

Example 3-11 Updating a CONFIG Node

This example updates the host that the node cfg02 represents to adc02.example.com.

asadmin> update-node-config --nodehost adc02.example.com cfg02
Command update-node-config executed successfully.

See Also

update-node-config(1)

You can also view the full syntax and options of the subcommand by typing asadmin help update-node-config at the command line.

To Change the Type of a Node

The subcommands for updating a node can also be used to change a CONFIG node to an SSH node or to change an SSH node to a CONFIG node

Changing a CONFIG node to an SSH node enables SSH communication for the node. As part of this process, you can also change other configuration data for the node.

Options of the subcommands for updating a node specify the new values of the node's configuration data. For most options, if you omit the option, the existing value is unchanged. However, default values are applied if any of the following options of the update-node-ssh subcommand is omitted:


Caution

Caution - Changing an SSH node to a CONFIG node disables remote communication for the node.


Before You Begin

Ensure that the following prerequisites are met:

  1. Ensure that the DAS is running.

    Remote subcommands require a running server.

  2. Run the update-node-ssh subcommand or the update-node-config subcommand, depending on the current type of the node.
    • To change a CONFIG node to an SSH node, run the update-node-ssh subcommand on the node.
      asadmin> update-node-ssh [options] config-node-name
      options

      Options of the update-node-ssh subcommand for changing the node's configuration data. For information about these options, see the update-node-ssh(1) help page.

      config-node-name

      The name of the CONFIG node to change.

    • To change an SSH node to a CONFIG node, run the update-node-config subcommand on the node.
      asadmin> update-node-config [options] ssh-node-name
      options

      Options of the update-node-config subcommand for changing the node's configuration data. For information about these options, see the update-node-config(1) help page.

      ssh-node-name

      The name of the SSH node to change.

Example 3-12 Changing a CONFIG Node to an SSH Node

This example changes the CONFIG node cfg02 to an SSH node .

asadmin> update-node-ssh cfg02
Command update-node-ssh executed successfully.

See Also

You can also view the full syntax and options of the subcommand by typing the following commands at the command line.