5.1 Installing the PostgreSQL Package and Dependencies on an Independent Host

When you enable and configure Orchestration Server auditing, you create a small custom database and a simple schema that persists all of the Orchestration Server jobs that have been run, along with their parameters. The database also maintains the login or logout activity of the Orchestration Server users and resources and includes an “actions” table that records provisioning actions and their status (started, failed, completed successfully, etc.).

NOTE:We recommend that you install the PostgreSQL packages on a SLES 10 SP3 server (or SLES 11 SP1 server) that is different from the server where you install the Orchestration Server. This ensures an adequate amount of space for running the server as the database is used.

We also recommend that you open TCP port 5432 (or whatever port you configure PostgreSQL to use—5432 is the PostgreSQL default) in the firewall of the RDBMS host. Without an open port in the host firewall, a remote Orchestration Server cannot access the audit database.

For high availability Orchestration Server configurations, you need to install the database outside of the high availability cluster.

If the SLES 10 SP3 machine (or the SLES 11 SP1 machine) does not have PostgreSQL packages installed and running, use YaST to search for postgresql-server, then install the package and its dependencies.

You can also run the following command from the bash prompt:

yast2 -i postgresql-server

When PostgreSQL is installed, you need to create the default database and start it. Use the following commands:

su - postgres

initdb

pg_ctl start

These commands create or update the PostgreSQL privilege database and installs the prepared tables. For more detail about what you will see when you run these commands, see Detail.

NOTE:You cannot run the pg_ctl command as root. You must first change to the superuser for PostgreSQL (su - postgres). Failure to issue this command first results in the following messages:

# pg_ctl start
pg_ctl: cannot be run as root
Please log in (using, e.g., "su") as the (unprivileged) user that will
own the server process.