Removes Watson Explorer Engine from maintenance mode,
allowing other Watson Explorer Engine processes to start. Additional
command-line arguments can be supplied to start the Watson Explorer Engine query service and scheduler.
Synopsis
velocity-startup [-h|-help]
[-installation-dir /path/to/engine/installation]
[-quiet]
[-start-query-service]
[-start-scheduler]
[-yes]
Description
The velocity-startup command is located in the bin
subdirectory of a Watson Explorer Engine installation. (On
Microsoft Windows systems, this command has the .exe file extension.) Executing this
command with the right options takes a Watson Explorer Engine
installation out of maintenance mode, enabling Watson Explorer Engine processes to be started, but does not actually
start any Watson Explorer Engine processes.
Executing the velocity-startup command with the -start-scheduler
option starts the Watson Explorer Engine scheduler with a "boot"
message, causing the scheduler to start all Watson Explorer Engine services that have been registered to start at boot time. Schedulable services include
repository synchronization, building a dictionary, building and emailing a report, running
alerts, starting or stopping a search collection crawl, starting or stopping the query
service, or testing a specified source.
Executing the velocity-startup command with the
-start-query-service option starts the Watson Explorer Engine query service, which enables a Watson Explorer Engine installation to respond to queries.
Note: When starting the embedded Watson Explorer Engine web server for the first time on Microsoft Windows systems that are running the Windows
firewall or which support User Account Control (UAC) warnings, your system will display a
dialog requesting that you unblock the program in your firewall or otherwise grant the
application access to your network. You must approve whichever of these access requests you
see in order for applications to be able to use this web server.
Options
- -h|-help: Displays a usage message and exits without performing any
other actions.
- -installation-dir/path/to/engine/installation:
Enables you to specify the location of the Watson Explorer Engine installation that you want to start. If no
installation directory is specified, the velocity-startup command
assumes that the Watson Explorer Engine installation directory
is the parent of the directory in which the velocity-startup application is
located.
- -quiet: Suppresses normal output and warnings. Errors will still be
displayed. Specifying this option implies the -yes option. On Windows systems, this
option also suppresses the "Press return to continue" message that is shown at the end of
each Watson Explorer Engine administrative command.
- -start-query-service: Starts the Watson Explorer Engine query service, enabling the copy of Watson Explorer Engine that is associated with this instance of the
velocity-startup command (or the version in the directory specified
using the -I option to respond to incoming queries.
- -start-scheduler: Starts the Watson Explorer Engine scheduler with a "boot" message, causing the
scheduler to start all Watson Explorer Engine services that
have been registered to start at boot time.
- -yes: Proceeds without prompting for confirmation
Messages
The velocity-startup command displays the message "Velocity has been
started" when it is successful. Depending on the command-line options that you specify, you
may be prompted for other information or see additional messages, such as the following:
- "Press Return to continue": (Microsoft Windows only) Shown after the
velocity-startup completes the startup process but before it exits, in order to
enable you to see any messages that may have been generated in the command window during
the startup process.
See the Watson Explorer Engine Message Reference Manual
for detailed information about any other messages that you may receive from the
velocity-startup command.
Exit Status
Exits with status 0 when the command is successful.
Note: On Linux systems, exit codes above 127 are returned by the shell. Please
consult the documentation for the shell that you are using for more information.