This Server Portal Reference introduces the role and the Server Portal tool used by a PlateSpin Orchestrate job manager, also referred to as the PlateSpin Orchestrate “end user.” The guide provides an overview of the web-based Orchestrate Server Portal and explains how to use the portal to monitor and manage applications running on the PlateSpin Orchestrate Server. You can use this reference along with the information in PlateSpin Orchestrate 2.6 Command Line Reference. Along with the Platespin Orchestrate Server Portal, you can use the zos command line tool to monitor jobs.The guide is organized as follows:
The contents of this guide are of interest to 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.
As data center managers or IT or operations administrators, it is assumed that users of the product have the following background:
General understanding of network operating environments and systems architecture.
Knowledge of basic Linux shell commands and text editors.
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 www.novell.com/documentation/feedback.html and enter your comments there.
In addition to this Server Portal Reference, PlateSpin Orchestrate 2.6 includes the following additional guides that contain valuable information about the product:
This Server Portal Reference is updated periodically. To view the most recent version, visit the Novell Cloud Manager 1.1 documentation Web site and look for the documentation updates section included at the end of the book.
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
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.