WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Updating a user-defined extension

On all systems, you can change a user-defined extension file.

You must stop and restart the broker for your changes to show, However, you are not required to stop and restart the broker in the following two scenarios:
  • If you have created an execution group in the WebSphere® Message Broker Toolkit, but have not yet deployed to it, you can add the .lil, .pdb, and .jar files to your chosen directory.
  • If an object has already been deployed to the execution group that you want to use, add the .lil, .pdb, and .jar files to your chosen directory and use the mqsireload command to restart the group. You cannot overwrite an existing file on the Windows system when the broker is running because a file lock is put in place by the operating system.

These two scenarios must be used with caution, because any execution group that is connected to the same broker also detects the new .lil, .pdb, and .jar files when that execution group is restarted, or when an object is first deployed to it. If you restart the broker, you must ensure that anyone with an interest in a particular execution group is made aware that recent changes have been made to the broker.

These two scenarios assume that you have used either the mqsichangebroker command or the mqsicreatebroker command to notify the broker of the directory in which the user-defined extension files have been placed.

To change a user-defined extension file:

  1. Stop the broker by using the mqsistop command.
  2. Update or overwrite the .lil or .jar file.
  3. Restart the broker by using the mqsistart command.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:33


Task topicTask topic | Version 8.0.0.7 | as10006_