In UNIX environments, you start the CAS Service from a command prompt. In Windows enviroments, you can start the service from a command prompt, but it is optional.
The only prerequisite to this task is that the CAS software must be
installed. This means that the
cas-service.bat
(for Windows) or
cas-service.sh
(for UNIX) scripts must be
available. Note that for the UNIX
cas-service.sh
script, you must have Execute
rights to the file.
Note
The CAS Service can be slow to startup if it contains large Record Store instances and has not been cleanly shutdown.
To start the CAS Service from a command prompt:
Open a command prompt and navigate to the
bin
directory.In a default installation on Windows, this is
C:\Endeca\CAS\<version>\bin
.Run the
cas-service.bat
script (for Windows) orcas-service.sh
script (for UNIX).For example, in a default installation on a Windows machine, the command is as follows:
C:\Endeca\CAS\<version>\bin>cas-service
This command starts the CAS Service on the default port 8500 with a workspace directory of
Endeca\CAS\workspace
.Note that you do not see any startup messages. All messages are sent to the CAS Service log (by default,
workspace\logs\cas-service.log
). However, if there is an error in setting up logging, all messages are sent to the console.Verify that the server is running by opening a Web browser and entering a URL with the CAS Service host and port number followed by
cas/?wsdl
. For example, in a default installation:http://localhost:8500/cas/?wsdl
You see the CasCrawlerService WSDL in the Web browser window, which indicates that the CAS Service is running.
The workspace directory has these sub-directories:
state
contains acrawlerDb
subdirectory that stores a unified crawl history (that is, one crawl history for all crawls defined for this CAS Server) and contains anoutput
directory which is the default location for the crawl output files.logs
contains thecas-service.log
log file for the CAS Service.