Micro Focus SiteScope – Tips and Tricks

Table of Contents

4. Micro Focus SiteScope – Tips and Tricks – Apr 2021

Sitescope – How to add Remote Server Configuration for NetApp ONTAP 9.3 device

Do you want to add Remote Server Configuration for NetApp ONTAP 9.3 device? Does SiteScope support NetApp ONTAP 9.3 devices as remote servers?

Unfortunately, SiteScope doesn’t support ONTAP devices as remote servers. There are a few more options to retrieve data from them I.e.,

1. Work with scripts and alerts.

2. Create a script monitor to extract counters from ONTAP devices and trigger alerts.

SiteScope configuration wizard export configuration feature runs forever

Do you know that the SiteScope configuration wizard export configuration feature ran all night, but still did not complete? We need help to determine the cause and solution to this issue. Are there logs for the export configuration feature? If so, where are they located?

For simplifying this error, run the config tool with Admin rights permissions.

SiteScope applet loading fails with a “NoClassDefFound” exception

The applet in SiteScope loading fails with a “NoClassDefFound” exception

If applet loading fails with a “NoClassDefFound” exception, follow the below written steps to upload it.

Step 1: Select the Keep temporary files on my computer option in your client Java configuration (Control Panel > Java > General Tab > Temporary Internet Files > Settings).

Step 2: If security issues require it, delete the temporary files manually when you finished using the SiteScope applet:

Step 3: Choose the SiteScope applet.

Step 4: Select Start > Control Panel > Java > General tab.

Step 5: Select Temporary Internet Files section, click Settings, and then click Delete Files.

SiteScope applet loading fails with a “NoClassDefFound” exception

SiteScope does not start and an error message is displayed.

If you encounter an error message such as “The Java Runtime Environment cannot be loaded”, or any other unknown error while starting the SiteScope applet, perform the steps below.

After each step, try to reopen SiteScope. If SiteScope fails again, proceed to the next step.

Close all the browser’s windows.

End all remaining browser processes (if any remained) using Windows Task Manager.

Clean the local Java applet cache. Select Start > Control Panel > Java. In the General tab, click Settings > Delete Files and then click OK.

Clean the local Java applet cache by deleting the content of the following folder: C:\Documents and Settings\<user_name>\Application Data\Sun\Java\Deployment\cache.

SiteScope – SSL configuration not retained after a SiteScope version upgrade on Windows

The Upgrader has a few problem i.e. it is unable to read the environment variable %SISINSTALLER_PATH% during the upgrade and hence unable to locate the backed-up server.xml file.etained after upgrade in Windows.The SSL configuration is not retained after upgrade on a Windows machine.You can view the following message in the SiteScope_config_tool.log file:

“Server.xml doesn’t exist. Not an upgrade scenario.”

The Upgrader has a few problems i.e. it is unable to read the environment variable %SISINSTALLER_PATH% during the upgrade and hence unable to locate the backed-up server.xml file.etained after upgrade in Windows.

Now let’s look at the solutions.

Solution 1

Follow the below written steps to restore the backed-up server.xml.

Step 1: Go to %SITESCOPE_HOME%\Tomcat\conf directory and take backup of the server.xml file.

Step 2: Replace the server.xml file in the %SITESCOPE_HOME%\Tomcat\conf directory with the server.xml file available at the following location:

%SITESCOPE_HOME%\tools\SiteScopeHardeningTool\SSL_TOOL_DATA

Step 3:Open this server.xml file and locate the section of the file that looks like the following:

<Connector port=”8443″ server=”******” compressableMimeType=”text/html,text/xml,text/javascript,text/css,image/x-icon,application/json” noCompressionUserAgents=”gozilla, traviata” compressionMinSize=”2048″ compression=”on” truststoreType=”%%TRUSTSTORE_TYPE%%” trustStorePass=”%%TRUSTSTORE_PASS%%” trustStoreFile=”%%TRUSTSTORE_PATH%%” keystoreType=”%%KEYSTORE_TYPE%%” keystrokes=”%%KEYSTORE_PASS%%” keystoreFile=”%%KEYSTORE_PATH%%” SSLVerifyClient=”true” SSLEnabled=”true” clientAuth=”%%CLIENT_AUTHENTICATION%%” ciphers=”%%CIPHERS_LIST%%” sslEnabledProtocols=”TLSv1,TLSv1.1,TLSv1.2,SSLv2Hello” secure=”true” scheme=”https” debug=”0″ acceptCount=”100″ disableUploadTimeout=”true” enableLookups=”false” maxSpareThreads=”75″ minSpareThreads=”25″ maxThreads=”150″ maxHttpHeaderSize=”8192″/>

