Server Setup

Server setup

Scribe Server supports a number of relational databases that can be used to store the application configuration and production data. The database is selected from the DB adaptor pop-up list; this should be done before the Server is started.

Scribe Server maintains a connection to the database where the configuration and production data are stored. In order to connect to the database, the Server must know the following:

Option Description

Database server host Name of the computer where the database server runs

Database server port Port on the database server host the database server is listening to for the client connections.

Database name Some relational databases require a "database name" (SID in Oracle, Databank in MImer) that along with the database server host and port number are required to establish connection with the database.

These parameters should be provided by the Database Administrator.

Scribe Server maintains two sets of login identities:

for logging into the database, and
for logging into the Server

Logging into the database is done by the Server on behalf of the Client. The database login and password are encrypted inside the Server setup XML files, and are not disclosed to the end user. They can either be provided by the Database Administrator, or created by Scribe Server if they do not exist; in the latter case Scribe Server Administrator application will ask the user for the DBA password before creating the new login identity.

Scribe maintains a privileged Administrator login account that is authorized to create/drop databases, user logins/passwords, and edit the user access rights.

Option Description

Database login account The account Scribe will use to log into the database. You can set a new account and password (see below); in this case the database will ask you for the DBA password to authorize creation of the new account. All Scribe clients will log into the database using this account.

Database login password Password used to authenticate logging into the database. The password is masked in the input field, and encrypted in the setup XML file.

Scribe admin account Scribe Administrator account that has rights to create/drop user accounts, set user access rights etc. The Administrator account is password-protected (see below) and should be used by the Administrator only.

Scribe admin password Password used to authenticate logging into Scribe. The password is masked in the input field, and encrypted in the setup XML file.

Scribe Server provides the following logging facilities that can help in troubleshooting:

Option Description

Generate SQL trace for debugging SQL commands executed by Scribe can be saved in the log file and examined by the support staff to diagnose problems. This option should be used sparingly, as it increases the workload on Scribe server and taxes the CPU. The permissible settings are YES or NO.

Log execution trace information about program's execution, including the SQL trace, can be saved in a file for diagnostics by setting this option to YES.

If this option is set to YES, Scribe Server creates a file for each client session named traceYYYYMMDD_N.log, where YYYYMMDD is the date of the session, and N is the session number. The log files are located in logs/<User login> directory in the installation directory of Scribe Server. For instance, the log files created for user Heidi are saved in directory logs/Heidi.

If this option is set to NO, Scribe Server creates a single file called error.log in the installation directory of Scribe Server. SQL commands and error messages generated by all Client sessions are stored in this file. The file is overwritten when the Server restarts.

Option	Description
Database server host	Name of the computer where the database server runs
Database server port	Port on the database server host the database server is listening to for the client connections.
Database name	Some relational databases require a "database name" (SID in Oracle, Databank in MImer) that along with the database server host and port number are required to establish connection with the database.

Option	Description
Database login account	The account Scribe will use to log into the database. You can set a new account and password (see below); in this case the database will ask you for the DBA password to authorize creation of the new account. All Scribe clients will log into the database using this account.
Database login password	Password used to authenticate logging into the database. The password is masked in the input field, and encrypted in the setup XML file.
Scribe admin account	Scribe Administrator account that has rights to create/drop user accounts, set user access rights etc. The Administrator account is password-protected (see below) and should be used by the Administrator only.
Scribe admin password	Password used to authenticate logging into Scribe. The password is masked in the input field, and encrypted in the setup XML file.

Option	Description
Generate SQL trace for debugging	SQL commands executed by Scribe can be saved in the log file and examined by the support staff to diagnose problems. This option should be used sparingly, as it increases the workload on Scribe server and taxes the CPU. The permissible settings are YES or NO.
Log execution trace	information about program's execution, including the SQL trace, can be saved in a file for diagnostics by setting this option to YES. If this option is set to YES, Scribe Server creates a file for each client session named traceYYYYMMDD_N.log, where YYYYMMDD is the date of the session, and N is the session number. The log files are located in logs/<User login> directory in the installation directory of Scribe Server. For instance, the log files created for user Heidi are saved in directory logs/Heidi. If this option is set to NO, Scribe Server creates a single file called error.log in the installation directory of Scribe Server. SQL commands and error messages generated by all Client sessions are stored in this file. The file is overwritten when the Server restarts.