velocity-cmd [-h|-help] [-installation-dir /path/to/velocity/installation] [-list] [-list-xml] [-user userid] {<function> [help|<name>=<value>]}
The velocity-cmd command is located in the bin subdirectory of a Watson Explorer Engine installation. This command enables you to execute any Watson Explorer Engine SOAP/REST API function from the command line. Additionally, the command can be used to provide detailed help for an API function.
The velocity-cmd command must be able to contact an executable that supports the full Watson Explorer Engine SOAP/REST API. When using velocity.aspx as the primary executable for Watson Explorer Engine, you must use the velocity-config command to modify the global/api-url variable to explicitly set the location of the velocity.aspx application, as in the following example:
velocity-config global/api-url=http://url/to/velocity.aspx
When executed with no arguments, the velocity-cmd command displays the same output as if it had been called with its -help option.
If the installation directory has been specified incorrectly, the following message will appear:
There has been a problem:
The directory 'directory' does not appear to be a
valid Velocity Installation. Your installation may
be incomplete or you may need to specify the '-I' option, followed
by the name of the directory in which Velocity is
installed. (ID: CLI_BAD_VELOCITY_DIR_ERROR)
If a user that does not exist in Watson Explorer Engine has been specified, the following message will appear:
There has been a problem:
(ID: CORE_AUTHENTICATE_ERROR) Login failed because
the user does not exist or the password was incorrect.
If an API call that does not exist in the Watson Explorer Engine SOAP/REST API is specified, the following message will appear:
There has been a problem:
(ID: XML_FUNCTION_NOT_DEFINED_ERROR) "function""API call" is not defined
See the Velocity API Developers Guide for detailed information about any other messages that you may receive from the velocity-config command.
Input Example:
./velocity-cmd -list
Output Example:
List functions:
alert-list-xml: Retrieves a list of alerts for all users.
This function has no inputs
returns:
Type: nodeset
throws:
- alert-list
alert-run: Starts the alert service and run alerts for user or id provided.
input:
- user: Run all alerts for this user.
Type: nmtoken
Required: No
- alert-id: Run alert which has this id.
Type: string
Required: No
throws:
- alert-run
alert-service-start: Starts the alert service and run all user alerts.
This function has no inputs
throws:
- alert-service-start
alert-service-status-xml: Retrieves the status of the alert service, whether it is running or not.
This function has no inputs
returns:
Type: nodeset
throws:
- alert-service-status
.
.
.
Input Example:
./velocity-cmd -U administrator dictionary-list-xml
Output Example:
<dictionaries> <dictionary name="english" /> <dictionary name="doc-search-dictionary" /> <dictionary name="test" /> <dictionary name="default" /> <dictionary name="base" /> </dictionaries>
Exits with status 0 when the command is successful.