Novell PLATESPIN ORCHESTRATE Installation and Configuration Guide
Installation and Configuration Guide
Novell®
PlateSpin Orchestrate
novdocx (en) 13 May 2009
AUTHORIZED DOCUMENTATION
2.0.2
October 9, 2009
www.novell.com
PlateSpin Orchestrate 2.0 Installation and Configuration Guide
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.
novdocx (en) 13 May 2009
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).
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.
novdocx (en) 13 May 2009
novdocx (en) 13 May 2009
4 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
Contents
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
novdocx (en) 13 May 2009
Contents 5
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
novdocx (en) 13 May 2009
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
6 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
About This Guide
novdocx (en) 13 May 2009
This Installation and Configuration Guide explains how to install, monitor, and manage applications
running on PlateSpin
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:
®
Orchestrate 2.0 from Novell®. It helps you plan the installation of the basic
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.
About This Guide 7
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:
novdocx (en) 13 May 2009
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.
8 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
1
Planning the Orchestrate Server
novdocx (en) 13 May 2009
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
1
Section 1.1.6, “Other Orchestrate Clients,” on page 15
Planning the Orchestrate Server Installation
9
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
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 eDirectory
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.
TM
.
novdocx (en) 13 May 2009
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
Hardware
SUSE
Processor: Xeon* 2.8 GHz 32-bit, or equivalent AMD or Intel
®
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)
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.
NOTE: For more information about the requirements for virtual machine management, see
Section 1.1.5, “Orchestrate VM Client,” on page 14.
10 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
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.
novdocx (en) 13 May 2009
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 multicastbased file transfers are 239.192.10.10-14.
The following illustration shows these relationships.
Planning the Orchestrate Server Installation 11
Figure 1-1 PlateSpin Orchestrate Network Resources
VM Builders
OS Install Sources
Auto-install files
novdocx (en) 13 May 2009
Managed
Resources
VM Guests & Hosts
TCP 8649 (localhost)
TCP 8100
TCP 8101
TCP 8100
TCP 8101
UDP 4011-4014
(multicast)
UDP/TCP 8649
Orchestrate Service
Admin Portal-TCP 8001
User Portal-TCP 8080
(optionally TCP 80)
Monitoring Service
Monitor Web Server-TCP 80
Monitor Collector-TCP 8649
(optionally TCP 80)
TCP 5900, 5901, etc. for VM console access
TCP 8100
TCP 8101
“zos” CLI
JMX 1099
“zosadmin” CLI
JMX 1099
Orchestrate
Development Client
JMX 1099
TCP 8100
Orchestrate VM
Client
12 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
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
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)
novdocx (en) 13 May 2009
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.
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
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
Planning the Orchestrate Server Installation 13
Host Operating System Minimum Requirements Recommended Hardware
novdocx (en) 13 May 2009
SLES 10 SP2 x86 or x86_64
2 GB RAM
30 GB Hard Drive Space
Windows Server 2008 enabled
with Hyper-V
1GHz (x86 processor) or
1.4GHz (x64 processor)
512MB RAM
x86 or x86_64
4+ GB RAM
100+ GB Hard Drive Space
2+ GHz
2+ GB RAM
40+ GB Hard Drive Space
10 GB Hard Drive Space
ESX 3.0.x/3.5.x *Subject to the VMWare support
matrix
VMware Virtual Center *Subject to the VMWare support
matrix
VMware Server *Subject to the VMWare support
matrix
*Subject to the VMWare support
matrix
*Subject to the VMWare support
matrix
*Subject to the VMWare support
matrix
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
Operating System Installation File
SLES 10 SP2 (32-bit)
SLES 10 SP2 (64-bit)
SLES 11 or SLED 11 (32-bit)
SLES 11 or SLED 11 (64-bit)
Windows XP or Vista (32-bit or 64-bit)
/i386/SLE10/nvmminst
/x86_64/SLE10/nvmminst
sles11/i386/SLE11/nvmminst
sles11/x86_64/SLE11/nvmminst
\Windows\nvmminst.exe
14 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
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
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)
novdocx (en) 13 May 2009
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.
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.
Planning the Orchestrate Server Installation 15
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
novdocx (en) 13 May 2009
PlateSpin
Orchestrate
Component
Orchestrate
Server
Supported Operating
System
SLES 10 SP2 (32-bit
or 64-bit)
Installation Method and Source
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 (.
program (.
For installation details, see Section 2.2, “Installing and
Configuring All PlateSpin Orchestrate Components Together,” on
page 21.
/guiconfig
).
/config
) or by using a GUI
16 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009
PlateSpin
Orchestrate
Component
Orchestrate
Agent
Supported Operating
System
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)
Installation Method and Source
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
that you can download from the Administrator Information
page. See Section 2.3, “Installing the Orchestrate Agent
Only,” on page 45.)
.sh
After Orchestrate Server installation, available from the
server through a downloadable installation script (
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.
.sh
file
file)
Windows Server
2003 (32-bit or
64-bit)
Windows Server
2008 (32-bit or
64-bit)
VMware ESX
3.0.x
VMware ESX
3.5.x
After Orchestrate Server installation, available from the
server through a downloadable installation script (
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.
.sh
file)
After Orchestrate Server installation, available as a
downloadable GUI installation program (
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.
.exe
file) from the
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.
Planning the Orchestrate Server Installation 17
novdocx (en) 13 May 2009
PlateSpin
Orchestrate
Component
Orchestrate
Clients
Supported Operating
System
SLES 10 SP2
(32-bit or 64-bit)
SLES 11 (32-bit
or 64-bit)
SLED 11 (32-bit
or 64-bit)
Windows XP (32-
bit or 64-bit)
Windows Vista
(32-bit or 64-bit)
Installation Method and Source
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 (
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.
.sh
After Orchestrate Server installation, available as a
downloadable GUI installation program (
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.
.exe
file) in the
After Orchestrate Server installation, available as a
downloadable GUI installation program (
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.
.exe
file) from the
file)
VM Builder SLES 10 SP2
(32-bit and 64bit)
SLES 11 (32-bit
and 64-bit)
Monitoring
Server
SLES 10 SP2
(32-bit and 64bit)
YaST Installation (required in order to use VM Client)
YaST Installation (required in order to use VM Client)
18 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
novdocx (en) 13 May 2009
PlateSpin
Orchestrate
Component
Monitoring
Agent
Supported Operating
System
SLES 9 SP3 (32-
bit and 64-bit)
Installation Method and Source
YaST Installation or RPMs on ISO (required in order to use VM
Client)
SLES 10 SP1
(32-bit and 64bit)
SLES 10 SP2
(32-bit and 64bit)
SLES 11 (32-bit
and 64-bit)
RHEL 4 (32-bit
and 64-bit)
RHEL 5 (32-bit
and 64-bit)
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.
Planning the Orchestrate Server Installation 19
novdocx (en) 13 May 2009
20 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
2
Installation and Configuration
novdocx (en) 13 May 2009
2
This section explains the installation and setup of various components of PlateSpin® Orchestrate
from Novell
Section 2.1, “Installation Prerequisites,” on page 21
Section 2.2, “Installing and Configuring All PlateSpin Orchestrate Components Together,” on
page 21
Section 2.3, “Installing the Orchestrate Agent Only,” on page 45
Section 2.4, “Installing the Orchestrate Development Client Only,” on page 72
Section 2.5, “Installing the Orchestrate VM Client,” on page 81
Section 2.6, “Uninstalling the VM Client,” on page 92
Section 2.7, “Determining the Product Version,” on page 96
®
.
2.1 Installation Prerequisites
During installation of an PlateSpin Orchestrate component, you need to have the following
information available:
(Optional) certificate authority information (internal, or signed certificate, private key, and
public certificate)
License key (a 90-day trial option is available)
For more information on these items, see Table 2-1, “PlateSpin Orchestrate Configuration
Information,” on page 31.
2.2 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
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.
The PlateSpin Orchestrate Server (Orchestrate Server) is supported on SUSE Linux Enterprise
Server 10 Service Pack 2 (SLES 10 SP2) only. 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 Chapter 3, “First Use of Basic PlateSpin Orchestrate Components,”
on page 99.
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,” on page 9.
®
Linux* Enterprise Server (SLES) 10 machine.
Installation and Configuration
21
The VM Builder cannot be installed on a VM and must only be installed on the host operating
system of the VM Builder node. Multiple servers with VM host capability can be used as VM
Builder machines to make the VM Builder group.
This section includes the following information:
Section 2.2.1, “Installation and Configuration Steps,” on page 22
Section 2.2.2, “PlateSpin Orchestrate Configuration Information,” on page 30
Section 2.2.3, “Correcting Configuration Errors and Repeating the Configuration Process,” on
page 35
Section 2.2.4, “Installing and Configuring the Orchestrate Server for Use with a PostgreSQL
Audit Database on a Different Host,” on page 35
Section 2.2.5, “Installing and Configuring the Orchestrate Server for Use with a Local
PostgreSQL Audit Database,” on page 40
Section 2.2.6, “Configuring the Audit Database After PlateSpin Orchestrate Is Configured,” on
page 43
Section 2.2.7, “Configuring the Remote Audit Database after PlateSpin Orchestrate Is
Configured,” on page 44
novdocx (en) 13 May 2009
Section 2.2.8, “Modifying Audit Database Tables to Accommodate Long Names,” on page 44
2.2.1 Installation and Configuration Steps
To install and configure a complete PlateSpin Orchestrate system (except the VM Client) on a SLES
machine:
1 Review Chapter 1, “Planning the Orchestrate Server Installation,” on page 9 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:
root
4a Log in to the target SLES 10 SP2 server as
4b In the YaST Control Center, click Software, then click Add-on Product to display the Add-
on Product Media dialog box.
4c In the Add-on Product Media dialog box, select the ISO media (Local Directory or DVD)
to install.
4c1 (Conditional) Select DVD, click Next, insert the DVD, then click Continue.
, then open YaST2.
4c2 (Conditional) Select Local Directory, click Next, select the ISO Image check box,
browse to ISO on the file system, then click OK.
4d Read and accept the license agreement, then click Next to display YaST2.
4e In YaST2, click the Filter drop-down menu, then select Patterns to display the install
patterns available on the PlateSpin Orchestrate ISO.
22 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
4f 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.
novdocx (en) 13 May 2009
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 Appendix A, “PlateSpin Orchestrate
Components: Install Patterns,” on page 125.
Virtual Machine Builder: This pattern is an agent that builds the VM images as the
jobs are sent to it by the Orchestrate Server. The Xen hypervisor must exist on the
server where this pattern is installed.
For better scale and performance, we recommend that this pattern be installed to a
different server than the one where the Orchestrate Server is installed.
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 Appendix A, “PlateSpin Orchestrate Components: Install
Patterns,” on page 125 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.3, “Installing the Orchestrate Agent
Only,” on page 45.
4g Click Accept to install the packages.
Installation and Configuration 23
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.
TIP: 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:
6a Make sure you are logged in as
root
to run the configuration script.
6b 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.
novdocx (en) 13 May 2009
This program will configure PlateSpin Orchestrate 2.0
Select whether this is a new install or an upgrade
i) install
u) upgrade
- - - - - -
Selection [install]:
6c 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.0 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
4) yes PlateSpin Orchestrate VM Builder
Select from the following:
1 - 4) toggle selection status
a) all
n) none
f) finished making selections
q) quit -- exit the program
Selection [finish]:
24 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
The list shows the products listed whose patterns you previously installed.
6d Determine which installed products you want to configure. The options are listed with
option numbers.
6d1 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.
6d2 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.2.2,
“PlateSpin Orchestrate Configuration Information,” on page 30
6d3 When the you have finished answering questions about the configuration, continue
with Step 8.
7 (Conditional) If you are using the GUI Configuration Wizard:
7a 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.
novdocx (en) 13 May 2009
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.
7b Click Next to display the license agreement.
Installation and Configuration 25
7c Accept the agreement, then click Next to display the PlateSpin Orchestrate components
page.
novdocx (en) 13 May 2009
This section discusses new installation. For information about upgrading, see the
PlateSpin Orchestrate 2.0 Upgrade Guide.
7d Select New Installation, then click Next to display the PlateSpin Orchestrate components
page.
26 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
The components page lists the PlateSpin Orchestrate components that are available for
configuration. By default, all installed components are selected for configuration.
7e Click Next to confirm the components you want to install.
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.
novdocx (en) 13 May 2009
See Step 7e1 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 7f to continue.
7e1 (Conditional) Specify a name for this monitored node. The default name is the
computer name.
Select the Configure this computer check box if you want this computer to be a
Monitoring Server, then click Next and continue with Step 7f.
Installation and Configuration 27
If you do not select this check box and click Next, a second page of the Monitoring
Configuration Wizard is displayed.
Continue with Step 7e2.
7e2 (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.
7e3 Click Next and continue with Step 7f.
7f (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
novdocx (en) 13 May 2009
If you are configuring this Orchestrate Server for a non-clustered instance, click Next.
7g 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,”
on page 31 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.
28 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
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.
novdocx (en) 13 May 2009
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
7h Click Next to display the following wizard page.
7i Click Next to launch the configuration script. When the configuration is finished, the
following page is displayed:
7j Click Finish to close the configuration wizard.
Installation and Configuration 29
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
Chapter 3, “First Use of Basic PlateSpin Orchestrate Components,” on page 99 for
detailed information about getting resources to manage in the PlateSpin Orchestrate
system.
novdocx (en) 13 May 2009
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.2.3, “Correcting Configuration Errors and Repeating the
Configuration Process,” on page 35.
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.3,
“Installing the Orchestrate Agent Only,” on page 45.
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.
10a Open the
bash shell script at
/opt/novell/zenworks/zos/server/bin
.
zoc
On Microsoft* Windows*, the path to the console is
files\novell\zos\clients\bin\zoc.bat
. For more information, see Section 2.3,
“Installing the Orchestrate Agent Only,” on page 45.
10b 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.
)
-Xmx
10c Change the value in the
argument from 256MB to 512MB.
2.2.2 PlateSpin Orchestrate Configuration Information
The following table describes the information required by the PlateSpin Orchestrate configuration
config
(
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.
30 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
) and the configuration wizard (
guiconfig
). The information is organized to make it
Loading...