Update business-level applications

We can update business-level applications by deleting or changing composition units, or by mapping composition units to different deployment targets.

Determine the changes to make to the application. Also, determine whether the changed application can run on the deployment targets.

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

To change a composition unit containing an enterprise bundle archive (EBA) asset, see information about modifying the configuration of EBA assets.

Update consists of adding new composition units to an application, replacing or removing composition units, or mapping composition units to different deployment targets.

We can add an asset or shared library composition unit to multiple business-level applications. However, each composition unit for the same asset must have a unique composition unit name. We can add a business-level application composition unit to more than one business-level application.

This topic describes how to update business-level applications using the administrative console. Alternatively, we can use the wsadmin tool.

Tasks

• Delete composition units from a business-level application.
  1. Go to the business-level application settings page.

     Click Applications > Application Types > Business-level applications > application_name in the console navigation tree.

  2. Select each composition unit of the application to delete.

  3. Click Delete.

  4. On the Delete composition unit from business-level application page, confirm the deletion and click OK.

• Add new or updated assets, shared libraries, or other business-level applications to a business-level application.
  1. Update asset binary files or shared libraries as needed.

  2. If we are adding new assets that are not registered with the product management domain, import the assets.

  3. If we are updating existing assets, use the Update option to update asset files.

     Before updating a shared library, we must manually stop all Java EE applications that depend on that shared library. After updating the shared library, manually restart the Java EE applications. We might need to synchronize configuration changes to the target node. Java EE applications do not automatically restart when a shared library is updated.

  4. On the business-level application settings page, specify the type of composition unit to add.

     • To add an asset, under Deployed assets, click Add > Add Asset.

     • To add a shared library, under Deployed assets, click Add > Add Shared Library.

     • To add a business-level application, under Business-level applications, click Add.

  5. On the New composition unit page, select a unit from the list of available units> Continue.

  6. On the Set options page, change the composition unit settings as needed, and then click Next.

  7. On the Map composition unit to a target page, change the deployment target as needed> Next.

     This page is not shown when we add a business-level application.

  8. On the Summary page, click Finish.

  9. If the product adds the unit successfully, click Manage application.

     If the unit addition is not successful, read the messages, and try adding the unit again. Correct the errors noted in any messages.

  10. On the Adding composition unit to the business-level application page, click Save.

  11. Repeat these steps to add any other assets, shared libraries, or applications needed by the business-level application.

  The business-level application settings page displays the configuration unit names.

• Map composition units to different deployment targets.

  1. On the composition unit settings page, select the composition unit to change.

  2. Under Current targets, click Modify Target.

  3. On the Map targets page, change the target.

     1. From the list of available clusters and servers, select a different deployment target.

     2. Click >> to add the deployment target to the Selected list.

     3. To remove a deployment target from the Selected list, select the target and click <<.

     4. Click OK.

  The business-level application settings page displays the selected deployment target.

What to do next

Save the changes to the administrative configuration.

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

Related:

Installable enterprise module versions

Import assets

Update assets

Deploy and administering business-level applications

Modify the configuration of an EBA asset

Server collection

Business-level application settings

Add composition unit settings

Set options settings

Map target settings

Composition unit settings