Use this page to view composition unit settings and to change the configuration properties of a composition unit. The specific settings that are available for configuration can vary, depending upon the contents of the composition unit. For example, there are additional configuration settings if the asset contained in the composition unit is an SCA composite, or an OSGi application.
To view this administrative console page, click
. The deployed asset is a composition unit of the business-level application.Specifies a unique identifier for a composition unit that is registered in the application management domain.
The identifier has the format WebSphere:unit_typename=unit_name. For example, for the MyApp.jar asset, the backing identifier might be WebSphere:assetname=MyApp.jar.
You cannot change the identifier on this page.
Data type | String |
Units | Configuration unit identifier |
Specifies the 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 that you 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 |
Specifies whether to start the composition unit when the product 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 |
Specifies whether the product restarts the composition unit after the composition unit is updated.
The 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.
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 |
Specifies the current targets for the composition unit.
To change the deployment targets, click Modify targets then select a different set of deployment targets from the list of available clusters and servers.
For SCA, you must specify only a single server or cluster as the target. Do not map an SCA composition unit to multiple servers or clusters.
Specifies the component names and component implementations of SCA composites in the application.
Column | Description |
---|---|
Component Name | Specifies the name of a component associated with the SCA composite. |
Component Implementation | Specifies the name of the class or code implementing the component. |
None indicates that the SCA composite does not have defined components.
Specifies the names and values of SCA composite properties in the application.
Column | Description |
---|---|
Property Name | Specifies the name of an SCA composite property. |
Property Value | Specifies the value of the property. |
None indicates that the SCA composite does not have defined name-value properties.
Specifies the sources and targets of wires in the SCA composite.
Column | Description |
---|---|
Wire Source | Specifies the source of a wire in the SCA composite. |
Wire Target | Specifies the target of the wire. |
None indicates that the SCA composite does not have defined wires.
The deployment status shows whether updates are available for the EBA asset that is contained in the composition unit. If a new version of an EBA asset is available, and all bundle downloads for the asset are complete, you can update the EBA composition unit so that the business-level application uses the latest configuration. You do not have to update the composition unit every time you update the asset.
If the status is "New OSGi application deployment available", the Update to latest deployment ... button is available. Click this button to bring the EBA composition unit up-to-date and run the updated business-level application. If any of the updates need configuration changes, a wizard prompts you to update the configuration information.
When you save the changes to the EBA composition unit, the associated business-level application is updated to use the new configuration. If the business-level application is running, the bundle and configuration updates are applied immediately. If possible (that is, depending on the nature of the updates) the system applies the updates without restarting the application. Updates that pull in new use bundles at run time prompt a full restart of the application. Updates that pull in new provision bundles might also prompt a full application restart.