Micro Focus SiteScope – Tips and Tricks

3. Micro Focus SiteScope – Tips and Tricks – Mar 2021

1. Procedure to set an email display in the default settings window in the Email preferences

A user has encountered problems when trying to set a display name for the email.

The complications faced can be solved with the steps that are instructed below.

The user cannot use “SiteScope – Test <sitescope_admin@mycompany.com>” on “Administrator email address” or in “From email address” because the SiteScope doesn’t support it and follows a separate format.


If the format above is not followed, then the user will continue to receive an error message.

However, there remains a way that this error can be avoided.

1. Close the SiteScope.

2. Then, run <SiteScope>\bin\PersistencyViewer.bat

3. The user is then instructed to open the persistence which is offered by the GUI (open it by going to the select persistence path option and selecting open).

4. At the ‘Filter by type’ select


click on “MailDefaultPreferences_”

  edit the field “_fromAddress” and enter 

for example, “Friendly Displayname  sitescope_admin@mycompany.com

   click OK and Continue.

5. Restart the SiteScope.

6. Try sending a test email and it will be displayed as,

From: Friendly.Displayname.sitescope_admin@mycompany.com

SiteScope test message (2001:0:9d38:6abd:38fa:1e8a:efcb:a1f9)

This is a test. This is only a test.

– SiteScope

The email address is modified by SiteScope to make it comply with the mentioned standard by replacing the spaces with “.”, resulting in “Friendly.Displayname.sitescope_admin@mycompany.com

2. Cross-reference list for official versions versus internal version of OBM/SiteScope

The introduction of the new version scheme


It has become difficult to find out the corresponding version in “v.u.f.” (Version.update.fix), for example, “11.70.”

The solution for the issue is instructed below.


  •   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 = (usually called 11.0)

Operations Bridge Manager Suite Releases

  • 9.26 classic
  • 10.00 classic
  • 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


  • 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 =
  • 2019.08 = 11.5.191
  • 2019.11 =
  • 2020.02 = container
  • 2020.05 = 11.6.2     

The versions can be retrieved through the GUI:

 Go to help and select about.

shows (for example)


        2019.02 | Build: SiteScope 11.70.54 64-bit JVM, Build 67 



        2018.11 | Build: 

There might also be a file as part of the installation depending on the product used with this information.

Operations Bridge Manager

  file <OBM_install_dir>\dat\version.txt

    Product: Operations Bridge Manager

    Version: 10.71

    Build: 016.001

    OfficialRelease: 2018.11


3. Steps to solve the failure of SiteScope SQL BD from not getting updated

Recent reports from the users show that there have been issues with the updating of SiteScope SQL BD. 

The solution suggested to the trouble encountered is listed.

Here it is noted that the table was created in the database but there was no data inserted in the table.

SiteScope – Even though the database logging was enabled, there was no data present in the database.

The debug can be enabled by adding the following statements to \conf\core\Tools\log4j\PlainJava\log4j.properties

The issue is found to be caused by the database.

The error that appears in the log file shows that the SiteScope tries to create a database table that is already existing.

Other errors that appear show that the SiteScope tries to enter the data into the table which has wrong columns.

For fixing the error:

1. Close the SiteScope service.

2.  Drop the empty table on the database side.

3.  Modify \groups\master.config

     Change the table name to create table and insert table to a different name. 

For example, the table to used below is called SIteScopeLog_01

_logJdbcCreateSiteScopeLog=CREATE TABLE SiteScopeLog_01 (datex VARCHAR(255), serverName VARCHAR(255), class VARCHAR(255), sample VARCHAR(255), category VARCHAR(255), groupName VARCHAR(255), monitorName VARCHAR(255), status VARCHAR(255), monitorID VARCHAR(255), value1 VARCHAR(255), value2 VARCHAR(255), value3 VARCHAR(255), value4 VARCHAR(255), value5 VARCHAR(255), value6 VARCHAR(255), value7 VARCHAR(255), value8 VARCHAR(255), value9 VARCHAR(255), value10 VARCHAR(255))



