Job Management Partner 1/Software Distribution Setup Guide

[Contents][Glossary][Index][Back][Next]

Appendix E.4 System configuration

To convert JP1/Software Distribution's protocol to HTTP, place Internet Gateway and HTTP Gateway between the JP1/Software Distribution nodes where you want to use HTTP. Place Internet Gateway at the higher system on the route using HTTP, and place HTTP Gateway at the lower system.

Once you have installed Internet Gateway and HTTP Gateway, they are handled transparently without being recognized by the managing server as a level in the hierarchy.

Note that the higher system directly connected to Internet Gateway must be running JP1/Software Distribution version 06-71 or later. Similarly, the lower system directly connected to HTTP Gateway must be running JP1/Software Distribution version 06-71 or later.

The following figure shows the JP1/Software Distribution system configuration when using Internet Options.

Figure E-3 JP1/Software Distribution system configuration when using Internet Options

[Figure]

Organization of this subsection
(1) Internet Gateway
(2) HTTP Gateway
(3) Proxies and firewalls
(4) Notes on system configuration

(1) Internet Gateway

The number of HTTP Gateways that can be connected to an Internet Gateway depends on the higher system connected to Internet Gateway. When the higher system is a central manager, we recommend between 50 and 100. When the higher system is a SubManager, we recommend between 20 and 50.

Internet Gateway can be installed on the same machine as the higher system.

(a) Minimum system requirements
Resource Requirement
CPU At least 1 GHz (2 GHz or more recommended)
Memory 1,000 + 50 x number of simultaneous HTTP Gateway connections (KB unit: kilobytes)
Disk space 5 megabytes + number of simultaneous HTTP Gateway connections x size of packages to be distributed
However, when using split distribution, calculate the required disk space using the following formula:
5 megabytes + number of simultaneous HTTP Gateway connections x size package is split into
(b) Operating system

Windows Server 2003, Windows XP Professional, Windows 2000, or Windows NT Server 4.0

(c) Required software

Microsoft Internet Information Services 5.0 or later, or Microsoft Internet Information Server 4.0 or later must be installed.

In this appendix, Microsoft Internet Information Services 5.0 and later and Microsoft Internet Information Server 4.0 and later are referred to collectively as Microsoft Internet Information Services, unless otherwise noted.

(2) HTTP Gateway

You must have HTTP Gateway on each directly connected lower system. If there are multiple clients, place a relay system directly under HTTP Gateway.

HTTP Gateway can be installed on the same machine as the lower system.

(a) Minimum system requirements
Resource Requirement
CPU At least 1 GHz (2 GHz or more recommended)
Memory 3,000 kilobytes
Disk space 5 megabytes + size of package to be distributed
However, when using split distribution, calculate the required disk space using the following formula:
5 megabytes + size package is split into
(b) Operating system

Windows Server 2003, Windows XP, Windows 2000, Windows NT 4.0, Windows Me, or Windows 98

(c) Required software

Microsoft Internet Explorer 5.01 or later must be installed.

(3) Proxies and firewalls

You can use transparent proxies compatible with HTTP 1.0 and later. Transparent proxies are proxies that require authentication for access and certification of the client itself. Transparent proxies do not make any changes to requests and responses. You can also use packet filtering firewalls that allow HTTP to pass through, and application gateway firewalls.

Internet Options is compatible with proxies and firewalls that do not require settings at the client.

The following are representative of products with applicable proxies:

(4) Notes on system configuration

When you use Internet Options, job execution requests from a higher system are not received by the lower system. Jobs are executed only in response to requests from a lower system. Therefore, as shown in the figure below, when the system is configured so that only some of the lower systems use HTTP Gateway, jobs are executed only in response to requests from a lower system even between the relay systems that do not use HTTP Gateway and the central manager (shaded area in the figure).

Figure E-4 System configuration in which HTTP Gateway is used solely in some lower systems

[Figure]