1.4 How Orchestrator Components Communicate

The following diagram illustrates how the various components of ZENworks Orchestrator communicate with the Orchestrator Server. An explanation for each communication link follows the diagram.

Figure 1-3 Communication Ports Used By the Orchestrator Server

  1. Users who open the User Portal for managing jobs do so by opening a Web browser and entering the URL to the Orchestrator Server followed by the port designated for the User Portal during installation. In a basic installation of ZENworks Orchestrator, this is port 80. The URL would therefore be entered as follows:

    http://DNS_Name_or_IP_Address:80

  2. Administrators who want more information about Orchestrator and a method to access or install additional clients or agents can access the Administrator Information page. To do so, he or she opens a Web browser and enters the URL to the Orchestrator Server, followed by the port designated for the Web Info page during installation. In a basic installation of ZENworks Orchestrator, the default is port 8001. The URL would therefore be entered as follows:

    http://DNS_Name_or_IP_Address:8001

  3. The Orchestrator Server establishes and maintains contact with an installed Orchestrator Agent on a computing resource through port 8100 using a custom protocol.

  4. When a user invokes the zos command line interface (available after ZENworks Orchestrator clients are installed on a machine), or when he or she launches the Java toolkit SDK from the Web Info page, those client tools communicate with the Orchestrator Server over ports 8100 and 8101.

  5. When the administrator invokes the zosadmin command line interface (available after ZENworks Orchestrator clients — including the console — are installed on a machine), or when he or she starts the ZENworks Orchestrator Console, those client tools communicate with the Orchestrator Server over port 1099, which uses a Java RMI (Remote Method Invocation) protocol.