BAC/BSM – How to access the automatic login mechanism

In the Web browser, enter the following URL:

http://<server_name>/topaz/TopazSiteServlet?autologin=yes&strategyName=Topaz&requestType=login&userlogin=<loginname>&userpassword=<password>&createSession=true

where server_name represents the name of the BAC Center server, and login name and password represent the login name and password of a user defined in BAC/BSM.

This works (at least) from BAC 6.x up to BSM 9.20

Advertisements

BSM 9.20 – after upgrade from BSM 9.1x profile database size starts increasing

BSM 9.20 – after upgrade from BSM 9.1x profile database size starts increasing

With the update to BSM 9.20, some new tables for BPM and RUM have been added to the profile database:

Business Process Monitor

BPM_TRANS_3DAY

Aggregated transaction response time and availability data (daily) by transaction, script

BPM_TRANS_ERRS_3DAY

Daily extended transaction error information (transaction errors, transaction breakdown errors, transaction page component breakdown errors) by transaction, script

BPM_TRANS_3HR

Aggregated (hourly) transaction response time and availability data by transaction, script

BPM_TRANS_ERRS_3HR

Hourly extended transaction error information (transaction errors, transaction breakdown errors, transaction page component breakdown errors) by transaction, script

Real User Monitor

RUM_EVENTS_3DAY

Aggregated (daily by application, location) Real User Monitor Events data

RUM_EVENTS_3HR

Aggregated (hourly by application, location) Real User Monitor Events data

RUM_TRANSACTIONS_3DAY

Aggregated (daily) Real User Monitor transaction data by transaction

RUM_TRANSACTIONS_3HR

Aggregated (hourly) Real User Monitor transaction data by transaction

as these table have been added, the values for "Keep Data for" in

BSM -> Admin -> Platform -> Setup and Maintenance > Data Partitioning and Purging

are all set to the default, which is "INFINITE".

Modify the values for "Keep Data for" in

BSM -> Admin -> Platform -> Setup and Maintenance > Data Partitioning and Purging

for the new tables to reflect the same / similar settings as the old tables have.

Admin user has incorrect time, non-admin users show correct time

When logged in as ‘admin’ user the wrong time is displayed.

Regular users see correct Daylight Savings Time (DST).

For instance, the real time according to Daylight Savings Time right now is 5:27pm. If logged in as "admin" and run a report, current time as 4:27pm.

The admin user has been set to a different time zone.

To fix this Administrators can check the timezone of any user using the following query on the management database:

select * from USERS

In BSM 9.xx, you can change the timezone for any user by logging into BSM as your admin user and navigating to:

Admin->Platform->Users and Permissions->User Management

Once you click on a User in the left navigation pane, you should see a Time zone: setting in the General tab on the right:

Once you change the time zone of the user, this should be reflected in the query you are running in the BSM Management database:

select * from USERS

How to enable Cross VM on probes

Enable Corba cross-VM on both probes. In diagnostics 8.x we added cross-VM support for pure IIOP which covers RMI over IIOP as well.

Enable Corba Cross-VM by following the steps below on both the probes:

a) Disable RMI in the points file in auto_detect.points file ([RMI] active = false)

b) Enable the Corba points (there is a Corba section towards the end of the auto_detect.points file)

c) Read the documentation under [Corba cross-VM Documentation] section of the points file and follow ALL the steps listed there.

d) After doing all of the above, the "jvmEntries" should look something like below.

-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.mercury.opal.javaprobe.handler.corba.CorbaORBInitializer

and

<java-agent-install-dir>/lib/probeCorbaInterceptors.jar

No data is displayed for “IBM WebSphere” monitors in the Diagnostics tab

LoadRunner: 9.52 running on Windows 2003, HP Diagnostics: Version 8.0, WebSphere Commerce: 6.x on AIX.

Retrieving data for the "Stand Views" graphs in diagnostics is working fine, but nothing is displayed for the "IBM WebSphere" views.

Java 2 Security is NOT enabled. The HP Diagnostics Performance Monitoring Infrastructure (PMI) statistic sets are selected as Extended.

Checking the probe.log on the AIX machined shows the following WARN log:

2010-05-06 10:20:09,836 WARN com.mercury.diagnostics.capture.metrics [Metrics Collection] Error initializing com.mercury.diagnostics.capture.metrics.jmx.JMXCollector@ca1f548

java.lang.IllegalAccessError: com.mercury.diagnostics.capture.metrics.jmx.JMXCollector tried to access method com/mercury/diagnostics/capture/metrics/jmx/JMXCollector$AttributesAndDescriptors.add(Ljava/lang/String;Lcom/mercury/diagnostics/common/metrics/MetricDescriptor;)V

Invalid classpath configuration on the IBM Websphere – HP Diagnositcs boot loader on the AIX machine.

Check the Boot Classpath configuration in the WebSphere Admin Console and ensure it has all the correct entries.

In this case it should have read:

/opt/MercuryDiagnostics/JavaAgent/DiagnosticsAgent/classes/IBM/1.4.2__1:

/opt/MercuryDiagnostics/JavaAgent/DiagnosticsAgent/classes/boot

but it did not have the first entry (1.4.2__1)

How can a probe (Java Agent) be bound to a specific network interface (NIC)

If the Diagnostics Java Agent (probe) is installed on a server that has multiple network interfaces (NIC) and there is a requirement to ensure that all network communications between the probe and its Mediator server occurs via a specific NIC

To bind the Java Agent (probe) to a specific network interface, edit the probe configuration file:

<Diagnostics_probe_install>\etc\webserver.properties

and specify the host address the probe is to bind to using:

# Host address to bind to. Uncomment this and specify an IP address if

# the SUT has multiple interfaces, and only one should be responding to

# HTTP requests.

#jetty.listen.host = 0.0.0.0

Restart the probe to apply the new configuration.

Exception Signal 11 while starting Java probe with the WebSphere

Immediately upon starting the WebSphere application server with Diagnostics Probe, the JVM crashes. In the dump file from the crash, if "Exception Signal 11" is observed in WebSphere logs.

E.g.

JVMDG217: Dump Handler is Processing Signal 11 – Please Wait.

JVMDG303: JVM Requesting Java core file

JVMDG304: Java core file written to /opt/WebSphere/AppServer/javacore.20101129.161814.22608.txt

JVMDG215: Dump Handler has Processed Exception Signal 11.

"signal 11 received" is seen in java core dump logs too.

Process level CPU usage metrics are not supported in probe for Linux 1.4.2 core, and though the probe should detect this initially, in some cases this didn’t happen.

Comment out the following metrics in etc/metrics.config file and restart the application/probe again:

ProcessMetrics/processCpuUtil=ProcessCpuUtil|percent|Probe

ProcessMetrics/processCpuUtilAbs = ProcessCpuUtilAbs|percent|Probe