PlateSpin Orchestrate 2.0 High Availability Configuration Guide

This High Availability Configuration Guide provides the information for installing and configuring PlateSpin® Orchestrate 2.0 from Novell® in a high availability environment. The guide provides information about the components and configuration steps necessary for preparing this environment, including instructions for configuring the PlateSpin Orchestrate Server in a cluster. The guide also provides some information regarding the behaviors you can expect from PlateSpin Orchestrate in various failover scenarios. The guide is organized as follows:


The contents of this guide are of interest to the following individuals:

VM Administrator: A PlateSpin Orchestrate virtual machine (VM) administrator manages the life cycle of the VMs in the enterprise, including creating, starting, stopping, migrating, and deleting VMs. For more information about the tasks and tools used by the VM administrator, see the PlateSpin Orchestrate 2.0 VM Client Guide and Reference.

Orchestrate Administrator: A PlateSpin Orchestrate Administrator deploys jobs, manages users, and monitors distributed computing resources. Administrators can also create and set policies for automating the usage of these computing resources. For more information about the tasks and tools used by the Orchestrate Administrator, see the PlateSpin Orchestrate 2.0 Administrator Reference.

User: The end user of PlateSpin Orchestrate, also called a “Job Manager,” runs and manages jobs that have been created by a Job Developer and deployed by the administrator. It is also possible that the end user could be a developer who has created applications to run on distributed computing resources. For more information about the tasks and tools used by the Job Manager, see the PlateSpin Orchestrate 2.0 Server Portal Reference.

Job Developer: The developer controsl a self-contained development system where he or she creates jobs and policies and tests them in a laboratory environment. When the jobs are tested and proven to function as intended, the developer delivers them to the PlateSpin Orchestrate administrator. For more information about the tasks and tools used by the job developer, see the PlateSpin Orchestrate 2.0 Developer Guide and Reference.

Prerequisite Skills

As data center managers or IT or operations administrators, it is assumed that users of the product have the following background:


We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the bottom of each page of the online documentation, or go to and enter your comments there.

Documentation Updates

For the most recent updates of this High Availability Guide, visit the PlateSpin Orchestrate 2. Web site.

Documentation Conventions

In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.

When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as Linux or UNIX*, should use forward slashes as required by your software.