Micro Focus Application Performance Management – Tips And Tricks

Table of Contents

3. Application Performance Management – Tips And Tricks – Feb 2021

1. SiteScope / OBM – error “No trusted certificate found” in SiteScope’s error.log error

The user face an error <date/time> [com.mercury.sitescope.integrations.bac.reporter.GuaranteedBusReporter[pue01vm0150.mydomain.myorg][CacheSender]] (ApacheHttpUtils.java:512) ERROR while sending the data to the URL: https://pue01vm0150.mydomain.myorg:443/ext/mod_mdrv_wrap.dll?type=wde_bin_handler&message_subject=topaz_report/samples, host: pue01vm0150.mydomain.myorg, port: 443, UsingProxy: false, isHTTPS(SSL): true, javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found.

While running SiteScope 11.92 on Windows via HTTPS

Integrated with OBM 2020.05 on Windows running via HTTPS in <SiteScope>\logs\error.log the user can see the following entries over and over again:

<date/time> [com.mercury.sitescope.integrations.bac.reporter.GuaranteedBusReporter[pue01vm0150.mydomain.myorg][CacheSender]] (ApacheHttpUtils.java:512) ERROR – problem while sending data to URL: https://pue01vm0150.mydomain.myorg:443/ext/mod_mdrv_wrap.dll?type=wde_bin_handler&message_subject=topaz_report/samples error:  URL: https://pue01vm0150.mydomain.myorg:443/ext/mod_mdrv_wrap.dll?type=wde_bin_handler&message_subject=topaz_report/samples, host: pue01vm0150.mydomain.myorg, port: 443, UsingProxy: false, isHTTPS(SSL): true, javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found, currentRetry: 0

The message on the screen: No trusted certificate found indicates SiteScope is unable to find a trusted certificate for “pue01vm0150.mydomain.myorg.net”.

To fix the issue following steps must be followed

  • Go to SiteScopy GUI -> Preferences -> Certificate Preferences.
  • Click on the Star Symbol = Import Certificates
  • Under Source Selection enter the URL and Port Host: pue01vm0150.mydomain.myorg  Port: 443
  • Click to load.
  • Select the certificate SiteScope loaded.
  • Click for import.
  • The screen would show the message:  Import Complete

 Successfully imported 1 certificate(s)

After following the steps the certificate shows up in the list of certificates while the error in error.log doesn’t occur anymore.

2. APM 9.40 – LDAP Authentication is not working anymore after the LDAP configuration was deleted in error and had to be re-created Error

The user faces an issue in AMP 9.40 when the LDAP authentication stops working after LDAP configuration gets deleted and it has to be recreated. The same error occurs when the user updates the APM to 9.51 IP1. The error is observed for APM 9.40 on the windows 2012 version. The user authentication is done via LDAP and Active Directory.

By some mistake the APM LDAP profile for Active Directory Authentication has been deleted. The user re-create the profile from scratch but now AD users are not able to authenticate. APM users have been deleted the APM -> Platform-> Users and Permissions in order to let APM recreate the users but it still doesn’t work.

APM returns with the error message “Wrong username or Password” always. For the local users the APM Authentication is just fine. LDAP directory mapping and user listing is also working.

There is a different environment using APM 9.40 basically using the same LDAP configuration, which works perfectly fine. Neither normal nor debug logging provided enough information the users can only see is:

