Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

EJB: Overview

Configuration Options     Related Tasks     Related Topics

Use this page to view basic information about the selected EJB.

Configuration Options

Name Description
Name

The name of this application deployment.

Archive Version

The archive version, from the manifest or overridden during deployment.

Plan Version

The deployment plan version, specified during deployment.

Application Name

The name of this application deployment.

EJB Module Name

The name of this module.

Bean Name

The name of this bean.

Path

The URI, located on the Administration Server, of the original source files for this application.

Relative paths are based on the root of the Administration Server installation directory. It is highly recommended that you use absolute paths to minimize possible issues when upgrading the server.

If the application is not being staged (StagingMode==nostage) then the path must be valid on the target server.

The path to an Enterprise application (EAR) is the location of the EAR file or the root of the EAR if it is unarchived. e.g. Path="myapps/app.ear" is valid. If the application is a standalone module, then the path is the parent directory of the module. For example, if the module is located at myapps/webapp/webapp.war, the Path="myapps/webapp" is correct, whereas Path="myapps/webapp/webapp.war" is incorrect.

MBean Attribute:
ApplicationMBean.Path

Changes take effect after you redeploy the module or restart the server.

Path

The path to the source of the deployable unit on the Administration Server.

Rules:

If the source path is relative, it is resolved relative to InstallDir/app if InstallDir is not null; Otherwise, it is resolved relative to domain root.

Use AbsoluteSourcePath to get a fully resolved value.

MBean Attribute:
AppDeploymentMBean.SourcePath

Changes take effect after you redeploy the module or restart the server.

Install Directory

The path to application's install-root directory, relative to the domain/config/deployments directory.

When the Install Directory is specified, SourcePath, PlanDir, and PlanPath are derived from this path, and need not be specified.

Default value for this is the name of the deployment.

MBean Attribute:
AppDeploymentMBean.InstallDir

Changes take effect after you redeploy the module or restart the server.

Deployment Plan

The path to the deployment plan document on Administration Server.

Rules:

If the plan path is a relative path, it is resolved relative to PlanDir if PlanDir is not null; otherwise, it is resolved relative to domain root.

Use AbsolutePlanPath to get a fully resolved value.

If there is no plan, this returns no plan specified.

MBean Attribute:
AppDeploymentMBean.PlanPath

Staging Mode

The mode that specifies whether an application's files are copied from a source on the Administration Server to the Managed Server's staging area during application preparation.

Security Model

The security model specifies how this deployment should be secured.

Deployment Order

An integer value that indicates when this unit is deployed, relative to other deployable units on a server, during startup.

Units with lower values are deployed before those with higher values.

MBean Attribute:
AppDeploymentMBean.DeploymentOrder

Changes take effect after you redeploy the module or restart the server.

Deployment Principal Name

A string value that indicates what principal should be used when deploying the file or archive during startup and shutdown. This principal will be used to set the current subject when calling out into application code for interfaces such as ApplicationLifecycleListener. If no principal name is specified, then the anonymous principal will be used.

MBean Attribute:
BasicDeploymentMBean.DeploymentPrincipalName

Changes take effect after you redeploy the module or restart the server.

Related Tasks

Related Topics


Back to Top