Manage applications through programming

Through Java MBean programming, you can install, update, and delete a J2EE application on WebSphere Application Server. This task assumes a basic familiarity with MBean programming. For information on MBean programming, see MBean Java application programming interface (API) documentation.

For information on the restarting of updated applications, refer to Fine-grained recycle behavior in IBM WebSphere Developer Technical Journal: System management for WebSphere Application Server V6 -- Part 5 Flexible options for updating deployed applications.

Before you can install or change an application on WebSphere Application Server, first create or update your application and assemble it using an assembly tool.

Overview

Besides installing, uninstalling, and updating applications through programming, you can additionally install, uninstall, and update J2EE applications through the administrative console or the wsadmin tool. All three ways provide identical updating capabilities.

Procedure

1. Perform any or all of the following tasks to manage your J2EE applications through programming.

   • Access the application management function.This topic provides examples to access the application management functionality:

     • From WebSphere Application Server code

     • From outside WebSphere Application Server

     • When WebSphere Application Server is not running

   • Install an application.

     This topic provides an example for initially installing an application on WebSphere Application Server.

   • Uninstall an application.

     This topic provides an example for uninstalling an application that resides on WebSphere Application Server.

   • Manipulate additional attributes for a deployed application.

     This topic provides an example for manipulating attributes that are not exposed through the AppDeploymentTask object.

   • Share sessions for application management.

     This topic provides an example for saving application-specific updates for a deployed application to a session, and then to the configuration repository.

   • Update an application.

     This topic provides an example for updating the installed application on WebSphere Application Server with a new application. When you completely update an application, the deployed application is uninstalled and the new enterprise archive (EAR) file is installed.

   • Add to, update, or delete part of an application.

     This topic provides an example used to to add, update, or delete part of an application on WebSphere Application Server.

   • Edit an application.

     This topic provides an example used to to edit an application on WebSphere Application Server.

   • Add a module.

     This topic provides an example for adding a module to an application that resides on WebSphere Application Server.

   • Update a module.

     This topic provides an example for updating a module that resides on WebSphere Application Server. When you update a module, the deployed module is uninstalled and the updated module is installed.

   • Delete a module.

     This topic provides an example for deleting a module that resides on WebSphere Application Server. When you delete a module, the deployed module is uninstalled.

   • Add a file.

     This topic provides an example for adding a file to an application that resides on WebSphere Application Server.

   • Update a file.

     This topic provides an example for updating a file on WebSphere Application Server. When you update a file, the deployed file is uninstalled and the updated file is installed.

   • Delete a file.

     This topic provides an example for deleting a file on WebSphere Application Server. When you delete a file, the deployed file is uninstalled.

2. Save your changes to the master configuration repository.

3. Synchronize changes to the master configuration across the nodes for the changes to take effect.

What to do next

Related concepts

Related tasks

Related information