Use administrative programs (JMX)
Overview
You can administer WAS and your applications using...
- wsadmin
- console
- administrative command-line tools
- Java APIs
You can use the command-line tools from automation scripts to control the servers.
WAS supports access to the administrative functions through a set of Java classes and methods. You can write a Java program that performs any of the administrative features of the WAS administrative tools. You can also extend the basic WAS administrative system to include your own managed resources.
You can prepare, install, uninstall, edit, and update applications through programming. Preparing an application for installation involves collecting various types of WAS-specific binding information to resolve references that are defined in the application deployment descriptors. This information can also be modified after installation by editing a deployed application. Updating consists of adding, removing or replacing a single file or a single module in an installed application, or supplying a partial application that manipulates an arbitrary set of files and modules in the deployed application.
Updating the entire application uninstalls the old application and installs the new one. Uninstalling an application removes it entirely from the WAS configuration.
Perform any or all of the following tasks to manage WAS and your J2EE applications through programming.
Procedure
- Create a JMX remote client program by using the JMX remote API (JSR 160)..
This topic describes how to develop a JMX remote program that uses the JMX remote API (JSR 160) to access the WAS administrative system.
- Create a custom Java administrative client program using the Java administrative APIs.
This topic describes how to develop a Java program that uses the WAS administrative APIs to access the administrative system of WAS.
- Extend the WAS administrative system with custom MBeans.
This topic describes how to extend the WAS administration system by supplying and registering new JMX MBeans in one of the Application Server processes. In this case, you can use the administrative classes and methods to add newly managed objects to the administrative system.
- Deploy and manage a custom Java administrative client program for use with multiple J2EE appservers.
This topic describes how to connect to a J2EE server, and how to manage multiple vendor servers.
- Manage applications through programming
This topic describes how, through Java MBean programming, to install, update, and delete a J2EE application on WAS.
- Extend application management operations through programming
This topic describes how, through programming, to use the common deployment framework to add additional logic to application management operations.
Results
Depending on which tasks you complete, you have created your own administrative program, extended the WAS console, connected and managed vendor servers, or managed your applications through programming.
What to do next
You can continue to administer WAS and your applications through programming or in combination with the tools that come with the WAS.
JMX
Creating a custom Java administrative client program using WAS administrative Java APIs
Creating a JMX client program using the JMX Remote application programming interface
Extending the WAS administrative system with custom MBeans
Administrative programs for multiple J2EE appservers
Deploying and managing a custom Java administrative client program with multiple J2EE appservers
JMX V1.0 to JMX V1.2 migration
JMX interoperability
Managed object metadata
Manage applications through programming
Extending application management operations through programming