OBA 3.x does not work with SiteScope 11.4x without a workaround

OBA does not work with SiS 11.4x without a workaround. The workaround is :
Workaround for 11.4x
1. After creating the SiteScope collection within OBA, open the SiteScope UI.
2. Navigate to the integration preference.
3. Select the integration “opsa_opsa_default and click the “Edit” pencil icon.
4. Do not change anything. Simply click the OK button.
5. SiteScope data should now be sent to OBA.
Advertisements

Generic Data Integration queue exceeded allowed size

Problem

ERROR – Generic Data Integration queue exceeded allowed size 500* olest samples were discarded

*this value may vary, 500 is the default value.

Cause

This message occurs when remote system which should consume data from Sitescope over “generic data integration” channel is down or can not process messages from SiteScope.

The value of _dataSamplesQueueMaxSize is the upper limit of the data integration sample’s queue. If this limit is reached, old samples are discarded. If this value is limiting the data queue, then we need to increase that number.

Fix
For further debbuging the below appenders can be added in either the log4j.properties or bac_integration.properties; these files are located on the directory: \SiteScope\conf\core\Tools\log4j\PlainJava
###################################################################################
# Generic Event Integration
###################################################################################
log4j.category.genericEventIntegration=DEBUG, generic.event.integration.appender
log4j.additivity.genericEventIntegration=false
log4j.appender.generic.event.integration.appender=org.apache.log4j.RollingFileAppender
log4j.appender.generic.event.integration.appender.File=../${log.file.path}/generic_event_integration.log
log4j.appender.generic.event.integration.appender.MaxFileSize=${def.file.max.size}
log4j.appender.generic.event.integration.appender.MaxBackupIndex=${def.files.backup.count}
log4j.appender.generic.event.integration.appender.layout=org.apache.log4j.PatternLayout
log4j.appender.generic.event.integration.appender.layout.ConversionPattern=%d [%t] (%F:%L) %-5p – %m%n
log4j.appender.generic.event.integration.encoding=${general.encoding}
###################################################################################
# Generic Data Integration
###################################################################################
log4j.category.genericDataIntegration=DEBUG, generic.data.integration.appender
log4j.additivity.genericDataIntegration=false
log4j.appender.generic.data.integration.appender=org.apache.log4j.RollingFileAppender
log4j.appender.generic.data.integration.appender.File=../${log.file.path}/generic_data_integration.log
log4j.appender.generic.data.integration.appender.MaxFileSize=${def.file.max.size}
log4j.appender.generic.data.integration.appender.MaxBackupIndex=${def.files.backup.count}
log4j.appender.generic.data.integration.appender.layout=org.apache.log4j.PatternLayout
log4j.appender.generic.data.integration.appender.layout.ConversionPattern=%d [%t] (%F:%L) %-5p – %m%n
log4j.appender.generic.data.integration.encoding=${general.encoding}
To solve this problem proceed with below steps:
1. stop SiteScope service
2. increase the queue sizes in “master.config” to below values:
     _dataSamplesQueueMaxSize=2000
     _dataSamplesQueueDiscardSamples=1000
3. restart sitescope after changing these parameters.
After the change, run the problematic monitor(s) and confirm SiteScope data is arriving successfully.

Configure the Microsoft Azure Monitor in SiteScope

How to Configure the Azure Monitor

  1. Prerequisites
  • Make sure you have the user permissions and credentials required for this monitor as specified in Monitor Permissions and Credentials.
  • This monitor is available with all editions except Community edition. Contact your HPE sales representative for more information.
  • A valid subscription to Azure service.
  1. Perform the following configuration tasks on the Azure Dashboard.

