Micro Focus Application Performance Management (APM) Solutions allow you to isolate problems real-time for all of your applications whether on-premise, cloud, or mobile.
This post will have the monthly Micro Focus Service Manager Tips and Tricks which will be a consolidation of various common issues in Micro Focus Service Manager. Do check out this article for troubleshooting tips and tricks for other tools.
1. Application Performance Management – Tips And Tricks – Dec 2020
1. Retrieving the Apache Web Server/Tomcat/Java version
It often happens that we are unable to extract the Apache Web server. There is a solution available, it may seem technically difficult, but it is quite effective.
These are for the Apache Web Server Version
For the Linux version
/opt/HP/BSM/WebServer/bin/httpd -v
Server version: Apache/2.2.21 (Unix)
For the Windows version
<HPBSM>\WebServer\bin>httpd -v
Server version: Apache/2.2.21 (Win32)
Some other versions that are available:
- 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
Specifically for Tomcat and JVM Version
You need to initialise the commands given below from your device.
<application-install> or <tomcat-install> directory:
You need to make sure that if you don’t have your personal Java home directory in your path environment variable, then you must include this path to your <java-home>/bin directory in the java command.
In Linux Operating System
java -cp lib/catalina.jar org.apache.catalina.util.ServerInfo
In Windows Operating System
java.exe -cp lib\catalina.jar org.apache.catalina.util.ServerInfo
You need to check your Tomcat version because, in accordance with that, the command below might work as well:
<tomcat-install>\bin\version.bat / version.sh
Some common examples of this :
BPM 9.24 on Windows, installed into C:\BPM
Then you need to 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, will be directly installed into C:\HP\BPM
Then you must 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, will be directly installed into C:\MF\BPM
Then you need to 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, will be automatically installed into C:\SiteScope
Then you need to 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, it will be 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, this will be installed into C:\SiteScope
You need to 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.
You need to take notice that the JVM version returned will always depend on the system-wide setting of the 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
This is the JBoss and Tomcat version for the BSM.
For recollecting the JBoss version, you need to check the logfile.
<HPBSM>\log\jboss_boot.log
Then you need to look for this log below specifically:
INFO – Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)
The result above is particularly for BSM 9.25 IP1
To recollect the JBoss version, you need to check for this log file below carefully:
<RUM_Engine>\log\jboss_boot.log
Then particularly search for the line below:
INFO [AbstractServer] JBossAS [6.1.0.Final “Neo”] Started in 1m:39s:75ms
The above is precisely the result for RUM Engine 9.25.
This is particularly Tomcat for RUM ClientMonitor Probe.
ClientMonitor Probe 9.26, will be installed into C:\HPRUMClientMonitorProbe
Then you need to 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
This is the Tomcat version embedded in JBoss.
From the JBoss version 4.2 and upwards, all of this is bundled with Tomcat,
The only thing is that it will be a forked version of it, that is known as JBossWeb. It will be maintained individually, not dependent on the Tomcat codebase.
It is based on the specific JBoss version (the one here is 6.1.0) user can utilize the 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
2. How to resolve the missing pages error in Business Service Management
Sometimes there are few corrupted or missing pages in BSM or my BSM that cause an error. This problem can be solved by following the steps given below:
This is the fix 1
- You need to backup HPBSM\conf\uimashup\import\loaded
- You need to copy HPBSM\conf\uimashup\import\loaded
- And then paste to HPBSM\conf\uimashup\import\toload
- Then you simply need to go to the JMX console http://<gatewayserver>:8080/jmx-console
- Under the foundation, you need to click on service=UIMDataLoader
- Then you make sure to invoke the method: boolean loadAllData() with customerId 1
The fix above is quite popular and efficient, but in case that does not work it could be because the reloading of the pages failed due to some errors, to solve this you can use the fix given below:
It could be because there was some kind of corruption in the UIM pages table, like incorrect or a duplicate page name.
HPBSM\conf\uimashup\import\loaded could have two names of the same file. All you need to do is delete the duplicate files in the \conf\uimashup\import\loaded folder.
This is fix 2:
This fix better is used as a last resort as it often deletes custom pages that you will further need them to recreate. That is not the case for the users who do not have any custom pages, they don’t need to worry.
- You need to Backup \conf\uimashup\import\loaded
Then make sure to remove all the duplicate entries in the \conf\uimashup\import\loaded folder.
- Then you need to copy HPBSM\conf\uimashup\import\loaded
- And then paste to HPBSM\conf\uimashup\import\toload
- After that, you need to execute the statements given below against all of the BSM databases you have. Then make sure to save all of its contents.
You need to select* from UIM_PAGES order by name
- Then terminate or delete the entire content of UIM_PAGES table with the command given below:
delete from UIM_PAGES
- Then visit the GW JMX console.
- You will find Foundation, so under that, you need to click on service=UIMDataLoader
- Then you need to execute function void start() – this function is very crucial as it is responsible for loading all the UI mashup metadata and data XML files on Start. It also uploads all the out of box pages accurately.
As informed before this fix will remove all the custom data which could be a good and clean start for any BSM pages corruption.
3. Instructions to solve APM 9.40 not responding to Open Token Identity Management Logout URL defined settings
Sometimes it happens that the APM 9.40 version completely ignores the Open Token Identity Management Logout URL defined settings. It also fails to redirect the user to the defined logout URL in the Identity Management settings.
It is a well-known fact that Open Token is clearly not certified with APM. You will find an ER in IDEA.
Generally, the APM product manager has reviewed the request. It has also mentioned that the requested (ER) is contemplated but not really on the near-term roadmap.
You can follow the instructions given below to solve this issue:
You need modify the file given <APM>/AppServer/webapps/site.war/framework/top_logout.jsp
And after that:
//CSRF token include
topLogoutHelperURL = CsrfHelper.addCsrfTokenToUrl(request, topLogoutHelperURL);
Then 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
==============
4. When there is a “GW Server- BSM_DT service is not available” error on the screen
It often happens that the APM 9.40 version and later versions after the upgrade, GW Server –BSM_DT Service is not available.
- You need to stop APM.
GW should be the first one, then failover DPS (if available), and then the primary DPS.
- Then from APM management DB, you need to clean all HA tables.
Just the exact way it is documented in the Disaster Recovery- Cleanup Procedure in the APM documentation.
- Then from the APM Management DB table Properties, you need to delete the Bus cluster information.
Just the exact way it is documented in the Disaster Recovery- Cleanup Procedure in the APM documentation.
- Then you need to delete this folder: <HPSM>\HornetQ\data on all servers.
- Then you need to activate the Configuration Wizard on all the servers.
Primary should be the first one, then failover DPS (if applicable or available) and then the GWs.
It is noted that sometimes the Configuration Wizard was the cause for the RTSM master key corruption, hence ODB was unable to start at all. It is also observed that this issue is usually experienced when the system has been updated from APM 9.30.
5. When the APM application health would not allow special characters
Sometimes it happens that the special characters are not allowed to be inserted while creating an application. And that it was implemented with respective security reasons. And that it was implemented with respective security reasons. Usually, it happens with HTML pages that many special characters have been restricted due to security purposes. Usually, it happens with HTML pages that many special characters have been restricted due to security purposes. Characters given below are the ones that are restricted:
/ \ : * ? ‘ ” < > # % ˆ ( ) [ ] =
Then the user can use “{“ & “}” in the Application name.
6. Instructions to steer clear with the OBM/SiteScope – official versions against internal versions with the help of the cross-reference list
There is a huge debate about the Operation Bridge Manager (OBM)/ SiteScope, the official versions versus internal versions. Like the SiteScope 2020.10= 11.93 OBM, 2020.05= 11.0 CMDB. You can decide for yourself which one suits better and is best with the help of the cross-reference list.
In 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
In Operational Bridge Manager
- 2017.11 = 10.63
- 2018.02 = 10.64 + fixes (this only applies to the container version)
- 2018.05 = 10.70
- 2018.08 = 10.70 + fixes (this only applies to the container version)
- 2018.11 = 10.71
- 2019.02 = 10.72 + fixes (this only applies to the container version)
- 2019.05 = 10.80
- 2019.08 = 10.81 + fixes (this only applies to the container version)
- 2019.11 = 10.82
- 2020.05 = 11.00.010.011 (Also known as 11.0)
In 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
In 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
All these versions can be retrieved through the Graphic User Interface (GUI):
- You need to go to Help and then select About.
Just for instance, it shows:
SiteScope
2019.02 | Build: SiteScope 11.70.54 64-bit JVM, Build 67
Or
OBM
2018.11 | Build: 10.71.016.001
It also depends upon the individuality of the product, so there could also be a file which is already a part of the installation with the information.
For SiteScope
file <SiteScope_install_dir>\dat\version.txt
Product: HPE SiteScope
Version: 11.60.83
Build: 82
For 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
7. When integrating SiteScope version 11.33 IP3 with the APM 9.50 results in a failure
It often happens that there is an error while integrating SiteScope 11.33 IP3 with APM 9.50 most of the time. Many users have tried to harden the SiteScope 11.33 IP3 Patch with the self-signed cert. They also tried to integrate it with 9.50, it worked fine yet the console in SAM on APM 9.50 was not being able to launch. This problem is usually caused when one or more packages have not been upgraded accurately. You can solve this issue by following the steps given below:
- You need to open:
RTSM JMX console
default credentials are an admin.
- Then you need to go to UCMDB:service=Packaging Services – Packaging Services.
- Then you must find the Display Deployed packages.
- You need to check for the ODB packages that are to be listed. Then if you find them, then choose one for deploying.
- When the deploy procedure is finished, you have to redeploy them all.
After you are done redeploying, you may find a set of list of errors. You will also get a list of deployed packages; the ratio will be in favour of the Deployed packages.
The results will show, as mentioned below:
while – as expected – several deployments failed
******** operation has failed for 78 resources ********
many (the majority) worked
******** 3445 deployed resources : ********
After you have finished with all the procedures mentioned above, you need to remember to restart your APM environment.
8. When there are errors as reported by validateEumModel
It sometimes happens that validateEumModel reports an error or malfunctions. You need to validate the EUM model and then investigate for corruption or anything missing, access: