Publish/subscribe within WebSphere Business Integration Message Broker is managed from the workbench, which is used to connect brokers in a topology or hierarchy, and to administer topic-based security (if a User Name Server is in use). Like other workbench changes, you need to deploy any changes that you make so that updates are sent to the broker.
This section outlines some common problems that can arise when using publish/subscribe. It contains advice for dealing with the problems:
Message persistence in publish/subscribe is normally preserved. However, a subscriber might not get the expected persistence if ACLs do not allow it.
The JIT compiler will load and run correctly if LIBPATH is not set. This is the simpler case and you are recommended not to set LIBPATH. You can make libraries available by linking them into /var/wmqi/lib (for all WebSphere Business Integration Message Broker for AIX processes) or /usr/lib (for all processes on the system). WebSphere Business Integration Message Broker for AIX configuration does this for DB2 libraries.
If it is necessary to set LIBPATH, update it to include the directory /usr/java130/bin.
For example, you can use the following command to start the broker:LIBPATH=/usr/local/lib:/usr/java130/bin mqsistart mybroker
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
au16630_ |