Business-level application settings

Use this page to configure a business-level application.

To view this administrative 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

Specifies a 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:

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 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 you 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.

Table 2. Deployed assets button descriptions. Use the buttons to add or delete composition units.
Button Resulting action
Add > Add Asset For assets that contain Java Platform, Enterprise Edition (Java EE) applications or modules, opens the application installation wizard. On the Select installation options page of this wizard, you can specify a Business-level application name value that identifies the target business-level application. On the Map shared library relationships page, you 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

Specifies the business-level applications in this business-level application.

The table provides a name, description, and the runtime status of each contained business-level application.

Table 3. 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 tasks
Creating business-level applications
Creating business-level applications with the console
Listing assets using programming
Related reference
Asset collection
Shared library relationship and mapping settings
Object names: What the name string cannot contain


Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 7:16:32 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-express-iseries&topic=urun_rapp_inst_bla
File name: urun_rapp_bla_inst.html