Micro Focus Application Performance Management – Tips And Tricks

Table of Contents

4. Application Performance Management – Tips And Tricks – Mar 2021

1. APM – Application Health doesn’t allow special characters

Summary

Here is the issue with APM – Application Health doesn’t allow special characters.

Application Health doesn’t allow special characters in the business application name. For the time being, it’s impossible to use special characters for the Business Application names with the Application Health page in APM.

As the CIs are synced from uCMDB and the names contain parenthesis in the most cases, we are unable to change/save settings through this page.

Solution

However, this issue needs to be resolved. Characters aren’t allowed while creating an application. It was implemented intentionally because of security reasons.

Since it is an HTML page some special characters have been restricted for security purposes.

For your reference below are the characters that are restricted:

 / \ : * ? ‘ ” < > # % ˆ ( ) [ ] =

You can use “{“ & “}” in the Application name.

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

Summary

SiteScope, Operations Bridge Manager (OBM), uCMDB SiteScope 2020.10 = 11.93 OBM 2020.05 = 11.0 CMDB

With the introduction of the new versioning scheme yyyy.mm,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”.

Solution

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

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

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 

There may be a file as apart of installation with this information depending on the product. Here are the files

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

Official Release: 2018.11

OfficialBuild: 10.71.016.001

3. Unable to integrate SiteScope11.33 IP3 with APM 9.50

Summary

You know, we are unable to integrate SiteScope11.33 IP3 with APM 9.50. Below written are the versions.

APM Version: 9.50SiteScope version: 11.33 IP3

OS Version: Windows 2012 R2

We did harden on our SiteScope (11.33 IP3 Patch) with a self signed cert and tried integrating it with APM 9.50. It’s integrated fine, however we are not able to launch the console in SAM on APM 9.50. 

Solution

We need to resolve this issue. Actually, it seems that one or more packages have not been upgraded correctly. We got this hint while looking at the logs updated.

To resolve the issue follow the below written steps.

Step 1: Go to the RTSM JMX console.

Step 2: Use the link   http://:21212/jmx-console for default credentials that are admin.

Step 3: Go to UCMDB: service=Packaging Services – Packaging Services.

Step 4: Go to display deployed packages.

Step 5: Check for the odb packages to be listed and if this is true choose to undeploy.

This will take a while. Once this has been done redeploy them all.

When finished, you might get a list of errors, but hopefully also a list of deployed packages, it should now show a much higher number then before.

Here are results.:

while – as expected – several deployments failed

******** operation has failed for 78 resources ********

many (the majority) worked

******** 3445 deployed resources: ********

Once this has been done, please restart your APM environment.

4. BSM / APM – data to be retrieved to enable Support / CPE / R&D to fix EUM Model Validation errors / Model corruption / errors returned by validateEumModel

Summary

You may have already learnt that there are errors in validateModel.Let us see how to tackle these errors. But first we will gain some knowledge about EUM model corruption.

EUM Model Corruption

It describes an inconsistency of the data related to CIs within the Management database or between the Management database and RTSM database. Due to this model corruption, many functionality issues would occur.

For example,

We will be unable to access the EUM settings tab, because it fails with error “Network error to get BSM server”.

We will be unable to access the configuration details of an Application or BTF, it fails with error Failed to load Business Transaction Flow <name> Business Process Monitor properties.Failed to get BPM configuration for Business Application CI.

Application / BTFs are greyed out and unable to access a BTF shows inactive with error”Failed to load Business Process Monitor Application Defaults. Network error to get BSM server”and cannot be deleted.

Application / BTF is greyed out and unable to access, it fails with error”Unable to load data”.

We will be unable to delete the Application, it fails with error Failed to update BPM configuration for Business Application CI.

System Error occurred:Failed to update BPM configuration for Business Application CI.

Failed to find element of type BPM configuration for Business Application CI identified by <CI ID>

We will be unable to create a new application, when the user goes to Admin -> End User Management, and tries to create, it fails with error “Failed to update BPM configuration for Business Application CI. System error occurred: {0}”.

We will be unable to remove the data collectors assigned to an application or BTF, fails with error Failed to remove BPM Configuration for Business Application CI.

System error occurred: org.hibernate.TransientObjectException: object references an

unsaved transient instance – save the transient instance before flushing:

com.mercury.am.eum.bpm.model.jpa.BpmScriptJpaImpl.bpmBusinessRFloxConfig.

Solution

To validate the EUM model and check for corruption, access http://<Gateway_Server>:29000 Topaz: service=EUM Administration Service at

