Avaya CMS Supervisor Clients Installation and

Chapter 3: Getting started with CMS

Supervisor Web

This chapter provides information about accessing CMS reports using CMS Supervisor Web.

CMS Supervisor Web has been introduced in CMS R16.3 as a new method of accessing CMS reports using your web browser.

Signing in

You need the CMS Server address and domain to sign in to CMS Supervisor Web. For example, if your server is cms163.avaya.com, go to the following URL using any web browser.

https://cms163.avaya.com:8443/CMSWeb/

Note:

Note:

The ’s’ in https is important as all data in CMS Supervisor Web is secured using https.

In the User ID and Password fields, enter the same information you currently use for CMS

Supervisor or Terminal Emulator.

Certificates

When you first open the login web page, you can see a certificate warning message. Each web browser displays this information differently but the warning is similar in all cases. To get rid of the warning message, the certificate should be "accepted". The steps you take to accept and install the certificate are different depending on your browser version.

Note:

Note:

Chrome and Edge users do not need to install the security certificate.

Avaya CMS Supervisor R18 Installation and Getting Started October 2016

21

Chapter 3: Getting started with CMS Supervisor Web

Accepting a security certificate when using IE 10 and IE 11

Carry out the following steps on IE10/IE11 desktop to install and import the security certificate when you first attempt to log in to CMS Supervisor Web. After you install and import the certificate using IE10/IE11 desktop, you can access the CMS Supervisor Web login page using

IE 10/IE 11 Modern.

1. When the system displays the Certificate Error dialog, select Continue to this website

(not recommended).

The Address Bar turns red.

2. Click the Certificate Error button.

3. On the Security Report dialog box, select View Certificate.

4. On the Certificate dialog box, select Install Certificate.

5. On the Certificate Import Wizard dialog box, if prompted to choose a Store Location, select Current User and click Next.

6. On the Certificate Import Wizard dialog box, select Automatically select the certificate

store based on the type of certificate and click Next.

7. On the Certificate Import Wizard dialog box, click Finish.

8. Click OK to close the Certificate Import Wizard completion dialog.

9. Click OK to exit the Certificate dialog box.

The system displays the Logon dialog.

Accepting a security certificate when using Firefox

1. When the system displays This Connection is Untrusted dialog, select I understand the

Risks.

2. Click Add Exception.

3. When the system displays Add Security Exception dialog, click Confirm Security

Exception.

The Logon dialog is displayed.

Accepting a security certificate when using Safari

1. Open the web client URL.

The system displays Safari can’t verify the identity of the website.

22

Avaya CMS Supervisor R18 Installation and Getting Started October 2016

22

Certificates

2. Click Show Certificate.

3. Click Trust.

4. Change the value of the When using this certificate field to Always Trust.

This will change the values of the Secure Socket Layers (SSL) and X.509 Basic Policy fields to Always Trust.

5. Click Continue.

You are prompted to provide super user authentication to make the changes for the

Certificate Trust Settings.

6. Type the super user Username and Password.

After you successfully authenticate, the system does not prompt that the certificate is not verified for that system.

Exporting and importing a CMSWeb certificate in Internet Explorer

Often on Windows 7, connections to a CMS server happen through the Windows security screen because the CMSWeb certificate is either insecure or invalid. This forces the user to select the "Continue to this site" option. If the user exports and imports this certificate, the system does not display the Windows security screen when the connections are established.

Exporting the CMSWeb certificate

1. Click on Certificate error on the browser window. Select View Certificates.

The system displays the Certificate screen.

2. Select the Details tab and select the option Copy to File.

The system displays the Certificate Export Wizard | Welcome screen.

3. Click Next.

The system displays the Certificate Export Wizard | Export File Format screen.

Select the option, DER encoded binary X.xxx (.CER).

4. Click Next.

The system displays the Certificate Export Wizard | File to Export window.

5. Select the Browse button and select a directory for the file and enter a filename.

Note:

Note:

Keep the default file extension.

6. Click Next.

The system displays the Certificate Export Wizard | Completing the Certificate Export

Wizard screen.

Avaya CMS Supervisor R18 Installation and Getting Started October 2016

23

Chapter 3: Getting started with CMS Supervisor Web

7. Click Finish.

The system displays the Certificate Export Wizard successful message.

8. Click OK.

Importing the CMSWeb certificate

1. Open the browser and select Tools | Internet options.

The system displays the Internet Options screen.

2. Select the Content tab and click on Certificates.

The system displays the Certificates screen.

3. Select the Trusted Root Certification Authorities tab and click on Import.

The system displays the Certificate Export Wizard | Welcome screen.

4. Click Next.

The system displays the Certificate Import Wizard screen.

5. Click Browse.

The system displays the Browse window. Locate the file saved with File Export and select Open.

6. Click Next.

The system displays the Certificate Import Wizard | Certificate Store window. Select

Place all certificates in the following store, click Browse, and select Trusted Root

Certification Authorities.

7. Click Next.

The system displays the Certificate Import Wizard | Completing the Certificate Import

Wizard window.

8. Click Finish.

The system displays a Security Warning message.

9. Click Yes.

The system displays the Certificate Import Wizard successful message.

10. Click OK.

The system displays the Certificates screen. Scroll through the list and verify that system added the certificate successfully.

11. Click Close.

The system displays the Internet Options screen.

12. Click OK.

Close and reopen the browser to connect to the desired CMS.

24

Avaya CMS Supervisor R18 Installation and Getting Started October 2016

24

Adobe Flash

Adobe Flash

CMS Supervisor Web reports use Adobe Flash Player to run in your browser. If you do not have

Adobe Flash installed, or you have an older version installed, you are prompted to upgrade when you open the login page. CMS Supervisor Web reports do not work on systems that cannot run the latest version of Adobe Flash Player.

To check which version of Adobe Flash Player your browser is running, go to http://www.adobe.com/software/flash/about/

If your browser does not automatically offer to install a newer version of Adobe Flash Player (for example, if you do not have Adobe Flash Player installed or are using a version prior to 10.3), you can download the latest version here:

http://get.adobe.com/flashplayer/

Note:

Note:

Not all operating systems and/or devices support suitable versions of Adobe

Flash Player.

Link status icons and Menu bar

Once you sign in, link status icons at the top of the web page show the current ACD Status. The

ACD status has to be interpreted as follows:

●

●

Red, which is at the upper position, indicates no traffic.

Yellow, which is at the middle position, indicates an indeterminate state which includes the state during pump up.

●

Green, which is at the lower position, indicates traffic.

Use the menu bar of the web page providing options <login name> and Help to set your password, set preferences, see the About information, open Help contents and sign out.

Changing ACD and running reports

The menu bar of the web page contains the option Reports to change the selected ACD and display historical, integrated, or real-time reports.

Click the drop-down list of ACDs to obtain the list of available ACDs, pseudo ACDs and ACD groups. Click the option you wish to use as the current ACD.

Avaya CMS Supervisor R18 Installation and Getting Started October 2016

25

Chapter 3: Getting started with CMS Supervisor Web

Click Historical, Integrated, or Realtime to populate the left side of the web page with the available report categories.

Search in the header provides the reports and administrative options based on the search criteria. Search results for reports are based on the report name or description.

To view the report properties, click the information icon to the right of the report description.

To run a report, click the report name or description. The report opens in a new browser window or browser tab depending on your browser settings.

The Report Window

When you click Run to run a report, a report window opens for you to provide input values for the report.

For some reports, a field has a Browse button which you can use to select values instead of typing the full information. This method requires entries in the Dictionary. Other Browse buttons simplify selecting dates and times. When entering dates, a single mouse click selects an individual date. To enter multiple dates, hold down the Control key as you click multiple dates.

To enter a date range, hold down the Shift key when you click the end of the range.

Once CMS Supervisor Web displays the report in the Report Window, it displays buttons Set

Input, Print and Export to CSV at the top of the Report Window. Click Set Input to reopen the report input pop-up where you can modify input values without restarting the report. Click Print to print the report. Do not use the print button in the browser as it will not format the output correctly. Click Export To CSV to export the report data to a file in csv format. You can then import the report into other applications.

In reports, where CMS Supervisor Web displays tables, you can resize columns by dragging the vertical bar between them.

Thresholds

Press the select button on the mouse, which is usually the left mouse button, when the mouse pointer is over an entry in a table where you want to set thresholds. A pop-up appears if drill down reports or thresholds are available for that data. Click Threshold in the pop-up menu.

