Server Status and Control Commands

isdecisionengine

Use the isdecisionengine command to determine if the server is a TIBCO® Patterns Matching Platform server with the machine learning features.

isgipenabled

Use the isgipenabled command to determine if the GIP prefilter for performance optimization is currently enabled on the TIBCO® Patterns server.

issortenabled

Use the issortenabled command to determine if SORT prefilter for performance optimization is currently enabled on the TIBCO® Patterns server.

svrshutdown [-pidfile <file-path>] [-waittime <wait-time >]

This command will cause the TIBCO® Patterns server to perform a controlled shutdown.

If the –pidfile option is given it checks for the existence of the file: <file-path>, if the file doesn’t exist, the command completes successfully without further action.  If the file exists it sends a shutdown command to the TIBCO® Patterns server and then waits <wait-time > seconds (default 10 seconds) for the pid file <file-path> to be removed, checking once a second.  If the file is removed it exits successfully.  If it is not removed after <wait-time> seconds the file is read to retrieve the process ID and that process is killed.  If the kill is successful the command completes successfully, otherwise it completes with an error message.  This sequence is designed to ensure the TIBCO® Patterns server is shut down before this command returns.

If the –pidfile option is not given it sends a shutdown command to the TIBCO® Patterns server and completes successfully.

svrnoop

This command performs no action.  It is used to verify that a connection to the server can be made and that the server is up and operational.

svrversion

The svrversion command returns the release level of theTIBCO® Patterns server.

svrlogon

The svrlogon command turns on matching engine query logging. Note that the matching engine query logging functionality must be enabled at engine startup by specifying a query log file or this command fails.

svrlogoff

The svrlogoff command turns off matching engine query logging. Note that the matching engine query  logging functionality must be enabled at engine startup by specifying a query log file or this command fails.