WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Displaying deployment environment status using the command line

You can display the current status of a deployment environment using the wsadmin command.

Before you begin

The admin client must connect to the deployment manager for which you are displaying the status.

Required security role for this task: When security and role-based authorization are enabled, you must use a userid and password with administrator or operator authority to perform this task.

About this task

This task displays the current status of a deployment environment and uses the wsadmin command.

Procedure
  1. Open a command window. .

    The wsadmin command can be found at either the <ESB>/profiles/<dmgr profile>/bin directory, or the <ESB>/bin directory

  2. At the command prompt, enter the wsadmin command to enter the command environment.
    Note: Make sure wsadmin connects to the correct deployment manager, when running in connected mode.
  3. Use the showDeploymentEnvStatus command to show the current status of the deployment environment.
    Note: If administrative security is on, you will be prompted for a user ID and password, if you do not supply it in the command.
    The following table lists the results that might be returned.
    Note: Some of the states listed in the table are valid for configured topologies only. The states that are apply to configured topologies only are noted as such.
    Table 1. States of a topology instance in order of least to most available
    State Description
    Incomplete The deployment environment is not missing any elements but is incomplete in some way.

    Incomplete state may mean the deployment environment is missing a required role, node, comp or dependencies .

    The warning message contains additional details.

    Complete This state is also known as Not configured and it means that the configuration is known and complete but has not yet been generated.
    Configured This means the configuration is in synch.
    Partially configured The deployment environment has been generated but deferred configuration has not been completed.
    Unknown The system cannot determine the current state of the deployment environment. A resync operation could be performed on this state.
    Stopped

    State applies to configured topologies only.

    All deployment targets in the topology are stopped.
    Running

    State applies to configured topologies only.

    The deployment environment is available and all functions are running.
    Partially started

    State applies to configured topologies only.

    The deployment environment is available but at least one function is partially running.
    Starting

    State applies to configured topologies only.

    The deployment environment is starting.
    Partially stopped

    State applies to configured topologies only.

    The deployment environment is available but at least one function is stopped or partially stopped.
    Stopping

    State applies to configured topologies only.

    The deployment environment is stopping
    Unavailable

    State applies to configured topologies only.

    The deployment environment state is unavailable.

Example

This example displays the status of a deployment environment (MyDepEnv) on the host (myDmgr) with administrative security enabled.
Note: If you are running the admin client from the deployment manager bin folder, you do not need to include the -host and -port parameters in the command.
wsadmin -connType SOAP -host myDmgr -port 8879 -user dmgradmin -password dmgrpass
> $AdminTask showDeploymentEnvStatus {-topologyName myDepEnv}
The -connType parameter specifies the type of connection to be used; the default argument is SOAP.
Note: As the default is SOAP, you do not need to give explicitly if SOAP is the connection type that is being used.
The -host parameter specifies the host used for the SOAP or RMI connection. The default value for -host is the local host.
Note: If the node is running on the local host, you don not need to specify -host
Note: If you disable administrative security, you do not need to provide a user ID and password.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tadm_dispdepenvdefstatcmd.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).