2.3 Installing and Configuring All PlateSpin Orchestrate Components Together

This section discusses the installation and configuration of all PlateSpin Orchestrate components (except the Orchestrate VM Client) on one SUSE Linux Enterprise Server (SLES) 10 SP3 or SLES 11 SP1 machine. The steps are shown as an installation example; you would not normally install all of these components together on a single machine in a data center.

You should install the PlateSpin Orchestrate Server on a dedicated server for optimal performance.

After you install and configure the components you want from PlateSpin Orchestrate, there are other basic tasks you need to perform to make the PlateSpin Orchestrate system perform at a basic level. Those tasks are documented in Section 3.0, First Use of Basic PlateSpin Orchestrate Components.

IMPORTANT:The Orchestrate Monitoring Server can be installed on any server because it runs independently of the other components. For more information, see Section 1.1, PlateSpin Orchestrate Requirements.

This section includes the following information:

2.3.1 Installation and Configuration Steps

To install and configure a complete PlateSpin Orchestrate system (except the VM Client) on a SLES machine:

  1. Review Section 1.0, Planning the Orchestrate Server Installation to verify that the device where you want to install the Orchestrate Server software fulfills the necessary requirements.

  2. Download the appropriate PlateSpin Orchestrate Server ISO (32-bit or 64-bit) to an accessible network location.

  3. (Optional) Create a DVD ISO (32-bit or 64-bit) that you can take with you to the machine where you want to install it.

  4. Install PlateSpin Orchestrate software:

    1. Log in to the target SLES server as root, then open YaST2.

    2. In the YaST Control Center, click > Software, then click Add-on Product to display the Add-on Product Media dialog box.

    3. In the Add-on Product Media dialog box, select the ISO media (Local Directory or DVD) to install.

      1. (Conditional) Select DVD, click Next, insert the DVD, then click Continue.

      2. (Conditional) Select Local Directory, click Next, select the ISO Image check box, browse to ISO on the file system, then click OK.

    4. Read and accept the license agreement, then click Next to display YaST2.

    5. In YaST2, click the View drop-down menu, then select Patterns to display the install patterns available on the PlateSpin Orchestrate ISO.

    6. Select the PlateSpin Orchestrate installation patterns that you want to install:

      • Orchestrate Server: This pattern is the gateway between enterprise applications and resource servers. The Orchestrate Server manages computing nodes (resources) and the jobs that are submitted from applications to run on these resources.

      • Monitoring Server: Uses open source Ganglia monitoring of the performance of certain data on network resources in a user-defined time period.

        This pattern can be installed on a server where any other PlateSpin Orchestrate pattern is installed, or on a server by itself.

      • Orchestrate Agent: This pattern is installed on all computing resources that are to be managed. It runs applications under the management of the Orchestrate Server and reports its status to the Orchestrate Server.

      • Development Client: Installing this pattern lets the administrator of a computing resource troubleshoot, initiate, change, or shut down server functions for PlateSpin Orchestrate and its computing resources. For information about the tools included in this pattern, see PlateSpin Orchestrate Clients in Section A.0, PlateSpin Orchestrate Components: Install Patterns.

      • Monitoring Agent: This pattern is installed with any installation of the Orchestrate Server. It installs the Ganglia Agent on each monitored node, which collects performance metrics and sends the data to the Orchestrate Monitoring Server.

      Refer to the information in Section A.0, PlateSpin Orchestrate Components: Install Patterns for more detail about these patterns.

      If you choose not to install the PlateSpin Orchestrate Agent or the PlateSpin Orchestrate Clients on some machines now, you can install them later by using installers that are accessible from a hosted Web page from the PlateSpin Orchestrate Server, or you can repeat this process by downloading the ISO to the machine where you want to install the agent or clients. For more information, see Section 2.4, Installing the Orchestrate Agent Only.

    7. Click Accept to install the packages.

  5. Configure the PlateSpin Orchestrate components that you have installed. You can use one of two methods to perform the configuration:

    • The PlateSpin Orchestrate product configuration script. If you use this method, continue with Step 6.

    • The GUI Configuration Wizard. If you use this method, skip to Step 7.

    HINT:The text-based configuration process detects which RPM patterns are installed, but the GUI Configuration Wizard requires that you specify the components to be configured.

    IMPORTANT:The configuration tools produce a configuration file that can be used to automatically reconfigure your system after an upgrade. If you use the tools to reconfigure your server after the original configuration has been done, make sure you reconfigure all of the components that are installed on the system (this is the default).

  6. (Conditional) If you are using the PlateSpin Orchestrate product configuration script, run the script:

    1. Make sure you are logged in as root to run the configuration script.

    2. Run the script, as follows:

      /opt/novell/zenworks/orch/bin/config

      When the script runs, the following information is initially displayed:

      Welcome to PlateSpin Orchestrate.

