Configuring The Remote Audit Database After Platespin Orchestrate Is Configured; Modifying Audit Database Tables To Accommodate Long Names - Novell PLATESPIN ORCHESTRATE 2.0.2 - INSTALLATION AND CONFIGURATION GUIDE 10-09-2009 Installation And Configuration Manual

Hide thumbs Also See for PLATESPIN ORCHESTRATE 2.0.2 - INSTALLATION AND CONFIGURATION GUIDE 10-09-2009:
Table of Contents

Advertisement

2.2.7 Configuring the Remote Audit Database after PlateSpin
Orchestrate Is Configured
If you have already installed and configured PlateSpin Orchestrate, it is still possible to configure an
audit database.
1 On the PlateSpin Orchestrate host machine, use your favorite editor to edit the script
novell/zenworks/zos/server/conf/audit_db_def.sql
1a Replace the
zos_db
1b Replace the
zos
2 Use the following commands to run the modified script as the PostgreSQL database
administrator for the remote database:
su - postgres
psql -h <psql-server-addr> -d postgres -U postgres -f audit_db_prep.sql
3 Use the following command to log into PostgreSQL, using the database name and schema
owner substituted in Step 1 above:
su - postgres
psql -h <psql-server-addr> -d zos_db -U zos -f audit_db_def.sql
4 Confirm that the database username and password match the values used when creating the
schema owner database user in
Database" on page
5 Confirm that the database username and password match the values you replaced in the
variables of the
6 Click Connect.
The Is Connected check box is selected: the Orchestrate Server is connected to the database so
that any queued data and subsequent job, user, and resource events are written there.
2.2.8 Modifying Audit Database Tables to Accommodate Long
Names
If your installation of PlateSpin Orchestrate uses Grid Object names that have an unusual number of
characters, the server might lose its connection with the audit database.
44
PlateSpin Orchestrate 2.0 Installation and Configuration Guide
variable with the PostgreSQL database name (for example,
${DB_NAME}
).
variable with the PostgreSQL schema owner name (for example,
${DB_USER}
).
"Creating a PlateSpin Orchestrate User for the PostgreSQL
39. In this example, the username is
script. In this example, the username is
.sql
.
and the password is
zos
zos
and the password is
zos
/opt/
.
.
zos

Advertisement

Table of Contents
loading

This manual is also suitable for:

Platespin orchestrate 2.0.2

Table of Contents