Netcool Configuration Manager - Base Presentation server

The Presentation server not only supports the GUI and API clients; it is used by both the reporting and Netcool Configuration Manager - Compliance solutions as a means to ensure security policy is enforced.

The Presentation server mainly supports the Netcool Configuration Manager - Base GUI and API requests for data and submission of tasks to the Netcool Configuration Manager - Base execution queues.

Both the GUI and API requests are executed on either port 16310 or 16311 if secure connections are required. These are the defaults used by the Netcool Configuration Manager - Base installer and could be changed if the customer so chooses.

Netcool Configuration Manager - Base GUI has IDT - which is used to generate secure and logged connections to network devices using the Netcool Configuration Manager - Base infrastructure. These secure connections from the user's client machine connect up to the Presentation server over one of two ports, either 8104 or 8105.

The IDT daemon can be configured in one of two ways. The recommended method of implementation is for most customers to run IDT inside its own JVM instead of inside the Worker server's JVM. This allows IDT to have its own resources instead of sharing them with Unit of Work processing. This recommended method utilizes port 8105. Port 8104 is the other option when the IDT daemon runs inside the Worker server JVM. Port numbers 8105 and 8104 are defaults used at install time that can be changed.

The Presentation server also has to support calls from both the Netcool Configuration Manager - Compliance server (if implemented) and the Reporting server. These two servers connect by using the API port 16310 or 16311 to communicate with the Netcool Configuration Manager - Base implementation.

These connections are designed to ensure that the security model that is defined in Netcool Configuration Manager - Base is not violated by either Netcool Configuration Manager - Compliance or the reporting engine.

Most notably is to make sure that the devices that cannot be seen in Netcool Configuration Manager - Base are not viewable either in reporting or Netcool Configuration Manager - Compliance. In multiple Presentation server environments, Netcool Configuration Manager - Compliance and reporting only need to point to one of these servers.

An optional piece of software that most customers use is known as the Out of Band Change (OOBC) daemon. This tool is designed to monitor Syslog messages and set up device synchronizations when it sees activity of interest. This software is hosted on the server where Syslog messages are aggregated. This daemon then connects to the Netcool Configuration Manager - Base Presentation server via the API and submit synchronization tasks against the devices the rules matched on. OOBC connects to the Presentation server using either port 16310 or 16311.

Finally, the Netcool Configuration Manager - Base administrator needs to be able to reach the server either by using the preferred method of SSH (port 22) or Telnet (port 23). If Telnet is chosen, then it is necessary to enable FTP ports (port 20, 21) to allow the movement of files back and forth.