Step 4: Replace the placeholders %%TRUSTSTORE_TYPE%%, %%TRUSTSTORE_PASS%%, %%TRUSTSTORE_PATH%%, %%KEYSTORE_TYPE%%, %%KEYSTORE_PASS%%, %%KEYSTORE_PATH%%, %%CLIENT_AUTHENTICATION%%, and %%CIPHERS_LIST%% with the values from the backed-up server.xml file.

Step 5: Replace the backed-up server.xml file is available at the following location:

INSTALLER_DIR>\customtls_settings

where, <INSTALLER_DIR> is the location where the sitescope bits are placed.

Step 6: Restart SiteScope.

Solution 2

Configure SiteScope hardening again using the SiteScope Hardening Tool.

APM / BSM / BPM / SiteScope / RUM Engine – how to retrieve the Apache Web Server / Tomcat / Java version

How to retrieve the Apache Web Server / Tomcat / Java version in APM / BSM / BPM / SiteScope / RUM Engine?

Apache Web Server Version

Linux

/opt/HP/BSM/WebServer/bin/httpd -v

Server version: Apache/2.2.21 (Unix)

Windows

<HPBSM>\WebServer\bin>httpd -v

Server version: Apache/2.2.21 (Win32)

Here are some versions:

BSM 9.25     – Apache 2.2.27

BSM 9.26 – Apache 2.4.16

BSM 9.26 IP2 – Apache 2.4.20

APM 9.30     – Apache 2.4.18

APM 9.40     – Apache 2.4.23

APM 9.50     – Apache 2.4.23

APM 9.51     – Apache 2.4.23

Tomcat and JVM Version

Now, run the following commands from your <application-install> or <tomcat-install> directory.

Note: If you do not have your Java Home directory included in your PATH environment variable, you will need to include the path to your <java-home>/bin directory in front of the java command.

Here are some commands for other versions.

Linux

java -cp lib/catalina.jar org.apache.catalina.util.ServerInfo

Windows

java.exe -cp lib\catalina.jar org.apache.catalina.util.ServerInfo

But depending on the Tomcat version, this command might work as well:<tomcat-install>\bin\version.bat / version.sh

For example:

BPM 9.24 on Windows, installed into C:\BPM

change to directory C:\BPM\ServletContainer\lib

java.exe -cp catalina.jar org.apache.catalina.util.ServerInfo

Server version: Apache Tomcat/7.0.42

Server built:   Jul 2 2013 08:57:41

Server number:  7.0.42.0

..

JVM Version: 1.7.0_15-b03

JVM Vendor: Oracle Corporation

BPM 9.26 IP1 on Windows

Server version: Powered by HP

Server built:   Jul 2 2013 08:57:41

Server number:  7.0.42.0

..

JVM Version: 1.7.0_79-b15

JVM Vendor: Oracle Corporation

BPM 9.40 on Windows, installed into C:\HP\BPM

change to directory C:\HP\BPM\ServletContainer\lib

java.exe -cp catalina.jar org.apache.catalina.util.ServerInfo

Server version: Apache Tomcat/8.5.4

Server built:   Jul 6 2016 08:43:30 UTC

Server number:  8.5.4.0

BPM 9.52 on Windows, installed into C:\MF\BPM

change to directory C:\MF\BPM\ServletContainer\lib

java.exe -cp catalina.jar org.apache.catalina.util.ServerInfo

Server version: Apache Tomcat/8.5.4

Server built:   Jul 6 2016 08:43:30 UTC

Server number:  8.5.4.0

SiteScope 11.24 on Windows, installed into C:\SiteScope

change to directory C:\SiteScope\Tomcat\server

java.exe -cp lib\catalina.jar org.apache.catalina.util.ServerInfo

Server version: Apache Tomcat/5.5.33

Server built:   Feb 8 2011 05:13:31

Server number:  5.5.33.0

..

JVM Version: 1.7.0_15-b03

JVM Vendor: Oracle Corporation

SiteScope 11.33 IP2 on Windows, installed into C:\SiteScope

change to directory C:\SiteScope\Tomcat\bin

version.bat

..

