Unable to uninstall BPM version 7.x

Current version of BPM must be uninstalled before a new version can be installed.

The following things must be checked:

* Was the BPM restarted after the uninstall of the previous version?

* Find and rename the file called vpd.properties file and create an empty one.

Check if these three keys exist in the Windows registry and remove them, followed by a reboot of the BPM server:

HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\HP Business Process Monitor

HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\Mercury Business Process Monitor

Advertisements

How can OMi be helped to distinguish two CIs of the same type from each other when they both have identical names

Discovered topology does not help OMi to distinguish two CIs from each other because both CIs have identical names.

Users can configure CI resolution enrichment rules to enrich the CI resolution cache with additional keywords for a specific CI. These keywords are provided by another CI in their neighborhood. To enrich a CI, these steps can be followed:

1. Go to Admin -> Platform -> Infrastructure Settings – > Applications: Operations Management -> Operations Management – CI resolver Settings.

2. Modify the XML file under Cache Modification Configuration setting.

3. Add the Enrichment rule by adding a line like the one in bold before </CiResolver> after </IgnoreAttributes> tags as follows (in this particular case, jmsserver CI Types are enriched with the name attribute of related j2eedomain CI Types):

…..

<IgnoreAttribute>wmi_ntdomain</IgnoreAttribute>

</IgnoreAttributes>

<Enrichment>[jmsserver].from:composition.[j2eedomain].name</Enrichment>

</CiResolver>

4. Save the setting and allow CI Resolver some time to cache again CIs based on new setting.

Following the example of step number 3., enrichment modification will make an event with CI Hint in form jboss_server:<domain_name> to be resolved with the appropriate jmsserver CI.

How to test Sub Component property in OMi

If you want to test the Sub Component property in OMi and no data collectors are sending samples to OMi.

In order to facilitate the analysis, generation of events in OMi with customer attributes can be used.

Events with customer attributes can be generated in OMi by using sendEvent.bat tool with the -ca option.

Syntaxis has the following structure:

sendEvent.bat [-ca|-customAttribute <Name> <Value>]

HP UCMDB Data Flow Probe installation wizard launch “Server Configuration Problem” alert

HP Universal Configuration Management Database (UCMDB) Data Flow Probe (DFP) Configuration page of installation wizard might throw error "Server Configuration Problem", although the application server address is entered properly:

During the installation DFP tries to ping the application server address.

However, the ping might be forbidden due to peculiar company security policies. Therefore, the wizard evokes the aforementioned alert.

From the dialog simply select "Ignore" to continue.

Afterwards, the DFP status can be checked from "Data Flow Management" page within the BSM administration interface.

Error: “Missing index: annoToEventRefIdx in table: (table_name) in column: (Column_Name). This column already has an index with different name!”

Running the Upgrade Wizard on BSM 9.13 server the upgrade process stuck at Event schema upgrade and shows error (log upgrade):

"Missing index: annoToEventRefIdx in table: (table_name) in column: (Column_Name). This column already has an index with different name!"

More details:

2012-10-09 15:23:54,389 [pool-2-thread-1] (SimpleSqlStatement.java:40) ERROR – SQL Statement failed: Following sql statement failed:ALTER TABLE EVENT_FORWARDING_INFO ADD(ID VARCHAR2(255 CHAR)) — [mercury][Oracle
JDBC Driver][Oracle]ORA-01430: column being added already exists in table

2012-10-09 15:23:54,389 [pool-2-thread-1] (Step.java:96) ERROR – Task execution failed

com.mercury.infra.flowmngr.exceptions.TaskExecutionException: java.sql.SQLException: Following sql statement failed:ALTER TABLE EVENT_FORWARDING_INFO ADD(ID VARCHAR2(255 CHAR))

Caused by: java.sql.SQLException: Following sql statement failed:ALTER TABLE EVENT_FORWARDING_INFO ADD(ID VARCHAR2(255 CHAR))

Caused by: java.sql.SQLSyntaxErrorException: [mercury][Oracle JDBC Driver][Oracle]ORA-01430: column being added already exists in table

This issue happens, because before the upgrade be performed, the checkIndices.bat tool need be execute it, for check the changes in the Event DB.

The checkIndices.bat tool is located in, HPBSM\opr\support\checkIndices.bat

If this tool wasn’t execute in BSM 9.0x when the upgrade check the indices in the Event schema, this issue will show up because need the indices for continue working.

To fix this issue, please follow these steps:

1-) Run the CheckIndices.bat tool, in the command prompt with the parameter -v, like this:

HPBSM\opr\support>CheckIndices –v

This is for check what are the issues related to the indices in the Event schema.

After run this tool, you will see something like this, in case that the schema has issues.

BSM 9.x – Failed to create local impact view – how to increase the limit of 1000 CIs

BSM 9.x – Failed to create local impact view. To change the default limit of 1000 CIs to a higher number the following error message is shown:

Failed to create local impact view; the number of CIs exceeds the limit.

The default limit of the number of CIs in on LIV is 1000

This setting needs to be changed via JMX console, as the element is not visible in the Infrastructure Settings UI.

To change the limit:

http://<BSM_server>:8080/jmx-console

Go to

Foundations

service=Infrastructure Settings Manager

Execute

java.lang.String getCustomerSettingsDefaultValues()

contextName "liv-engine"

This reports the current settings:

Setting’s Name Setting’s value

liv.engine.maxLivsAmount 100

liv.engine.maxLivSize 1000

liv.engine.secondsBetweenTopologyPolling 5

liv.engine.successiveChangesBeforeRebuild 3

Now execute

void setSettingValuePerCustomerId()

contextName "liv-engine"

settingName "liv.engine.maxLivSize"

newValue 5000 (for example)

and verify the result:

java.lang.String getCustomerSettingsDefaultValues()

contextName "liv-engine"

It now should show

Setting’s Name Setting’s value

liv.engine.maxLivsAmount 100

liv.engine.maxLivSize 5000

liv.engine.secondsBetweenTopologyPolling 5

liv.engine.successiveChangesBeforeRebuild 3

Note:

Due to the additional calculations done with LIVs involved, it is NOT recommended to significantly increase this number

Log4j management web interface for Business Service Manager 9.2x

This article will help you to work easier with the log4j logging levels & log files, when performing troubleshooting in Business Service Manager (BSM) 9.2x

There is a tool with web interface called BSM Logging Administrator.

Its access URL is:

http://<BSM_IP>/topaz/removeCustAppender.jsp

One of the new useful functions is search. If you have a Java error message or exception, you can search for a specific appender name using the java class name that drops the error or info message.

Some of the log4j appender names correspond to the Java class names that they serve.

New custom log files can be created with the tool.

NOTE: Do not leave the DEBUG mode enable after the troubleshooting process!

Click on button “Back to Main Page” if it is visible and Search is not working.

If too many appenders are in DEBUG mode the HDD could get read/write overload and disk space issue.

Default folder for the log files is BSM/log/temp.