getBPMDefaultVirtualHost command
Traditional:
Use the getBPMDefaultVirtualHost command
to get the Business Automation Workflow default
virtual host.
The getBPMDefaultVirtualHost command is run using the AdminTask object of the wsadmin scripting client.
Prerequisites
The following conditions must be met:
- In a network deployment environment, run the command on the deployment manager node. In a single-server environment, run the command on the stand-alone server.
- If the deployment manager or stand-alone server is stopped, use
the
wsadmin -conntype noneoption to run the command in disconnected mode (which is the recommended mode for this command). - If the deployment manager or stand-alone server is running, you must connect with a user ID that has WebSphere® Application Server configurator privileges. Do not use the
wsadmin -conntype noneoption.
Location
Start the wsadmin scripting client from the profile_root/bin directory. The getBPMDefaultVirtualHost command does not write to a log file, but the wsadmin scripting client always writes a profile_root/logs/wsadmin.traceout log file where you will find exception stack traces and other information.
Syntax
getBPMDefaultVirtualHost
[-de deployment_environment_name]Parameters
- -de deployment_environment_name
- A parameter that specifies the name of the current deployment environment. If there is only one deployment environment in the WebSphere cell, you can omit this parameter.
Note: If a Business Automation Workflow default
virtual host has not been set, the getBPMDefaultVirtualHost command
will return an empty string.
Examples
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 Jython example uses the getBPMDefaultVirtualHost command
to get the default virtual host:
wsadmin -user admin -password admin -lang jython
wsadmin>AdminTask.getBPMDefaultVirtualHost(['-de', 'De1'])