Server version: Apache Tomcat/7.0.69

Server built:   Apr 11 2016 07:57:09 UTC

Server number:  7.0.69.0

..

JVM Version: 1.7.0_51-b13

JVM Vendor: Oracle Corporation

SiteScope 11.40 on Windows, installed into C:\SiteScope

change to directory C:\SiteScope\Tomcat\bin

version.bat

..

Server version: Apache Tomcat/7.0.77

Server built:   Mar 28 2017 16:01:48 UTC

Server number:  7.0.77.0

..

JVM Version:    1.8.0_131-b11

JVM Vendor: Azul Systems, Inc.

Note:The JVM version returned depends on the system-wide setting of JRE_HOME:

version.bat

Using CATALINA_BASE:   “C:\SiteScope\Tomcat”

Using CATALINA_HOME:   “C:\SiteScope\Tomcat”

Using CATALINA_TMPDIR: “C:\SiteScope\Tomcat\temp”

Using JRE_HOME:    “C:\Program Files (x86)\Java\jre7”

Server version: Apache Tomcat/7.0.69

Server built:   Apr 11 2016 07:57:09 UTC

Server number:  7.0.69.0

..

JVM Version: 1.7.0_51-b13

JVM Vendor: Oracle Corporation

version.bat

Using CATALINA_BASE:   “C:\SiteScope\Tomcat”

Using CATALINA_HOME:   “C:\SiteScope\Tomcat”

Using CATALINA_TMPDIR: “C:\SiteScope\Tomcat\temp”

Using JRE_HOME:        “C:\SiteScope\Java”

Server version: Apache Tomcat/7.0.69

Server built:   Apr 11 2016 07:57:09 UTC

Server number:  7.0.69.0

..

JVM Version:    1.8.0_92-b15

JVM Vendor: Azul Systems, Inc.

Some SiteScope – Apache Tomcat versions:

SiteScope 11.24 – Apache 5.5.33

SiteScope 11.33 – Apache 7.0.69

SiteScope 11.40 – Apache 7.0.77

SiteScope 11.51 – Apache 7.0.82

SiteScope 11.60 – Apache 7.0.90

SiteScope 11.90 – Apache 7.0.94

SiteScope 11.91 – Apache 7.0.96

SiteScope 11.92 – Apache 7.0.100

SiteScope 11.93 – Apache 7.0.105

JBoss and Tomcat for BSM

To retrieve the JBoss version, please check the logfile.

 <HPBSM>\log\jboss_boot.log and search for the line

 INFO  – Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)

The above is the result for BSM 9.25 IP1

JBoss and Tomcat for RUM Engine

To retrieve the JBoss version, check the logfile

 <RUM_Engine>\log\jboss_boot.log and search for the line

INFO  [AbstractServer] JBossAS [6.1.0.Final “Neo”] Started in 1m:39s:75ms 

The above is the result for RUM Engine 9.25.

Tomcat for RUM ClientMonitor Probe

ClientMonitor Probe 9.26, installed into C:\HPRUMClientMonitorProbe

change to directory C:\HPRUMClientMonitorProbe\Tomcat\bin

version.bat

..

Server version: Apache Tomcat/7.0.56

Server built:   Sep 26 2014 12:08:24

Server number:  7.0.56.0

..

ClientMonitor Probe 9.40 – 8.5.4

Tomcat version embedded in JBoss

From JBoss 4.2 and upwards, it doesn’t come bundled with Tomcat,but a forked version of it, called JBossWeb. It’s separately maintained, independent of the Tomcat code base.

Based on the JBoss version (here it is 6.1.0) one then can check the following site for the JBoss Web version:

JBoss Enterprise Application Platform 6

JBoss AS 6.1.0 comes with JBoss Web 7.2.0.Final

JBoss 4.2.3 (used with for example BSM 9.25) comes with Tomcat 6.0.13

SiteScope 11.32 – Email Preferences – Default Settings – how to set a email display name

How to set up an email display name in SiteScope 11.32 – email Preferences – Default? Customers are trying to set a display name for an email address so when SiteScope sends an email the from is like:” SiteScope – Test” <[email protected]>

When this email is viewed/previewed, it has a nice display name. But SiteScope – Preferences – Email Preferences – Default Settings – Edit dialog does not accept any of the following:

“SiteScope – Test” <[email protected]>

“SiteScope – Test <[email protected]>”

\”SiteScope – Test\” \<[email protected]\>

