Administer stand-alone nodes using the administrative agent

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

Install the WAS product.

The administrative 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 administrative agent to configure the administrative agent, view and change properties for nodes registered to the administrative 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 administrative agent when the node is also registered to the job manager.


Results

Depending on the tasks that you completed, we might have configured the administrative agent, registered and unregistered application server nodes with job managers, viewed or changed properties for a node registered to the administrative 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 administrative agent. We can further configure the administrative agent using the links on the configuration tab of the administrative agent panel. We can register more nodes with the administrative agent using the registerNode command. We can unregister nodes from the administrative agent using the deregisterNode command.

We can register and unregister nodes with a job manager.

If we plan to change the system clock, stop all the application servers, the node agent servers, the deployment manager server, the administrative agent server, and the job manager server first. After you stop the servers, change the system clock, and then restart the servers. If we change the system clock on one system, you must 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.

(zos) If we plan to change the system clock, stop all the application servers, the node agent servers, the deployment manager server, the administrative agent server, the job manager server, and the location service daemon first. After you stop the servers and location service daemon, change the system clock, and then restart the servers and location service daemon. If we change the system clock on one system, you must 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.


Subtopics


Related concepts

  • Administrative agent


    Related tasks

    Administer nodes remotely using the job manager

    Create management profiles with administrative agents

    manageprofiles command

  • startServer command

    (zos) START command

  • registerNode command
  • deregisterNode command
  • stopServer command

    (zos) STOP command