The health page for the communication server contains information about the various caches, who is logged in, and what the last jobs posted were. It can be found at the following address: http://<machine>:<port>/<path>/health. Example address: http://localhost:7080/cs/health
Protocol version: This is the version being used by the communication service
Protocol mismatch errors: This shows a value greater than zero if any agents talking to the communication service are using an outdated protocol.
Interactive jobs: The number of interactive jobs that the service is waiting for a response on
Pending billing requests (interactive and automatic): <?>
Last jobs synchronization result: Whether the last attempt at jobs synchronization passed or failed
Local jobs: <?>
Cached billing codes: The number of billing codes, at all levels, that are in the communication service cache
Cached top level billing codes: The number of tier 1 billing codes in the communication service cache
Cached users: The number of users in the communication service cache
Cached users with PIN: The number of users in the communication service cache that have a defined PIN
Default user domain: The value that will be appended to billing records that do not have a defined domain.
Interactive clients cleanup interval: <?>
Interactive clients cleanup threshold: <?>
Interactive clients: The number of interactive clients currently talking to the communication service.
Cache data
The communication service uses three caches -
- Meta data cache
- Contains billing code information
- Users cache
- Contains all the users who are not hidden
- Devices cache
- Contains information about all the defined devices
Last update result shows what occurred the last time the cache was updated
- PostponedNoUpdates
- There were no updates - the cache was not changed
- Success
- There was an update and the cache was successfully modified
Missing the error conditions for this
Session Table
The session table provides information about all the users connected to the communication service
Session id: The guid associated with the session
Registered at: When the user first established a connection with the service
Last seen at: The last time the user communicated with the service
User name: The person who initiated the session
User domain name: The domain the person is using. Can be the workstation name.
Machine name: The name associated with the machine the user established the session from.
IP addresses: The IP4 addresses that the user is logged in from. Can be more than one.
Pending print/copy/phone: The number of jobs of each type that are waiting to be billed
Scheduled print/copy/phone: The number of jobs of each type that waiting to be written to the database
Last Posted Table
The last posted table shows information about the jobs the communication service has received
Device info: The device the job was generated from
Billing: Whether the job was posted through interactive or automatic billing
Type/Source: <?>
User name: The user who generated the job
User domain name: The domain the user is logged into
User machine name: The name associated with the machine the user established the session from.
Tracked date: When the job was initiated
Label: The file name (if any) associated with the job
Job guid: The guid assigned when the job was generated