Currently, we only have a bogus email address I.e. [email protected]

But we would like to send corrections by replying to an alert email for our users.

The “SiteScope – Test <[email protected]>”   does not give chance for usage on “Administrator email address” or in “From email address” because SiteScope verifies whether you enter a valid email address or not. This address has to be of the format <whatever>@<whatever.whatever> otherwise the error Field does not match email address format is returned.

There is a way for this problem: complete support is not guaranteed. Let us check the steps related to this.

Step 1: Stop SiteScope run <SiteScope>\bin\PersistencyViewer.bat.

Step 2: Open the persistence which is offered by the GUI (Select Persistency Path -> Open)- at “Filter By Type”.

Step 3: Select com.mercury.sitescope.platform.coonfigmanager.preferences.PreferenceConfig.

Step 4: Click on “MailDefaultPreferences_”.

Step 5: Edit the field “_fromAddress” and enter (for example)  Friendly Displayname [email protected]

Step 6: Click OK and Commit start SiteScope.

Step 7: From test email, it will show from: [email protected]

SiteScope test message (2001:0:9d38:6abd:38fa:1e8a:efcb:a1f9)This is a test. This is only a test.SiteScope…

SiteScope modifies the email address to make it comply with whatever standard by replacing the spaces with resulting in “[email protected]

This is as close as one can get without opening an ER.

SiteScope- unable to deploy template – fails with Failed to commit – uniqueness violation

Some problems like unable to deploy template – fails with Failed to commit – uniqueness violation are seen on SiteScope 11.4x up to 11.9x.When trying to load many (in 100s) URL monitors in various monitoring groups using Template,the expected layout is something like…

App01

  url1

  url2

  url3

App02

  url4

  url5I

An error occurs while deploying the template using a CSV file.It creates a group,also the first URL monitor and then fails.Logs show the following error for the subsequent URL monitors.

Error:

Error in template ‘Bulk URL Monitor Load’ encountered:

Failed to commit – uniqueness violation – the name ‘App02’ exists in the requested destination.

How can multiple monitors be deployed under one group using a template?

If you want to deploy or create templates with a parent group, then the following steps need to be considered.

Step 1: First select the option to allow this need to be enabled:SiteScope -> Preferences -> Infrastructure Preferences -> Template Settings.

Step 2:Allow creation of template monitors directly under a template entity

and restart SiteScope

After following the steps,one can create in a template a monitor directly under the template, there is no need to create a group in between anymore.Without this change you need to create the monitor under a template group.When now the template is deployed, it tries to create the SiteScope group with the name of the template group.This works the first time, but fails any other time because the group exists already.

Note that now the group the monitors are created under needs to be create manually, in this example App01 and App02

OBM / Sitescope – official versions versus internal version, for example SiteScope 2020.10 == 11.93 – cross-reference list

The SiteScope, Operations Bridge Manager (OBM ), uCMDB SiteScope 2020.10 = 11.93 OBM 2020.05 = 11.0 CMDB crossed the reference list.The new versioning scheme  yyyy.mm has been introduced.

For example “2018.11” it can get tough to find out the corresponding version in “v.u.f.” (version.update.fix), for example “11.70”.

SiteScope 

2018.05 = 11.50.87
2018.08 = 11.51.131
2018.11 = 11.60.83
2019.02 = 11.70.54 
2019.05 = 11.80.35 
2019.08 = 11.90.453
2019.11 = 11.91
2020.05 = 11.92.51
2020.10 = 11.93.101

Operations Bridge Manager (OBM)

2017.11 = 10.63
2018.02 = 10.64 plus fixes (applies to the "container" version only)
2018.05 = 10.70
2018.08 = 10.70 plus fixes (applies to the "container" version only)
2018.11 = 10.71
2019.02 = 10.72 plus fixes (applies to the "container" version only)
2019.05 = 10.80
2019.08 = 10.81 plus fixes (applies to the "container" version only)
2019.11 = 10.82
2020.05 = 11.00.010.011 (usually called 11.0)

Operations Bridge Manager Suite Releases

Release
9.26 classic
10.00 cclassi
10.01 classic
10.11 classic
10.12 classic
10.60 classic
10.62 classic
10.63 classic
2018.02 = 10.64 container
2018.05 = 10.70 container
2018.08 = 10.70 container
2018.11 = 10.71 classic and container
2019.02 = 10.72 container
2019.05 = 10.80 classic and container
2019.08 = 10.81 container
2019.11 = 10.82 classic and container
2020.05 = 11.00 classic
2020.11 = 11.01 classic and container

