Set options settings

Use this page to specify options for the composition unit to be added to the business-level application. The product supplies default values for the options if you do not specify a value.

To view this administrative console page, click Applications > Application Types > Business-level applications > application_name . On the business-level application settings page, specify the type of composition unit to add:

Backing identifier

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,unit_typeversion=version_number. For example, for the MyApp.jar asset, the backing identifier might be WebSphere:assetname=MyApp.jar.

Data type String
Units Composition unit identifier

Name

Specifies the name of the composition unit.

For example, for the MyApp.jar asset, the name might be MyApp.jar.

A unit name cannot begin with a period (.), cannot contain leading or trailing spaces, and cannot contain any of the following characters:

Table 1. Characters that you cannot use in a name. The product does not support these characters in a name.
Unsupported characters
  forward slash $   dollar sign '  single quote mark
\  backslash =   equal sign " double quote mark
* asterisk % percent sign |   vertical bar
,  comma +   plus sign <  left angle bracket
:  colon @ at sign >  right angle bracket
;  semi-colon #   hash mark & ampersand (and sign)
? question mark ]]> No specific name exists for this character combination
Data type String

Description

Specifies a description for the composition unit.

Starting weight

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

Start composition unit upon distribution

Specifies whether to start the composition unit after the product distributes the composition unit to other locations.

The default is not to start the composition unit.

Data type Boolean
Default false

Restart behavior on update

Specifies whether the product restarts deployment targets after updates to the composition unit.

Usually, a composition unit is mapped to one or more deployment targets. This setting determines whether the product restarts those targets after editing the composition unit.

Table 2. Restart behavior on update options. Depending on your selection, the product restarts all target nodes, the nodes controlled by sync plug-ins, or no nodes.
Option Description
ALL The product restarts each target node of the composition unit after editing the composition unit.
DEFAULT The product restarts the nodes controlled by the sync plug-ins after editing the composition unit.
NONE The product does not restart nodes after editing the composition unit.



Related concepts
Business-level applications
Related tasks
Creating business-level applications with the console
Related reference
Business-level application collection
Map target settings


Terms and conditions for information centers | Feedback

Last updatedLast updated: Jan 16, 2013 3:37:33 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v700osgijpa&product=was-nd-mp&topic=urun_rapp_bla_create_cuoptions
File name: urun_rapp_bla_create_cuoptions.html