Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Deploy and administering enterprise applications
Update enterprise application files
We can update Java EE application files deployed on a server.
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. v8.0 supports Java EE 6 enterprise applications and modules.
If you are deploying Java EE 6 modules, ensure that the deployment target and its node support v8.0. We can deploy Java EE 6 modules to v8.0servers or to clusters that contain v8.0 cluster members only. We cannot deploy Java EE 6 modules to servers on v7.x or 6.x nodes or to clusters that contain v7.x or 6.x cluster members.
The admin console Server collection pages show the versions for deployment targets.
Update 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
- Determine which method to use to update the application files. The product provides several ways to update modules.
- Update the application files using
- Administrative console
- Drag and drop to a monitored directory
- 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.
- If needed, restart the application manually so the changes take effect. Start the deployed application files using
- Administrative console
- wsadmin startApplication
- Java programs that use ApplicationManager or AppManagement MBeans
When you update an application while it is running, the product automatically stops the application or only its changed components, updates the application logic, and restarts the stopped application or its components.
New feature: If you update module metadata while an application is running, restarting the application might not be sufficient for the changes to take effect. For example, if you change descriptors in running Java EE 6 applications that use annotations, reinstall the application. If you change classes that introduce, remove, or alter class hierarchies within an application, and those changes impact annotated classes, you also must reinstall the application.
What to do next
Save the changes to your administrative configuration.
When saving the configuration, synchronize the configuration with the nodes where the application is expected to run.
- We must use either the admin console or wsadmin scripting to synchronization a node. Of these two options, is the best way to perform this operation. The Nodes panel in the administrative console includes the Synchronize operation.
If you need to use wsadmin scripting to synchronize a node, use the NodeSync mbean's sync() command.
- Do not restart the node agent as part of the synchronize node process. Administration operations, such as node synchronization for application deployment, or updates that take place while the node agent is starting, that are initiated through the node agent, and affect the application servers, fail until the node agent has a chance to discover the application servers.
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.
Related
Ways to update enterprise application files
Update enterprise applications with the console
Prepare for application update settings
Hot deployment and dynamic reloading
Assembly tools
Installable enterprise module versions
Start or stop enterprise applications
Start applications using wsadmin.sh
Install enterprise application files by adding them to a monitored directory
Update installed applications using wsadmin.sh
Manage applications through programming
Troubleshoot deployment
Configure enterprise application files
Deploy and administering enterprise applications
Related
Server collection
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