WAS v8.5 > Administer applications and their environment > Deploy enterprise applications > Update enterprise application files

Ways to update enterprise application files

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

Ways to update application files. We can update application files using the console, wsadmin, programming, or deployment tools

Option Method Comments Start after update
Administrative console update wizard

See Update enterprise applications with the console.

To remove a single file from a Java EE application or module, see the topic on removing enterprise files.

Briefly, do the following:

  1. Go to the Enterprise applications page. Click Applications > Application Types > WebSphere enterprise applications in the console navigation tree.

  2. Select the application to update and click Update.

  3. On the Prepare for application update page, identify the application, module or files to update and click Next.

  4. Complete steps in the update wizard and click Finish.

On the Prepare for application update page:

  • Use Full application to update an .ear file.
  • Use Single module to update a .war, .sar, enterprise bean .jar, or connector .rar file.

  • Use Single file to update a file other than an .ear, .war, .sar, EJB .jar, or .rar file.

  • Use Partial application to update or remove multiple files.

On the Enterprise applications page, select the updated application and click Start.
Monitored directory If you installed an application or module by adding it to a monitored directory, we can update it by adding an application or module that has the same file name to the monitored directory. Refer to the topic on installing enterprise application files by adding them to a monitored directory. After application or module installation, the product starts it automatically.
Application properties files Create a properties file that specifies to update application files. Then, run the wsadmin applyConfigProperties command in any of the following ways:

  • In a script
  • At a command prompt
  • By adding the properties file to a dragDropDeployableApps/deploymentProperties monitored directory

Refer to the topic on installing enterprise application files by adding properties files to a monitored directory. After application or module installation, the product starts it automatically.
wsadmin scripts

See the topic on updating installed applications using wsadmin.sh.

Use the update command or the updateInteractive command in a script or at a command prompt. For more information on the update and updateInteractive commands, see the topic on commands for the AdminApp object. The Getting started with wsadmin scripting topic provides an overview of wsadmin. Start the application using the invoke command and the startApplication attribute. For more information about the invoke command, see the topic on commands for the AdminControl object.
Java application programming interfaces

See the topic on using administrative programs (JMX).

Update deployed applications by completing the steps in the topic on managing applications through programming. Update an application in the following ways:

  • Update the entire application

  • Add to, replace or delete multiple files in an application

  • Add a module to an application
  • Update a module in an application
  • Delete a module in an application

  • Add a file to an application
  • Update a file in an application
  • Delete a file in an application

  • Invoke the AdminApp startApplication command.
  • Invoke the startApplication method on an ApplicationManager MBean using AdminControl.

Rapid deployment tools

See topics under Rapid deployment of J2EE applications.

Briefly, do the following:

  1. Update your J2EE application files.

  2. Set up the rapid deployment environment.

  3. Create a free-form project.
  4. Launch a rapid deployment session.
  5. Drop your updated application files into the free-form project.

Rapid deployment tools offer the following advantages:

  • We do not need to assemble your J2EE application files prior to deployment.
  • We do not need to use other installation tools mentioned in this table to deploy the files.

Use any of the previous options to start the application. Clicking Start on the Enterprise applications page is the easiest option.
Hot deployment and dynamic reloading Briefly, do the following:

  1. Update the application (.ear), web module (.war), enterprise bean .jar or HTTP plug-in configuration file.
  2. Follow instructions in Hot deployment and dynamic reloading to update your file.

If you are new to WebSphere Application Server, use the dmgr console to update applications. That option is easier.
Hot deployment and dynamic reloading is more difficult to complete. You must directly manipulate the application or module file on the server where the application is deployed.
Use any of the previous options to start the application. Clicking Start on the Enterprise applications page is the easiest option.

We can update .ear, enterprise bean .jar, web module .war, Session Initiation Protocol (SIP) archive (.sar), connector .rar, application client .jar, and any other files used by an installed application.

If the application is updated while it is running, WAS automatically stops the application, updates the application logic and restarts the application. If the application does not start automatically, start it manually using one of the Starting options. For more 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.

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, you must 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.


Related


Update enterprise application files
Remove enterprise files
Install enterprise application files by adding them to a monitored directory
Install enterprise application files by adding properties files to a monitored directory
Get started with wsadmin scripting
Start applications using wsadmin.sh
Use administrative programs (JMX)
Manage applications through programming
Start an application through programming
Update installed applications using wsadmin.sh


Reference:

Enterprise application page
Commands for the AdminApp object using wsadmin.sh
Commands for the AdminControl object using wsadmin.sh


Related information:

IBM WebSphere Developer Technical Journal: System management for WAS V6 -- Part 5 Flexible options for updating deployed applications

Rapid deployment of J2EE applications


+

Search Tips   |   Advanced Search