_logJdbcInsertSiteScopeLog=INSERT INTO SiteScopeLog_01 VALUES(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)

4. Restart the SiteScope service.

The data appears in the table: SiteScopeLog_01 from DataBase: SITESCOPE_DSO once the database is recreated.

4. Solution for the problem with the silent Login feature. KM03759713

Recently the silent login feature has not been working properly and the solution for this issue is given below.

According to with the documentation, the silent Login feature has been discontinued for SiteScope version 11.90 and 2020.05

Silent Login
(Feature is discontinued)

Silent Login
(Feature is discontinued)

The available options are:

Single Sign-on option (SSO): This option is a method of access control that would enable the user to log in once and gain access to the resources of the multiple software systems without the need for logging in for the second time.

The following SSO authentication strategies are supported by the SiteScope.

Lightweight Single Sign-On (LW-SSO). It is the default single sign-on authentication strategy for SiteScope. The LW-SSO is embedded in the SiteScope and an external machine is not required for authentication.

The default passphrase string for all software applications on integration with the LW-SSO must immediately be changed after installing the SiteScope.

 Lightweight Directory Access Protocol (LDAP). The user can configure the authentication using the Lightweight Directory Access (LDAP). This option enables you to use an external LDAP server to store authentication information such as usernames and passwords. SiteScope uses LDAP to verify customer Credentials. You can enable or disable the LDAP authentication from user management preferences.

5. Solution for the trouble faced while installing SiteScope 11.33 on top of SiteScope 11.30

Users were unable to install SiteScope 11.33 on top of SiteScope 11.30.

An error message was also displayed “ERROR: SiteScope v11.30 is not installed or some configuration files are missing”

Note: Even though the versions are dated already, proper troubleshooting information is given below.

The SiteScope 11.30 was installed on windows 2008 server into C:\SiteScope

When updating to SiteScope 11.33 by executing HPSiS1133_11.33_setup.exe 

the Installer GUI opens up and fails during the check of the “Product Requirements”:


ERROR: SiteScope v11.30 is not installed or some configuration files are missing

The installation logfile


(same in C:\Users\Administrator\AppData\Local\Temp\HPSiS1133_11.33_HPOvInstaller.txt)



2020-12-01 07:06:49,834 INFO – Performing the Requirements Checks

2020-12-01 07:06:49,839 INFO – Details :  performing checks … please wait

2020-12-01 07:06:49,866 INFO – Executing initialize action : InstallerEngine.jar

2020-12-01 07:06:52,748 INFO – Executing initialize action : validate_sis_installation.bat

2020-12-01 07:06:54,612 ERROR – [Failed]: ERROR: SiteScope v11.30 is not installed or some configuration files are missing



For troubleshooting the issue,

while the installer is still running, the script validate_sis_installation.bat can be found at


for example


The error message itself is generated during the flow of the script execution

<check name="CheckScriptRunner">
<title>HPE SiteScope installation validation...</title>
<exec name="validate_sis_installation.bat" halt_on_err="true" command="$DEFAULT_SHELL$">
<args>/c $RESOURCES$$FSEP$validate_sis_installation.bat $RESOURCES$ PRE_INSTALL @DOT_VERSION@</args>
<err_msg>ERROR: SiteScope v11.30 is not installed or some configuration files are missing</err_msg>

Executed the installed with DEBUG logging enabled:

  HPSiS1133_11.33_setup.exe -DLOGLEVEL=DEBUG
