Network Deployment (Distributed operating systems), v8.0 > Scripting the application serving environment (wsadmin)


Use the wsadmin scripting AdminControl object for scripted administration

The AdminControl scripting object is used for operational control. It communicates with MBeans that represent live objects running a WebSphere server process.

It includes commands to query existing running objects and their attributes and invoke operation on the running objects. In addition to the operational commands, the AdminControl object supports commands to query information on the connected server, convenient commands for client tracing, reconnecting to a server, and start and stop server for network deployment environment.

Many of the operational commands have two sets of signatures so that they can either invoke using string based parameters or using Java Management Extension (JMX) objects as parameters. Depending on the server process to which a scripting client is connected, the number and type of MBeans available varies. When connected to an application server, only MBeans running in that application server are visible.

If a scripting client is connected to a dmgr, then all MBeans in all server processes are visible. If a scripting client is connected to a node agent, all MBeans in all server processes on that node are accessible.

Manage the cycle of an application:

To see a list of all available commands for the AdminControl object:


Procedure


Related


ObjectName, Attribute, and AttributeList classes using wsadmin.sh
Example: Collecting arguments for the AdminControl object using wsadmin.sh
Example: Identifying running objects using wsadmin.sh
Specify running objects using wsadmin.sh
Identify attributes and operations for running objects using wsadmin.sh
Performing operations on running objects using wsadmin.sh
Modify attributes on running objects using wsadmin.sh
Synchronize nodes using wsadmin.sh


Related


Commands for the AdminControl object using wsadmin.sh

+

Search Tips   |   Advanced Search