Below is the first page of the Administrative Agent Howto Module from my WebSphere Application Server 8 Network Deployment Essentials course.

A Stand-alone application server can have the administration console deployed in it. The application server and the applications deployed in it can be managed through the administration console. This approach works fine in a small installation with one or two application server instances. But in a large installation with multiple application servers, it becomes difficult to manage due to the following reasons.

1. Administrators have to remember multiple ports, i.e. the administrative console port for every application server.

2. The same administrative console web application is deployed in all the application servers, which is in a way inefficient.

3. Difficult to manage from a security point of view, as multiple ports are to be opened up for administrators.

4. Job Managers cannot manage a stand-alone Base/Express server. It can manage these servers only through Administrative Agent.

An administrative agent is a separate process that can be used to manage all the application servers running in a machine i.e. within a single OS image. If you have an administrative agent in a machine, you need not have administrative console application deployed in the application server. This reduces the memory footprint of the application server.

In this HowTo, we will be creating two application server profiles appsrv31 and appsrv32. We then create the Administrative agent profile adminagent30 using PMT. The administrative agent is configured as an Operating System service. The setup is shown in the above diagram.

The base nodes appsrv31_node and appsrv32_node are then registered to the administrative agent. We then explore administrative agent console. Finally we de-register the base nodes from the administrative agent. We then de-promote administrative agent from an operating system service status.


Leave a Reply