3.1 Orchestrator Server Requirements

The network server where you install the Orchestrator Server software must meet the following requirements:

Table 3-1 Orchestrator Server Requirements



Server Usage

  • ZENworks Orchestrator Server: Your server might be capable of handling tasks in addition to the tasks an Orchestrator Server performs for ZENworks Orchestrator. However, we strongly recommend that you install the Orchestrator Server software on a dedicated server to ensure optimal performance. For example, you might not want the server to host Novell eDirectory™.

  • ZENworks Virtual Machine Warehouse/Builder Server: You can install ZENworks Virtual Machine Management (the VM Warehouse and VM Builder patterns) on the same computer as the Orchestrator Server. However, for better scale and performance we recommend that you install these Virtual Machine Management patterns on a separate server.

  • ZENworks Monitoring Server: This pattern is an Apache Web server that can be installed on the Orchestrator Server, the VMM Server, or on its own Monitoring Server. It does not rely on the other Orchestrator patterns to run and does not use a lot of resources.

Refer to the information in Section A.0, ZENworks Orchestrator Components: Install Patterns for more detail about these patterns.

Operating System

  • SUSE® Linux Enterprise Server 10 (SLES 10) Service Pack 1 (SP1) or Service Pack 2 (SP2), on the 32-bit (x86) and 64-bit (x86-64) architectures (Intel* and AMD* Opteron* processors)


  • Processor: (minimum) Xeon* 2.8 GHz 32-bit, or equivalent AMD or Intel processor; (recommended) Dual-Core Xeon 4 GHz 32-bit or 64-bit

  • RAM: (minimum) 2 GB; (recommended) 4 GB

  • Disk Space: (recommended for installing) 350 MB; (recommended for managign fewer than 100 resources) 1 GB.

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.

TCP Ports

The server must allow traffic on TCP ports 80, 8001 8100, 8101, and 1099:

  • Port 80 is used for communication with the Orchestrator User Portal.

    If the server is running other services on ports 80, such as Apache requests on behalf of ZENworks Monitoring, the installation program asks you for new ports to use.

  • Port 8001 is used for communication with the Administrator Information page.

  • Port 8100 is used with a custom protocol for communication with the Orchestrator 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 or for running the Orchestrator Console.

NOTE:For more information about the requirements for Virtual Machine Management, see Section 3.5, Tested Platforms and Installation Methods for Virtual Machine Management Components.