Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide |
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 Test if an SSH Node is Reachable
Updating and Changing 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
A CONFIG node does not support remote communication. If SSH is not set up and you plan to administer your instances locally, the instances can reside on CONFIG nodes. You cannot use CONFIG nodes for instances that you plan to administer centrally.
GlassFish Server enables you to create CONFIG nodes for use by instances, obtain information about CONFIG nodes, and delete CONFIG nodes that are no longer required.
The following topics are addressed here:
Use the create-node-config command in remote mode to create a CONFIG node.
Note - If you create an instance locally on a host for which no nodes are defined, you can create the instance without creating a node beforehand. In this situation, GlassFish Server creates a CONFIG node for you. The name of the node is the unqualified name of the host. For more information, see To Create an Instance Locally.
Remote subcommands require a running server.
Note - Only the options that are required to complete this task are provided in this step. For information about all the options for configuring the node, see the create-node-config(1) help page.
asadmin> create-node-config [--nodehost node-host] [--installdir install-dir ] node-name
The name of the host that the node represents. You may omit this option. The name of the host can be determined when instances that reside on the node are created.
The full path to the parent of the base installation directory of the GlassFish Server software on the host, for example, /export/glassfish3/. You may omit this option. The installation directory can be determined when instances that reside on the node are created.
Your choice of name for the node that you are creating.
Example 3-6 Creating a CONFIG Node
This example creates the CONFIG node cfg01. The host that the node represents and the installation directory of the GlassFish Server software on the host are to be determined when instances are added to the node.
asadmin> create-node-config cfg01 Command create-node-config executed successfully.
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help create-node-config at the command line.
Next Steps
After creating a node, you can create instances on the node as explained in To Create an Instance Locally.
Use the list-nodes-config subcommand in remote mode to obtain information about existing CONFIG nodes in a domain.
Note - To obtain information about all existing nodes in a domain, use the list-nodes(1) subcommand.
Remote subcommands require a running server.
asadmin> list-nodes-config
Example 3-7 Listing Basic Information About All CONFIG Nodes in a Domain
This example lists the name, type, and host of all CONFIG nodes in the current domain.
asadmin> list-nodes-config localhost-domain1 CONFIG localhost cfg01 CONFIG cfg01.example.com cfg02 CONFIG cfg02.example.com Command list-nodes-config executed successfully.
Example 3-8 Listing Detailed Information About All CONFIG Nodes in a Domain
This example lists detailed information about all CONFIG nodes in the current domain.
asadmin> list-nodes-config --long=true NODE NAME TYPE NODE HOST INSTALL DIRECTORY REFERENCED BY localhost-domain1 CONFIG localhost /export/glassfish3 cfg01 CONFIG cfg01.example.com /export/glassfish3 yml-i1 cfg02 CONFIG cfg02.example.com /export/glassfish3 yml-i2 Command list-nodes-config executed successfully.
See Also
You can also view the full syntax and options of the subcommands by typing the following commands at the command line:
asadmin help list-nodes
asadmin help list-nodes-config
Use the delete-node-config subcommand in remote mode to delete a CONFIG node.
Deleting a node removes the node from the configuration of the DAS. The node's directories and files are deleted when the last GlassFish Server instance that resides on the node is deleted.
Before You Begin
Ensure that no GlassFish Server instances reside on the node that you are deleting. For information about how to delete an instance that resides on a CONFIG node, see To Delete an Instance Locally.
Remote subcommands require a running server.
asadmin> list-nodes-config --long=true
asadmin> delete-node-config node-name
The name of the node that you are deleting.
Example 3-9 Deleting a CONFIG Node
This example confirms that no instances reside on the CONFIG node cfg01 and deletes the node cfg01.
asadmin> list-nodes-config --long=true NODE NAME TYPE NODE HOST INSTALL DIRECTORY REFERENCED BY localhost-domain1 CONFIG localhost /export/glassfish3 cfg01 CONFIG cfg01.example.com /export/glassfish3 cfg02 CONFIG cfg02.example.com /export/glassfish3 yml-i2 Command list-nodes-config executed successfully. asadmin> delete-node-config cfg01 Command delete-node-config executed successfully.
See Also
You can also view the full syntax and options of the subcommands by typing the following commands at the command line:
asadmin help delete-node-config
asadmin help list-nodes-config