Note:  These tasks need to be completed by a user with Global Administrators permissions.

  1. Either create a new resource or use an existing one.  Example, create a new Windows Server 2012 R2 VM.
  2. Create an Active Directory user for monitoring purposes, example SiteScope (the user does not need Global Administrators permissions).
  3. Create an Application Registration in Azure Active Directory
    1. Select App registration
    2. Click New application registration
      1. Enter a name, example SiteScope
      2. Set Application type to “Web app / API
      3. Enter a Sign-on URL like http://SiteScope
      4. Note:  This does not need to be a valid URL, just a valid format.
      5. Click Create
  4. Configure the Application Registration
    1. Select the newly created App registration
    2. Click Settings
      1. Select Required permissions
        1. Under Windows Azure Active Directory grant all delegated permissions.
        2. Add Windows Azure Service Management API
        3. Under Windows Azure Service Management API grant all delegated permissions.
      2. Select Keys
      3. Enter a Description like SiteScope
      4. Select a Duration
      5. Click Save
      6. Record the Key value to some safe location, it is only displayed once.  Example /ABDCo5KinoVbIRxp/VP45698UWR4l4T+PGE8zC0kY=
  5. Configure the resource.  Example Windows Server 2012 R2 VM
  6. Select Access control (IAM)
  7. Click Add
    1. Add the App registration, example SiteScope, and select role Owner
    2. Add the user created for monitoring, example SiteScope, and select role Owner
  8. Gather required data for configuring the Microsoft Azure Monitor in SiteScope
    1. Go to your App registration, example SiteScope
      1. Record the Application ID, example 123eb32c-d68b-4e9d-4567-890cf7452c6a
    2. Go to Azure Active Directory and select Properties
      1. Record the Directory ID, example 0f8a123f-d8aa-1e12-12b2-4567c2accb8f
  1. Configure the monitor properties. See the UI descriptions for details.

Value Mappings

Microsoft Azure

SiteScope

Directory ID Tenant ID
Application ID Client ID
Key Client Secret

SiteScope – Supported browsers

As of SiteScope 11.24, the list of supported browsers is as follows
(taken from SiteScope Deployment Guide -> Installation Requirements -> Client System Requirements)

SiteScope client is supported on all Microsoft Windows operating systems using the following:

Supported Browsers: SiteScope UI

– Microsoft Internet Explorer 7, 8, 9, 10

Note for Internet Explorer 10:
+ Alert, Monitor, and Server-Centric Reports are supported in compatibility mode only.
+ There is no support for add-ons, like Java, when Internet Explorer 10 is used from the Start screen.
To use SiteScope in Internet Explorer 10, you must switch to Internet Explorer desktop mode and install java.
For details, see http://windows.microsoft.com/en-us/internetexplorer/install-java#ie=ie-10.

– Mozilla Firefox (latest certified version: 24.0 ESR)

– Safari (7.0.4) on Mac OS (10.9.3)

Supported Browsers: Unified Console (Multi-View, Event Console)

– Google Chrome (latest certified version: 34.0.1847.137 m)

– Mozilla Firefox (latest certified version: 24.5. 0 ESR)

– Safari (latest certified version: 5.1.7 for Windows; 7.0.3 for Mac OS)

– Internet Explorer 9, 10, 11

Note:
+ Internet Explorer 9 is supported with the following limitations:
– It is not supported on Microsoft Windows 7 N Edition.
– It is not supported on Microsoft Windows Server 2008.
+ SiteScope Multi-View is no longer officially supported in Internet Explorer 8, and we recommend switching to one of the supported
browsers. The tab functionality in the Web Dashboard does not work in Internet Explorer 8.

– iPad 3 with Safari (iOS 7 with latest updates)
– Android tablet with Chrome 34.0.1847 (Full HD display)

Supported Browsers: SiteScope Multi-View Page in MyBSM
– Internet Explorer 8, 9, 10

SiteScope UNIX Monitor Installation

Requirements

Below are the requirements to install and monitor UNIX using SiteScope.

· Server Resource monitor license

· LoadRunner 7.51 or above:

· For LoadRunner 7.6 or above, the SiteScope UNIX monitor is built into the Controller.

· For LoadRunner 7.51 SP1, make sure that you install the Controller add-in, LR_New_SiteScope_Monitor.exe. This is available in the Patches database ® LoadRunner ® 7.51 SP1 ® Performance Monitor ® LR751SP1P2 ® LoadRunner 7.51 SP1 SiteScope Unix monitor for LoadRunner version 7.51.

