Novell PLATESPIN ORCHESTRATE 2.0.2 - UPGARDE GUIDE... Operator's manual

Novell®
www.novell.com
novdocx (en) 13 May 2009
AUTHORIZED DOCUMENTATION
PlateSpin Orchestrate 2.0 Installation and Configuration Guide
PlateSpin Orchestrate
2.0.2
October 9, 2009
Installation and Configuration Guide

novdocx (en) 13 May 2009
Legal Notices
Novell, Inc., makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc., reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc., makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.,
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Copyright © 2008-2009 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc., has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).

novdocx (en) 13 May 2009
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.

4PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009

Contents 5
Contents
novdocx (en) 13 May 2009
About This Guide 7
1 Planning the Orchestrate Server Installation 9
1.1 PlateSpin Orchestrate Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1.1 Orchestrate Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.2 Required Network Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1.3 Orchestrate Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1.4 VM Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1.5 Orchestrate VM Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.1.6 Other Orchestrate Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2 Component Installation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2 Installation and Configuration 21
2.1 Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2 Installing and Configuring All PlateSpin Orchestrate Components Together. . . . . . . . . . . . . . 21
2.2.1 Installation and Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2.2 PlateSpin Orchestrate Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.2.3 Correcting Configuration Errors and Repeating the Configuration Process . . . . . . . 35
2.2.4 Installing and Configuring the Orchestrate Server for Use with a PostgreSQL Audit
Database on a Different Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.2.5 Installing and Configuring the Orchestrate Server for Use with a Local PostgreSQL
Audit Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.2.6 Configuring the Audit Database After PlateSpin Orchestrate Is Configured . . . . . . . 43
2.2.7 Configuring the Remote Audit Database after PlateSpin Orchestrate Is Configured. 44
2.2.8 Modifying Audit Database Tables to Accommodate Long Names. . . . . . . . . . . . . . . 44
2.3 Installing the Orchestrate Agent Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.3.1 Installing the Orchestrate Agent Using the Product ISO . . . . . . . . . . . . . . . . . . . . . . 46
2.3.2 Installing the Orchestrate Agent from the Administrator Information Page . . . . . . . . 60
2.3.3 Performing a Silent Install of the PlateSpin Orchestrate Agent on Multiple Network
Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
2.3.4 Installing the PlateSpin Orchestrate Agent on Other Supported Operating Systems 68
2.3.5 Automatically Installing the Orchestrate Agent on a VM Host Using a Job . . . . . . . . 72
2.4 Installing the Orchestrate Development Client Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.4.1 Installing the Orchestrate Development Client for Windows from the Administrator
Information Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
2.4.2 Using the ISO to Install the Orchestrate Development Client on Windows Machines 77
2.4.3 Installing the Orchestrate Development Client for SLES 10 From the Administrator
Information Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
2.4.4 Using the ISO to Install the Orchestrate Client on SLES 10 Machines . . . . . . . . . . . 78
2.4.5 Using the ISO to Install the Orchestrate Client on SLES 11 Machines . . . . . . . . . . . 79
2.5 Installing the Orchestrate VM Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
2.5.1 Minimum Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
2.5.2 Installing the Orchestrate VM Client on the Windows Operating System . . . . . . . . . 83
2.5.3 Installing Orchestrate VM Client in a Linux Environment. . . . . . . . . . . . . . . . . . . . . . 87
2.6 Uninstalling the VM Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
2.6.1 Uninstalling the Orchestrate VM Client from the Windows Operating System . . . . . 93
2.6.2 Uninstalling Orchestrate VM Client in a Linux Environment . . . . . . . . . . . . . . . . . . . 94
2.7 Determining the Product Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

6PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009
3 First Use of Basic PlateSpin Orchestrate Components 99
3.1 Walkthrough: Launching the PlateSpin Orchestrate Development Client . . . . . . . . . . . . . . . . 99
3.2 Walkthrough: Logging In to the PlateSpin Orchestrate Server . . . . . . . . . . . . . . . . . . . . . . . 101
3.2.1 Logging In by Using the Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
3.2.2 Logging In Explicitly to a Named Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
3.2.3 Logging In As Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
3.3 Walkthrough: Creating a Resource Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
3.3.1 Opening the Resources Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
3.3.2 Automatically Registering a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.3.3 Manually Registering a Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
3.3.4 Selecting a Resource for Manual Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
3.4 Walkthrough: Observing Discovery Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
3.5 Walkthrough: Deploying a Sample Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
3.6 Walkthrough: Creating a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
3.6.1 Opening the Users Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
3.6.2 Automatically Registering a User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
3.6.3 Manually Registering a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3.6.4 Logging In a User for Manual Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
3.7 Walkthrough: Running the Sample Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
3.8 Walkthrough: Looking at the Job After It Has Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
3.8.1 Verification at the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
3.8.2 Verification at the Jobs Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
3.8.3 Verification at the Server Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
3.9 Walkthrough: Using the zosadmin Command to Gather Information. . . . . . . . . . . . . . . . . . . 122
3.10 Stopping and Starting PlateSpin Orchestrate Components . . . . . . . . . . . . . . . . . . . . . . . . . . 122
3.10.1 Stopping and Starting the PlateSpin Orchestrate Server . . . . . . . . . . . . . . . . . . . . 123
3.10.2 Stopping and Starting the PlateSpin Orchestrate Agent . . . . . . . . . . . . . . . . . . . . . 123
3.10.3 Starting and Stopping the PlateSpin Orchestrate Development Client . . . . . . . . . . 124
A PlateSpin Orchestrate Components: Install Patterns 125
A.1 Installation Patterns in YaST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
B Installing the Orchestrate Monitoring Agent On Windows Machines 127
B.1 Installing the Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
B.1.1 Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
B.1.2 Installing the Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
B.1.3 Starting and Stopping the Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
B.1.4 Uninstalling the Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
B.2 Configuring the Monitoring Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
C Documentation Updates 131
C.1 October 9, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
C.2 July 15, 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
C.3 June 17, 2009 (2.0.2 Release). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

About This Guide 7
novdocx (en) 13 May 2009
About This 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.
Chapter 1, “Planning the Orchestrate Server Installation,” on page 9
Chapter 2, “Installation and Configuration,” on page 21
Chapter 3, “First Use of Basic PlateSpin Orchestrate Components,” on page 99
Appendix A, “PlateSpin Orchestrate Components: Install Patterns,” on page 125
Appendix B, “Installing the Orchestrate Monitoring Agent On Windows Machines,” on
page 127
Appendix C, “Documentation Updates,” on page 131
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.
Audience
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.

8PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009
Prerequisite Skills
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.
Feedback
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 (http://
www.novell.com/documentation/feedback.html) 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:
PlateSpin Orchestrate 2.0 Getting Started Reference
PlateSpin Orchestrate 2.0 Upgrade Guide
PlateSpin Orchestrate 2.0 High Availability Configuration Guide
PlateSpin Orchestrate 2.0 Administrator Reference
PlateSpin Orchestrate 2.0 VM Client Guide and Reference
PlateSpin Orchestrate 2.0 Virtual Machine Management Guide
PlateSpin Orchestrate 2.0 Development Client Reference
PlateSpin Orchestrate 2.0 Command Line Reference
PlateSpin Orchestrate 2.0 Server Portal Reference
PlateSpin Orchestrate 2.0 Developer Guide and Reference
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 (http://www.novell.com/documentation/
pso_orchestrate20/) 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 (®, TM, 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.

Planning the Orchestrate Server Installation
1
9
novdocx (en) 13 May 2009
1
Planning the Orchestrate Server
Installation
Before you begin installing PlateSpin®Orchestrate 2.0 from Novell®, you need to compare your
system resources with the requirements of the PlateSpin Orchestrate product. This section includes
information to help you with that evaluation so that you can adequately plan for the installation. The
following subsections are included:
Section 1.1, “PlateSpin Orchestrate Requirements,” on page 9
Section 1.2, “Component Installation Methods,” on page 16
1.1 PlateSpin Orchestrate Requirements
This section includes the hardware and software requirements for the following PlateSpin
Orchestrate components:
Section 1.1.1, “Orchestrate Server,” on page 10
Section 1.1.2, “Required Network Resources,” on page 11
Section 1.1.3, “Orchestrate Agent,” on page 13
Section 1.1.4, “VM Hosts,” on page 13
Section 1.1.5, “Orchestrate VM Client,” on page 14
Section 1.1.6, “Other Orchestrate Clients,” on page 15

10 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009
1.1.1 Orchestrate Server
The network machine where you install the Orchestrate Server software must meet the following
requirements:
Table 1-1 Orchestrate Server Requirements
NOTE: For more information about the requirements for virtual machine management, see
Section 1.1.5, “Orchestrate VM Client,” on page 14.
Item Requirement
Server Usage PlateSpin Orchestrate Server: Your server might be capable of
handling tasks in addition to the tasks an Orchestrate Server
performs for PlateSpin Orchestrate. However, we strongly
recommend that you install the Orchestrate Server software on a
dedicated server to ensure optimal performance. For example, you
might not want the server to host Novell eDirectoryTM.
NOTE: Although you can install the PlateSpin Orchestrate Server on
a Virtual Machine, do not try to manage that server using PlateSpin
Orchestrate. In addition, installing the server on a VM slows down
the performance of the product.
PlateSpin Orchestrate Monitoring Server: This pattern is an
Apache* Web server that is installed alongside the Orchestrate
Server.
Refer to the information in Appendix A, “PlateSpin Orchestrate
Components: Install Patterns,” on page 125 for more detail about these
patterns.
Operating System SUSE®Linux Enterprise Server 10 (SLES 10) Service Pack 2 (SP2),
on the 32-bit (x86) and 64-bit (x86-64) architectures (Intel* and
AMD* Opteron* processors)
Hardware Processor: Xeon* 2.8 GHz 32-bit, or equivalent AMD or Intel
processor (minimum); Dual-Core Xeon 4 GHz 32-bit or 64-bit
(recommended)
RAM: 2 GB minimum; 4 GB recommended
Disk Space: 350 MB minimum for installing; 1 GB recommended for
managing fewer than 100 resources.
Hostname Resolution The server must resolve device hostnames by using a method such as
DNS (recommended).
IP Address The server must have a static IP address or a permanently leased DHCP
address.

Planning the Orchestrate Server Installation 11
novdocx (en) 13 May 2009
1.1.2 Required Network Resources
The Orchestrate Server must allow traffic on TCP ports 80, 8001, 8100, 8101 (these four ports are
configurable), and UDP and TCP port 1099 (mandatory). The following list summarizes the
network resources required in a PlateSpin Orchestrate setup:
Port 80 is used for the Server Portal when monitoring is not installed. When monitoring is
installed, the monitoring related Apache server takes port 80 and the Server Portal is moved to
port 8080. The Monitoring Server transparently routes communication for the PlateSpin
Orchestrate Server Portal to port 8080.
Port 8001 is used for communication with the Administrator Information page.
Port 8100 is used with a custom protocol for communication with the Orchestrate Agent and
for invoking the zos command line interface or opening the Java* Developer’s toolkit.
Port 8101 is also used for invoking the zos command line interface or opening the Java
Developer’s toolkit by using TLS.
Port 1099 is used with RMI for invoking the zosadmin command line interface and/or for
running the Orchestrate Development Client.
Monitored systems (physical and virtual) send metrics to the Monitoring Server on UDP port 8649.
The Monitoring Server is installed on the same system as the PlateSpin Orchestrate Server.
Connections to VM consoles are accommodated through a VNC client. Typically, this means TCP
port 5900 for the first VM on a VM host, 5901 for the second, and so on. Note that these connections
go to the VM host, exposing the console on behalf of the VM.
Datagrid multicast file transfers use UDP ports 4011-4014 are used. UDP port 4000 is used as a
datagrid multicast request port and a control channel port. Multicast groups for datagrid multicast-
based file transfers are 239.192.10.10-14.
The following illustration shows these relationships.

12 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009
Figure 1-1 PlateSpin Orchestrate Network Resources
Orchestrate Service
Admin Portal-TCP 8001
User Portal-TCP 8080
(optionally TCP 80)
VM Builders
OS Install Sources
Auto-install files
Managed
Resources
VM Guests & Hosts
Monitoring Service
Monitor Web Server-TCP 80
Monitor Collector-TCP 8649
(optionally TCP 80)
TCP 8100
JMX 1099
JMX 1099
JMX 1099
TCP 8101
TCP 8100
TCP 8101
“zos” CLI
“zosadmin” CLI
Orchestrate
Development Client
Orchestrate VM
Client
TCP 8100
TCP 8100
TCP 8101
UDP 4011-4014
(multicast)
UDP/TCP 8649
TCP 8649 (localhost)
TCP 5900, 5901, etc. for VM console access

Planning the Orchestrate Server Installation 13
novdocx (en) 13 May 2009
1.1.3 Orchestrate Agent
PlateSpin Orchestrate manages jobs on and gathers data about data center computing resources
running the PlateSpin Orchestrate Agent and meet the following minimum requirements:
Table 1-2 Orchestrate Agent Requirements
1.1.4 VM Hosts
We recommend that computers designated as VM hosts in your data center be able to host the VM
and run it according to designated parameters of the specific VM. The processor architecture must
match the designated VM’s processor in architecture, although not in version number. In order for a
machine to serve as a host machine, it must also have a hypervisor installed along with the operating
system. For a detailed list of the supported hypervisors, see Table 2-2 on page 69.
Table 1-3 Minimum and Recommended Hardware Requirements for VM Host Machines
Item Requirement
Operating System Linux machines:
SUSE Linux Enterprise Server 9 SP3 (32-bit or 64-bit)
SUSE Linux Enterprise Server 10 SP1 (32-bit or 64-bit)
SUSE Linux Enterprise Server 10 SP2 (32-bit or 64-bit)
SUSE Linux Enterprise Server 11 (32-bit or 64-bit)
Red Hat* Enterprise Linux* 4 (32-bit or 64-bit)
Red Hat Enterprise Linux 5 (32-bit or 64-bit)
Windows* machines:
Windows Server* 2003 (32-bit or 64-bit)
Windows Server 2008 (32-bit or 64-bit)
VMware* console operating systems:
ESX machine:
ESX 3.0.x/3.5.x
Hardware The Orchestrate Agent does not require a minimum hardware
configuration other than a minimum recommended disk space of 100 MB.
TCP Ports The computing node communicates with the Orchestrate Server over a
custom protocol. The server listens for the agent on port 8100 and 8101
(port 8101 is for secure agent connections). Network firewalls need to
allow outgoing agent connections to these ports on the server.
Host Operating System Minimum Requirements Recommended Hardware
SLES 11 x86 or x86_64
2 GB RAM
30 GB Hard Drive Space
x86 or x86_64
4+ GB RAM
100+ GB Hard Drive Space

14 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009
1.1.5 Orchestrate VM Client
The VM Client allows you to manage VMs in your enterprise. You can install the VM Client
interface on the following platforms:
Table 1-4 VM Client Supported Operating Systems and Installation Files
SLES 10 SP2 x86 or x86_64
2 GB RAM
30 GB Hard Drive Space
x86 or x86_64
4+ GB RAM
100+ GB Hard Drive Space
Windows Server 2008 enabled
with Hyper-V
1GHz (x86 processor) or
1.4GHz (x64 processor)
512MB RAM
10 GB Hard Drive Space
2+ GHz
2+ GB RAM
40+ GB Hard Drive Space
ESX 3.0.x/3.5.x*Subject to the VMWare support
matrix
*Subject to the VMWare support
matrix
VMware Virtual Center *Subject to the VMWare support
matrix
*Subject to the VMWare support
matrix
VMware Server *Subject to the VMWare support
matrix
*Subject to the VMWare support
matrix
Operating System Installation File
SLES 10 SP2 (32-bit)
SLES 10 SP2 (64-bit)
/i386/SLE10/nvmminst
/x86_64/SLE10/nvmminst
SLES 11 or SLED 11 (32-bit)
SLES 11 or SLED 11 (64-bit)
sles11/i386/SLE11/nvmminst
sles11/x86_64/SLE11/nvmminst
Windows XP or Vista (32-bit or 64-bit) \Windows\nvmminst.exe
Host Operating System Minimum Requirements Recommended Hardware

Planning the Orchestrate Server Installation 15
novdocx (en) 13 May 2009
1.1.6 Other Orchestrate Clients
You can monitor and run jobs, run the command line interfaces, and create and modify jobs by using
the tools and monitors included with the PlateSpin Orchestrate Clients. PlateSpin Orchestrate
manages jobs on and gathers data about data center computing resources that meet the following
minimum requirements:
Table 1-5 Orchestrate Client Requirements
IMPORTANT: The platforms listed here have been tested for the 2.0 release, and are the only
platforms supported at this time.
Some of the install programs for other operating systems that are embedded with the Administrator
Information page have not been tested for this release.
Item Requirement
Operating System Linux machines:
SUSE Linux Enterprise Server 10 SP2 (32-bit or 64-bit)
SUSE Linux Enterprise Server 11 (32-bit or 64-bit)
SUSE Linux Enterprise Desktop 11 (32-bit or 64 bit)
Windows machines:
Windows XP (32-bit or 64-bit)
Windows Vista* (32-bit or 64-bit)
Hardware The Orchestrate Development Client installation does not require a
minimum hardware configuration other than a minimum recommended
disk space of 100 MB and an SVGA-grade monitor.
TCP Ports The Orchestrate Clients consist of various components that communicate
with the Orchestrate Server:
Port 8100 is used with a custom protocol for invoking the zos
command line interface or for opening the SDK (Java Developer’s
toolkit).
Port 8101 is also used for invoking the zos command line interface
or opening the Java Developer’s toolkit by using TLS.
Port 1099 is used with RMI for invoking the zosadmin command line
interface or for running the Orchestrate Development Client.

16 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009
1.2 Component Installation Methods
The following table shows the installation methods you can use for the Orchestrate Server, the
Orchestrate Agents, the Orchestrate VM Client, and the other Orchestrate clients:
Table 1-6 PlateSpin Orchestrate Installation Methods and Sources
PlateSpin
Orchestrate
Component
Supported Operating
System Installation Method and Source
Orchestrate
Server
SLES 10 SP2 (32-bit
or 64-bit)
Available as an RPM package distribution (ISO images, 32-bit or
64-bit) from the Novell Downloads Web site (http://
download.novell.com) after purchase and receipt of a license key.
Uses the Add-On CD installation (PlateSpin Orchestrate Server
pattern) available in YaST.
Requires server configuration after installation by using a text
interface at the Linux console (. /config ) or by using a GUI
program (.
/guiconfig ).
For installation details, see Section 2.2, “Installing and
Configuring All PlateSpin Orchestrate Components Together,” on
page 21.

Planning the Orchestrate Server Installation 17
novdocx (en) 13 May 2009
Orchestrate
Agent
SLES 9 SP3 (32-
bit or 64-bit)
SLES 10 SP1
(32-bit or 64-bit)
SLES 10 SP2
(32-bit or 64-bit)
SLES 11 (32-bit
or 64-bit)
RHEL 4 (32-bit or
64-bit)
RHEL 5 (32-bit or
64-bit)
Available as an RPM package distribution (ISO images, 32-
bit or 64-bit) from the Novell Downloads Web site (http://
download.novell.com) after purchase and receipt of a
license key. Uses the Add-On CD installation (PlateSpin
Orchestrate Agent pattern) available in YaST.
For installation details, see Section 2.2, “Installing and
Configuring All PlateSpin Orchestrate Components
Together,” on page 21.
NOTE: YaST installation is supported only on SLES 10 and
SLES 11, not on RHEL platforms or SLES 9. For these last
two platforms, use either the RPMs located on the ISO
(found in the RHEL or SLES9 directories) or use the
.sh file
that you can download from the Administrator Information
page. See Section 2.3, “Installing the Orchestrate Agent
Only,” on page 45.)
After Orchestrate Server installation, available from the
server through a downloadable installation script ( .sh file)
from the Administrator Information page (port 8001) or run
as a post-install from the ISO image.
For installation details, see Section 2.3, “Installing the
Orchestrate Agent Only,” on page 45.
Windows Server
2003 (32-bit or
64-bit)
Windows Server
2008 (32-bit or
64-bit)
After Orchestrate Server installation, available from the
server through a downloadable installation script ( .sh file)
from the Administrator Information page (port 8001) or run
as a post-install from the ISO image.
For installation details, see Section 2.3, “Installing the
Orchestrate Agent Only,” on page 45.
After Orchestrate Server installation, available as a
downloadable GUI installation program ( .exe file) from the
Administrator Information page (port 8001).
For installation details, see “Using the ISO to Install the
Orchestrate Agent on Windows Machines” on page 60 in
Section 2.3, “Installing the Orchestrate Agent Only,” on
page 45.
VMware ESX
3.0.x
VMware ESX
3.5.x
Available as an RPM package distribution (ISO images, 32-
bit or 64-bit) from the Novell Downloads Web site (http://
download.novell.com) after purchase and receipt of a
license key. Uses the Add-On CD installation (PlateSpin
Orchestrate Agent pattern) available in YaST.
For installation details, see Section 2.2, “Installing and
Configuring All PlateSpin Orchestrate Components
Together,” on page 21.
After Orchestrate Server installation, available from the
server through a downloadable RPM from the Administrator
Information page (port 8001) or run as a post-install from the
ISO image.
For installation details, see Section 2.3, “Installing the
Orchestrate Agent Only,” on page 45.
PlateSpin
Orchestrate
Component
Supported Operating
System Installation Method and Source

