Java client connectivity to batch applications running on z/OS
By using a client connection, an IBM® MQ classes for Java application on z/OS® can connect to a queue manager on z/OS that has the ADVCAP(ENABLED) attribute. Use of a client connection can simplify IBM MQ topologies.
A value of ADVCAP(ENABLED) applies only to a z/OS queue manager, licensed as IBM MQ Advanced for z/OS, Value Unit Edition (see IBM MQ product identifiers and export information) and running with QMGRPROD set to ADVANCEDVUE.
See DISPLAY QMGR for more information on ADVCAP and START QMGR for more information on QMGRPROD.
An IBM MQ classes for Java application on z/OS cannot use a client mode connection to connect to a queue manager that is not running on z/OS, or to a queue manager that does not have the ADVCAP(ENABLED) option set.
If an IBM MQ classes for Java application on z/OS attempts to connect using client mode, and it is not allowed to do so, MQRC_ENVIRONMENT_ERROR is returned.
Advanced Message Security (AMS) support
From IBM MQ 9.0.5, IBM MQ classes for Java client applications can use AMS when connecting to IBM MQ Advanced for z/OS, Value Unit Edition queue managers on remote z/OS systems.
The Bouncy Castle jar files are shipped with the IBM MQ for z/OS IBM MQ classes for Java package.
jceracfks
, is supported in
keystore.conf on z/OS only, where:- The property name prefix is
jceracfks
and this name prefix is case insensitive. - The key store is a RACF keyring.
- Passwords are not required, and will be ignored. This is because RACF keyrings do not use passwords.
- If you specify the provider, the provider must be
IBMJCE
.
jceracfks
with AMS, the key store must be in the form:
safkeyring://user/keyring
, where:safkeyring
is a literal and this name is case insensitiveuser
is the RACF user id that owns the keyringkeyring
is the name of the RACF keyring and the name of the keyring is case sensitive
JOHNDOE
:
jceracfks.keystore=safkeyring://JOHNDOE/drq.ams.keyring