This program will configure PlateSpin Orchestrate 2.5.0

Select whether this is a new install or an upgrade

i) install
u) upgrade
- - - - - -

Selection [install]:

    3. Determine whether this is a new installation or an upgrade.

      This example procedure discusses standard installation, so specify i (for install) or press Enter to accept the default. For more information about upgrade, see the PlateSpin Orchestrate 2.5 Upgrade Guide.

      When you make the selection, the following information is displayed:

      Select products to configure

 #   selected  Item
 1)    yes     PlateSpin Orchestrate Monitoring Service
 2)    yes     PlateSpin Orchestrate Server
 3)    yes     PlateSpin Orchestrate Agent

Select from the following:
  1 - 4)  toggle selection status
       a)  all
       n)  none
       f)  finished making selections
       q)  quit -- exit the program
Selection [finish]:

      The list shows the products listed whose patterns you previously installed.

    4. Determine which installed products you want to configure. The options are listed with option numbers.

      1. Select or deselect an option by typing its number to toggle its selection status, or type a and press Enter to select all of them.

      2. When you have selected the products you want to configure, type f and press Enter to finish the selection and begin the configuration.

        For information to help you complete the configuration process, see Section 2.3.2, PlateSpin Orchestrate Configuration Information

      3. When the you have finished answering questions about the configuration, continue with Step 8.

  7. (Conditional) If you are using the GUI Configuration Wizard:

    1. Enter the following command at the bash prompt of the machine where you installed the PlateSpin Orchestrate patterns:

      /opt/novell/zenworks/orch/bin/guiconfig

      The GUI Configuration Wizard launches.

      IMPORTANT:If you have only a keyboard to navigate through the pages of the GUI Configuration Wizard, use the Tab key to shift the focus to a control you want to use (for example, a Next button), then press the spacebar to activate that control.

    2. Click Next to display the license agreement.

    3. Accept the agreement, then click Next to display the PlateSpin Orchestrate components page.

      This section discusses new installation. For information about upgrading, see the PlateSpin Orchestrate 2.5 Upgrade Guide.

    4. Select New Installation, then click Next to display the PlateSpin Orchestrate components page.

      The components page lists the PlateSpin Orchestrate components that are available for configuration. By default, all installed components are selected for configuration.

    5. Click Next to confirm the components you want to configure.

      or

      Deselect any PlateSpin Orchestrate components that you do not want to configure, then click Next.

      (Conditional) If you selected the PlateSpin Orchestrate Monitoring Service as a component to install, the Monitoring Service Configuration page is displayed.

      See Step 7.e.a to continue.

      (Conditional) If you did not select the PlateSpin Orchestrate Monitoring Service as a component to install, the High Availability configuration page is displayed.

      See Step 7.f to continue.

      1. (Conditional) Specify a name for this monitored node. The default name is the computer name.

        Select the Configure this computer to be the Monitoring Server check box if you want this computer to be a Monitoring Server, then click Next and continue with Step 7.f.

        If you do not select this check box and click Next, a second page of the Monitoring Configuration Wizard is displayed.

        Continue with Step 7.e.b.

      2. (Conditional) Specify the host name or IP address you want to associate to this monitored node. This node sends its metrics to the Monitoring Server you specify.

      3. Click Next and continue with Step 7.f.

    6. (Conditional) If you are configuring this Orchestrate Server in a High Availability environment, select the Install to a High Availability check box, then specify the fully qualified cluster hostname or IP Address.

      or

      If you are configuring this Orchestrate Server for a non-clustered instance, click Next.

    7. On the settings pages and the succeeding pages of the wizard, provide information to be used in the configuration process. As the configuration questions in the wizard continue, refer to the information in Table 2-1, PlateSpin Orchestrate Configuration Information for details about the configuration data that you need to provide. The GUI Configuration Wizard uses this information to build a response file that is consumed by the setup program inside the Configuration Wizard.

      When you have finished answering the configuration questions in the wizard, the PlateSpin Orchestrate Configuration Summary page is displayed.

      IMPORTANT:Although this page of the wizard lets you navigate by using the Tab key and the spacebar, you need to use the Ctrl+Tab combination to navigate past the summary list. Click Back if you accidentally enter the summary list, and re-enter the page to navigate to the control buttons.

      By default, the Configure now check box on this page is selected. If you accept the default of having it selected, the wizard starts PlateSpin Orchestrate and applies the configuration settings. If you deselect the check box, the wizard writes out the configuration file to /etc/opt/novell/novell_zenworks_orch_install.conf without starting PlateSpin Orchestrate or applying the configuration settings.

      You can use this .conf file to start the Orchestrate Server or Agent and apply the settings either manually or with an installation script. Use the following command to run the configuration:

      /opt/novell/zenworks/orch/bin/config -rs

    8. Click Next to display the following wizard page.

    9. Click Next to launch the configuration script. When the configuration is finished, the following page is displayed:

    10. Click Finish to close the configuration wizard.

      IMPORTANT:When the installation and configuration are complete, you need to register the resources to be managed by the PlateSpin Orchestrate system. Please refer to Section 3.0, First Use of Basic PlateSpin Orchestrate Components for detailed information about getting resources to manage in the PlateSpin Orchestrate system.

  8. Open the configuration log file (/var/opt/novell/novell_zenworks_orch_install.log) to make sure that the components were correctly configured.

    You might want to change the configuration if you change your mind about some of the parameters you provided in the configuration process. For information about what to do in these circumstances, see Section 2.3.3, Correcting Configuration Errors and Repeating the Configuration Process.

  9. Access the PlateSpin Orchestrate Administrator Information Page to verify that the Orchestrate Server is installed and running. Use the following URL to open the page in a Web browser:

    http://DNS_name_or_IP_address_of_Orchestrate_Server:8001

    The Administrator Information page includes links to separate installation programs (installers) for the PlateSpin Orchestrate Agent and the PlateSpin Orchestrate Clients. The installers are used for various operating systems. You can download the installers and install the agent or the clients on any supported machine you choose. For more information, see Section 2.4, Installing the Orchestrate Agent Only.

  10. (Conditional and Optional) If you installed the PlateSpin Orchestrate Clients, you can increase the heap size that the JVM handles. This enables the console to manage a larger number of objects.

    1. Open the zoc bash shell script at /opt/novell/zenworks/zos/server/bin.

      On Microsoft Windows, the path to the console is program files\novell\zos\clients\bin\zoc.bat. For more information, see Section 2.4, Installing the Orchestrate Agent Only.

    2. Inside the script, find the following line where the JVM parameters are defined:

      JVMARGS="-Xmx256m -Xms256m -Xmn64m -XX:NewSize=64m -XX:MaxNewSize=64m"

      The -Xmx argument specifies the maximum heap size for the JVM. Increasing the heap size prevents a JVM out of memory condition.

    3. Change the value in the -Xmx argument from 256MB to 512MB.