java.lang.String validateEumModel enter

Customer id: 1

Eum Model: ALL

Full Model Scan: yes

Fix Model If Needed: no (Note: NEVER EVER use yes here!)

and click Invoke

If the result is

Result value: Bpm Model Validation

====================

BPM Model is VALID

Rum Model Validation

====================

RUM Model is VALID

General Model Validation

========================

General Settings are VALID

All is fine and no action is required here.

If however some corruption or inconsistencies are reported, for example

Bpm Model Validation

==================

0 point to non existing BusinessTransaction CI Id=d269fad1964abbd34b018bba8002ef1e

Error in BPM Model validation. method:public void com.mercury.am.eum.bpm.validator.BpmModelValidator.visit(com.mercury.am.eum.bpm.model.BpmTx)

bpm_script is linked to an agent and btf that does not have monitoring params bean. scriptId=2308 BTF, it=2eece0f6f19804fe2ecaff0b67d8179b agentId=71

or

# bpm_script is linked to an agent and btf that does not have monitoring params bean. scriptId=274 BtfId=4e37ca26556697199314f1f9ec91479b agentId=73# ===>: Record missing in EUMBPM_AGENT_BTF_CONFIG for the script in EUMBPM_SCRIPTS. scriptId=274 BtfId=4e37ca26556697199314f1f9ec91479b agentId=73

or

bpm_agent configured to non-existing Location: agentId=67 locationId=5cd5f6983b565decea795846694524fe hostKey=147.214.38.220 name=EV002481F48850_1(the exact output depends on the type of corruption and the BSM/APM version)

Support / CPE / R&D needs to be involved in fixing the issue.

Note

Don’t be creative and try fixing the issue on your own, always involve CPE / R&D for assistance!

Yes, some things could be fixed without help from CPE / R&D, but if something is done wrong,

there is a high chance that the corruption will be bigger afterwards!

Data to be provided when opening a case with Support / CPE / R&D:

output from validateEumModel as shown above via http://<Gateway_Server>:29000 -> Topaz:service=EUM Administration Service -> validateEumModel data from the following databases and tables, exported in Excel format with headers.

RTSM database

select * FROM CDM_BUSINESS_TRANSACTION_1

select * FROM CDM_BUSINESS_APPLICATION_1

select * FROM CDM_BUSINESS_TRAN_1008487667

select * FROM CDM_LOCATION_1

Management database

SELECT * FROM EUMBPM_SCRIPTS

SELECT * FROM EUMBPM_BTFS

SELECT * FROM EUMBPM_TRANS

SELECT * FROM EUMBPM_TRANS_SCRIPTS

SELECT * FROM EUMBPM_APPLICATIONS

SELECT * FROM EUMBPM_AGENT_JOBS

SELECT * FROM EUMBPM_BTF_AGENT_CONFIG

SELECT * FROM EUMBPM_AGENT_BTF_CONFIG

SELECT * FROM EUMBPM_AGENT_BTF_SCHEDS

SELECT * FROM EUMBPM_SCHEDS

SELECT * FROM EUMBPM_WTS

SELECT * FROM EUMBPM_SINGLE_URLS

SELECT * FROM EUMBPM_AGENTS

SELECT * FROM EUMBPM_BTF_LOC

SELECT * FROM EUMBPM_CLIENT_DEVICE

SELECT * FROM EUMBPM_CLIENT_OS

SELECT * FROM EUMBPM_HOSTS

SELECT * FROM EUMBPM_LAT

SELECT * FROM EUMBPM_PROPERTIES

SELECT * FROM EUMBPM_SCRIPT_PARAMS

SELECT * FROM EUMBPM_SCRIPT_PARAMS_OV

SELECT * FROM EUM_360_LICENSE

Profile database

select * from BPM_AGENTS_DIM  

select * from APPLICATIONS_DIM 

select * from LOCATIONS_DIM  

select * from SCRIPTS_DIM  

select * from TRANSACTIONS_DIM

select * from BPM_AGENTS_DIM 

A screenshot of the issue Java Console output loggrabber filesets from all serversbCPE / R&D usually comes back with a list of SQL statements which need to be executed to fix the issue.

5. How to turn on JVM GC (Garbage Collection) logs in ALM

Summary

JVM heap consumption needs to be checked from time to time so to understand the levels of heap consumption as well the garbage collection. It is valuable in some cases to understand this.

Solution

Now we will follow some steps for checking the JVM heap consumption.

