Target specific application status

Use this page to view mappings of deployed applications or modules to servers.

Also use this page to enable or disable the automatic starting of an application when the server on which the application resides starts.

To view this administrative console page, click Applications > Application Types > WebSphere enterprise applications > application_name > Target specific application status.

When security is enabled, a separate application list is shown for each of your administrative roles. Supported roles include monitor, configurator, operator, administrator, deployer, and administrative security manager. For example, when you have the administrator role, the statement "You can administer the following resources" is shown followed by a list of servers that you can administer.

Target

States the name of the target server to which the application or module maps. You specify the target on the Manage modules page accessed from the settings for an application.

Node

Specifies the node name if the target is a server.

Version

Specifies the version level of the target. The target can be a Version 7.x, 6.x or 5.x deployment target.

A 7.x deployment target is a server with all members on a WebSphere® Application Server Version 7.0 or later product.

A 6.x deployment target is a server with all members on a WebSphere Application Server Version 6 product.

A 5.x deployment target is a server with at least one member on a WebSphere Application Server Version 5 product.

An application, enterprise bean (EJB) module, Session Initiation Protocol (SIP) module (SAR), or Web module must be installed on a Version 7.x target under any of the following conditions:

If a module supports Java 2 Platform, Enterprise Edition (J2EE) 1.4, then you must install the module on a Version 6.x or 7.x deployment target. Modules that call a 6.1.x API or use a 6.1.x feature can be installed on a 6.1.x or 7.x deployment target. Modules that call a 6.0.x API or use a 6.0.x feature can be installed on a 6.0.x, 6.1.x or 7.x deployment target. Modules that require 6.1.x feature pack functionality can be installed on a 7.x deployment target or on a 6.1.x deployment target that has been enabled with that feature pack.

If JavaServer Pages (JSP) precompilation, EJB deployment (ejbdeploy), or Web Services deployment (wsdeploy) are enabled, then you can deploy applications to only those targets that have same product version as the deployment manager. If applications are targeted to servers that have an earlier version than the deployment manager, then you cannot deploy to those targets. Thus, if JSP precompilation, ejbdeploy, or wsdeploy are enabled, then you must deploy the application on a 6.1.x or 7.x target.

You can install an application or module developed for a Version 5.x product on a 7.x, 6.x or 5.x deployment target.

Similarly, a resource adapter (connector) module, or RAR file, developed for a Version 5.x product can reside on a 7.x, 6.x or 5.x target, provided the module does not support Java Cryptography Architecture (JCA) 1.5 and does not call any 7.x or 6.x runtime application programming interfaces (APIs). If the module supports JCA 1.5 or calls a 7.x or 6.x API, then the module must reside on a 7.x or 6.x target.

Auto Start

Specifies whether the application modules installed on the target server are started (or enabled) when the server starts. This setting specifies the initial state of application modules. A Yes value indicates that the corresponding modules are enabled and thus are accessible when the server starts. A No value indicates that the corresponding modules are not enabled and thus are not accessible when the server starts.

By default, Auto Start is enabled. Thus, by default an installed application starts automatically when the server on which the application resides starts.

If you have an administrative role with an authority higher than monitor, you can enable and disable the automatic starting of the application. To disable the automatic starting of the application, enable the Select check box beside the target server and click Disable Auto Start. When automatic starting is disabled, the application does not start when its server starts. To enable the automatic starting of the application, select the target and click Enable Auto Start.

Application Status

Indicates whether the application deployed on the application server is started, stopped, or unknown.

Table 1. Application status. Shows whether the application is running.
Started Started Application is running.
Partial Start Partial Start Application is in the process of changing from a Stopped state to a Started state. Application is starting to run but is not fully running yet. The application might be in the Partial Start state because one of its application servers is not started.
Stopped Stopped Application is not running.
Partial Stop Partial Stop Application is in the process of changing from a Started state to a Stopped state. Application has not stopped running yet.
Unknown Unknown Status cannot be determined.

An application with an unknown status might, in fact, be running but have an unknown status because the server running the administrative console cannot communicate with the server running the application.

Pending Pending Status is temporarily unknown pending an event that a user did not initiate, such as pending an asynchronous call.
Not applicable Not applicable Application does not provide information as to whether it is running.

The status of an application on a Web server is always Unknown.




Related tasks
Configuring enterprise application files
Disabling automatic starting of applications
Related reference
Manage modules settings
Reference topic    

Terms of Use | Feedback

Last updated: Oct 20, 2010 11:50:58 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-base-iseries&topic=urun_rtargetmap
File name: urun_rtargetmap.html