Updating enterprise application files

You can update Java™ Platform, Enterprise Edition (Java EE) application files deployed on a server.

Before you begin

Update your Java EE application or modules and reassemble them using an assembly tool. Typical tasks include adding or editing assembly properties, adding or importing modules into an application, and adding enterprise beans, Web components, and files.

Also, determine whether the updated files can be installed to your deployment targets. WebSphere® Application Server Version 7.x supports Java EE 5 enterprise applications and modules.

If you are deploying Java EE 5 modules, ensure that the deployment target supports Version 7.x. You can deploy Java EE 5 modules only to Version 7.x and later servers. You cannot deploy Java EE 5 modules to Version 6.x deployment targets.

The administrative console Server collection pages show the versions for deployment targets.

About this task

Updating consists of adding a new file or module to an installed application, or replacing or removing an installed application, file or module. After replacement of a full application, the old application is uninstalled. After replacement of a module, file or partial application, the old installed module, file or partial application is removed from the installed application.

Procedure

  1. Determine which method to use to update your application files. The product provides several ways to update modules.
  2. Update the application files using
    • Administrative console
    • wsadmin scripts
    • Java application programming interfaces
    • WebSphere rapid deployment of Java EE applications

    In some situations, you can update applications or modules without restarting the application server using hot deployment. Do not use hot deployment unless you are an experienced user and are updating applications in a development or test environment.

  3. Start the deployed application files using
    • Administrative console
    • wsadmin startApplication
    • Java programs that use ApplicationManager or AppManagement MBeans

What to do next

Save the changes to your administrative configuration.

Next, test the application. For example, point a Web browser at the URL for a deployed application (typically http://hostname:9060/Web_module_name, where hostname is your valid Web server and 9060 is the default port number) and examine the performance of the application. If the application does not perform as desired, edit the application configuration, then save and test it again.




In this information ...


Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 20, 2010 11:50:58 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-base-iseries&topic=trun_app_upgrade
File name: trun_app_upgrade.html