Use AdminControl 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.
AdminControl includes commands to...
- query existing running objects and their attributes
- invoke operation on the running objects
- query information on the connected server
- perform client tracing
- reconnect to a server
- 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 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 appserver, only MBeans running in that appserver 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.
General method to manage the cycle of an application:
- Install the application.
- Edit the application.
- Update the application.
- Uninstall the application.
ObjectName, Attribute, and AttributeList classes
Example: Collecting arguments for AdminControl
Example: Identifying running objects
Specifying running objects using wsadmin
Identifying attributes and operations for running objects with wsadmin
Performing operations on running objects using wsadmin
Modify attributes on running objects with wsadmin
Synchronizing nodes with wsadmin
Related
Commands for AdminControl