2.3.2 PlateSpin Orchestrate Configuration Information

The following table describes the information required by the PlateSpin Orchestrate configuration (config) and the configuration wizard (guiconfig). The information is organized to make it readily available if you want to evaluate the entire product. The information is listed in the order that it is presented in the configuration file.

Table 2-1 PlateSpin Orchestrate Configuration Information

Configuration Information

Explanation

Orchestrate Monitoring

If you installed the Orchestrate Monitoring Server and the Orchestrate Monitoring Agent, the following questions are asked during the configuration process.

  • Monitored or Monitoring: You can configure this host to be the Monitoring Server or a monitored node. Configure this host as the Monitoring Server? (y/n)

    • Default value = yes (if the Monitoring Server is installed on this machine)

    • This question always appears if you installed the Monitoring Server component.

    • Because the configuration already knows that Orchestrate Monitoring is installed, you are choosing whether the machine being installed to is to be the controlling node for monitoring.

  • Monitoring Server: Specify the hostname or IP address of the Monitoring Server.

    • Default value = none

    • This question appears if you did not install the Monitoring Server on this machine. It is the name or IP address of the server (also known as the controlling node) where the Monitoring Agent will send its metrics.

  • Location: Enter a name describing this monitored computer’s location.

    • Default value = name_of_this_computer

    • This question always appears if you specify this computer as a monitored node (that is, you answer no when asked if this machine is to be the Monitoring Server).

    • The descriptive name you create here appears in the Monitoring user interface as the location of the device.

