Network Deployment (Distributed operating systems), v8.0 > Set up the application serving environment > Administer nodes and resources

Administer stand-alone nodes using the admin agent

We can configure an admin agent, view or change stand-alone application server nodes registered to the admin agent, and view or change job manager configurations for a registered node. An admin agent provides a single interface to administer application servers in, development, unit test, or server farm environments, for example.

Install the WAS product.

The admin agent provides a single interface to administer multiple unfederated (stand-alone) application server nodes in, for example, development, unit test, or server farm environments. By using a single interface to administer the application servers, you reduce the overhead of running administrative services in every application server.

We can use the administrative console of the admin agent to configure the admin agent, view and change properties for nodes registered to the admin agent, register and unregister application server nodes with job managers, and view and change job manager configurations for a registered node. A job manager allows you to asynchronously submit and administer jobs for a node registered to the admin agent when the node is also registered to the job manager.

Procedure

• Set up the admin agent environment.

  Create an admin agent profile and one or more stand-alone application server profiles, called nodes, on the same computer and then register the node profiles with the admin agent.

• Start and stop the admin agent as needed.

  The admin agent must be running to check for jobs for its registered stand-alone application server nodes.

• View and change properties for the admin agent.

  1. Click System Administration > Administrative agent from the navigation of the admin agent administrative console.

     • Optionally view the admin agent properties on the Configuration tab and the Runtime tab.

     • Optionally select Start components as needed on the Configuration tab. Click Apply, and then click OK.

       Select the setting allows admin agent components to start dynamically as needed for applications.

• View and change properties for a node registered to the admin agent.

  1. Click System Administration > Administrative agent > Nodes.
     • We can view the nodes registered to the admin agent.

     • Optionally click Register with Job manager to register an application server node with a job manager.

     • Optionally click Unregister from a Job Manager to unregister an application server node from a job manager.

  2. Click System Administration > Administrative agent > Nodes > node_name .

     • Optionally select Poll jobs from job manager to have the admin agent retrieve jobs from the job manager for this node.

     • To change other properties for the node, click the links under Additional Properties.

• View and change job manager configurations for a registered node.

  1. Click System Administration > Administrative agent > Nodes > node_name > Job managers to view the job managers to which the node is registered.

  2. Click System Administration > Administrative agent > Nodes > node_name > Job managers > job_manager_UUID to change job manager-related properties for the registered node.

     • Optionally change the polling interval by entering an integer value.

       The admin agent uses the polling interval to check for jobs from the job manager for this registered node.

     • Optionally change the web address of the job manager that the admin agent polls for this registered node.

• Unregister a stand-alone application server node from the admin agent.

  Unregister nodes if you no longer need the node in the admin agent environment or if you intend to delete the stand-alone application server node profile. Run the deregisterNode command to unregister a node.

Results

Depending on the tasks that you completed, you might have configured the admin agent, registered and unregistered application server nodes with job managers, viewed or changed properties for a node registered to the admin agent, or viewed and changed the job manager configuration for a registered node.

What to do next

We can continue to administer registered nodes from the admin agent. We can further configure the admin agent using the links on the configuration tab of the admin agent panel. We can register more nodes with the admin agent using the registerNode command. We can unregister nodes from the admin agent using the deregisterNode command.

We can register and unregister nodes with a job manager.

If you plan to change the system clock, stop all the application servers, the node agent servers, the dmgr server, the admin agent server, and the job manager server first. After you stop the servers, change the system clock, and then restart the servers. If you change the system clock on one system, ensure the clocks on all systems that communicate with each other and have WAS installed are synchronized. Otherwise, you might experience errors, such as security tokens no longer being valid.

Related

Set up the admin agent environment
Start and stop the admin agent
Administrative agent settings
Node collection for the admin agent
Unregistering nodes of the admin agent
Register or unregister with job manager settings
Job manager collection
Administrative agent
Administer nodes remotely using the job manager
Create management profiles with admin agents
manageprofiles command

Related

startServer command
registerNode command
deregisterNode command
stopServer command

+

Search Tips   |   Advanced Search