The HTTP monitor requires an Internet browser to be installed on the monitoring computer. This browser will communicate with ITP/Server over HTTP. Retrieving queue status data and optionally sending commands to change the characteristics of specific jobs.
To monitor ITP/Document Services, start a browser and have it load the URL:
http://<host[:port]>/queue
Example
http://itpserver.company.com/queue
Or
http://itpserver.company.com:3080/queue
The latter URL specifies a port. This is necessary when a custom port is set for he HTTP Monitor.
By default the page will refresh itself once every minute. This setting can be changed in the page. By entering a different number after 'Refresh rate:' and pressing the 'Set' button. The display can be manually refreshed by using the refresh button of the browser. The jobs in this page are sorted on order of execution priority. The page allows the user to change priority levels, to suspend and resume jobs, and to remove jobs from the queue. This can be done by checking the appropriate check boxes or editing the priority edit boxes. The changes are sent to the server by pressing the 'commit changes' button.
Note
Changes in the browser are lost when the browser refreshes the page before 'commit changes' button is pressed.
When the changes are sent to the server and processed the browser will be updated to show the current queue status.
For the HTTP Monitor a port number or symbolic name must be set and security restrictions can be set. When no security settings are present the default value will be used. It can be set to one of:
Access is restricted to the local host. Access is restricted to clients running on the host (when using the IP address 127.0.0.1).
No access restrictions
Network access list: Access is based on a comma-separated list of numerical IP addresses and their network masks. This list can include and/or exclude specific hosts and/or parts of a network. IP addresses are specified in the format n.n.n.n/m where n.n.n.n is the IP number of the host/network and m is the number of bits in the netmask. All bits in this mask must match the IP number for the entry to match. Example: 10.0.0.10 specifies host 10.0.0.10 (with default netmask 255.255.255.255) 10.0.0.10/24 specifies network 10.0.0. with netmask 255.255.255.0. This defines a range of hosts from 10.0.0.0 to 10.0.0.255. 0.0.0.0/0 specifies any IP address.
Hosts can be granted access by prefixing their address with a '+', or denied access by prefixing a '-'. The first match in the access list will determine whether or not ITP/Server will grant access to the client. Example: PortSecurity=-10.0.0.4,10.0.0.0/24,127.0.0.1 will deny access to host 10.0.0.4 but grant access to all other hosts in the range 10.0.0.0 to 10.0.0.255, as well as to the local server using the localhost address.
Default access is restricted to the local host.
HTTP Monitor uses three templates to display the data. All three can be changed or different templates can be chosen. The check box:' Use custom HTML templates' enables the template select boxes. The browse buttons will give you access to the templates.
Note
Be careful if you alter a template. We recommend that you work on a copy.
This page, qmontpl.htm, called with http://<hostname>:<port number>/queue, displays all jobs in the ITP/Server queue.
This page, smontpl.htm, called with http://<hostname>:<port number>/service, displays the service used by the ITP/Document Processor Manager.
This page, lmontpl.htm, called with http://<hostname>:<port number>/log, displays the ITP/Server log.