Type of Configuration

Select whether this is a standard or high-availability server configuration.

  • Default value = standard

  • Your answer here determines whether this is a standard installation or a High Availability installation.

    This section discusses standard installation, so specify s (for standard) or press Enter to accept the default. For more information about High Availability configuration, see the PlateSpin Orchestrate 2.5 High Availability Configuration Guide.

Orchestrate Server

Because the PlateSpin Orchestrate Server must always be installed for a full PlateSpin Orchestrate system, the following questions are always asked when you have installed server patterns prior to the configuration process:

  • PlateSpin Orchestrate grid name: Select a name for the Orchestrator grid.

    • Default = hostname_grid

    • A grid is an administrative domain container holding all of the objects in your network or data center. The PlateSpin Orchestrate Server monitors and manages these objects, including users, resources, and jobs.

    • The grid name you create here is displayed as the name for the container placed at the root of the tree in the Explorer panel of the Orchestrate Development Client.

  • PlateSpin Orchestrate Administrator user: Create an Administrator user for PlateSpin Orchestrate.

    • Default = none

    • The name you create here is required when you access the PlateSpin Orchestrate Console or the zosadmin command line interface.

    • You should remember this username for future use.

  • PlateSpin Orchestrate Administrator password: Specify the password for <Administrator user>

    • Default = none

    • This password you create here is required when you access the PlateSpin Orchestrate Console or the zosadmin command line interface.

    • You should remember this password for future use.

  • Audit Database: Enable auditing?

  • License file: Specify the full path to the license file.

    • Default = none

    • A license key (90-day evaluation license or a full license) is required to use this product. You should have received this key from Novell, then you should have subsequently copied it to the network location that you specify here. Be sure to include the name of the license file in the path.

Orchestrate Server (continued)

  • Server Portal 1: Specify the Server Portal port.

    • Default = 8080 (if Monitoring is installed) or 80 (if Monitoring is not installed).

    • Because Apache uses port 80 for Orchestrate Monitoring, it forwards non-monitoring requests to the Orchestrate Server on the port you specify here.

  • Administrator Information port 1: Specify the Administrator Information page port.

    • Default = 8001

    • Port 8001 on the Orchestrate Server provides access to an Administrator Information page that includes links to product documentation, agent and client installers, and product tools to help you understand and use the product. Specify another port number if 8001 is reserved for another use on this server.

  • Agent Port 1: Specify the Agent port.

    • Default = 8100

    • Port 8100 is used for communication between the Orchestrate Server and the Orchestrate Agent. Specify another port number if 8100 is reserved for another use.

  • TLS Certificate and Key 1: Generate a TLS certificate and key?

    Specify the full path to the TLS server certificate.

    Specify the full path to the TLS server private key.

    • Default = yes (the Orchestrate Server must generate a certificate and key for authentication)

    • A PEM-encoded TLS certificate and key is needed for secure communication between the Orchestrate Server and Orchestrate Agent.

    • If you respond with no, you need to provide the location of an existing certificate and key.

  • TLS Server Certificate 2: Specify the full path to the TLS server certificate.

    • Default = /etc/ssl/servercerts/servercert.pem

    • Specify the path to the existing TLS certificate.

  • TLS Server Key 2: Specify the full path to the TLS server private key.

    • Default = /etc/ssl/servercerts/serverkey.pem

    • Specify the path to the existing TLS private key.

  • Xen VNC password: Set the password that will be used for VNC on Xen virtualization hosts.

    • You will need this password when you log into virtual machines through VNC.

Orchestrate Agent

