Use administrative programs (JMX)

This topic describes how to use Java application programming interfaces (APIs) to administer WAS and to manage your applications.

 

Before you begin

We can administer WAS and your applications through tools that come with the product or through programming with the Java APIs.

The wsadmin scripting tool, the administrative console, and the administrative command-line tools come with the product. These administrative tools provide most of the functions that we need to manage the product and the applications that run in WebSphere Application Server. Use the command-line tools from automation scripts to control the servers. Scripts that are written for the wsadmin scripting tool offer a wide range of possible custom solutions that one can develop quickly.

Investigate these tools with the Java APIs to determine the best ways to administer WebSphere Application Server and your applications. For information on the Java APIs, view Java Management Extensions (JMX) API documentation

 

Overview

WebSphere Application Server supports access to the administrative functions through a set of Java classes and methods. We can write a Java program that performs any of the administrative features of the WAS administrative tools. We 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 WebSphere Application Server-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 Java 2 Platform, Enterprise Edition (J2EE) applications through programming.

 

Steps for this task (dependent on configuration)

 

Result

Depending on which tasks you complete, you have created your own administrative program, extended the WAS administrative console, connected and managed vendor servers, or managed your applications through programming.

 

What to do next

We can continue to administer WAS and your applications through programming or in combination with the tools that come with the WebSphere Application Server.

 

See also


Java Management Extensions
Creating a custom Java administrative client program using WAS administrative Java APIs
Extending the WAS administrative system with custom MBeans
Developing administrative programs for multiple Java 2 Platform, Enterprise Edition application servers
Deploying and managing a custom Java administrative client program with multiple Java 2 Platform, Enterprise Edition application servers
Migrating Java Management Extensions V1.0 to Java Management Extensions V1.2
Java Management Extensions interoperability
Managed object metadata
Manage applications through programming