uCMDB

11.0.12
2018.05 = 11.1.92
2018.08 = 11.2.96
2018.11 = 11.3.124
2019.02 = 11.4.125
2019.05 = 11.5.0.127
2019.08 = 11.5.191
2019.11 = 11.6.0.96
2020.02 = 11.6.1.106 container
2020.05 = 11.6.2     

Versions can be retrieved via the GUI:

Help -> About shows (for example) SiteScope 2019.02 | Build: SiteScope 11.70.54 64-bit JVM, Build 67 

Or

OBM 2018.11 | Build: 10.71.016.001 

Depending on the product there also might be a file as part of the installation with this information.

SiteScope

file <SiteScope_install_dir>\dat\version.txt

Product: HPE SiteScope

Version: 11.60.83

Build: 82

Operations Bridge Manager

file <OBM_install_dir>\dat\version.txt

Product: Operations Bridge Manager

Version: 10.71

Build: 016.001

OfficialRelease: 2018.11

OfficialBuild: 10.71.016.001

How to recreate the SiteScope service (Windows Only)

Did you lose your SiteScope service in Windows?You can reinstall the SiteScope service in case of corruption or deletion.You only need to execute the following command.

Here is the command by which you can re-install SiteScope.

SiteScopeService.exe -install <servicepath> <serviceparams> [servicename] [-force]

Reinstallation of SiteScope service:

Step 1: Open the Command window as administrator

Step 2: Navigate to <SiteScope root directory>\tools

Step 3: Run the command SiteScopeService.exe -install <servicepath> <serviceparams> [servicename] [-force]

This should creates the following registry key HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Services -> <SiteScope service> -> ServiceParam 

Servicepath:

“<SiteScope root directory>\SiteScope”

Example: “C\SiteScope”

Service Param:

"-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=28006 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -server -Xmx512m -Xms512m -Xmn160m -Xrs -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:MaxPermSize=240m -XX:+HeapDumpOnOutOfMemoryError -showversion -Dcatalina.home="<SiteScope root directory>\Tomcat" -Djava.security.auth.login.config=file://///${catalina.home}/../conf/jaas.config -Dflipper.param.file=..\conf\flipperSiteScope.properties -Dtopaz.home=.. -Dnetworkaddress.cache.ttl=86400 -Dnetworkaddress.cache.negative.ttl=0 -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -DSiteScope=true -cp "<SiteScope root directory>\Tomcat\bin\bootstrap.jar" org.apache.catalina.startup.Bootstrap start"

Important:Make sure to update the service path in the ServiceParam string.

Example:

"-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=28006 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -server -Xmx512m -Xms512m -Xmn160m -Xrs -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:MaxPermSize=240m -XX:+HeapDumpOnOutOfMemoryError -showversion -Dcatalina.home="C:\SiteScope\Tomcat" -Djava.security.auth.login.config=file://///${catalina.home}/../conf/jaas.config -Dflipper.param.file=..\conf\flipperSiteScope.properties -Dtopaz.home=.. -Dnetworkaddress.cache.ttl=86400 -Dnetworkaddress.cache.negative.ttl=0 -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -DSiteScope=true -cp "C:\SiteScope\Tomcat\bin\bootstrap.jar" org.apache.catalina.startup.Bootstrap start" 

ServiceName:

servicename

Example: “SiteScope”

Full command :

"SiteScopeService.exe -install "C:\SiteScope" "-Dcom.sun.management.jmxremote=true -Dcom.sun.management.jmxremote.port=28006 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -server -Xmx512m -Xms512m -Xmn160m -Xrs -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:MaxPermSize=240m -XX:+HeapDumpOnOutOfMemoryError -showversion -Dcatalina.home="C:\SiteScope\Tomcat" -Djava.security.auth.login.config=file://///${catalina.home}/../conf/jaas.config -Dflipper.param.file=..\conf\flipperSiteScope.properties -Dtopaz.home=.. -Dnetworkaddress.cache.ttl=86400 -Dnetworkaddress.cache.negative.ttl=0 -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -DSiteScope=true -cp "C:\SiteScope\Tomcat\bin\bootstrap.jar" org.apache.catalina.startup.Bootstrap start" SiteScope -force"