Integration with BMC AMI Strobe for Java
With this feature, the JVM Dashboard view provides a broader view and enhanced visual analysis of graphs in a UI platform, as shown in the following example:
JSON measurements file
A JSON measurements file is created for each successful sampling request and written to the USS directory. Customers can add the USS directory path in the HCTMPDIR parameter in the MJEENVxx BBPARM member. If you don't specify a directory in the HCTMPDIR parameter, the JSON measurements file is written to the /tmp space directory by default.
Strobe status field
The Strobe Status field in the following views displays the current Strobe Measurement status for each JVM monitored by BMC AMI OpsMJE:
- JVMDISC
- JVMDISCD
- JVMDTGT
- JVMDZCON
- JVMDCPU
The Strobe measurement statuses are as follows:
- (Default) N/A
- Started
- Queried
- Stopped
- Deleted
For more information about JVM views, seeAll JVM Views. For information about the JVMDZCON view, seez/OS Connect EE statistics views.
Request types for Strobe and MJEJVM communication
The following table describes the request types for Strobe and product JVM (MJEJVM) communication:
Request type | Description |
|---|---|
Start | Specifies the target JVM and any other parameters needed by the JMX agent This request type accepts a set of name/value pairs ("tags") that the caller can specify. Tags are added to the JSON measurement file, which allows the requestor (Strobe) to match a JSON measurement file with the request that started it. |
Query | Gets the measurement status known to OpsMJE, including the location of the data file (Optional) The status of stopped or completed measurements persists until the measurement or some configured interval is completed. This information includes the list of tags that the caller specified when each measurement started. |
Stop | Stops an in-progress measurement (for example, if the user has determined that they targeted the wrong JVM or the performance impact is causing issues.) |
Delete | Issued after BMC AMI iStrobe has collected the data file |
When the PAS log requests a request from Strobe, MJEJVM issues the acknowledgment message from the following message:
MJEVM373I Received Strobe requestTypeSample command for JVM=jvmNumber ASID=ASid JMXPort=portNumber
Strobe uses the TCPMJEPORT parameter specified in the MJEENVxx BBPARM member of OpsMJE, and this parameter specifies the Port number through which Strobe can communicate with the MJEJVM.
Example
Strobe for Java architecture flow
The following figure shows the process for Strobe for Java requests. The figure does not include the process for JMX.