2020-11-19 14:09:30,563 [ajp-/127.0.0.1:8009-1] (IdmSsoUtils.java:44) DEBUG - isIdmSsoEnabled = false
2020-11-19 14:09:45,792 [ajp-/127.0.0.1:8009-1] (LDAPAuthenticationLoginHandler.java:56) DEBUG - InitParams was called for LDAPAuthenticationLoginHandler with params: 'OWASP_CSRFTOKEN=LH8H-YB84-2S0C-UC4O-7AJB-1DM6-LVEV-NG0X'.
2020-11-19 14:09:45,793 [ajp-/127.0.0.1:8009-1] (LoginHandler.java:310) DEBUG - Login for user sdudev in progress.
2020-11-19 14:09:45,794 [ajp-/127.0.0.1:8009-1] (LDAPAuthenticationStrategy.java:57) DEBUG - Handling request to authenticate using LDAP the following LDAPContext:sdudev
2020-11-19 14:09:45,800 [ajp-/127.0.0.1:8009-1] (LDAPAuthenticationStrategy.java:113) DEBUG - Handling request to authenticate using LDAP: try to find ldap domain by login name sdudev
2020-11-19 14:09:45,836 [ajp-/127.0.0.1:8009-1] (LoginHandler.java:760) ERROR - Can't authenticate user due to TMC error: Authentication Manager authentication failure The throne message is: Failed to authenticate user with uuid 'sdudev'' , Authentication Status: Authentication failed
2020-11-19 14:09:45,837 [ajp-/127.0.0.1:8009-1] (AuthenticationLoginHandlerAdapter.java:338) INFO  - Error while handling login request for user sdudev, redirecting to null.

As per the source code it seems that this either is not a plain LDAP issue, or no LDAP issue at all, but the code also tells that it is really difficult to get hold of the real issue. As the one part of the code doesn’t return a useful status upon failure and the developers need to use a trick to identify where the reason for an authentication issue is.

Due to this R&D created some debug bits to dump some LDAP-related fields into the log. As per usersynch.log it has been found that the display name is returned empty from LDAP: 2020-11-11 15:34:33,550 [ajp-/127.0.0.1:8009-1] (LDAPUtils.java:464) DEBUG – Found user ”, with uuid: sdudev

It turned out that this field was empty because the user authentication check failed, so the R&D started on a work around binary which uses a different field for verification. When it comes to this point of applying the bits the environment has been updated from APM 9.40 to APM 9.51 IP1.

Now LDAP has been configured exactly the same way as done on the other working environment which has been updated to APM 9.51 IP1 as well it fails still with the error: ERROR – Can’t authenticate user due to TMC error: Authentication Manager authentication failure The throne message is: Failed to create a new user for LDAP user:

The cause of the issue is that as the environment has been UPDATED from APM 9.40 to APM 9.51 IP1 the database used is still the same. On APM 9.40 the working LDAP configuration has been deleted in error, configuration has been added back in now it doesn’t work anymore.

There is an assumption that deleting the LDAP configuration resulted in some “leftover” entries somewhere in the configuration, which is kept in the database. When configuring LDAP again, these leftover entries are not corrected, overwritten or deleted, as it might be required.

To fix the issue the following steps are performed:

  • Stop APM, GW first, and then DPS.
  • Create a back copy of the APM Management database table in: SETTINGS_PARAMETERS
  • Delete * from SETTING_PARAMETERS where sp_context = ‘LdapGlobalSettings’.
  • Start APM first DPS and then GW
  • Configure LPAP via the GUI as did before.
  • Check the behaviour
  • On a test system running APM 9.40 LDAP has been set up, and deleted.
  • When checking the table in SETTING_PARAMETERS afterwards, the user can still find some entries related to LDAP entries: SELECT SP_CONTEXT,SP_NAME, SP_VALUE from SETTING_PARAMETERS where sp_context=’LdapGlobalSettings’
SP_CONTEXT      SP_NAME                  SP_VALUE LdapGlobalSettings  ldap.enable.user.sync    true
LdapGlobalSettings  ldap.settings.internalLogin  true
  • On other systems where the LDAP never configured, there are no entries for: SELECT SP_CONTEXT,SP_NAME, SP_VALUE from SETTING_PARAMETERS where sp_context=’LdapGlobalSettings’ at all.
  • The users after performing the above steps found four entries of LDAP in the database table after they have deleted the LDAP configuration.
  • The user didn’t keep the count of these entries so there is no explanation about what they were additional to:
LdapGlobalSettings  ldap.enable.user.sync    true
LdapGlobalSettings  ldap.settings.internalLogin  true
  • The four entries were deleted while the LDAP configured again and now the authentication works again.
  • The user clarified that deleting the LDAP-related “leftover entries” from the database table has been done on APM 9.40 multiple times, but did not resolve the issue at that time.

