Setting up JVM targets individually
On EZJE, hyperlink on Setup MJEJVM targets under Setup & Configuration.
The JVM Add Targets wizard is displayed.
JOB Information
Job Name MJEDZERV Jobname for JVMs
JMX Information
Description ZconnectEE-0192 JVM auto c JVM Description
JMX Port 0 JMX Listener Port
Security Suffix NO N Create MJESSL Member?
JMX Protocol JRMP REST, IIOP or JRMP
Debug Level 00 Debug Level Control
JVM History D Capture JVM History
Health Center Information (ACTIVE AUTO)
Health Center Port SCAN HC Listener Port
HC Security Suffix NO Only valid with Port
nnnnn
Collect
Garbage Collection Y (Y|N)
Classes Y (Y|N)
Class Histogram Y (Y|N) * Interval 15 Minutes *
Object Allocation O (Y|N|O) * between 0 and 0 bytes *
Event Only Mode Y
z/OS Connect EE Information
HTTP Port 0 Used if MJESSL suffix is NO
HTTPS Port 0 requires MJESSL value
Security Suffix NO MJESSL suffix for this connection
End to add this target
Cancel to exit without adding
HELP to display helpComplete the fields as described in the following table:
Field
Default value
Description
Job Name=jobName
No default
Job name on which you want to set up a target
JMX Information
Description=description
No default
Description of the target
JMX Port=n
0
JMX listening port for BMC AMI Ops Monitor for Java Environments
This port number should match the port that you set up for the JVM in the Configuration JMX setup. For more information, see Configuring-JMX-and-IBM-Health-Center.
Security Suffix=[NO | xx]
NO
Suffix of the SSL member that you want the new target to use
Valid values are:
- NO (the default), which adds SSL member MJESSLNO to the target. MJESSLNO contains no SSL parameters.
- xx, representing a two-character user-specified suffix of an existing SSL member. Alternatively, if you want to create a new SSL member, specify a suffix for the new SSL member.
Create MJESSL Member?=[Y | N]
N
Whether to create a new SSL security profile
JMX Protocol=[JRMP | IIOP | REST]
JRMP
Connection protocol as defined in the target JVM for JMX connectivity
Valid values are:
- IIOP
- JRMP
REST
Debug Level=nn
00
Level of debugging for each JMX connection to the target JVM
Valid values are 00 and 01.
History=[D | Y | N]
D
Whether to collect history data
Valid values are:
- D (the default), uses the value that is specified in MJEINIxx
- Y, collects history data
N, does not collect data
Health Center Information
Health Center Port=[Scan | nnnnn]
Scan
Health Center port to which the product should connect
Valid values are:
- Scan, the product scans the target address space for a listening Health Center port
- nnnnn, representing a port number
Security Suffix=[NO | xx ]
NO
Suffix of the SSL member that you want to use for building Health Center security properties for the JVM
Valid values are:
- NO (the default), which adds SSL member MJESSLNO to the target. MJESSLNO contains no SSL parameters.
- xx, representing a two-character user-specified suffix of an existing SSL member. Alternatively, if you want to create a new SSL member, specify a suffix for the new SSL member.
Garbage Collection=[Y | N]
Y
Whether to collect information about garbage collectors
Classes=[Y | N]
Y
Whether to collect information about the Java classes being loaded and their usages
Class Histograms=[Y | N]
*Interval nn minutes*
Y, 15
Whether to collect class histograms
Valid values are:
- Y (the default), collects class histograms at nn minute intervals
- N, no class histograms are collected
Object Allocation=[O | Y | N] *between nnnn and nnnn bytes*
O
Whether to collect out-of-line memory allocations
Valid values are:
- O (the default), collects all memory allocations within the JVM
- Y, collects all memory allocations between nnnn and nnnn bytes
- N, no memory allocations are collected
Event Only Mode=Y
Y
Whether Health Center should operate in only event mode
z/OS Connect EE Information
HTTP Port= nnnnn
0
Port number for a http listener port
The product uses this port if you specify Security Suffix=NO for the z/OS Connect EE target.
HTTPS Port=nnnnn
0
Port number for a https listener port
The product uses this port if you specify an SSL member for the z/OS Connect EE target.
Security Suffix=[NO | xx ]
NO
Suffix of the SSL member that you want to use for building z/OS Connect EE security properties for the JVM
Valid values are:
- NO (the default), which adds SSL member MJESSLNO to the target. MJESSLNO contains no SSL parameters.
- xx, representing a two-character user-specified suffix of an existing SSL member. Alternatively, if you want to create a new SSL member, specify a suffix for the new SSL member.
- (optional) To add additional JVM targets, complete the following steps for each additional target:
On the COMMAND line, enter N (Next).A message indicates that the target entry was built.
- Complete each dialog field for the new target.
- When finished adding targets, on the COMMAND line enter E (End).
If you specified Y in the Create MJESSL Member? field, complete the Create Security Member dialog and then enter SAVE on the COMMAND line.
Field
Default value
Description
Description=description
No default
Description of the SSL member
Member Suffix=xx
xx
Suffix for the new SSL member
Define a two-character number or alphanumeric suffix.
SSL Enabled=[YES | NO]
N
Whether the target JVM requires SSL security for the connection
Password Auth=[YES | NO]
N
Whether the target JVM requires authenticating the user ID and password for JMX connectivity
Client Auth=[YES | NO]
N
Whether the target JVM requires SSL client authentication
SSL Debug=[YES | NO]
N
Whether to create debug information on connection communications
Keystore=keystorePath
No default
USS path to a keystore for SSL handshaking
When the target JVM requires SSL security (SSL Enabled=YES), the implementation of SSL security is either Java SSL (JSSE) or IBM RACF SSL.
Valid values are as follows:
- Java SSL (JSSE) – the file path of the keystore
- RACF SSL – the name of the RACF keyring
Key Password=keystorePassword
No default
Password for the specified keystore
Key Type=keystoreType
No default
Type of keystore
Valid values are:
- Java SSL (JSSE) – JKS
- RACF SSL – JCERACFKS
Truststore=truststorePath
No default
USS path to a truststore for SSL handshaking
When the target JVM requires SSL security (SSL Enabled=YES), the implementation of SSL security is either Java SSL or RACF SSL.
Valid values are as follows:
- Java SSL (JSSE) – the file path of the truststore
- RACF SSL – the name of the RACF keyring
Trust Password=truststorePassword
No default
Password for the specified truststore
Trust Type=truststoreType
No default
Type of truststore
Valid values are:
- Java SSL (JSSE) – JKS
- RACF SSL – JCERACFKS
In the Save Current Targets dialog, take one of the following actions:
Action
Steps
To install the new targets into the running PAS and save the target definitions
1. In the Member Suffix field, define a two-character number or alphanumeric suffix.
2. In the Overwrite field, define one of the following values:
- Y to overwrite existing members with the specified suffix
N to retain the existing member
3. On the COMMAND line, enter Persist.
To install the new targets into the running PAS without saving the target definitions
On the COMMAND line, enter Install.
To save the target definitions
1. In the Member Suffix field, define a two-character number or alphanumeric suffix.
2. In the Overwrite field, define one of the following values:
- Y to overwrite existing members with the specified suffix
N to retain the existing member.
3. On the COMMAND line, enter Save.
When EZJE returns, the Setup MJEJVM targets option has changed to MJEJVM targets (unless you saved without installing to the PAS, in which case the option remains unchanged).