WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

Chapter 7. Administration of WebSphere processes 241

environments relying on automated operations, including application deployment and server

monitoring.

The deployment managers exist as peers. One is considered active, also known as primary,

and hosts the administrative function of the cell. The others are backups in standby mode. If

the active manager fails, a standby takes over and is designated the new active deployment

manager. A command line utility is provided to clone the original cell deployment manager

into additional deployment managers. Each deployment manager is installed and configured

to run on a different physical or logical computer. The deployment managers need not be

hosted on homogenous operating platforms, although like platforms are recommended. Each

deployment manager shares the same instance of the master configuration repository and

workspace area. These must be located on a shared file system.

The file system must support fast lock recovery. The IBM General Parallel File System

(GPFS™) is recommended, and the Network File System Version 4 (NFS) is also an option. If

you use the high-availability deployment manager on AIX Version 5.3 and are using NFS

Version 4, you must have bos.net.nfs.client version 5.3.0.60 or later.

Normal operation includes starting at least two deployment managers. A new highly-available

deployment manager component runs in each deployment manager to control which

deployment manager is elected as the active one. Any other deployment manager in the

configuration is in standby mode. The on demand router (ODR) is configured with the

communication endpoints for the administrative console, the wsadmin tool, and scripting. The

ODR recognizes which deployment manager instance is active and routes all administrative

communication to that instance. The HA deployment manager function supports only use of

the JMX SOAP connector. The JMX RMI connector is not supported in this configuration.

More information about configuring a high-availability deployment manager is at the following

information center website:

http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/topic/com.ibm.websphere.wve.doc/ae/

twve_xdsoconfig.html

7.2 Working with the administrative agent

An administrative agent process is managed in the same manner as an application server

process. The process name is adminagent.

7.2.1 Starting and stopping the administrative agent

To view the status of the administrative agent process:

<profile_root_path>/bin/serverStatus.sh(bat) -all

To start an administrative agent, run the following command:

<profile_root_path>/bin/startServer.sh(bat) adminagent

To stop an administrative agent, run the following command:

<profile_root_path>/bin/stopServer.sh(bat) adminagent

242 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

7.2.2 Administrative agent configuration settings

To view the administrative manager from the administrative console, click System

administration  Administrative agent. You have two pages available, the Runtime tab

and the Configuration tab. Figure 7-4 shows the Configuration tab.

Figure 7-4 Administrative agent configuration tab

Administrative agent Configuration tab

The following list describes the two notable options in this window:

 Java SDKs

This option lets you view and chose the required version of SDKs for your deployment

manager process. WebSphere Application Server V8.5 lets you select between Java SDK

versions 1.6 and 1.7, both of them available for 32 and 64-bits systems. To be able to

select between Java SDK versions 1.6 and 1.7, you must install both versions first. The

default version that is selected when installing is Java SDK 1.6. If both versions are

installed on your system, you can chose one of them and set it as default by clicking the

Make Default button. Save your changes and restart the deployment manager process to

use the newly selected JAVA SDK version.

 Ports

Select the Ports link to view and manage the ports that the administrative agent uses.

Administrative agent Runtime tab

In addition to the Configuration page, the administrative console contains a Runtime tab for

the administrative agent. To view the Runtime tab, click System administration 

Administrative agent and then click the Runtime tab at the top of the page. Figure 7-5 on

page 243 shows the Runtime tab.

Chapter 7. Administration of WebSphere processes 243

Figure 7-5 Administrative agent Runtime tab

The state is Started because otherwise you cannot access the administrative console.

The only link in the window panel is for Product Information. Select Product Information to

open a new page that provides information about the level of code running on the

administrative agent system. This page also provides links for more detailed information,

including the installation history for the product and maintenance.

Product information is stored as XML files in the install_root/properties/version/ folder

and can be viewed with the administrative console, as shown in Figure 7-6.

Figure 7-6 Product information