WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with the WebSphere MQ messaging provider > Install WebSphere MQ to interoperate with WAS > Maintain the WebSphere MQ resource adapter

Ensuring that servers use the latest available WebSphere MQ resource adapter maintenance level

To ensure the WebSphere MQ resource adapter is automatically updated to the latest available maintenance level when we apply WAS fix packs, we can configure all servers in the environment to use the latest version of the resource adapter contained in the fix pack that we have applied to the installation of each node.

Updates to the WebSphere MQ resource adapter that is installed with WAS are included in WAS Fix Packs. You must only update the WebSphere MQ resource adapter using the "Update resource adapter facility if you require a specific version of the resource adapter, instead of the most recent version. To install a specific version of the resource adapter, see Install a specific maintenance level of the WebSphere MQ resource adapter.

We can use the following Jython and Jacl commands to determine the level of the WebSphere MQ resource adapter currently being used by WAS:

• Jython:

  You must press Return twice after entering this command in order to run it.

  wmqInfoMBeansUnsplit = AdminControl.queryNames("WebSphere:type=WMQInfo,*")
  wmqInfoMBeansSplit = AdminUtilities.convertToList(wmqInfoMBeansUnsplit)
  for wmqInfoMBean in wmqInfoMBeansSplit: print wmqInfoMBean; print AdminControl.invoke(wmqInfoMBean, 'getInfo', '')

• Jacl:

  set wmqInfoMBeans [$AdminControl queryNames WebSphere:type=WMQInfo,*]
  foreach wmqInfoMBean $wmqInfoMBeans {
  puts $wmqInfoMBean;
  puts [$AdminControl invoke $wmqInfoMBean getInfo [] []]}

Use this task if any of the following circumstances apply to your configuration, and to configure all servers in the environment to use the latest version of the WebSphere MQ resource adapter:

• The JVM logs of any application server in the environment contain the following entry:

  WMSG1625E: It was not possible to detect
  the WebSphere MQ messaging provider code at the specified path <null>

• One or more nodes has previously been manually updated to use a specific maintenance level of the WebSphere MQ resource adapter that is now superseded by the latest version of the resource adapter contained in the current WAS maintenance level.

When we have performed the following steps for all cells and single server installations in the environment, your servers will automatically receive maintenance to the WebSphere MQ resource adapter when a new fix pack is applied.

1. Start the application server.
   
2. Copy the following Jython script into a file called convertWMQRA.py, then save it into the profile_root/bin directory.
   

   ras = AdminUtilities.convertToList(AdminConfig.list('J2CResourceAdapter'))
   
   for ra in ras :
      desc = AdminConfig.showAttribute(ra, "description")
      if (desc == "WAS 7.0 Built In WebSphere MQ Resource Adapter") or 
         (desc == "WAS 7.0.0.1 Built In WebSphere MQ Resource Adapter") or 
         (desc == "WAS Built In WebSphere MQ Resource Adapter"):
         print "Updating archivePath and classpath of " + ra
         AdminConfig.modify(ra, [['archivePath', "${WAS_INSTALL_ROOT}/installedConnectors/wmq.jmsra.rar"]])
         AdminConfig.unsetAttributes(ra, ['classpath'])
         AdminConfig.modify(ra, [['classpath', "${WAS_INSTALL_ROOT}/installedConnectors/wmq.jmsra.rar"]])
         AdminConfig.save()
      #end if #end for

3. Use wsadmin to run the Jython script that we have just created.
   

   Open a command prompt and navigate to the profile_root/bin directory, then enter the following command:

   wsadmin -lang jython -f convertWMQRA.py
4. Stop all servers in the profile.
   

5. Run the osgiCfgInit command from the profile_root/bin directory.
   

   The osgiCfgInit command resets the class cache used by the OSGi runtime environment.

6. Restart all servers in the profile.
   

If you continue to experience problems after performing the steps described in this topic, and we have previously used the Update resource adapter... button on the JMS Provider Settings panel in the dmgr console to update the WebSphere MQ resource adapter on any nodes in the environment, it is possible that you are experiencing the issue described in APAR PM10308.

Reference:

JMS provider settings

+

Search Tips   |   Advanced Search