· SiteScope Lite installation:

· For LoadRunner 8.x , the SiteScope Lite installation file is available in the additional components CD under SiteScope -> sitescopelrsetup.exe

· For LoadRunner 7.6 or above, the SiteScope Lite installation file (SiteScopeSetupForLR.exe) and SiteScope Lite license is available in the Patches database ® LoadRunner ® 7.6 ® Performance Monitor ® LR76P6 – LoadRunner 7.6 SiteScope Siebel and SAP Portal Add-in for LoadRunner.

· For LoadRunner 7.51 SP1, the SiteScope Lite installation file and SiteScope Lite license is available in the Patches database ® LoadRunner ® 7.51 SP1 ® Performance Monitor ® LR751SP1P2 ® LoadRunner 7.51SP1 SiteScope Unix monitor for LoadRunner version 7.51.

SiteScope Installation

Ensure you have LoadRunner 7.51 SP1 or above installed. Ideally, you will want an extra machine for the SiteScope installation:

· First machine ® Controller

· Second machine ® SiteScope

· Third machine ® Load Generator

· Fourth machine ® Load Generator

Etc.…

In this situation, SiteScope will be gathering information from the Unix Servers and displaying them via a Web interface. The Controller will then connect to the SiteScope installation and retrieve this data during the scenario run.

General Installation

  1. Obtain the SiteScope Lite installation file and SiteScope Lite license.

2. On the machine where you wish to install SiteScope, run the installation file as explained in the Requirements section.

3. In the “Administrator E-mail Address” window, enter an E-mail if you want a designated person to receive Alerts, reports, and status messages. Otherwise, click <Next> to proceed to the next window.

4. Follow all the defaults settings to complete the SiteScope Lite installation.

5. When the installation of SiteScope is completed, a browser will automatically come up with instructions on how to start SiteScope. The way to bring up SiteScope is via a browser with the URL http://<machine-name>:8888/SiteScope.

As you can guess, SiteScope installs its own Web Server as an interface to the application.

License Installation for SiteScope

  1. The first time you start SiteScope, you will get a “SiteScope First Time Setup” page. Click on “Skip this Page” to go to main SiteScope site.

2. Once the Auto Configuration completes, you will be brought to the main SiteScope page.

3. Click on the “Preferences” link from the main SiteScope panel.

4. Enter the license in the “License Number” textbox.

5. Click the “Save Changes” button.

How to remove existing groups

On the SiteScope main page, you will see the following groups by default:

· Network

· Server

You are recommended to delete both of these groups.

1. Click on the group name (e.g., Network, or Server).

2. At the bottom of the page, click on “Delete this Group.”

3. On the Confirmation page, click on the “Delete <GroupName>” button to confirm the deletion.

How to add a SiteScope UNIX monitor group

  1. On the SiteScope main page, click on “Create Groups.”
  2. Enter a name for the group (e.g., LoadRunner Unix).
  3. Click on the “Add” button.

How to add a monitor to a group

Example:

Steps to add a CPU monitor:

1. From the SiteScope main page, click on the group name to go to the group.

2. Click on “Add a New Monitor to this Group.”

3. Click on “Add CPU Utilization Monitor.”

4. Click on “Choose a Server.” (This portion will add your Unix server to the machine list.)

5. Click on “Setup Unix Remote.”

6. Click on “Add a Remote Machine.” Enter the following information:

· Server Address

· OS Type

· Connection method: Choose “Telnet” as the connection method.

SiteScope uses a telnet login to access the machine and run standard Unix commands to gather machine statistic information. Due to this new process, you must ensure that you have a valid account that you can telnet into. In addition, you must ensure that the account you are using allows all the SiteScope commands to be executed. You can see a list of the commands SiteScope uses within the files in the C:<SiteScope>templates.os folder.

· Login and Password

· [Optional] Modify the waiting prompt on the Advanced Options.

7. Click on “Add Remote Server.” An automated test process to make sure SiteScope can access the machine is performed.

