Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment


Manage applications through programming

Through Java MBean programming, you can install, update, and delete a Java Platform, Enterprise Edition (Java EE) application on a WAS deployment target.

This task assumes a basic familiarity with MBean programming. For information on MBean programming, see MBean Java API documentation. In this information center, click Reference > Mbean interfaces.

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

Before you can install or change an application on a deployment target, first create or update the application and assemble it using an assembly tool.

Besides installing, uninstalling, and updating applications through programming, you can additionally install, uninstall, and update Java EE applications through the admin console or wsadmin.sh. All three ways provide identical updating capabilities.


Procedure

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

    • Access the application management function.

      This topic provides examples to access the application management functionality:

      • From WAS code

      • From outside WAS

      • When WAS is not running

    • Install an application.

      This topic provides an example for initially installing an application on a deployment target such as a server or cluster.

    • Uninstall an application.

      This topic provides an example for uninstalling an application that resides on a deployment target.

    • 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 a server or cluster with a new application. When you completely update an application, the deployed application is uninstalled and the new EAR file is installed.

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

      This topic provides an example that you can use to add, update, or delete part of an application on a server or cluster.

    • Edit an application.

      This topic provides an example that you can use to edit an application on a server or cluster.

    • Add a module.

      This topic provides an example for adding a module to an application that resides on a server or cluster.

    • Update a module.

      This topic provides an example for updating a module that resides on a server or cluster. 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 a server or cluster. 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 a server or cluster.

    • Update a file.

      This topic provides an example for updating a file on a server or cluster. 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 a server or cluster. 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

If we have further application updates, you can do the updates through programming, the admin console, or wsadmin.sh.

We can use the common deployment framework to add additional logic to application management operations. See Extend application management operations through programming. The tasks that the extensions provide are available through all the administrative clients, such as wsadmin.sh, the admin console, or through programmatic APIs that the AppManagement MBean provides.


Related


Application management
Access the application management function
Install an application through programming
Uninstall an application through programming
Manipulating additional attributes for a deployed application
Sharing sessions for application management
Update an application through programming
Add to, updating, or deleting part of an application through programming
Edit applications
Prepare a module and adding it to an existing application through programming
Prepare and updating a module through programming
Delete a module through programming
Add a file through programming
Update a file through programming
Delete a file through programming
Extend application management operations through programming
Ways to install enterprise applications or modules
Ways to update enterprise application files
Deploy and administering enterprise applications
Get started with wsadmin scripting
Assembling applications

+

Search Tips   |   Advanced Search