You can install and configure the Orchestrate Agent on any computing node. It is not necessary to install it on the same machine with the Orchestrate Server. If you installed the Orchestrate Agent, the following questions are asked in the configuration process.

  • Agent Name: Specify the name of the Orchestrate Agent on this node.

    • Default = none

    • The name you specify here is used by the Orchestrate Agent to authenticate to the Orchestrate Server.

  • Orchestrate Server: Specify the hostname or IP address of the Orchestrate Server.

    • Default = none

    • Specify the DNS name or IP address of the Orchestrate Server that this agent binds to.

  • Orchestrate Server Certificate 3: Do you want to specify an existing Orchestrate Server certificate?

    • Default = no

    • In configuring the Orchestrate Server, you either entered a PEM-encoded TLS certificate and key, or the system generated them.

    • If you answer no, the agent always trusts the server certificate. The certificate is downloaded from the Orchestrate Server to the Orchestrate Agent the first time the Agent connects.

    • If you answer yes, the Agent uses the certificate to verify that it is communicating with the correct server.

  • Virtual Machine 3: Is the host a Virtual Machine?

    • Default = no

    • This setting helps the PlateSpin Orchestrate system to know how to treat this host.

  • Agent Port 3: Specify the Agent port on the Orchestrate Server.

    • Default = 8100

    • Port 8100 is used for communication between the Orchestrate Server and the Orchestrate Agent. Specify another port number if 8100 is reserved for another use.

    • For an Agent installed on ESX, configure port 8101.

  • Agent IP Address: Specify an optional local bind address for the agent.

    • Default = none

    • If specified, the Agent tries to use this address locally when it connects to the Server. Otherwise, the operating system automatically sets the local address for each connection. This value is not normally needed.

  • Orchestrate Server Certificate File 4: Specify the path to the Orchestrate Server certificate file.

    • Default = /root/zos_server_cert.pem

Configuration Summary

When you have completed the configuration process, you have the option of viewing a summary of the configuration information.

  • View summary: Do you want to view summary information?

    • Default = yes

    • Answering yes to this question displays a list of all the PlateSpin Orchestrate components you have configured and the information with which they will be configured.

    • Answering no to this question starts the configuration program.

  • Configuration information change: Do you want to make any changes?

    • Default = no

    • Answering yes to this question restarts the configuration process so that you can make changes to the configuration information.

    • Answering no to this question starts the configuration program.

1 This configuration parameter is considered an advanced setting for the Orchestrate Server in the PlateSpin Orchestrate Configuration Wizard. If you select the Configure Advanced Settings check box in the wizard, you have the option of changing the default values. If you leave the check box deselected the setting is configured with normal defaults.

2 This configuration parameter is considered an advanced setting for the Orchestrate Server in the PlateSpin Orchestrate Configuration Wizard. If you select the Configure Advanced Settings check box in the wizard, this parameter is listed, but default values are provided only if the previous value is manually set to no.

3 This configuration parameter is considered an advanced setting for the Orchestrate Agent in the PlateSpin Orchestrate Configuration Wizard. If you select the Configure Advanced Settings check box in the wizard, the setting is configured with normal defaults. Leaving the check box deselected lets you have the option of changing the default value.

4 This configuration parameter is considered an advanced setting for the Orchestrate Agent in the PlateSpin Orchestrate Configuration Wizard, but only if you set Provide Existing Orchestrate Server Certificate to yes.

2.3.3 Correcting Configuration Errors and Repeating the Configuration Process

If you want to reconfigure the components of a PlateSpin Orchestrate system that you previously installed and configured, you can rerun the configuration script or the GUI Configuration Wizard and change your responses during the configuration process.

2.3.4 Uninstalling the Orchestrate Server

If you want to uninstall the Orchestrate Server at any time, see the detailed instructions in Section D.0, Uninstalling the Orchestrate Server

2.3.5 Installing and Configuring the Orchestrate Server for Use with a PostgreSQL Audit Database on a Different Host

When you install PlateSpin Orchestrate, you can optionally point it to a relational database that you can use to audit the work done by the product. There is no relational database management system bundled with the product, but because PlateSpin Orchestrate is supported by default on SLES 11 SP1, use a PostgreSQL database that ships with SLES 10 (or SLES 11)and configure it for use with PlateSpin Orchestrate auditing. If you want to use another database, you have to configure it separately for use with PlateSpin Orchestrate.

Installing the PostgreSQL Package and Dependencies on an Independent Host

When you enable and configure PlateSpin Orchestrate auditing, you create a small custom database and a simple schema that persists all of the PlateSpin Orchestrate jobs that have been run, along with their parameters.The database also maintains the login or logout activity of the PlateSpin Orchestrate 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 PlateSpin Orchestrate 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 Orchestrate Server cannot access the audit database.

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

If you want to run the database on the same host with PlateSpin Orchestrate, see Section 2.3.6, Installing and Configuring the Orchestrate Server for Use with a Local PostgreSQL Audit Database.

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 as follows:

