PlateSpin Orchestrate 2.0 Installation and Configuration Guide

This Installation and Configuration Guide explains how to install, monitor, and manage applications running on PlateSpin® Orchestrate 2.0 from Novell®. It helps you plan the installation of the basic PlateSpin Orchestrate components, to install them, and helps you understand how to use them in basic usage scenarios.

Information in this guide includes content about the latest release, which currently stands at 2.0.1.

For information about installing and using the Virtual Machine management capabilities of PlateSpin Orchestrate, see the PlateSpin Orchestrate 2.0 VM Client Guide and Reference or the PlateSpin Orchestrate 2.0 Virtual Machine Management Guide.


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 has control of 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.

Additional Product Documentation

In addition to this Installation and Configuration Guide, PlateSpin Orchestrate 2.0 includes the following additional guides that contain valuable information about the product:

Documentation Updates

This Installation and Configuration Guide is updated periodically. To view the most recent version, visit the PlateSpin Orchestrate 2.0 documentation Web site and look for the documentation updates section included at the end of the book.

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.