Secured TIMS requires ORACLE has a precreated ORACLE instance.
Instance is everything it takes for ORACLE to run: background processes (programs), memory, and so on (but not the stored data itself). If the database were a filing cabinet, an instance would be a file clerk. There can be many instances of Oracle, each with its own database, just as there can be many file clerks, each with his or her own file cabinet. An instance is the means of accessing a database.
We recommend that you create a separate instance for TIMS with its own administrator user. This is good for scenarios that require TIMS to be separated from the other production Databases. Also make sure this instance is accessible by the administrator user and make sure to use this instance when creating the alias for TIMS.
How to secure a TIMS3 Oracle Database
* Assume that TIMS User has DBA role.
Please follow the steps below:
1. Run update script (Upv4.x.x.sql). This should update the TIMS database on Oracle server.
2. By default, the timsuser password is set to TIMS. Change timsuser password to something else so that the old versions of project navigator cannot login to this database.
3. Copy the new Project Navigator to your client test machine. The old version can be found in: (C:\program files\tims client access\) directory.
4. Please note: TIMS user account must have DBA privileges.
5. Login to TIMS3 with timsuser account (see fig.). The username and password will be stored therefore simple click OK for future logins. Check Auto Login to skip the login prompt.
6. Open the site settings in TOOLS menu. Create a site record for this site if not available. Check 'SecureDB' checkbox, update DB servername with your connect and remove the password and leave PWD=; (see fig.)
7. Click the SYSTEM TAB. Select the site you have just created and check the default site checkbox. (See fig.)
8. Add new users.