# 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.
Detail
postgres> initdb
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale en_US.UTF-8.
The default database encoding has accordingly been set to UTF8.

creating directory /var/lib/pgsql/data ... ok
creating directory /var/lib/pgsql/data/global ... ok
creating directory /var/lib/pgsql/data/pg_xlog ... ok
creating directory /var/lib/pgsql/data/pg_xlog/archive_status ... ok
creating directory /var/lib/pgsql/data/pg_clog ... ok
creating directory /var/lib/pgsql/data/pg_subtrans ... ok
creating directory /var/lib/pgsql/data/pg_twophase ... ok
creating directory /var/lib/pgsql/data/pg_multixact/members ... ok
creating directory /var/lib/pgsql/data/pg_multixact/offsets ... ok
creating directory /var/lib/pgsql/data/base ... ok
creating directory /var/lib/pgsql/data/base/1 ... ok
creating directory /var/lib/pgsql/data/pg_tblspc ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
creating configuration files ... ok
creating template1 database in /var/lib/pgsql/data/base/1 ... ok
initializing pg_authid ... ok
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the -A option the
next time you run initdb.

Success. You can now start the database server using:

    postmaster -D /var/lib/pgsql/data
or
    pg_ctl -D /var/lib/pgsql/data -l logfile start

postgres> postmaster -i

Configuring PostgreSQL to Accept Remote Database Connections

To configure the PostgreSQL database to accept remote database connections, you need to add the following line to the /var/lib/pgsql/data/pg_hba.conf file:

host    all      all         0.0.0.0/0      trust

NOTE:After initial configuration, you can replace the 0.0.0.0/0 with a more restrictive mask. In a high availability server configuration, make sure that each host in the high availability cluster is enabled as a remote host.

For added security, the /var/lib/pgsql/data/pg_hba.conf file should list only the desired hosts. For example, only the Orchestrate Server would be included in the trust line.

After you make the change to the pg_hba.conf file, you need to specify the following command so that you do not receive an error when remote hosts try to connect:

pg_ctl reload

If pg_hba.conf is not configured when attempting to connect, an error similar to the following is displayed:

psql: FATAL:  no pg_hba.conf entry for host "164.99.15.64", user "postgres", database "postgres", SSL off

Depending on the environment, you might have to perform some additional configuration for remote database setup. Editing the listen_addresses section of the postgresql.conf file enables the database server to listen for incoming connections on the specified IP addresses. The following is an excerpt from that section of the file:

listen_addresses = 'localhost'
                    # what IP address(es) to listen on;
                    # comma-separated list of addresses;
                    # defaults to 'localhost', '*' = all

After you modify the listen_addresses entry in postgresql.conf, use the following command to restart the PostgreSQL server (recommended in the PostgreSQL documentation):

pg_ctl restart

Logging in Locally to the PostgreSQL Database

When you have installed the database, the next step is to check that you can connect to the database on the database host. The default admin username is postgres. Use the following commands to set up a password for the postgres user on the database host machine:

psql

NOTE:Remember the password. You need it to log in later to log in to the database.

Running this command results in a screen like this:

Welcome to psql 8.1.11, the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms
       \h for help with SQL commands
       \? for help with psql commands
       \g or terminate with semicolon to execute query
       \q to quit

postgres=# alter user postgres password 'pass';
ALTER ROLE
postgres=#

Creating a PlateSpin Orchestrate User for the PostgreSQL Database

Next, set up a PostgreSQL user to own the audit database schema before you run the server configuration script or the GUI Configuration Wizard.

  1. On the database host machine, use the following commands to log in as root at the database host machine:

    su - postgres

    psql

  2. At the psql prompt on the database host, use the following command to create an audit database schema user, for example:

    postgres=# create user zos password 'zos';

    CREATE ROLE

    NOTE:Single quotes surrounding the password are required.

  3. Enter the \q command at the psql prompt to exit the database.

Configuring the PlateSpin Orchestrate Audit Database on a Separate Host

The easiest way to configure the audit database is to do so when you configure the PlateSpin Orchestrate Server. Use the following procedure to configure the database.

