Composition unit settings


 

+

Search Tips   |   Advanced Search

 

To edit composition unit settings...

Applications | Application Types | Business-level applications | application_name | composition_unit_name

Name

Logical name for the composition unit. We cannot change the name on this page.

Description

Description for the composition unit. We cannot change the description on this page.

Backing identifier

Unique identifier for a composition unit that is registered in the application management domain.

The identifier has the following format: WebSphere:unit_typename=unit_name. For example, for the MyApp.jar asset, the backing identifier might be WebSphere:assetname=MyApp.jar.

We cannot change the identifier on this page.

Data type String
Units Configuration unit identifier

Starting weight

Order in which composition units are started when the server starts. The starting weight is like the startup order. The composition unit with the lowest starting weight is started first.

The value set for Starting weight determines the importance or weight of a composition unit within the business level application. For example, for the most important composition unit within a business-level application, specify 1 for Starting weight. For the next most important composition unit within the business-level application, specify 2 for Starting weight, and so on.

Data type Integer
Default 1
Range 0 to 2147483647

Start on distribution

Whether to start the composition unit when WAS ND distributes the composition unit to other locations.

The default is not to start the composition unit.

This setting applies to asset or shared library composition units. This setting does not apply when the composition unit is a business-level application.

Data type Boolean
Default false

Recycle behavior on update

Whether WAS restarts the composition unit after the composition unit is updated.

Default is to restart the composition unit after partial updating of the composition unit.

This setting applies to asset or shared library composition units. This setting does not apply when the composition unit is a business-level application.


Table 1. Option descriptions

Option Description
ALL Restarts the composition unit after the entire composition unit is updated
DEFAULT Restarts the composition unit after the part of the composition unit is updated
NONE Does not restart the composition unit after the composition unit is updated

Current target

Existing deployment target for the composition unit.

To change the deployment target, click Modify target and select a different deployment target from the list of available clusters and servers.





Related concepts


Business-level applications

 

Related tasks


Create business-level applications

 

Related


Business-level application collection
Map target settings

 

Related information

Administrative console buttons