You 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 WebSphere® Application Server product.
You 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.
Depending on the tasks that you completed, you 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.
You can continue to administer registered nodes from the administrative agent. You can further configure the administrative agent using the links on the configuration tab of the administrative agent panel. You can register more nodes with the administrative agent using the registerNode command. You can unregister nodes from the administrative agent using the deregisterNode command.
You 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 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
you change the system clock on one system, you must ensure the clocks
on all systems that communicate with each other and have WebSphere Application Server installed
are synchronized. Otherwise, you might experience errors, such as
security tokens no longer being valid.
If
you 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 you change the system clock on one system, you must ensure
the clocks on all systems that communicate with each other and have WebSphere Application Server installed
are synchronized. Otherwise, you might experience errors, such as
security tokens no longer being valid.
In this information ...Subtopics
Related concepts
Related tasks
| IBM Redbooks, demos, education, and more(Index) |