Configuring the Reporting Database
To configure the reporting database, first install your Manager; second, configure the database; and third, configure the Manager to use the new database. Then, restart the Manager.
Install the Manager
| 1. | Install and configure your GridServer Manager. Restart the Manager after completing the installation. |
| 2. | Ensure that the tables.<db>.sql file needed by the createdb script is in the DS_MANAGER/webapps/livecluster/WEB-INF/etc/db directory. |
Configure the database
Procedure
| 1. | Set the CLASSPATH on the Manager containing the Director that communicates with the database. The CLASSPATH must include the database driver JAR files applicable to your database. For example, to create an SQL Server database in a UNIX shell: |
export CLASSPATH=JDBCDriver/msbase.jar:JDBCDriver/mssqlserver.jar:\ JDBCDriver/msutil.jar
replacing JDBCDriver with the actual path to the directory containing your driver JAR files.
| 2. | Run the createdb script provided in DS_MANAGER/webapps/livecluster/WEB-INF/etc/db directory on your Manager. Pass the name of the database properties file as an argument. Before you run the script, change the property file settings to match those of your database. |
Configure the Manager
Procedure
| 1. | Log in to the GridServer Administration Tool with an account that has a Security Role with the Manager Reconfigure feature enabled. |
| 2. | Go to Admin > System Admin > Manager Configuration > Database. |
| 3. | Configure the values in the Reporting Database Connection section using the appropriate table below. Note that hostname is the hostname and database is the name of the database. |
|
Property |
Value |
Oracle |
|
|
URL |
|
|
Driver |
|
|
Transaction Isolation |
|
Microsoft SQL Server |
|
|
URL |
( |
|
Driver |
|
|
Transaction Isolation |
|
PostgreSQL |
|
|
URL |
jdbc:postgresql:// |
|
Driver |
org.postgresql.Driver |
|
Transaction Isolation |
|
| 4. | Copy the corresponding JDBC driver’s JAR file into the Manager’s DS_MANAGER/webapps/livecluster/WEB-INF/lib directory. |
| 5. | Restart the GridServer Manager. |