8. Click on “Back to Remote Machines.”

9. Click on “Return to Choose Servers.”

10. Choose the server created from the “Server” drop-down list.

11. Click on “Choose Server.”

12. Change the update time to 15 seconds.

13. Click on “Add Monitor.”

You have now added a Unix CPU monitor to SiteScope.

How to add an additional monitor to a group

Example:

Steps to add a Memory monitor:

1. Click on “Add a New Monitor to this Group.”

2. Click on “Add Memory Monitor.”

3. Choose the server that you added previously.

4. Change the update time to 15 seconds.

5. Click on “Add Monitor.”

You have now added a Unix Memory monitor to SiteScope.

Setting up a SiteScope UNIX Monitor in the Controller

1. In the Controller, look for the SiteScope monitor in the System Resource Section.

2. Display the graph by dragging it to the right. Right-click in the graph and select “Add Measurement(s).” You should now see the SiteScope Dialog box.

3. Click on the first “Add” button. For the machine name, type in the IP address or the machine name of the system on which SiteScope is installed. Click <OK>.

4. Click on the Second “Add” button. You should now see a SiteScope Monitor Configuration window. In the left pane, you should see a tree with the monitors you have added into the SiteScope application. Simply highlight the available monitors and choose the counters in the right pane. Click <OK> to get out of the menus.

5. You have now set up the New UNIX SiteScope monitor.

Error in Sitescope’s bac_integration\discovery.log file

Business Availability Center (BAC) 8.04, SiteScope 10.11

SiteScope\bac_integration\discovery.log shows:

2010-10-01 17:14:42,610 [SiteScope Main] … UCMDB\.PROBE\.(\d+\.\d+.\d+)\.Build_(\d+) does not matches data in file c:\collectors\versions.properties

2010-10-01 17:14:42,610 [SiteScope Main] (CollectorsParameters.java:506) ERROR – Using default UCMDB.PROBE.8.0.Build_0

SiteScope and BPM installed on the same server is causing a port conflict.

If you have BPM and SiteScope installed on same machine, this creates a port conflict. BPM cannot be installed on the same machine as SiteScope.

SAP CCMS Monitors – Failed to Get Counters

Unable to manually add SAP CCMS Monitors for one particular SAP server instances, SiteScope shows an error: "Failed to get Counters"

This is not a SiteScope issue, is normally associated to Windows Buffer issues, this can be confirmed using SiteScope SAP DEBUG, a new log file will be created only for SAP monitors, the file name is sap_monitors.log, in this file a message like the following could be found it:

ERRNO TEXT WSAENOBUFS: No buffer space available

How to activate the SAP DEBUG

Open this file in your SiteScope server: SiteScope\conf\core\Tools\log4j\PlainJava\log4j.properties

At the end of the file, add these lines:

##################################################################################

# SAP monitors

##################################################################################

log4j.category.com.mercury.sitescope.monitors.sap=DEBUG, monitors.sap.appender

log4j.additivity.com.mercury.sitescope.monitors.sap=false

log4j.appender.monitors.sap.appender=org.apache.log4j.RollingFileAppender

log4j.appender.monitors.sap.appender.File=../${log.file.path}/sap_monitors.log

log4j.appender.monitors.sap.appender.MaxFileSize=${def.file.max.size}

log4j.appender.monitors.sap.appender.MaxBackupIndex=${def.files.backup.count}

log4j.appender.monitors.sap.appender.layout=org.apache.log4j.PatternLayout

log4j.appender.monitors.sap.appender.layout.ConversionPattern=%d [%t] (%F:%L) %-5p – %m%n

##################################################################################

Close the file and try to create the SAP monitor again.

As this is a Windows issue, we recommend review the following links:

http://sap.ittoolbox.com/groups/technical-functional/sap-basis/wsaenobufs-no-buffer-space-available-in-saprouter-1193692

http://technet.microsoft.com/en-us/library/bb124810%28EXCHG.65%29.aspx

http://support.microsoft.com/kb/196271/en-us