Updating enterprise application files

We can update Java EE application files deployed on a server.

Update the 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 the deployment targets. WAS V 7.x and later supports Java EE 5 enterprise apps and modules.

If deploying Java EE 5 modules, verify the deployment target and its node support V7.x. We can deploy Java EE 5 modules to V7.x servers or to clusters that contain Version 7.x cluster members only. We cannot deploy Java EE 5 modules to servers on V6.x nodes or to clusters that contain V6.x cluster members.

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

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.

 

1. Determine which method to use to update the application files.

   WAS ND v7.0 provides several ways to update modules.

2. Update the application files using
   • Administrative console

   • wsadmin scripts

   • Java APIs

   • WebSphere rapid deployment of Java EE applications

   In some situations, we can update applications or modules without restarting the appserver using hot deployment. Do not use hot deployment unless we 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

 

Next steps

Save the changes to the admin configuration.

When saving the configuration, synchronize the configuration with the nodes where the application is expected to run.

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 the 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.

Ways to update enterprise application files
Updating enterprise apps with the console
Preparing for application update settings
Hot deployment and dynamic reloading

 

Related concepts

Installable enterprise module versions

 

Related tasks

Starting applications with scripting
Updating installed applications with wsadmin
Manage applications through programming
Troubleshooting deployment
Deploy enterprise apps

 

Related information

IBM WebSphere Developer Technical Journal: System management for WAS V6 -- Part 5 Flexible options for updating deployed applications
WebSphere rapid deployment of Java EE applications