Generating a JVM list
To generate a list of all JVMs on a particular LPAR
- Copy the MJELGEN member from the BBSAMP library into your library, and open the file in an editing session.
In MJELGEN, change the following parameters:
Parameter
Description
input_dsn
Data set name for the MJEINPUT file
props_dsn
Data set name for storing JMX properties
bbproc_dsn
BMC AMI Ops Monitor for Java Environments BBPROC data set name
bbparm_dsn
BMC AMI Ops BBPARM data set name
storclas
Valid SMS storage class
- Locate the two TSO commands at the end of this *//* JCL (use PF8 to scroll to them) and select one for use in the JCL as follows:
- If you need to customize the output data set further, select the first TSO command.
- If you have no special considerations for your configuration, select the second TSO command.
In the selected TSO command, change the following parameters if required.
Parameter
Default value
Description
JTB( )=xx
00
Suffix for the MJEJTB member in BBIPARM
In most instances, this suffix is 00 unless you have a customized JTB suffix.
HC( )=[Y | N]
Y
Whether to enable the Health Center on the JVMs that you want to monitor
HCA()=path
--
Fully qualified zfs filename that contains the credentials for Health Center MBean authentication
HCR()=path
--
Fully qualified zfs filename that contains the credentials for Health Center MBean authorization
DFL( )=[Y | N]
Y
Whether to write a default profile
BMC AMI OpsMJE uses the default profile to automatically create targets for Health Center agents without defined targets.
SEC( )=[xx | NO]
NO
Suffix of the SSL member that you want the new target to use for JMX security
Valid values are:
- NO (the default) adds SSL member MJESSLNO to the target. MJESSLNO contains no SSL parameters
- xx, representing a two-character suffix of an existing SSL member
TGT( )=xx
00
Suffix for the MJETGT member that is created by the list processor job
PRO( )=[JRMP | IIOP]
JRMP
RMI protocol for the MJEJVM to communicate with remote user JVMs
PRE( )=xxx
MJE
Prefix for property members that are created for added JVMs
HST( )=[D | Y | N]
D
Whether to collect history data for JVMs
Valid values are:
- D (the default), uses the value that is specified for the MVHISTORY parameter in MJEINIxx
- Y, collects history data
- N, does not collect data
ZPT( )=path
/tmp
Directory for the list processor to write JMX property files for JVMs that use the USS file system for reading properties
HCS( )=[ xx | NO]
NO
Suffix of the SSL member that you want to use for building Health Center security properties for a JVM
Valid values are:
- NO (the default) adds SSL member MJESSLNO to the target. MJESSLNO contains no SSL parameters
- xx, representing a two-character suffix of an existing SSL member
HCG( )=[Y | N]
Y
Whether to gather garbage collection data from the Health Center
HCC( )=[Y | N]
Y
Whether to gather class data from the Health Center
HCH( )=nn
15
Interval (in minutes) to gather class histogram data from the Health Center
Valid values are 5 through 60. If you specify a zero value, no data is gathered.
HCO( )=[O | N]
O
Whether to gather out-of-line memory allocation data for the Health Center Valid values are:
- O (the default), collects all memory allocations within the JVM.
- N, no memory allocations are collected.
JPZ( )=[Y | N]
Y
Whether JMX port 0 is set for JVMs that you want to monitor.You specified the JMX port for each JVM in Configuring-JMX-and-IBM-Health-Center.
PRT( )=portNumber,portNumber... | startingPortNumber - endingPortNumber
No default
Range of available ports that the JMX JVM communications can use
You can specify ports from 1024 through 65535. Use a comma to separate individual ports, and use a dash to specify ranges.
- On the COMMAND line, type submit and press Enter.The job creates the MJEINPUT file, using the name that you specified for the input_dsn parameter.