Starting with version 9.1.01, the Virtual Chat diagnostics offers interactive diagnostics, which are GUI-based tools that provide you with information about users connected to BMC Virtual Chat and information about the ESChat servlet. The ESChat servlet provides the chat functionality.
The following topics are provided:
Set (or verify) the administration key by performing the following steps:
When viewing user information, you can view high-level information about all users or look at information about a specific user chat session. User information can help you diagnose issues in processing chat messages. For example, you can test whether AIML queries are being processed by Program D. When a new message is first detected and the details retrieved, it is possible that the message is only partially complete at this time. If this occurs, the current data is displayed and then as updates occur the table is updated as well. For example, in a situation where the Participant Chat Record attempts to deliver a message to a CNS servlet that is offline or doesn’t exist, there is a 30-second timeout. The table shows only data up through the Master Chat Record and then after the 30-second timeout the message as it propagates through the system and back to the user.The time that each module spends processing each message can help you determine the cause of delays.
For servlets, you can view the following information:
|Servlet||Lists all ESChat servlets accessing the BMC Remedy Action Request System Server (BMC Remedy AR System Server). Select any servlet to see details such as the IP address and free memory.|
|System Check||Provides information about the system check that is performed when the servlet is started or refreshed.|
|Diagnotics Items||Gives detailed diagnostic information for certain events, such as logins, AIML, and live agent requests. For each event, the diagnostic table displays the number of times that event has run, the last time that event ran, and processing time for that event. This table is refreshed when the servlet is loaded; it is not refreshed when you perform a configuration refresh of the servlet. You can use the information in this table to diagnose the cause of performance issues.|
|AR Server Connections||Displays basic information about the ESChat servlet connection to the configured AR System server, such as connection losses (if any).|
|Socket Connections||DIsplays information about socket connections made on to the ESChat servlet from the AR System server plug-in filters. Based on your AR System server configuration, each plug-in might have multiple instances running but is unique by port value. |
For each socket and plug-in, this option displays the server that it is running on, port values, and information about requests processed.
|Configuration||Displays a list of the configuration files, as loaded into the memory of the ESChat servlet. If you have custom configurations in overlays, you can confirm that the expected configuration elements are loaded. For more information about overlays, see Overlays for Self Service Portal custom configuration.|
|Forms||Displays the BMC Remedy AR System form data, the name of Self Service Portal Configuration entry, and whether the form is an overlay or not.|
Displays servlet information; contains all raw data, some of which is not displayed in other options.
Note: This information is displayed as raw data and has not undergone any processing.