John Ormerod 7.Aug.09 10:07 AM Lotus Notes Toolkit 6.1.1 Windows XP
I have been working through the hybrid Wiki-redbook on "Micro Broker with the SI Bus". However, I have not managed to get the Desktop broker to connect to the SI Bus in WAS 6.1 test environment installed in RSA.
I am in the middle of a customer Xpd development that keeps me on 6.1.1, so I can't use any MQTT v5 code, and I have had to modify one of two bits of the broker setup code to work around methods new in 6.2 (e.g MessagingEngine#getQueue()), but this has had the advantage of making me think a bit more!
I wondered if there are any common mistakes that stop a pipe from connecting to the SI Bus, or references to anything that describes how to trouble-shoot this?
I have had to make some broker config definition changes to accommodate the ports used on my WAS 6.1 system:
SIB_ENDPOINT_ADDRESS = 7277
SIB_ENDPOINT_ADDRESS = 9101
In the Connection Factory defs, for the Provider Endpoints, I specified:
192.168.1.2:7277:BootstrapBasicMessaging [My hostname has a hyphen in it, which requires a fixpak to sort out]
In the Micro Broker setup code in the Activator, I specified:
CONN_URL = "iiop://192.168.1.2:9101"; [Before, I had used EREBOR-JO for the host name, now I am trying the ip address]
The Admin GUI shows that the pipe is running, but it never shows it being connected. I have published a retained test message, and by adding a line of code to the refeshStatus() method, I can see that there is one retained publication. Which I assume is awaiting a connection being made to the SI Bus to effect the subscription.
The red book is not specific when it comes to defining the connection factory: should its scope be cell, cell+node or cell+node+server? I elected to use the narrowest scope. In an older doc that I found I already had, a Queue connection factory was used, so I tried that using cell scope, and modified the broker setup to use that. Still made no difference.
Also, the redbook does not say which options should be used when creating the IBM ClientJMS on J2SE with WAS. I used the following command:
java -jar sibc_install-o0902.06.jar -xpd jms_jndi_ibm d:\ibm\IBMClientJMSonJ2SEWAS