Database setup for Monitoring Component

This page contains the following sections:

Oracle Database

Before the system can be installed, it is essential that an Oracle database is installed and ready to be used. The Oracle database is not supplied with the service.monitor installation.

The following steps must be performed, either using the appropriate tools (e.g. SQLPlus) or on the command line. In this example, the tablespace created is given the name monitor and the user has the user name monitor and password monitor.

Creating the Tablespace and schema
CREATE TABLESPACE monitor
    DATAFILE '<PATH_TO_DATAFILE>.dbf'
    SIZE 50M
    AUTOEXTEND ON NEXT 200K
    MAXSIZE 1000M;
CREATE USER monitor identified by monitor;
ALTER USER monitor
      default tablespace monitor
      temporary tablespace TEMP;
GRANT UNLIMITED TABLESPACE TO monitor;
GRANT CONNECT, RESOURCE TO monitor;
GRANT CREATE SESSION TO monitor;
GRANT CREATE TABLE TO monitor;
GRANT CREATE SEQUENCE TO monitor;
Before running the script it is necessary to change the paths to the data file in the script to reflect your system, e.g. to: C:\oracle\oradata\instance\smdat.dbf
All tables required by the service.monitor are generated automatically during installation.

PostgreSQL Database

Before the system can be installed, it is essential that a PostgreSQL database is installed and ready to be used. The PostgreSQL database is not supplied with the service.monitor installation.

The following steps must be performed, either using the appropriate tools (e.g. pgadmin or psql) or on the command line. In this example, the database created is given the name servicemonitor and the user has the user name monitor and password monitor.

Creating a new database (Root rights are required)
CREATE Database servicemonitor;
Create a new database user
CREATE USER monitor;
ALTER USER monitor WITH PASSWORD 'monitor';
GRANT ALL PRIVILEGES ON DATABASE servicemonitor TO monitor;
All tables required by the service.monitor are generated automatically during installation.

MS SQL Server Database

Before the system can be installed, it is essential that a MS SQL Server database is installed and ready to be used. The MS SQL Server database is not supplied with the service.monitor installation.

All tables required by the service.monitor are generated automatically during installation.

Copy JDBC Driver

If you decided for container managed database connections (JNDI) the database drivers need to be copied manually to the right location (depending on the servlet container you use). Apache Tomcat requires the drivers to be located in <Tomcat>/lib. Db drivers are being excluded during installation into folders webapps/monitor and webapps/administration.

The files must be provided by the operator of the software:

  • ojdbc<version>.jar (Oracle)

  • postgresql-<version>.jar (PostgreSQL)

  • sqljdbc-<version>.jar (MS SQL Server)