These steps are only necessary if you want to allow users to run Live Monitoring from Replay, but connect to local Cores, for example to leverage the Live Screen Monitoring feature while keep accessing Live Monitoring from the Replay Server. As discussed in the chapter Live Monitoring with Replay Server the Replay Server does not have any connection to Screen Capture Server so when Live Monitoring is connecting to the Replay Server's Core it will not be able to provide Live Screen Monitoring. In order to do that the Live Monitoring must connect to another Core which has also the Screen Capture associated with it.

How does this work:

  1. If you do not do any specific configuration the Live Monitoring tab will always directly run the Live Monitoring console from the current server and connect to its Core, so in this case the Replay Server.
  2. By configuring the server selection as discussed bellow in the chapter you will allow users to choose which Core server will be used for the Live Monitoring to connect to so that user may pick the appropriate one based on which location he or she wants to monitor and where the Screen Capture is actually running.

User will always run the Live Monitoring console from the Replay Server so all the user privileges and restrictions will apply, however the Live Monitoring will directly communicate with the appropriate Core server.

The following example shows the Live Monitoring navigation page allowing users to choose from three different servers where Live Monitoring can connect:

  • Replay Server - In this case there will be no possibility to monitor agent desktops, however Replay Server can typically "see" all the existing calls regarding of the locations
  • DataCenter 1 - Allows to do full monitoring of the first location, The Data Center 1 including Live Screen Monitoring because of local Screen Capture Server running there.
  • DataCenter 2 - Allows to do full monitoring of the second location, The Data Center 2 including Live Screen Monitoring because of local Screen Capture Server running there.

Configuring the Navigation Page

Icon

The following steps require direct modification of the configuration files. Please be extremely careful as you can cause instability or complete outage of the system by incorrect modifications of the configuration files. 

Log in to the command line and make sure you have root privileges. Locate the configuration file:

/opt/callrec/etc/core.xml

To create a customized Live Monitoring navigation page you need to create a new configuration section within the core.xml file:

  1. Locate the following section:

    <SpecifiedConfiguration name="core"> 
    <Group name="RMIAPI"> 
  2. Inside of this configuration group (please double-check it is named "RMIAPI") create a new EqualGroup block for each Live Monitoring instance where its configuration will be specified. For the example above you will need to create three EqualGroup blocks: 

    <EqualGroup name="liveMonServer"> 
      <Value name="title">Replay</Value>
      <Value name="bindServer">replay</Value>
      <Value name="description">This is the Replay Server</Value>
    </EqualGroup>
    <EqualGroup name="liveMonServer"> 
      <Value name="title">Data Center 1</Value>
      <Value name="bindServer">core1</Value>
      <Value name="description">This server records Team 1 West</Value>
    </EqualGroup>
    <EqualGroup name="liveMonServer">
      <Value name="title">Data Center 2</Value>
      <Value name="bindServer">core2</Value>
      <Value name="description">This server records Team 2 East</Value>
    </EqualGroup>
  3. The following options can be provided:

    <Value name="title"> – optional, field specifying server title in Web UI, default value is the server name as specified in bindServer value. If there is no title field specified, then the default server name is used as well. For more information about how to set the bindServer name, see Configuring Live Monitoring in the Replay Server.

    <Value name="bindServer"> – mandatory, name of the server core which Live Monitoring should connect to.

    <Value name="description"> – optional, use to add information to display for that server. It is useful to include a description that identifies the site and team recorded by that server.

    Please note if there is something wrong with the configuration of bindServer, the whole entry will be ignored. As the configuration is processed, messages show up in webadmin.log, including warnings about ignored servers

  4. Restart the Web UI after editing core.xml using the command:

    /opt/callrec/bin/rc.callrec_web restart

    When the screen monitoring has been configured the selection screen appears after clicking the Live Monitoring button.

    Click the launch button of the required server to launch Live Monitoring. More than one Live Monitoring instances can be run at the same time.