IT29963: The JMSAdmin tool is partially shipped by the redistributable Java client "{version}-IBM-MQC-Redist-Java.zip"

APAR status

• Closed as program error.

Error description

• The redistributable Java client
  "{version}-IBM-MQC-Redist-Java.zip" contains the JMSAdmin.bat
  file used for launching the JMSAdmin tool on Windows, but does
  not include the JMSAdmin script for Linux and Unix platforms. It
  also does not include the sample configuration file
  JMSAdmin.config file for any platform, or the pre-requisite jars
  fscontext.jar and providerutil.jar which are needed to use the
  JMSAdmin tool to create JMS administered objects within a file
  system context (.bindings file), or for the redistributable Java
  client to access JMS administered objects stored within a file
  system context.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This affects users of the redistributable Java client who want
  to use the JMSAdmin tool to create JMS administered objects
  within a .bindings file associated with the file system context
  com.sun.jndi.fscontext.RefFSContextFactory.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The redistributable Java client
  "{version}-IBM-MQC-Redist-Java.zip" contained the Windows-only
  version of the JMSAdmin tool (JMSAdmin.bat), but did not
  contain:
  
  - The version of the JMSAdmin tool for Linux and Unix platforms
  (JMSAdmin).
  - The sample configuration file for the JMSAdmin tool
  (JMSAdmin.config)
  - Either of the pre-requisite jar files:
      - fscontext.jar
      - providerutil.jar
  
  These files were needed if the JMSAdmin tool was configured to
  create JMS administered objects within the file system context
  com.sun.jndi.fscontext.RefFSContextFactory (these objects were
  stored in a file called .bindings), or if an MQ classes for JMS
  application that was using the redistributable Java client
  needed to access JMS administered objects stored within a file
  system context.
  

Problem conclusion

• This APAR has modified the files included in both the
  redistributable Java client "{version}-IBM-MQC-Redist-Java.zip"
  and the self-extracting JAR file
  "{version}-IBM-MQ-Install-Java-All.jar".
  
  The redistributable Java client now does not include any of the
  files related to the JMSAdmin tool.
  
  The self-extracting JAR file
  "{version}-IBM-MQ-Install-Java-All.jar" has been updated to
  include all of the files related to the JMSAdmin tool, in
  addition to all of the files it did before. This means that the
  self-extracting JAR file now contains the following extra files:
  
  - The JMSAdmin.bat file used to start the JMSAdmin tool on
  Windows.
  - The JMSAdmin script that is used to start the tool on Linux
  and Unix platforms.
  - The sample configuration file for the JMSAdmin tool
  (JMSAdmin.config)
  
  The format of the self-extracting JAR file has also changed
  slightly. Previously, the self-extracting JAR file would install
  the com.ibm.mq.allclient.jar file and all of its pre-requisite
  JAR files into a directory called were installed into the
  wmq/JavaSE directory within the specified installation
  directory. Now, these files are installed into the
  "wmq/JavaSE/lib" directory. The files related to the JMSAdmin
  tool, which have been added to the self-extracting JAR file by
  the APAR, are installed into the "wmq/JavaSE/bin" directory.
  
  As a result of these changes, a client that is installed using
  the self-extracting JAR file can use the JMSAdmin tool installed
  as part of the JAR file to create JMS administered objects
  within a file system context (.bindings file). The client can
  also look up and use these administered objects.
  
  A client installed by unpacking the redistributable Java client
  does not contain the JMSAdmin tool, or its pre-requisite JAR
  files fscontext.jar and providerutil.jar. This means that the
  client can not connect to any file system contexts (.bindings
  files) created by a different installation which does have the
  JMSAdmin tool (note that the APAR has not changed this - the
  pre-requisite JAR files needed to connect to a file system
  context have never been included in the redistributable Java
  bundle).
  
  Customer who want to use a pre-existing file system context
  (.bindings file) with the redistributable Java client will have
  to obtain these pre-requisite jar files from Maven. The JAR
  files can be downloaded from:
  
  https://mvnrepository.com/artifact/com.sun.jndi/providerutil/1.2
  https://mvnrepository.com/artifact/com.sun.jndi/fscontext
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.8
  v9.2 LTS   9.2.0.2
  v9.x CD    9.2.2
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IBM MQ BASE MP

• Fixed component ID

  5724H7271

Applicable component levels