Validating the deployment environment definition from the command line

You can validate the deployment environment definition using the wsadmin command. Run this command before generating a deployment environment to make sure that the definition is valid.

Before you begin

The task assumes that the node has been federated to the deployment manager.

You must be on the deployment manager where you generated the deployment environment definition.

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 validates the deployment environment definition and uses the wsadmin command.

Procedure

Open a command window. The wsadmin command can be found in either of the following directories:
```
install_root/profiles/dmgr profile/bin
install_root/bin
```
At the command prompt, enter the wsadmin command to enter the wsadmin environment.
Enter the validateDeploymentEnvDef command to validate the deployment environment definition.
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.

Example

This example validates the deployment environment definition (myDepEnv) with administrative security enabled:

wsadmin -connType SOAP -host myDmgr -port 8879 -user dmgrAdmin -password -dmgrPass
> $AdminTask validateDeploymentEnvDef { -topologyName topOne}

Note: If you disable administrative security, you do not need to provide a user ID and password.

What to do next

Tip: After you have configured a network deployment environment, if you test the data store connection (for example, in the administrative console, on the page Resources > JDBC > Data sources), you get a message saying that the test connection operation failed with the exception com.ibm.wsspi.runtime.variable.UndefinedVariableException: Undefined Variable WAS_INSTALL_ROOT. This does not necessarily indicate that there will be a problem accessing the data source at run time. Ensure that the location of your JDBC driver files is accessible to every client that must use the data source, and configure the variable with the full path of that location. Disregard the test connection error unless you are also experiencing trouble connecting to the data store at run time. For additional information, see the WebSphere® Application Server documentation about the test connection service.