Step 1: Check the wrapper.conf file for editing, typically located in the given path: Windows: <drive>\ProgramData\Micro Focus\ALM\wrapper

Linux: /var/opt/ALM/wrapper

Step 2: Add a JVM Option… and specify a unique integer for the JVM number and specify an existing path, specify a file name.

For example, 36 is used…

wrapper.java.additional.36=-Xloggc:”D:/ProgramData/Micro Focus/ALM/log/GCLogs.txt”

Step 3: Start.36anges

Step 4: Restart the service (ALM/AgM/Octane)

Note: Each time the service is restarted the old GC log will be deleted and a new file created.

To read the GC log use GC Viewer which is free from here: https://github.com/chewiebug/GCViewer/wiki/Changelog

6. APM 9.51 – SLA availability measurement is not correct

Summary

Do you know APM 9.51 – SLA availability measurement is not correct?

Customers tried to create an SLA ( Clarion_Door(1) ) using configuration “breakdown by location” and with KPI Settings Cluster Availability for levels level “Service Level Agreement”, “Business Service” and “Business Application” and to “Group Average Value” to all KPIs below (see attachment .doc).

But the SLA that is delivered for June 2020 looks incorrect while location availability has values 99,081 % and 99,133 % for Group Average Value it delivers 98,345 % for the next higher (Cluster Availability) levels. The question is now why Cluster Availability value is 98,345, while the 2 location values below are 99,081 % and 99,133 % (it should be higher than 99 % somewhere around 99,179%).

Solution

The Cluster Availability rule calculates the availability of a cluster. A cluster is available when a defined, minimum number of child CIs reaches an availability threshold. This rule has a calculation cycle that is set by default to five minutes.

The rule calculates results in “buckets” of 5 minutes. Each “bucket” is considered available or not available based on the rule parameters, then the entire hour is aggregated to give an availability percentage. That value is then compared with the thresholds to determine KPI status.

Note: You can use this rule only when child CIs use the time-based calculation method (that is, their calculation method cannot be sample-based).

This is a KPI calculation rule. For details, see KPI Calculation Rules.

Example:

Suppose you want to build an SLA that reports downtime for tasks in a value chain service (needed to perform a Use Case). Service Level Management should report downtime if the chain is broken. If an application is down, the chain is broken. However, if two applications are down simultaneously, downtime is not doubled. There are five applications in the chain.

You create an SLA and set objectives for an Availability KPI so that the Minimum number of children should equal the total number of tasks. For each calculation cycle (five minutes), if one of the children fails (that is, its result is less than the value in the Availability threshold field), the group CI is considered unavailable during this cycle.

If we go by this explanation, the downtime gets affected when any of the entities under application is down. If the two entities under Clarion_door are down at different times, those will accumulate. However, if they are down simultaneously, their downtimes will not get doubled.

For instance if entity A is down for 7 minutes in a day and entity B was down for 5 minutes in a day. If both these downtimes occurred at different timings, cluster availability will show that application was down for 12 mins. However, if there was an overlap of 2 mins (meaning A&B were down at same time for 2 mins in the day), cluster availability will show a downtime of 10 mins.

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

Summary

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

Solution

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)

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

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.

Linux

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

Windows

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

Depending on the Tomcat version, this command might work as well:

<tomcat-install>\bin\version.bat / version.sh

examples:

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, 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, follow the below written command.

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

8. BSM – Missing pages in Business Service Management

Summary

This document describes possible causes for missing pages in BSM or MyBSM, the error messages received and steps for resolving the issue are included.

Problem

When there is a problem with loading pages in MyBSM or BSM – the uim.log on the BSM Gateway server has to be checked.

2014-01-14 17:25:24,416 [http-0.0.0.0-8080-1] (DataLoaderImpl.java:237) ERROR – Automatic data loading has failed

2014-01-14 17:26:36,909 [http-0.0.0.0-8080-2] (DataLoaderUtils.java:89) ERROR – The file bsmGrapherComponentDefinitions_2014-01-13_10-15-46.uim.xml could not be moved to directory C:\HPBSM\conf\uimashup\import\loaded\Components

2014-01-13 10:15:48,065 [main] (DataLoaderImpl.java:237) ERROR – Automatic data loading has failed

com.hp.bsm.uim.dataloader.DataLoaderException: Load pages data from XML files has errors.

at com.hp.bsm.uim.dataloader.util.DataLoaderUtils.loadPages(DataLoaderUtils.java:447)

at com.hp.bsm.uim.dataloader.DataLoaderImpl.loadPagesData(DataLoaderImpl.java:226)