Now the file *HPOvInstallerLog.txt shows:
INFO [Thread-109] com.hp.ov.installer.ovapp.misc.ScriptRunner (?:?) - Executing initialize action : validate_sis_installation.bat
DEBUG [Thread-109] com.hp.ov.installer.ovapp.misc.exec.ExecRunner (?:?) - Executing command : C:\Windows\System32\cmd.exe args : /c C:\Users\ADMINI~1\AppData\Local\Temp\HPSiS1133\validate_sis_installation.bat C:\Users\ADMINI~1\AppData\Local\Temp\HPSiS1133 PRE_INSTALL 11.33 
DEBUG [Thread-109] com.hp.ov.installer.ovapp.misc.exec.ExecRunner (?:?) - Executing in env : OVCSL_LOG_FILE=C:\Users\ADMINI~1\AppData\Local\Temp\HPSharedComp-install.log ..
DEBUG [Thread-109] com.hp.ov.installer.ovapp.misc.exec.ExecRunner (?:?) - Executing the populated command : C:\Windows\system32\cmd.exe /c C:\Windows\System32\cmd.exe /c C:\Users\ADMINI~1\AppData\Local\Temp\HPSiS1133\validate_sis_installation.bat C:\Users\ADMINI~1\AppData\Local\Temp\HPSiS1133 PRE_INSTALL 11.33 
DEBUG [Thread-109] com.hp.ov.installer.ovapp.misc.exec.ExecRunner (?:?) - Process Destroyed
DEBUG [Thread-109] com.hp.ov.installer.ovapp.misc.exec.ExecRunner (?:?) - [1] [1.764 secs] Command :C:\Windows\system32\cmd.exe /c C:\Windows\System32\cmd.exe /c C:\Users\ADMINI~1\AppData\Local\Temp\HPSiS1133\validate_sis_installation.bat C:\Users\ADMINI~1\AppData\Local\Temp\HPSiS1133 PRE_INSTALL 11.33  arguments : /c C:\Users\ADMINI~1\AppData\Local\Temp\HPSiS1133\validate_sis_installation.bat C:\Users\ADMINI~1\AppData\Local\Temp\HPSiS1133 PRE_INSTALL 11.33 
DEBUG [Thread-109] com.hp.ov.installer.ovapp.misc.exec.ExecRunner (?:?) - No Command Output.
DEBUG [Thread-109] com.hp.ov.installer.ovapp.misc.exec.ExecRunner (?:?) - No Command Error.
ERROR [Thread-109] com.hp.ov.installer.ovapp.check.CheckScriptRunner (?:?) - [Failed]: ERROR: SiteScope v11.30 is not installed or some configuration files are missing
DEBUG [Thread-109] com.hp.ov.installer.ovapp.core.InstallEntity (?:?) - Processing state for : CheckScriptRunner is set to : Completed with Failure

Fix for the issue:

Modified the script validate_sis_installation.bat and added some simple ECHO commands to see where the script fails 

