A schema is a set of database tables, and is used by the application to store timesheet data and settings. If you are hosting the application yourself you can review your schema settings, as well as edit or create a new schema. Normally you would use the schema created by the installer and never change these settings. But if you would like to use an external database like Microsoft SQL Server or Oracle, or if you installed the WAR version of the application, you will need to create a new schema before you can use the system.
Note: For security reasons you may only access the Schema page if you are on the computer running the timesheet service.
For a list of supported databases and versions refer to the System Requirements topic. The installer provides the following database:
Default TCP/IP Port: 3316
Administrative Login: See the "Bundled Software" section in timesheet-install.pdf
The Schema page is located at the following address:
If you changed the default HTTP port from 80 then you will need to specify the port number, too, for example:
This will load a page showing the current schema configuration. You can edit this schema configuration by clicking the Edit button, or create a new schema by clicking the Create button. Note that for security reasons you need to be using a browser on the same machine that the application is installed on.
Editing the schema configuration will not alter the schema, just the settings that the application uses to connect to the schema. Creating a new schema will not delete or alter the old schema, but will create a new schema and update the settings so that the application will use the new one.
The type of database management system (DBMS) to be used. The following types are supported:
The TCP/IP address or host name of the database server. Use localhost if the database server is running on the same computer as the application.
The TCP/IP port number used by the database server. The value will default to the number appropriate for the database type, which is generally the value you want to use.
Schema Name/Oracle SID
For Microsoft and MySQL the schema name is the name of the database. For Oracle you would use the SID (Server IDentifier).
The login name for the database account to use when connecting to the database server.
The password for the login.
When creating a new schema you have the following additional properties:
The login name for the administrative account for the database server. Note that if creating a new schema or database using the bundled MySQL database, the default administrative login is root with the password is timesheet.
The password for the administrative account. Note that if creating a new schema or database using the bundled MySQL database, the default administrative login is root with the password is timesheet.
New Schema Name
For Microsoft and MySQL this is the name of the new database to create. For Oracle this is the name of the new tablespace to create.
The login name for the new database account to use when connecting to the database server.
For Oracle Database 12c or later the login name must begin with the three characters 'C##' or 'c##' (without the quotes).
The password for the new login.
SQL Server 2005 Note: SQL Server 2005 has stricter login and password rules than SQL Server 2000 by default. Make sure the password for the new database schema doesn’t match the new schema name, as this will often cause an error. You can see details for the error message in the log files, located in the tomcat/logs directory of the installation directory.