You can update business-level applications by deleting or changing composition units, or
by mapping composition units to different deployment targets.
Before you begin
Determine the changes that you want to make to your application. Also, determine whether the
changed application can run on your deployment targets.
The administrative console Server pages show the versions for deployment targets.
If you want to change a composition unit that contains an enterprise bundle archive (EBA) asset,
see information about modifying the configuration of EBA assets.
About this task
Updating consists of adding new composition units to an application, replacing or removing
composition units, or mapping composition units to different deployment targets.
You 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. You 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, you can use the wsadmin tool.
Procedure
- Delete composition units from your business-level application.
- Go to the business-level application settings page.
Click in the console navigation tree.
- Select each composition unit of the application that you want to delete.
- Click Delete.
- 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 your
business-level application.
- Update asset binary files or shared libraries as needed.
- If you are adding new assets that are not registered with the product management domain, import
the assets.
- If you are updating existing assets, use the Update option to update
asset files.
Before updating a shared library, you must manually stop all Java EE applications that depend on
that shared library. After updating the shared library, manually restart the Java EE applications.
You might need to synchronize configuration changes to the target node.
Java EE applications do not automatically restart when a shared library is updated.
- On the business-level application settings page, specify the type of composition unit to
add.
- To add an asset, under Deployed assets, click .
- To add a shared library, under Deployed assets, click .
- To add a business-level application, under Business-level applications,
click Add.
- On the New composition unit page, select a unit from the list of available
units, and then click Continue.
- On the Set options page, change the composition unit settings as needed,
and then click Next.
- On the Map composition unit to a target page, change the deployment target
as needed, and then click Next.
This page is not shown when you add a business-level application.
- On the Summary page, click Finish.
- 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.
- On the Adding composition unit to the business-level application page,
click Save.
- 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.
- On the composition unit settings page, select the composition unit that you want to
change.
- Under Current targets, click Modify Target.
- On the Map targets page, change the target.
- From the list of available clusters and servers, select a different deployment target.
- Click >> to add the deployment target to the
Selected list.
- To remove a deployment target from the Selected list, select the target
and click <<.
- Click OK.
The business-level application settings page displays the selected deployment
target.
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.