Working with Node Agents using asadmin
You can perform the following node agent tasks with asadmin:
Creating a Node Agent
To create a node agent, run the asadmin command create-node-agent locally on the machine on which the node agent runs.
The default name for a node agent is the host name on which the node agent is created.
If you’ve already created a node agent placeholder, use the same name as the node agent placeholder to create the associated node agent. If you have not created a node agent placeholder, and the DAS is up and reachable, the create-node-agent command also creates a node agent configuration (placeholder) on the DAS.
For a complete description of the command syntax, see the online help for the command.
Example 7–1 Example of Creating a Node Agent
The following command creates a node agent:
asadmin create-node-agent --host myhost --port 4849 ---user admin nodeagent1 |
where myhost is the Domain Administration Server (DAS) hostname, 4849 is the DAS port number, admin is your DAS user, and nodeagent1 is the name of the node agent being created.
Note –
In the following situations, you must specify a DNS-reachable hostname:
-
If domains cross subnet boundaries (that is, the node agent and the Domain Administration Server (DAS) are in different domains, for example, sun.com and java.com)
-
If using a DHCP machine with a host name not registered in DNS.
Specify a DNS-reachable hostname by explicitly specifying the host name for the domain and the node agent when you create them:
create-domain --domainproperties domain.hostName=DAS-host-name create-node-agent --hostDAS-host-name --agentproperties remoteclientaddress=node-agent-host-name |
Another solution is to update the hosts hostname/IP resolution file specific to the platform so the hostname resolves to the correct IP address. However, when reconnecting using DHCP you might get assigned a different IP address. In that case, you must update the host resolution files on each server.
For more information, see:
Starting a Node Agent
Before a node agent can manage server instances, it must be running. Start a node agent by running the asadmin command start-node-agent locally on the system where the node agent resides.
For a complete description of the command syntax, see the online help for the command.
For example:
asadmin start-node-agent --user admin nodeagent1
where admin is your administration user, and nodeagent1 is the node agent being started.
For more information, see:
Stopping a Node Agent
Run the asadmin command stop-node-agent on the system where the node agent resides to stop a running node agent. The stop-node-agent command stops all server instances that the node agent manages.
For a complete description of the command syntax, see the online help for the command.
For example:
asadmin stop-node-agent nodeagent1
where nodeagent1 is the name of the node agent.
For more information, see:
Deleting a Node Agent
Before deleting a node agent, the node agent must be stopped. You can also delete a node agent if it has never been started, or never successfully able to contact the Domain Administration Server (that is, if it is still unbound).
Run the asadmin command delete-node-agent on the system where the node agent resides to delete the node agent files.
For a complete description of the command syntax, see the online help for the command.
For example:
asadmin delete-node-agent nodeagent1
where nodeagent1 is your node agent.
When deleting a node agent, you must also delete its configuration from the Domain Administration Server using either the Admin Console or the asadmin delete-node-agent-config command
For more information, see:
- © 2010, Oracle Corporation and/or its affiliates