18 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009
Orchestrate
Clients
SLES 10 SP2
(32-bit or 64-bit)
SLES 11 (32-bit
or 64-bit)
SLED 11 (32-bit
or 64-bit)
Available as an RPM package distribution (ISO images, 32-
bit or 64-bit) available from the Novell Downloads Web site
(http://download.novell.com) after purchase and receipt of a
license key. Uses the Add-On CD installation (PlateSpin
Orchestrate Agent pattern) available in YaST.
For installation details, see Section 2.2, “Installing and
Configuring All PlateSpin Orchestrate Components
Together,” on page 21.
After Orchestrate Server installation, available from the
server through a downloadable installation script ( .sh file)
from the Administrator Information page (port 8001) or run
as a post-install from the ISO image.
For installation details, see Section 2.3, “Installing the
Orchestrate Agent Only,” on page 45.
Windows XP (32-
bit or 64-bit)
Windows Vista
(32-bit or 64-bit)
After Orchestrate Server installation, available as a
downloadable GUI installation program ( .exe file) in the
ISO images (32-bit or 64-bit).
For installation details, see in “Using the ISO to Install the
Orchestrate Agent on Windows Machines” on page 60 in
Installing the Orchestrate Agent Only.
After Orchestrate Server installation, available as a
downloadable GUI installation program ( .exe file) from the
Administrator Information page (port 8001).
For installation details, see in “Using the ISO to Install the
Orchestrate Agent on Windows Machines” on page 60 in
Installing the Orchestrate Agent Only.
VM Builder SLES 10 SP2
(32-bit and 64-
bit)
SLES 11 (32-bit
and 64-bit)
YaST Installation (required in order to use VM Client)
Monitoring
Server
SLES 10 SP2
(32-bit and 64-
bit)
YaST Installation (required in order to use VM Client)
PlateSpin
Orchestrate
Component
Supported Operating
System Installation Method and Source

Planning the Orchestrate Server Installation 19
novdocx (en) 13 May 2009
NOTE: If you install or configure PlateSpin Orchestrate components using a trial key, the product
behaves normally for 90 days, although the trial key controls the number of users and managed
nodes you can configure. For fully supported functionality, product components require a purchased
license key. contact your Novell Sales Representative or a Certified Novell Partner for purchase
information.
Monitoring
Agent
SLES 9 SP3 (32-
bit and 64-bit)
SLES 10 SP1
(32-bit and 64-
bit)
SLES 10 SP2
(32-bit and 64-
bit)
SLES 11 (32-bit
and 64-bit)
RHEL 4 (32-bit
and 64-bit)
RHEL 5 (32-bit
and 64-bit)
YaST Installation or RPMs on ISO (required in order to use VM
Client)
PlateSpin
Orchestrate
Component
Supported Operating
System Installation Method and Source

20 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009