startDeploymentEnv command

Use the startDeploymentEnv command to start the deployment environment.

This command starts all the clusters that are defined for the Deployment Environment. For example, if you chose RemoteMessagingAndSupport as your pattern, this command starts the three clusters (ApplicationTarget, Messaging, and Support) that were created as part of that configuration.

Note: If you are using a SOAP connection, this command can take longer to complete than the specified SOAP timeout value. To prevent an exception, make sure the value for the com.ibm.SOAP.requestTimeout property in the profile_root/properties/soap.client.props file is sufficient for the startDeploymentEnv command to finish running.

Required parameters

-topologyName name_of_topology: Specifies the name of the deployment environment that you are starting.

Optional parameters

None.

Example

Note: The examples are for illustrative purposes only. They include variable values and are not meant to be reused as snippets of code.

The following example uses startDeploymentEnv to start a deployment environment.

Jython example:

AdminTask.startDeploymentEnv('[-topologyName MyDepEnv]')

Jacl example:

$AdminTask startDeploymentEnv {-topologyName MyDepEnv }