@echo off
:: validate_sis_installation.bat
:: Validates BSM MMR pre-requisites
echo 1
FOR /F "usebackq" %%A IN ('%ERR_FILE%') DO SET SIS32_EXISTS=%%~zA
) ELSE (
echo 2
FOR /F "usebackq" %%A IN ('%ERR_FILE%') DO SET SIS32ON64_EXISTS=%%~zA
echo 3
FOR /F "usebackq" %%A IN ('%ERR_FILE%') DO SET SIS64_EXISTS=%%~zA

and then executed it manually:

C:\Users\ADMINI~1\AppData\Local\Temp\HPSiS1133\validate_sis_installation.bat C:\Users\ADMINI~1\AppData\Local\Temp\HPSiS1133 PRE_INSTALL 11.33 

It turned out that for whatever reason the command querying the registry failed

  ERROR: The system was unable to find the specified registry key or value.

IF [%SIS64_EXISTS%] EQU [0] (
FOR /F "delims=" %%a in ('%CMD_64BIT% /c "%CSCRIPT_ENGINE% //nologo readRegistryValue.vbs %PACKAGE_REG_KEY%\%QUERY_VALUE%" ') do (set PRODUCT_VERSION=%%a)
FOR /F "delims=" %%a in ('%CMD_64BIT% /c "%CSCRIPT_ENGINE% //nologo readRegistry.vbs %SIS_REGROOT%\%INSTALLDIR%" ') do (set PRODUCT_HOME=%%a)

and thus neither 




were initialized properly, while executing the same command manually from the command line

  c:\>reg.exe query HKLM\SOFTWARE\Hewlett-Packard\SiteScope\{6F5CD31E-DDAF-4ECA-976F-74A369058440} /v ProductVersion

returned the data expected

    ProductVersion    REG_SZ    11.30.461

As a workaround, the script was changed from

IF [%PRODUCT_VERSION%] NEQ [11.30.461] (

SET FLAG_11_30=1


set PRODUCT_VERSION = 11.30.461

set PRODUCT_HOME= C:\SiteScope

IF [%PRODUCT_VERSION%] NEQ [11.30.461] (

SET FLAG_11_30=1

The installer was moved back one step by simply clicking on “PREVIOUS”, the updated file validate_sis_installation.bat was copied to 


and then by clicking on Next the installer used the update file.

With the “Product Requirements” checks now passed, SiteScope 11.33 could be installed.


In another environment, the script validate_sis_installation.bat worked perfectly fine, but at the end of the script another script is called:


:: Run Installation wizard


IF EXIST “%PRODUCT_HOME%\installation\bin\product_upgrade_wizard.bat” (

  %PRODUCT_HOME%\installation\bin\product_upgrade_wizard.bat” %TYPE% %INSTALLATION_NAME% %INSTALLATION_VERSION% %STEP% %GUID% >nul 2>&1

 ) ELSE (

exit /b 1


It was noted that the script product_upgrade_wizard.bat was causing the error, and the error only was reported up to validate_sis_installation.bat

6. Procedure for passing variables through Script Alerts

Some users find it difficult to pass variables through the Script Alerts. The instructions for the steps that are needed to be carried out are given below.

1. The user must add “Match value labels:” called: “returnval”

2. Then, use the “Match expression:” ◊ /(.*)/s  If the s id is not included then it won’t work.

3.  The “Timeout (Seconds):” cannot be “-1”. If so, change the value to “60” or the other to -1.

In the thresholds that were used. 

Condition: returnval
Operator: Contains
Value: ‘return val: 1’

The solution was found to work.

7. Solving the supported OS vulnerability issues for RUM

There has been an issue with the RUM 9.51 implementation which has a RUM with a probe that was installed in RHEL 7.5, vulnerabilities that were associated with Linux in accordance with the document, the maximum OS version supported by RUM probe is RHEL 7.5

The solution suggested is given below.

It was noted after thorough consideration and confirmed that it was not possible to use a different version than one that was documented or certified for RUM RHEL, for this case maximum version is 7.5 for RHEL.

The other option that is available here is to use a RUM client or create an ER requesting support for RHEL 8x.

The link for the detailed information is 

8. Instructions to stop old BSM server details from appearing after changing to new BSM servers

There are reports regarding the presence of old BSM server details while accessing new BSM servers even after updating. It can be seen under the platform administration window under the infrastructure settings which can be accessed from the setup and maintenance option. 

The solution for the problem faced is,


Tables from DataBase were backed up.

1. It is required that the user stop the DPS and gateways for the previous versions with sonic Bus in the way mentioned below:

• STOP Gateways first• Then STOP DPS 2 , then DPS1• Go to the “Schema” DataBase• Remove the desire host : xxxxxxxx with H_ID : XXX• Run the select query in the "Schema" DataBase to confirm all the information from the server to be removed in the Schema DataBase:Select * from HOSTS (Find the ID for the host you want to remove)Select from HOSTS_HOST_TYPES_PROP where HHTP_HOST2HOSTTYPES_ID in (Select hht_id from HOSTS_HOST_TYPES where HHT_HOST_ID =)Select from HOSTS_HOST_TYPES where HHT_HOST_ID =Select FROM HOSTSESSIONS where HS_HOSTID=Select from hosts where h_id =Select * from HOSTS (Find the ID for the host you want to remove)
Using the delete command the user is required to complete the host removal.
Select * from HOSTS (Find the ID for the host you want to remove) ◊ not for thisdelete from HOSTS_HOST_TYPES_PROP where HHTP_HOST2HOSTTYPES_ID in (Select hht_id from HOSTS_HOST_TYPES where HHT_HOST_ID =)delete from HOSTS_HOST_TYPES where HHT_HOST_ID =delete FROM HOSTSESSIONS where HS_HOSTID=delete from hosts where h_id =

Then, put up the running gateways and DPS. Run the config wizard tool to check if the host was removed properly.

To check if the host was removed properly, check the BSM platform by going to the platform administration window.

9. Steps to specify a channel name when connecting to MQ

Recently users have questioned if it was possible to specify a channel name when connecting to MQ.

The steps for the process are:

Launch the SiteScope UI as a desktop application from the SiteScope local client. It can be launched without the need for a browser as the SiteScope enables it.

To access secure connections (HTTPS) of SiteScope using the SiteScope local client, the user must install the site security certificate into the Trusted Root Certification Authorities where the local client is installed and running. Also, it is highly recommended to verify the digital signature of the SiteScope-Client-Tip.zip. The steps are provided in the ReadMe file of the SiteScope Local client.

Install the security certificate on the server where the thick client is installed

  1. Copy the security certificate from the SiteScope server.
  2. Double-click the .cer file.
  3. On the Certificate dialog box, click Install Certificate to start the Certificate Import Wizard.
  4. On the Welcome page, click Next.
  5. On the Certificate Store page, select Place all certificates in the following store and click Browse.
  6. In the Select Certificate Store dialog box, select Show Physical Stores.
  7. Double-click Trusted Root Certification Authorities, select Local Computer, and then click OK.

On the Certificate Store page, click Next.

  1. On the summary page, review the details and click Finish.

For launching it,

  1. Download the SiteScope-Client-2019.11.zip.
  2. Extract the contents of the SiteScope-Client-2019.11.zip to a location of your choice.
  3. Navigate to the dist folder and double-click SiteScopeClient.bat. The SiteScope Local Client window opens.
  4. Enter the SiteScope URL in the format http://<host name>:<port number>/SiteScope or https://<host name>:<port number>/SiteScope for HTTPS connections. The SiteScope login screen opens.
  5. Enter your user credentials. The SiteScope UI opens.


The following are the limitations of this release. 

  • Multiple instances of SiteScope using a single instance of the local client cannot be launched. However multiple instances of SiteScope can be launched using multiple local clients.
  • SiteScope with smart card authentication is not supported.
  • Unified Console for the Chinese and Japanese locale is not supported.
  • Report options such as Export in the Monitor, Alert, and Server-centric reports do not work.
  •  The local client has to be closed and relaunched to continue to work with the SiteScope UI on:

Loading a new license

Restarting SiteScope from infrastructure Preferences.

10. How to access the list of Free and open-source libraries used by APM

Users have asked for the procedure to access the list of open source libraries, versions, and license information used, and more specifically for the free and open-source (FOSS) library name.

Solution suggested:

The necessary information for accessing the list of free and open-source libraries used by APM can be found in the link.

11. Fix for the connection failure of the monitor to the remote login server

Users have encountered issues with the connection of the monitor to the remote login server.

The necessary solution for the trouble faced is given below.

After a thorough inspection, it is found that several monitors skipped. The users are required to change the heap size.

Action plan 1:

In the SiteScope server, the java heap size must be increased.

1. Terminate SiteScope service.

2. After going to the Registry Editor, follow this path.


After that edit the -Xmx and -Xms values to 8192.

3. The user must then go to the master. config and change or add the following parameter at the end of the list.

Garbage collector se usa cuando hay problemas de performance:
_runGPeriod=900000 –> to free memory

4. After completing the mentioned processes, reboot the server.

5. Restart the SiteScope Service.

The frequency from the ‘pharmacy’ monitors must be changed to check if the problem still continues.

In case if the problem remains, then the frequency of the URL and URL sequence monitors must be changed as well.