5.4 Configuring Ports for the Middle Tier Web Server and the Desktop Management Agent

The Desktop Management Agent can communicate with the ZENworks Middle Tier Server when the workstation is located either inside or outside the corporate firewall, provided that the Desktop Management Agent and the Web server software installed on the ZENworks Middle Tier Server machine (Apache HTTP Server on NetWare and Internet Information Server (IIS) on Windows) are set up to communicate on the same port.

You need to know how to configure the communication ports if the installation of the Web server changes the default port assignment from 80 and 443, if you want to either change or assign an additional port other than the default, or if you want to change the Desktop Management Agent port to match the Web server port.

NOTE:For a list of configurable ports, see the Port Number Assignments Appendix in Getting Results with Novell Web Servers and Tools in Managing Web Servers and Other Web Tools at the NetWare 6 documentation Web site.

This section includes the following information:

5.4.1 Configuring Ports for the Apache Web Server on NetWare 6.x

To configure ports for the Apache Web Server on NetWare 6.x, open and edit httpd.conf found in the sys:\apache\conf directory. Search for the line with the current port assignment. You can either change the port number or add additional port numbers. You can also designate whether the port is a secure port used for listening. Use the existing port configuration lines as templates if you create a new port assignment for a non-secure port. When you designate a secure (HTTPS) port, you must use port 443. For additional information about configuring ports in Apache 2 on NetWare 6.5, see Managing Listening Ports in the Apache Web Server Administration Guide for NetWare 6.5.

If you plan to use the Web browser view of the Novell Application Launcher®, myapps.html, you also need to edit its port number to match the port on the Apache Web server. On a NetWare 6.x server, myapps.html is located in the sys:\apache\nwdocs directory.

5.4.2 Configuring Ports for the Apache Web Server on Linux

To configure ports for the Apache Web Server on an OES Linux server, open and edit httpd.conf found in the /etc/apache2 directory. Search for the line with the current port assignment. You can either change the port number or add additional port numbers. You can also designate whether the port is a secure port used for listening. Use the existing port configuration lines as templates if you create a new port assignment for a non-secure port. When you designate a secure (HTTPS) port, you must use port 443.

To configure ports for the Apache Web Server on a SLES 9 SP1 server, open and edit listen.conf found in the /etc/apache2 directory. Search for the line with the current port assignment. You can either change the port number or add additional port numbers. You can also designate whether the port is a secure port used for listening. Use the existing port configuration lines as templates if you create a new port assignment for a non-secure port. When you designate a secure (HTTPS) port, you must use port 443.

If you plan to use the Web browser view of the Novell Application Launcher, myapps.html, you also need to edit its port number to match the port on the Apache2 Web server on Linux. You can find myapps.html in the DocumentRoot (for example in the /srv/www/htdocs directory). The myapps.html file is not installed if Apache2 is not installed on the Middle Tier Server.

5.4.3 Configuring Ports for IIS on Windows

  1. At the server's desktop, click Programs > Administrative Tools > Internet Services Manager > Internet Information Services to open to Internet Information Services window.

  2. Click the + symbol on the ZENworks Middle Tier Server icon to expand its hierarchy.

  3. Right-click Default Web Site > click Properties to open the Default Web Site Properties dialog box.

  4. On the Web Site page (the page opened by default) of the dialog box, change the port number in the TCP Port field. If you are designating a secure (HTTPS) port, you must use port 443.

    or

    On the Web Site page, click Advanced and follow the on-screen instructions to add multiple port numbers.

If you plan to use the Web browser view of the Novell Application Launcher, myapps.html, you also need to edit its port number to match the port on IIS. On a Windows server, myapps.html is located in the c:\inetpub\wwwroot directory.

5.4.4 Changing the DHost Port Assignment On a Windows 2000 Server with eDirectory 8.7.3 Installed

If you install eDirectory 8.7.3 on a Windows 2000 server, its DHost service is set to port 80 and starts running there. If you subsequently install the ZENworks Middle Tier Server to the same Windows 2000 server, the IIS Web server also tries to use port 80. This results in a port contention with the following message displayed:

Address already in use.

The ZENworks Middle Tier Server cannot start until you change the DHost port assignment to a port other than port 80. Use the following steps to change the DHost port assignment:

  1. Open ConsoleOne®, then double-click the root container where you installed eDirectory.

  2. Open the properties of Http Server-server_name, then click the Other tab.

  3. On the Other page, double-click httpDefaultClearPort, double-click 80, then change the port number to a port other than 80.

  4. Click OK, close ConsoleOne, then reboot the Windows server.

5.4.5 Configuring the Port for the Desktop Management Agent

Port 80 is assigned by default to the Desktop Management Agent during installation. You might want to change this assignment if the Web server port (either on Apache or IIS) has changed, or if you want to select an alternate port for the Desktop Management Agent that has already been configured for the Web server. For details about how to assign a port number for the Desktop Management Agent, see Step 8.

Even when the port has been assigned to the Desktop Management Agent after installation, users can designate a different port to connect with. For more information, see Customizing the Agent Login.