The scripting library provides multiple script procedures to automate your server configurations. This topic provides usage information for scripts that query, configure, and manage your node configurations. You can run each script individually, or combine procedures to create custom automation scripts for your environment.
This script configures the discovery protocol for the node of interest. If the discovery protocol that a node uses is not appropriate for the node, modify the configuration to use the appropriate protocol.
Argument | Description |
---|---|
nodeName | Specifies the name of the node. The node name is unique within the cell. A node name usually is identical to the host name for the computer. That is, a node usually corresponds to a physical computer system with a distinct IP host address. |
discoveryProtocol | Specifies the protocol that the node follows to retrieve information from a network. The Discovery protocol setting is only valid for managed nodes. Specify Transmission Control Protocol (TCP) or User Datagram Protocol (UDP). UDP is faster than TCP, but TCP is more reliable than UDP because UDP does not guarantee delivery of datagrams to the destination. Between these two protocols, the TCP default is recommended. |
Syntax
AdminNodeManagement.configureDiscoveryProtocolOnNode(nodeName, discoveryProtocol)
Example usage
AdminNodeManagement.configureDiscoveryProtocolOnNode("myNode", "UDP")
Argument | Description |
---|---|
nodeName | Specifies the name of the node to query. The node name is unique within the cell. A node name usually is identical to the host name for the computer. That is, a node usually corresponds to a physical computer system with a distinct IP host address. |
Syntax
AdminNodeManagement.doesNodeExist("nodeName")
Example usage
AdminNodeManagement.doesNodeExist("myNode")
Argument | Description |
---|---|
nodeName | Specifies the name of the node of interest. The node name is unique within the cell. A node name usually is identical to the host name for the computer. That is, a node usually corresponds to a physical computer system with a distinct IP host address. |
Syntax
AdminNodeManagement.isNodeRunning(nodeName)
Example usage
AdminNodeManagement.isNodeRunning("myNode")
This script displays a list of nodes in your environment.
Syntax
AdminNodeManagement.listNodes()
Example usage
AdminNodeManagement.listNodes()
This script restarts the nodes in your environment with node agents that are in the started state.
Syntax
AdminNodeManagement.restartActiveNodes()
Example usage
AdminNodeManagement.restartActiveNodes()
This script restarts the node agent of interest. Node agents are administrative agents that monitor application servers on a host system and route administrative requests to servers. A node agent is the running server that represents a node in a WebSphere® Application Server, Network Deployment environment.
Argument | Description |
---|---|
nodeName | Specifies the name of the node to restart. The node name is unique within the cell. A node name usually is identical to the host name for the computer. That is, a node usually corresponds to a physical computer system with a distinct IP host address. |
Syntax
AdminNodeManagement.restartNodeAgent(nodeName)
Example usage
AdminNodeManagement.restartNodeAgent("myNode")
This script stops the node of interest. Start or stop a node as needed when administering your WebSphere Application Server, Network Deployment environment. Before your environment can service requests, you must have the deployment manager and node started, and typically an HTTP server running.
Argument | Description |
---|---|
nodeName | Specifies the name of the node to stop. The node name is unique within the cell. A node name usually is identical to the host name for the computer. That is, a node usually corresponds to a physical computer system with a distinct IP host address. |
Syntax
AdminNodeManagement.stopNode(nodeName)
Example usage
AdminNodeManagement.stopNode("myNode")
This script stops the node agent of interest. Node agents are administrative agents that monitor application servers on a host system and route administrative requests to servers. A node agent is the running server that represents a node in a WebSphere Application Server, Network Deployment environment.
Argument | Description |
---|---|
nodeName | Specifies the name of the node. The node name is unique within the cell. A node name usually is identical to the host name for the computer. That is, a node usually corresponds to a physical computer system with a distinct IP host address. |
Syntax
AdminNodeManagement.stopNodeAgent(nodeName)
Example usage
AdminNodeManagement.stopNodeAgent("myNode")
This script propagates configuration changes to each active node in your environment. By default, this situation occurs periodically, as long as the node can communicate with the deployment manager.
Syntax
AdminNodeManagement.syncActiveNodes()
Example usage
AdminNodeManagement.syncActiveNodes()
This script propagates configuration changes to the node of interest. By default, this situation occurs periodically, as long as the node can communicate with the deployment manager.
Argument | Description |
---|---|
nodeName | Specifies the name of the node. The node name is unique within the cell. A node name usually is identical to the host name for the computer. That is, a node usually corresponds to a physical computer system with a distinct IP host address. |
Syntax
AdminNodeManagement.syncNode(nodeName)
Example usage
AdminNodeManagement.syncNode("myNode")