This displays the Threshold Settings dialog and allows you to configure the different threshold settings.

26

Avaya CMS Supervisor R18 Installation and Getting Started October 2016

26

Drill Down

Drill Down

Press the select button on the mouse, which is usually the left mouse button, when the mouse pointer is over an entry in a table where you want to drill down. A pop-up appears if drill down reports or thresholds are available for that data. Selecting a drill down report will cause the drill down report to open in a new window or tab.

Debugging CMS Supervisor Web

This section contains the following topics:

●

Debug settings on page 27

●

●

User level logging on page 28

Global level logging on page 29

Debug settings

The system stores debug settings for individual users in a common file on the CMS Server. The file is called userlog.properties and is present in location /opt/cmsweb/log.

This file contains three entries for each user. The entries and values stored for these entries are the following:

●

●

● username.LEVEL

- Valid values for username.LEVEL are OFF, FATAL, ERROR, WARNING, INFO,

DEBUG, TRACE, ALL.

- If you follow the above order of username.LEVEL values, each succeeding value provides more detailed tracing information.

- The default value for username.LEVEL is DEBUG.

username.FILESIZE

- Valid values for username.FILESIZE are 51200, 102400, 153600, 204800, 256000,

307200, 358400, 409600 and 460800.

- The default value for username.FILESIZE is 460800.

username.FILECOUNT

- Valid values for username.FILECOUNT are 2,3,4,5,6,7 and 8.

- The default value for

username.FILECOUNT is 3.

Avaya CMS Supervisor R18 Installation and Getting Started October 2016

27

Chapter 3: Getting started with CMS Supervisor Web

There are two ways to modify the values of username.LEVEL, username.FILESIZE and username.FILECOUNT. You can use either the GUI or edit the userlog.properties files to change the values.

Changing settings using the GUI

Use <login name> > Preferences > Tracing on the GUI which provides a way to alter the trace level, number of trace files, and rollover filesize.

To change the debug values in <login name> > Preferences > Tracing of the GUI, you must login using the account you wish to trace.

The main control panel page of the GUI changes to the new logging level when it receives the update from the server. Reports that start after the update has been received from the server use the new logging level. However, reports already running continue to use the previous logging level that was configured when the report was opened.

Changing settings using the userlog.properties file

The root user can modify the entries in the userlog.properties file using a text editor such as vi.

After the changes have been saved, it can take up to 30 seconds for the new values to reach the CMS Supervisor Web clients.

User level logging

The CMS server creates log files for users that have tracing enabled.The log files are located in the

/opt/cmsweb/log directory.

The name of the most recent log file is

<username>.log and older logfiles have the suffix .1,

.2, .3 and so on.

The table below displays the contents of the log file:

2011-09-20 15:44:11,174 DEBUG cmssvc - LEAVING getAllUserPropertiesHandler

2011-09-20 15:44:11,175 DEBUG cmssvc - ENTERING nextCallStack

2011-09-20 15:44:11,175 DEBUG cmssvc - nextCallStack: stack exhausted

2011-09-20 15:44:11,175 DEBUG cmssvc - ENTERING closeProgressWindow

2011-09-20 15:44:11,175 DEBUG cmssvc - LEAVING closeProgressWindow

2011-09-20 15:44:11,175 DEBUG cmssvc - ENTERING/LEAVING endCallStack

28

Avaya CMS Supervisor R18 Installation and Getting Started October 2016

28

Debugging CMS Supervisor Web

WARNING:

!

!

WARNING:

Logging is only available when a user is logged into the server. This means that until a successful login is achieved no logging will appear in a user's log file.

Global level logging

In addition to user level logging above, there are two log files that capture additional information:

●

/opt/cmsweb/tomcat/logs/cms_debug.log contains logging information for all

Avaya softwares running under tomcat or in the browsers.

●

●

/opt/cmsweb/tomcat/logs/catalina.out contains all the non Avaya Tomcat logging information in addition to the contents from cms_debug.log.

The normal CMS server logs, for example, elog, are also available.

Avaya CMS Supervisor R18 Installation and Getting Started October 2016

29

Chapter 3: Getting started with CMS Supervisor Web

30

Avaya CMS Supervisor R18 Installation and Getting Started October 2016

30