NOTE:The questions presented in the text-based config script are shown here, but the questions presented in the graphical Configuration Wizard are similar.

  1. After you have installed the PlateSpin Orchestrate packages you want, run the configuration (either the config script or the graphical Configuration Wizard) until you see the following question:

    Enable Auditing (y/n) [no]:

  2. Enter yes to answer this question. The following question displays:

    Configure Audit DB (y/n) [no]:

  3. Enter yes to answer this question. The following question displays:

    Jdbc URL [jdbc:postgresql://localhost/]:

  4. Enter the URL of the server where PostgreSQL is running, then press Enter.

    jdbc:postgresql://IP_address_of_database_server/

    This is a standard JDBC URL because this is a Java server that JDBC for the interface database. The URL must be properly formed, with a slash and without a database name at the end. We do not recommend using “localhost” as the URL.

    The following prompt is displayed:

    DB Admin Username:

  5. Specify the PostgreSQL database administrator username, then press Enter.

    This is the same username that was created when PostgreSQL was installed. In most instances, the username is postgres.

    The following prompt is displayed:

    DB Admin Password:

  6. Specify the PostgreSQL database administrator password, then press Enter.

    The following prompt is displayed:

    Retype password:

  7. Retype the database administrator password to verify it, then press Enter. The following prompt is displayed:

    ZOS Audit Database Name [zos_db]:

  8. Specify the name of the database you want to create for PlateSpin Orchestrate auditing, then press Enter. The following prompt is displayed:

    Audit DB Username:

  9. Specify the name you want to use for the PostgreSQL database user that will be used by PlateSpin Orchestrate for auditing (that is, a user with Read and Write privileges, not the administrator), then press Enter. The following prompt is displayed:

    Audit DB Password:

  10. Specify the password you want to use for authentication by the designated PostgreSQL database user, then press Enter. The following prompt is displayed:

    Retype password:

  11. Retype the password, then press Enter.

After you retype the new audit database password, the configuration interview for the Orchestrate Server continues normally.

2.3.6 Installing and Configuring the Orchestrate Server for Use with a Local PostgreSQL Audit Database

When you install PlateSpin Orchestrate, you can optionally point it to a relational database that you can use to audit the work done by the product. There is no relational database management system bundled with the product, but because PlateSpin Orchestrate is supported by default on either SLES 10 SP3 or SLES 11 SP1, you can use a PostgreSQL database and configure it for use with PlateSpin Orchestrate auditing. If you want to use some other database, you must configure it separately for use with PlateSpin Orchestrate.

Installing the PostgreSQL Package and Dependencies

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

For more information, see Section 2.3.5, Installing and Configuring the Orchestrate Server for Use with a PostgreSQL Audit Database on a Different Host.

If your SLES 10 SP3 or SLES 11 SP1 machine does not have the PostgreSQL package 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.

Configuring PostgreSQL to Accept Local Database Connections

To configure the PostgreSQL database to accept remote database connections, you need to change the following line in the /var/lib/pgsql/data/pg_hba.conf file:

host    all      all         0.0.0.0/0      ident sameuser

The line should be changed as follows:

host    all      all         0.0.0.0/0      trust

Logging in Locally to the PostgreSQL Database

When you have installed the database, the next step is to check that you can connect to the database on the database host. The default admin username is postgres. Use the following commands to set up a password for the postgres user on the database host machine:

psql

NOTE:Remember the password. You need it to log in to the database later.

Running this command results in a screen like this:

Welcome to psql 8.1.11, the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms
       \h for help with SQL commands
       \? for help with psql commands
       \g or terminate with semicolon to execute query
       \q to quit

postgres=# alter user postgres password 'pass';
ALTER ROLE
postgres=#

NOTE:This is the message you would see if logging in to Postgres on a SLES 10 SP3 server. If logging in to Postgres on a SLES 11 SP1 server, you would see a message indicating a login to psql 8.3.9.

Installing and Configuring the Local PlateSpin Orchestrate Audit Database

When you enable and configure PlateSpin Orchestrate auditing, you create a small custom database and a simple schema that persists all of the PlateSpin Orchestrate jobs that have been run, along with their parameters.The database also maintains the login or logout activity of the PlateSpin Orchestrate users and resources.

The easiest way to configure the audit database is to do so when you configure the PlateSpin Orchestrate Server. Use the following procedure to configure the database.

NOTE:The questions presented in the text-based config script are shown here, but the questions presented in the graphical Configuration Wizard are similar.

  1. After you have installed the PlateSpin Orchestrate packages you want, run the configuration (either the config script or the graphical Configuration Wizard) until you see the following question:

    Enable Auditing (y/n) [no]:

  2. Enter yes to answer this question. The following question displays:

    Configure Audit DB (y/n) [no]:

  3. Enter yes to answer this question. the following question displays:

    Jdbc URL [jdbc:postgresql://localhost/]:

  4. Press Enter to accept the default (jdbc:postgresql://localhost/) by pressing Enter.

    This is a standard JDBC URL because this is a Java server that uses JDBC for the interface database. The URL must be properly formed, with a slash and without a database name at the end.

    The following prompt is displayed:

    DB Admin Username:

  5. Specify the PostgreSQL database administrator username, then press Enter.

    This is the same name that was specified when PostgreSQL was installed. In most instances, the username is postgres.

    The following prompt is displayed:

    DB Admin Password:

  6. Specify the PostgreSQL database administrator password, then press Enter.

    The following prompt is displayed:

    Retype password:

  7. Retype the database administrator password to verify it, then press Enter. The following prompt is displayed:

    ZOS Audit Database Name [zos_db]:

  8. Specify the name of the database you want to create for PlateSpin Orchestrate auditing, then press Enter. The following prompt is displayed:

    Audit DB Username:

  9. Specify the name you want to use for the PostgreSQL database user that will be used by PlateSpin Orchestrate for auditing (that is, a user with Read and Write privileges, not the administrator), then press Enter. The following prompt is displayed:

    Audit DB Password:

  10. Specify the password you want to use for authentication by the designated PostgreSQL database user, then press Enter. The following prompt is displayed:

    Retype password:

  11. Retype the password, then press Enter.

After you retype the new audit database password, the configuration interview for the Orchestrate Server continues normally.

2.3.7 Configuring the 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 /opt/novell/zenworks/zos/server/conf/audit_db_prep.sql.

    1. Replace the ${DB_NAME} variable with the PostgreSQL database name (for example, zos_db).

    2. Replace the ${DB_USER} variable with the PostgreSQL schema owner name (for example, zos).

  2. Use the following commands to run the modified script as the PostgreSQL database administrator:

    su - postgres

    psql -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 -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 Creating a PlateSpin Orchestrate User for the PostgreSQL Database. In this example, the username is zos and the password is zos.

  5. Confirm that the database username and password match the values you replaced in the variables of the .sql script. In this example, the username is zos and the password is zos.

  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.3.8 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 /opt/novell/zenworks/zos/server/conf/audit_db_def.sql.

    1. Replace the ${DB_NAME} variable with the PostgreSQL database name (for example, zos_db).

    2. Replace the ${DB_USER} variable with the PostgreSQL schema owner name (for example, 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 Creating a PlateSpin Orchestrate User for the PostgreSQL Database. In this example, the username is zos and the password is zos.

  5. Confirm that the database username and password match the values you replaced in the variables of the .sql script. In this example, the username is zos and the password is zos.

  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.3.9 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.

If your Grid Objects are named with long names, you might have to configure some of the table columns in the audit database with different sizes. Here are some things you need to know about the database and how to make such changes:

  • The default length of some names is pre-defined in the audit database. For example, the username and the resource name size in the audit database both default to 30 characters in allowable length.

  • The workflow id (originWorkflowId, parentWorkflowId) in the workflow table is constructed by concatenating the name of the user who invoked the job + the name of the deployed job + an instance number. The default size value is 100.

  • The job instance id (jobinstanceid) in the workflow table includes either the deployed name of the job or a server component name that invoked the job. For example, when the Scheduler invokes the job, then Scheduler is concatenated with the deployed job name. For example: Scheduler(cpuinfo).

  • The name column in the sessions table records both user and resource names.

The sql table definition is found at <server>/conf/audit_db_def.sql.

Use sql commands to change an existing table column. The following excerpts from the database show some table columns that you might need to change:

CREATE TABLE    actions          (

                targetobjectname        VARCHAR(50)      NOT NULL,
                username                VARCHAR(30)      NOT NULL,
                jobinstanceid           VARCHAR(100)   


CREATE TABLE workflow (

       jobId VARCHAR(100) NOT NULL,
       jobInstanceName VARCHAR(100) NOT NULL,
       deployedJobName VARCHAR(30) NOT NULL,
       originWorkflowId VARCHAR(100) NOT NULL,
       parentWorkflowId VARCHAR(100),
       username VARCHAR(30) NOT NULL,



CREATE TABLE sessions (

       name VARCHAR(30) NOT NULL,