at com.hp.bsm.uim.dataloader.DataLoaderImpl.loadAllData(DataLoaderImpl.java:192)

at com.hp.bsm.uim.dataloader.DataLoaderImpl.start(DataLoaderImpl.java:

Caused by: java.lang.Exception: Failed to load object from file (fileName=C:\HPBSM\conf\uimashup\import\toload\Pages\SiteScopePagesDefinitions.uim.xml)

..

2014-01-13 19:18:27,269 [main] (DataLoaderEnvironment.java:52) ERROR – Data Loader configuration problem: missing Pages ‘toload’ directory

..

2014-01-14 12:40:38,551 [http-0.0.0.0-8080-2] (DataLoaderUtils.java:89) ERROR – The file omiEvents_2014-01-13_10-15-46.uim.xml could not be moved to directory C:\HPBSM\conf\uimashup\import\loaded\Events

2014-01-14 12:41:08,474 [http-0.0.0.0-8080-1] (DataLoaderUtils.java:89) ERROR – The file bsmGrapherComponentDefinitions_2013-11-02_14-23-29.uim.xml could not be moved to directory C:\HPBSM\conf\uimashup\import\loaded\Components

..

2014-01-14 17:25:23,887 [http-0.0.0.0-8080-1] (DataLoaderUtils.java:89) ERROR – The file bsmGrapherComponentDefinitions_2014-01-13_10-15-46.uim.xml could not be moved to directory C:\HPBSM\conf\uimashup\import\loaded\Components

The following error messages can be found in the uim.log on the Gateway server:

com.hp.bsm.uim.dataloader.DataLoaderException: Load components galleries from XML files has errors.

at com.hp.bsm.uim.dataloader.util.DataLoaderUtils.loadComponentsGallery(DataLoaderUtils.java:191)

at com.hp.bsm.uim.dataloader.DataLoaderImpl.loadComponentsGallery(DataLoaderImpl.java:210)

at com.hp.bsm.uim.dataloader.DataLoaderImpl.loadComponentsGallery(DataLoaderImpl.java:201)

at com.hp.bsm.uim.dataloader.DataLoaderImpl.loadAllData(DataLoaderImpl.java:191)

at com.hp.bsm.uim.dataloader.DataLoaderImpl.start(DataLoaderImpl.java:235)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at java.lang.Thread.run(Thread.java:744)

Caused by: java.lang.Exception: The file bsmGrapherComponentDefinitions_2014-01-13_10-15-46.uim.xml could not be moved to directory C:\HPBSM\conf\uimashup\import\loaded\Components

at com.hp.bsm.uim.dataloader.DataLoaderException.<init>(DataLoaderException.java:62)

..

The cause is corruption in the XML files. Corruption in the UIM pages table in BSM database.

The issue can be resolved by following Step 1 or Step 2:

STEP 1: Backup HPBSM\conf\uimashup\import\loaded

Copy HPBSM\conf\uimashup\import\loaded

Paste to HPBSM\conf\uimashup\import\toload

Go to the JMX console http://<gatewayserver>:8080/jmx-console

Under foundation, click on service=UIMDataLoader

Invoke the method: boolean loadAllData() with customerId 1

If the above fails, the probable reasons for reloading pages fails: There is corruption in the UIM pages table – such as duplicated page names. HPBSM\conf\uimashup\import\loaded has two of the same files – delete duplicate files in the \conf\uimashup\import\loaded folder

STEP 2:

Use this as the last option, because it will delete custom pages that you need to recreate them. If you do not have any custom pages, nothing to worry about.

Backup \conf\uimashup\import\loaded

1a. Remove duplicate entries in the \conf\uimashup\import\loaded folder

Copy HPBSM\conf\uimashup\import\loaded

Paste to HPBSM\conf\uimashup\import\toload

Execute the following statement against the BSM Management database and save content of it:

SELECT * from UIM_PAGES order by name

Delete entire content of UIM_PAGES table with following command: delete from UIM_PAGES

Go to the GW JMX console.

Under foundation, click on service=UIMDataLoader

Execute function void start () – this function will load all UI Mashup metadata and data XML files on start and will upload all the out of box pages cleanly.

However, the above procedure will delete all the custom pages which are created, as a result of that any custom page that has been created by the customer needs to be recreated.

This will be a good start for any BSM pages corruption, if there is corruption in Events and Components, we need the same thing for Events and Components.

Finally, after these steps, if there is still an issue, there is probably a corruption in Database tables or missing Database permissions.

9. APM 9.40 ignores Open Token Identity Management Logout URL defined settings

Summary

APM 9.40 ignores Open Token Identity Management Logout URL defined settings. We have tried using both relative paths and fully qualified URLs. By pressing logout, it does not redirect you to the defined Logout URL in the Identity Management settings. Logout Sequence captured via Web Debugger:

/topaz/framework/top_logout_helper.jsp

/topaz/personalize.do?event=persistContexts

/topaz/TopazSiteServlet?requestType=logout&goto=%2Ftopaz%2Flogout.jsp

Using the OpenToken IDM.

Solution

Here we can use open token,but it is not certified with APM.There is an ER in IDEA  https://community.softwaregrp.com/t5/Operations-Bridge-Idea-Exchange/Support-OpenToken-IDM-in-APM/idi-p/1659672

The APM product manager has reviewed the request and informed that the requested (ER) is being considered but not on the near-term roadmap.

Workaround:

Modify the file <APM>/AppServer/webapps/site.war/framework/top_logout.jsp

After the following line://CSRF token include

topLogoutHelperURL = CsrfHelper.addCsrfTokenToUrl(request, topLogoutHelperURL);

inserted:

//Modified by to support SSO

topLogoutHelperURL = getBaseURI(request)+”logout.jsp#friendlyLogout”;

topLogoutHelperURL = CsrfHelper.addCsrfTokenToUrl(request, topLogoutHelperURL);

topLogoutHelperURL = “https:///unprotect/logout/logout.asp?target=”+topLogoutHelperURL;

//Mod END

==============

10. APM 9.40 and later- After upgrade GW Server – BSM_DT Service is not available

Summary

APM 9.40 and later- After upgrade GW Server – BSM_DT Service is not available

Environment:

APM 9.40 on Red Hat Enterprise Linux Server release 6.9 (Santiago), 2 GW & 2 DPS

(seen on APM 9.50 and 9.51 as well) Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 

The upgrade from APM 9.30 to APM 9.40 has been performed according to the upgrade guide.

It was a direct upgrade and in general the upgrade procedure seemed to be successful.There were no errors during upgrade, except a known issue which is also mentioned within the upgrade guide.

During tests it has been noticed that the samples from the BPM data collector instances not getting processed unless the BSM_DT Service has been restarted manually via JMX:

Below error on the Gateway server corresponds to the same issue:

BSM_DT Service is not available (Normal during Service startup)

< date / time > [ajp-bio-127.0.0.1-8010-exec-5] (DTLModelLoader.java:73) ERROR – Failed to invoke get Cache.

com.mercury.am.platform.controller.ServiceNotAvailableException: java.rmi.ConnectException: Connection refused to host: ;

nested exception is: java.net.ConnectException: Connection refused

At the same time BPM logs show

< date / time > ERROR [SampleSenderThread (Site1)] [SamplesSenderThread] The BSM (URL: http://<APM_GW>) has returned unexpected response while attempting to send the samples: 400 Bad Request

The BSM_DT service can be restarted by the use of the following steps.

Step 1: Use your favorite browser access on the Gateway server http:://localhost:29000 Topaz: service=DowntimeServiceLauncher.

Step 2: Go to void stop.

Step 3: Click Invoke and wait 2 minutes.

Step 4: Check BSM Status to verify that BSM_DT under HAC Status is STOPPED.

Step 5: Repeat step 3.

Step 6: Check BSM Status to verify that BSM_DT under HAC Status is RUNNING.

Step 7: Then check if the error in the log is gone or not.

Following these steps will definitely solve your problem.

Solution

Here are the following steps for complete recovery: 

Step 1: Stop APM (GW first, then failover DPS (if available), then primary DPS) from APM Management DB clean all HA tables (as documented in the Disaster Recovery.

Step 2: Check procedure in the APM documentation from APM Management DB table PROPERTIES.

Step 3: Go to the BUS cluster information (as documented in the Disaster Recovery) and cleanup Procedure in the APM documentation).

Step 4: Clean up the folder <HPSM>\HornetQ\data on all servers.

Step 5: Execute the Configuration Wizard on all servers, primary DPS first, then failover DPS (if available).

Step 6: Go to GMW and start APM (primary DPS first, then failover DPS (if available), then GWs).

However, running the Configuration Wizard led to the famous RTSM master key corruption, so that ODB does not start anymore.

The workaround documented in KM03244356 had to be applied, which enabled APM to work again.

Note:

It seems that the issue is seen mainly in environments that have been updated from APM 9.30.