3. BPM 9.53 – BPM environments upgraded from 9.51 to 9.53 still show up with version 9.51 in APM EUM Settings Error

BPM environments upgraded from 9.51 to 9.53 still show up with version 9.51 in APM EUM Settings while the same issue occurs for BPM 9.53 on windows.

BPM on two systems have been upgraded from version 9.51 to version 9.53 but in APM -> EUM settings they are still displayed in 9.51. The updating of the code is fine and this is also reflected in the BPM Admin GUI under Help -> About Business Process Monitor

Business Process Monitor

9.53.91 | Build 298

The list under Admin -> End User Management -> Settings is supposed to reflect the version of BMP active on the BMP server. There might be a delay of some minutes after the user have updated BPM, but in general the information should be in sync. Support this tested with a BPM 9.53 on Windows instance, and connected it to an APM 9.40 instance, and all is fine, the version returned by BPM is the same as seen in Admin -> End User Management -> Settings. When the version is change in <BPM>\config\topaz_agent_ctrl.cfg (for example C:\ProgramData\MF\BPM\config\topaz_agent_ctrl.cfg from:

HostVersion=9.53
BuildNum=298
..

to

..
HostVersion=9.54
BuildNum=198
..

Save the file, restart BMP and refresh Admin -> End User Management -> Settings it shows 9.54. The file \topaz_agent_ctrl.cfg is getting updated at the end of the installation, so this is obvious that something went wrong. Checked the szenario with R&D, they tested various setups, but all worked as expected,in all cases the BPM version is displayed as 9.53 in APM -> EUM settings. When the user verified the file topaz_agent_ctrl.cfg of the system showing the issue after the update, as suspected it shows: [General]

Workspace=C:\ProgramData\MF\BPM\workspace

SelfUrl=http://10.182.55.206:2696

HostVersion=9.51

BuildNum=150

As workaround the user can manually modify the file <BPM>\config\topaz_agent_ctrl.cfg and change

  HostVersion=9.53

  BuildNum=298 as shown above and restart BPM, then APM shows the correct version, but the cause of the issue is still unclear.

When checking the log

  BPM_9.53_MicroFocusOvInstaller.txt

Shows:

2020-11-04 16:03:07,561 INFO - Executing finalize action : Running post-install script...
2020-11-04 16:03:23,905 INFO - The script C:\windows\System32\cmd.exe /c C:\Users\SVC_CO~1\AppData\Local\Temp\BPM\postinstall_bpm.bat SWING C:\Users\SVC_CO~1\AppData\Local\Temp\BPM  has returned a value of 0
..
2020-11-04 16:03:44,218 INFO - installation of Micro Focus Business Process Monitor 9.53 has taken 3 minutes and 7 seconds.

The most interesting part however can be found in installation\logs\bpm_post_install.log,

it shows a failure when trying to update the configuration file(s):

..
04/11/2020 16:03:20 INFO  [pool-3-thread-1] [BPMConfigUpgrader] Trying to parse [topaz_agent_ctrl.cfg] file
04/11/2020 16:03:20 INFO  [pool-3-thread-1] [BPMConfigUpgrader] Configuration file [topaz_agent_ctrl.cfg] parsed
..
04/11/2020 16:03:20 INFO  [pool-3-thread-1] [BPMConfigUpgrader] Config version is [9.51]
04/11/2020 16:03:20 INFO  [pool-3-thread-1] [BPMConfigUpgrader] Trying to execute update flow. version is [9.51]
04/11/2020 16:03:20 ERROR [AWT-EventQueue-0] [BpmConfigWizardFinish] An error occurred while trying to apply config.
java.util.concurrent.ExecutionException: java.lang.NullPointerException
   ..
Caused by: java.lang.NullPointerException
at com.mercury.topaz.agent.install.upgrader.BPMConfigUpgrader.executeUpgradeFlow(BPMConfigUpgrader.java:319) ~[bpm_install.jar:?]
   ..
It seems the update fails where it tries to read data out of the file topaz_agent_ctrl.cfg
  ..
  if(section.getName().contains(BpmConfigConstants.SITE)){
(line 319) -> String siteUrl = section.getParameter(com.hp.bsm.bpm.configuration.BpmConfigConstants.TopazAgentCtrl.Property.SiteUrl.toString()).getValue();  but still the file appears to be fine.

This would explain that an update from BPM 9.51 to 9.53 still shows up as BPM 9.51.

To fix the problem the following solution is accessible:

  • Restart prior to the update -> no change
  • Disable the AV software while installation   -> no change
  • Manually executed the post_intall.bat file from the <BPM_dir>\installation\bin directory with AV software stopped -> same error in the log.
  • Downloaded the installation bits again to rule out corruption -> no change
  • What finally work is:
  • Stop BPM
  • Run the post_install script
  • Instead of selecting “Yes, I want to keep all the current settings” select “No, I want to reconfigure the agent settings” and enter all the required parameters.
  • Restart the BPM
  • Now the BPM version is shown as 9.53 in APM -> Admin -> End User Management -> Setting
  • This creates a new file topaz_agent_ctrl.cfg.

4. APM 9.50 – Unable to login to APM with IE since the update Error

The issue that users face while trying to login to APM with the IE update is caused by Dynatrace OneAgent JS injection in APM 9.50. Since the upgrade of the pre-prod environment to APM 9.50, practically all the time people get in a logon page loop when submitting valid credentials.

Rarely, they get through it but sometimes their session gets ejected rapidly. The only way to login is with Chrome but no java applets there, so missing all the functionality they need or some local portable version of FireFox ESR 52.9.0 that can be assembled by themselves. The users refuse to validate this set up and this is a showstopper to move on with the PRD upgrade.

The solution to the issue is given in the below steps:

  • Prior to the update to APM 9.50 the user also started a proof of concept test with Dynatrace and had an OneAgent on that APM platform.
  • The proof of concept tests are long finished but they never got to clean up that agent, which the user just did today and with that, the system works all fine.
  • The user may extend their KB with the knowledge that a Dynatrace OneAgent JS injection can harm the APM JS code from the login page.
  • So if there is any such similar case in the future the user must always ask them if they have a Dynatrace agent installed.

5. APM 9.50 – after update from 9.30, CI Health Status is not getting updated in SH views Error

APM 9.50 after updating from 9.30 the CI Health Status is not getting updated in SH views. APM 9.50 after update from 9.30, CI Health Status is not getting updated in SH views. The user has recently upgraded from APM9.30 to APM 9.50 and found that the CI status is not getting updated in the service health views and status displays as ‘Not up to date’. All the prereqs were taken care of before the upgrade and the user does not have any custom views on the dashboards or the custom CI status alerts configured.

The below steps would help to fix the problem:

  • Stop IIS web server if using embedded Apache webserver please proceed to step 2.
  •  Stop BSM Gateway servers
  • Stop Failover DPS server
  • Stop Primary DPS server
  • Ensure no services are left running
  • Post Install.
    • Run postinstall.sh executable on Primary DPS
    • Run postinstall.sh executable on Failover DPS
    • Run postinstall.sh executable on Gateway servers.
  • Configuration Wizard
    • Run Configuration Wizard on Primary DPS
    • Run Configuration Wizard on Failover DPS
    • Run Configuration Wizard on Gateway servers
  • Start Primary DPS
  • Start Failover DPS
  • Start Gateway servers
  • Start IIS Web Server if using embedded Apache web server ignore this step.

6. APM / SiteScope – SAM menu is missing although a SAM license is enabled error

The user observes that APM / SiteScope – SAM menu is missing although a SAM license is enabled. SAM Menu is missing even though the user got the SAM license enabled. SAM is also enabled in Server Deployment.

The solution to fix the issue is given below:

  • DPS server was not aligned.
  • That is the reason the SAM Menu did not show.
  • After restarting the whole environment GWs and all DPS the servers were aligned, and the SAM menu showed up.

7. SiteScope 11.40 / APM 9.40 – SiteScope cannot sync topology to APM 9.40 error

SiteScope 11.40 / APM 9.40 – SiteScope cannot sync topology to APM 9.40. APM 9.30 has been upgraded to APM 9.40 while SiteScope 11.40. Integrating SiteScope with APM works fine, however SiteScope is unable to synchronize topology with APM. <SiteScope>\log\discovery.log shows:

2017-10-04 12:53:02,176 [AsyncConfigurationSender] (DiscoveryClient.java:785) ERROR - Error Downloading domain scope from server. the server responce:
B Server</title>    <link rel="stylesheet" type="text/css" href="./ucmdb-ui/static/act/stylesheets/login_hp.css"/>    <link rel="stylesheet" type="text/css" href="./ucmdb-ui/static/act/stylesheets/Properties.css"/> <link rel="stylesheet" type="text/css" href="./ucmdb-ui/static/CMS/css/CMSGeneralStyle.css"/> <meta http-equiv="Content-type" content="text/html;charset=UTF-8" />   <meta http-equiv="cache-control" content="no-cache"> <meta http-equiv="pragma" content="no-cache">   <meta http-equiv="expires" content="-1"></head><body class="login_hp"><table class="full_HV" width="180" border="0" cellspacing="0" cellpadding="0"> <tr>   <td class="login_top_left" colspan="2">          <table class="full_HV" border="0" cellspacing="0" cellpadding="0">            <tr>            <td class="login_logo">                <div class="combo" dir="ltr">                          <img src="./ucmdb-ui/static/CMS/images/login/login_logo.gif" alt='' border='0'>                </div>            </td>              <td/>              </tr>          <tr>            <td/>                  <td class="login_appname">                    <div class="version">HPE Universal CMDB 10.32 <br/>                  <!--DO NOT REMOVE THIS LINE--><!--UCMDB_CUSTOM_TITLE-->                </div>                </td>              </tr>    </table>     </td> <td class="login_top_right">              <br/> </td>    </tr>     <tr valign="top"> <td colspan="3">          <div id="statusBox" class="bottomBox">              <table width="100%" height="100%" border="0" cellspacing="0" cellpadding="0">                <tr>                    <td class="login_mid_left"/>                      <td class="login_mid_center">                      <table border="0" cellspacing="0" cellpadding="0">                        <tr>                                  <td>                                  <strong>                                    <div id="statusBoxMessage">                                        <!--DO NOT REMOVE THIS LINE--><!--LICENSE_PLACEHOLDER-->                                      </div>                                      </strong>                              </td>                                 </tr>                          </table>                  </td>                        <td class="login_mid_right">                    <table class="full_H" border="0" cellspacing="0" cellpadding="0">                         <tr>                                  <td>      <ul class="list"><li><a href="./ucmdb-ui/">UCMDB</a></li><li><a href="./ucmdb-ui/cms/directAppletLogin.action?cmd=SetMode&ApplicationMode=USER_MANAGER&navigation=true&interfaceVersion=9.0.0">User Management</a></li><li><u style='color: #7F7F7F' title="UCMDB Configuration Manager is not installed">UCMDB Configuration Manager</u></li><li><a href="/ucmdb-browser">UCMDB Browser</a></li>                                      <!--<li><a href="./ucmdb-ui/loadClassModelJavadoc.jsp">UCMDB Class Model</a></li>--><li><a href="./status/">Server Status</a></li>       <li><a href="./jmx-console/">JMX Console</a></li>       <li><a href="./ucmdb-api/connect">API Connection Test</a></li>           <li><a href="./ucmdb-api/download">API Client Download</a></li>                                          <li><a href="./ucmdb-docs/docs/eng/APIs/UCMDB_JavaAPI/">API Reference</a></li>          </ul>                              </td>               
       </tr>                    </table>                      </td>              </tr>                  <tr>                  <td/><td/>                  <!-- TODO The strings has to be moved to resources   -->                <td class="copyright">                              <span>© Copyright 1998-2017  Hewlett Packard Enterprise Development LP</span>                    </td>                  </tr> </table>          </div>   </td>    </tr></table></body></html>

The folder <SiteScope> discovery, scripts, is empty except for the directory custom, which contains the file placeholder.txt only.  

The issue is known as QCCR1I125008 Discovery Scripts not getting downloaded in SiteScope 11.33 IP1. The error shows that the uCMDB server response is a login page. The cause of the issue is because mam-collectors servlet is configured as HTTPS but the probe uses HTTP. Starting with uCMDB version 10.30, by default the HTTPS protocol is enabled for UCMDB server, with the HTTP protocol being disabled. APM 9.40 comes with uCMDB version 10.32.130.

To fix the issue following steps are to be followed:

  • The user needs to set mam-collectors and cm servlet to HTTP.
  • Not a plain uCMDB server and a UD probe, but APM 9.40 with RTSM that is based on the uCMDB 10.32 and SiteScope 11.40, the steps are slightly different than described in the service request.
  • In <HPBSM>\odb\conf\settings.override.properties
    •  Change # jetty.connections.http.enabled=true
    •  To jetty.connections.http.enabled=true.
  • Then Save the file.
  • The above step is not required in all installations.
  • Access the UCMDB JMX console:
    •    https://<ucmdb machine name or IP address>:8443/jmx-console
  • Select the service: Ports Management Services.
  • Invoke the HTTPSetEnablemethod.
  • The result should be: Mbean: UCMDB:service=Ports Management Services. Method: HTTPSetEnable operation succeeded. Will take effect after restart.
  • Invoke the Ports Details method while ensuring that the value in the Enabled column for the HTTP protocol is True.
  • The result should be:
   Mbean: UCMDB:service=Ports Management Services. Method: PortsDetails
Port Protocol Port number Is Enabled
HTTP 21212 true
HTTPS 8443 true
HTTPS - Requires client authentication 8444 true
  • Return to the Ports Management Services.
  • To map the Data Flow Probe connector to server authentication mode, invoke the mapComponentToConnectors with the following method parameters: component Name: mam-collectors is HTTP: true

All other flags: false

The result should be:   Mbean: UCMDB:service=Ports Management Services. Method: mapComponentToConnectors

   Operation succeeded. Component mam-collectors is now mapped to: HTTP ports.

  • Return to Ports Management Services.
  • To map the Confidential Manager connector to server authentication mode, invoke the mapComponentToConnectors with the help of the following parameters: componentName: cm

    is HTTP: true

    All other flags: false

The result should be: Mbean: UCMDB:service=Ports Management Services. Method: mapComponentToConnectors operation succeeded. Component cm is now mapped to: HTTP ports.

  • If the user wants to use multiple authentication methods they must make sure that the ports used by each of them are checked and set them to true when mapping both cm and mam-collectors.
  • In <SiteScope>\discovery\discovery_agent.properties

   Change appilog.agent.probe.protocol to appilog.agent.probe.protocol=http and save the file. The line needs to be added as it might not exist. This step is not required in all installations.

  • Restart SiteScope
  • Restart APM
  • In a web browser access uCMDB Server / RTSM with HTTP protocol and port 8080, for example: http://<server name or IP address>.<domain name>:8080 where the <server name or IP address>.<domain name> represents the fully qualified domain name (FQDN) of the DPS.
  • After SiteScope and APM are up and running the user could see: 962 items in folder <SiteScope>\discovery\scripts\ more or less
  • No errors in the discovery.log
  • No error in bac_integration.log
  • To trigger the re-synchronisation the user might require a hard-Sync from SiteScope.
  • This is nothing that happens on all APM 9.40 installations.
  • It is observed that these combinations work without any problems: fresh APM 9.40 + fresh SiteScope 11.40 fresh APM 9.40 + SiteScope 11.40 with SiteScope being updated from SiteScope 11.33.
  • If these combinations fail then: APM 9.40 with APM being updated from APM 9.30 + SiteScope 11.40. APM 9.40 with APM being updated from APM 9.30 + SiteScope 11.40 with SiteScope being updated from SiteScope 11.33.
  • An easy way to resolve the issue is to access the APM GUI.
  • Go to Administration -> Platform -> Infrastructure Settings.
  • Select Foundations: RTSM.
  • Under RTSM – Web Components to Connectors Mapping Settings change the setting for CM Port Mapping Mam-Collectors Port Mapping from
  • “HTTP” to “HTTP,HTTPS”
  • After saving the changes restart the APM.
  • This enables APM to also listen to https traffic for CM and Mam.Collectors.

8. APM 9.40 – SLA Report shows “No SLAs exist for this Provider” error

The micro focus product for this purpose is application performance management (bac) 7.52. In APM 9.40 the user might face an error SLA Report shows “No SLAs exist for this Provider”. APM Performance Management -> Service Level Management -> SLA reports -> SLA Status all shows the message: “No SLAs exist for this provider”. However, when the user inquires about the database using other OOTB reports it shows it has collected the data for those time periods. The raw data reports show the data, but the status is not updated.

The solution to fix the issue is given below:

  • The issue is resolved by the use of hotfix.
  • The hotfix can be requested via Support.

9. APM 9.30 – DPS doesn’t start, fails with “The pre-init checks fail.” error

While using APM 9.30 the user may face an error DPS doesn’t start, fails with “The pre-init checks fail.” The users are running a 2 server environment with separate DPS and GW servers on Windows 2012 R2. Last week the customer rebooted the DPS server after applying 2 Windows patches and now the DPS won’t start.

They rebooted several times but there is no change. The wrapper.log shows messages about a wrapper jar file with the wrong version, but those messages go back a couple of years. There a message like: INFO

jvm 1
2019/01/15 11:45:19
Exception in thread "nanny Manager:Initialize Task" java.lang.RuntimeException: Could not finish the pre initialization hooks!INFO
jvm 1
2019/01/15 11:45:19
at com.mercury.infra.nanny.manager.Main$InitializeTask.preInitialize(Main.java:68)INFO
jvm 1
2019/01/15 11:45:19
at com.mercury.infra.nanny.manager.Main$InitializeTask.run(Main.java:112)INFO
jvm 1
2019/01/15 11:45:19
at java.lang.Thread.run(Thread.java:745)INFO
jvm 1
2019/01/15 11:45:19
Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to remote://127.0.0.1:9999. The connection failed

The customer ran a Windows netstat command but it does not show any issues with port 9999.

The solution to fix the issue is given below:

On DSP:

  • Delete JBOSS cache
  • Delete the following file <HPBSM>\jboss-as\modules\system\layers\base\com\hp\bsm\platform\main\modules.xml
  • Delete the <HPBSM>\HornetQ\data folder
  • Run Post-install
  • Run Configuration wizard

On GW server:

  • Delete JBOSS cache
  • Delete the following file <HPBSM>\jboss-as\modules\system\layers\base\com\hp\bsm\platform\main\modules.xml
  • Delete the <HPBSM>\HornetQ\data folder
  • Run Post-install
  • Run Configuration wizard

Later start DPS it works along with GW. Customers are able to log in to APM successfully and use APM once again.

10.            APM 9.30 / BPM – how to control / restrict access to the BPM GUI error

The user is running APM 9.30 on Linux. The user needs to restrict access to the BPM UI and still give access to certain users.

The user would like to be able to control this within APM, thereby using Active Directory groups. The customer is looking for a chance to restrict the users in APM so they can only use the “Business Process Monitor Agent’s Console” button under Admin > End User Management > Settings without giving them access to delete any BPM or cause any problems in APM.

The solution for the issue is given below:

  • To Restrict Access to BPM Console throughout URL.
  • To achieve this the customer will need to run BPM post install wizard
  • Stop BPM service
  • Navigate to C:/HP/BPM/installation/bin/
  • Look for postinstall.bat
  • Run postinstall.bat with Admin Rights
  • Select option, No, I want to reconfigure BPM settings
  • Follow steps until we reach out to BPM Authentication.
  • With this above step the user can setup BPM Server authentication but this authentication allows only one user and one credential. Meaning to access BPM Console throughout the URL the user will need to use the one and only user.
  • To restrict access to BPM Console throughout APM drill-down.
  • Since there is a lookout to have drill down blocked out strictly for certain users there must be a separate group of users in which some of them are allowed to drill-down while the other ones will not. For example: Administration > Platform > User Management > Users and Permissions. Here I have selected group Roles Testing Then continued to > Context End User Management > BPM Agents > Roles and Operations.