Business-level application settings

WAS v8.5 > Reference > Sets
Business-level application settings page

Use this page to configure a business-level application.
To view this dmgr console page, click Applications > Application Types > Business-level applications > application_name.
This page is the same as the Adding composition unit to the business-level application page.

Name

Logical name for the application. An application name must be unique within a cell and cannot contain an unsupported character.
An application name cannot begin with a period (.), cannot contain leading or trailing spaces, and cannot contain any of the following characters:
Characters that we cannot use in a name. WAS v8.5 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

Information Value
Data type String

Description for the business-level application.

Deployed assets

Specifies the asset and shared library composition units in the business-level application. A composition unit is a registered asset or shared library that has additional configuration information, which we specify when adding the asset to the application.
For each composition unit, the table provides a name, description, asset type, and the runtime status of the composition unit.
Deployed assets button descriptions. Use the buttons to add or delete composition units.

Button Resulting action
Add > Add Asset For assets containing Java EE applications or modules, opens the application installation wizard. On the Select installation options page of this wizard, we can specify a Business-level application name value that identifies the target business-level application. On the Map shared library relationships page, we can identify the shared library files that individual modules need to run and specify composition unit names for the module-shared library relationships.
For non-Java EE assets, opens a wizard that helps you add an asset as a composition unit to your business-level application.
Add > Add Shared Library Opens a wizard that helps you add a library file as a composition unit to your business-level application.
Delete Deletes the composition unit from the product configuration repository and deletes the application binaries from the file system of all nodes where the application modules are installed.
On single-server installations, deletion occurs after the configuration is saved.

Business-level applications

Business-level applications in this business-level application.
The table provides a name, description, and the runtime status of each contained business-level application.
Business-level applications button descriptions. Use the buttons to add or delete composition units.

Button Resulting action
Add Opens a wizard that helps you add a business-level application to your business-level application.
Delete Deletes the business-level application from the product configuration repository and deletes the application binaries from the file system of all nodes where the application modules are installed.
On single-server installations, deletion occurs after the configuration is saved.

Related concepts:

Business-level applications

Related

Create business-level applications
Create business-level applications with the console
List assets using programming

Reference:

Asset page
Shared library relationship and mapping settings
Object names: What the name string cannot contain

+
Search Tips | Advanced Search

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

Button	Resulting action
Add > Add Asset	For assets containing Java EE applications or modules, opens the application installation wizard. On the Select installation options page of this wizard, we can specify a Business-level application name value that identifies the target business-level application. On the Map shared library relationships page, we can identify the shared library files that individual modules need to run and specify composition unit names for the module-shared library relationships. For non-Java EE assets, opens a wizard that helps you add an asset as a composition unit to your business-level application.
Add > Add Shared Library	Opens a wizard that helps you add a library file as a composition unit to your business-level application.
Delete	Deletes the composition unit from the product configuration repository and deletes the application binaries from the file system of all nodes where the application modules are installed. On single-server installations, deletion occurs after the configuration is saved.

Button	Resulting action
Add	Opens a wizard that helps you add a business-level application to your business-level application.
Delete	Deletes the business-level application from the product configuration repository and deletes the application binaries from the file system of all nodes where the application modules are installed. On single-server installations, deletion occurs after the configuration is saved.