InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.1: Administering applications (overview) >
Enterprise application properties

6.6.1.0: Enterprise application properties

Key:
Property name in the Java-based administrative console Applies to Java administrative console of Advanced Edition Version 4.0
Property name in the Web-based administrative console Applies to Web administrative console of Advanced Single Server Edition Version 4.0
Property name in the application client resource configuration tool Applies to Application Client Resource Configuration Tool

Archive URL  Property name in the Web-based administrative console
The path to the EAR file for the application
Context Root  Property name in the Web-based administrative console
The context root of the Web application contained in this enterprise application.

The context root is combined with the defined servlet mapping (from the WAR file) to compose the full URL that users type to access the servlet. For example, if the context root is /gettingstarted and the servlet mapping is MySession, then the URL is http://host:port/gettingstarted/MySession.

EnterpriseApp Name  Property name in the Java-based administrative console or Name  Property name in the Java-based administrative console  Property name in the Web-based administrative console
A logical name for the application. The name will be displayed in administration and configuration tools.
Execution State  Property name in the Java-based administrative console  Property name in the Web-based administrative console
For Advanced Edition: The current state of the application, such as running or stopped

For Advanced Single Server Edition: The execution state that you would like the application to have, the next time you start the product

Node  Property name in the Java-based administrative console
The administrative node with which the application is associated.
Path, or Remote Path on Server  Property name in the Web-based administrative console
The fully qualified path to the .ear, .jar, or .war file for which you are configuring an enterprise application

Use the first set of fields if the console and application files are on the same machine (whether or not the server is on that machine, too).

Use the second set of fields (including Remote Path...) if the application files already reside on the server machine, and the console is being run from a remote machine.

During application installation, application files are typically uploaded from a client machine containing the administrative console to the server machine, where they are deployed. In such cases, the Web browser running the administrative console is used to select EAR, WAR, or JAR modules to upload to the server machine.

In some cases, however, the application files will already reside on the file system of the machine running the application server. To have the application server install these files, (bypassing the upload stage), use the Remote Path option.

An example of the field value on Windows NT is C:\WebSphere\AppServer\installableApps\test.ear. You can optionally enter the application name to use for standalone modules (JAR, WAR) and the context root (used only for Web modules).

User/Role Mappings, Run As Mappings, Roles, Users, and Groups  Property name in the Java-based administrative console
See the properties for mapping security roles and "run as" roles to users and groups . This applies to Advanced Edition, but not to Advanced Single Server Edition.
Go to previous article: Administering applications (overview) Go to next article: 6.6.1.0.1.a: Assembly properties for security roles (application)

 

 
Go to previous article: Administering applications (overview) Go to next article: 6.6.1.0.1.a: Assembly properties for security roles (application)