Difference between revisions of "Recitalserver"

Revision as of 13:26, 8 October 2009

The Recital Server can be managed using the dbserver script.

Note: dbserver must be run as root. For systems with a hidden root account, please precede commands with ’sudo’.

start

Used to start the Recital Server. A confirmation message will be displayed showing whether the Recital Server was successfully started or not. Any errors in starting the server will be logged in the <path>/log/dbserver.log file. If the optional 'logging' parameter is specified, all server logging [1] will be enabled.

# dbserver start [logging]

restart

Used to restart (stop, then start) the Recital Server. A confirmation message will be displayed showing whether the Recital Server was successfully started or not. Any errors in starting the server will be logged in the <path>/log/dbserver.log file.

# dbserver restart

stop

Used to stop the Recital Server. A confirmation message will be displayed showing whether the Recital Server was successfully stopped or not.

# dbserver stop

status

Used to display the following status information for the Recital Server:

• Whether the Recital Enterprise Studio Server is active or not
• Whether the Recital Server is active or not
• Whether the Recital Web Server is active or not
• Whether the Recital Web Server is listening on its default port and/or port 80
• How many concurrent connections are licensed for each server
• How many concurrent connections are currently being used for each server
• Whether logging is enabled or not

# dbserver status

info

Used to display version and other information for the Recital Server:

• Platform
• Edition (DES3 enabled or not)
• Version
• Compilation date and time

# dbserver info