Using local connection with IIB10 field pack

Document ID : KB000112505
Last Modified Date : 21/12/2018
Show Technical Document Details
Introduction:
The IIB10 fieldpack on the CA MarketPlace does not provide support for broker connections via the Local Connect API and additionally when using the Webadmin port for broker connections does not support TLS 1.2 cipher suites - this KB contains additional information about an updated version that supports both. If this is required please contact support to obtain it.
Instructions:
The field pack zip file conatins a pdf help file in teh docs folder detailing installation instructions but the key to enableing the local connection moode is via the following property

# when this agent is runninng on the same host as IIB, binndings mode can be used to connect.
# only broker name is required to configure in this mode. host/port/user/password/ssl properties
are not required.
# the mq.broker.monitor.list should have the actual broker name for this to work. If broker name
is broker1, then the property should be set like below
#broker1.broker.localconnection=true
Additional Information:
If when running with local connection mode if the following messages are reproted

7/17/18 10:09:25 AM BST [INFO] [com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.v7.MBTreeConfigMain] Broker MYBROKERis configured to connect in local bindings mode.
7/17/18 10:09:25 AM BST [DEBUG] [com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.v7.MBTreeConfigMain] BIP8846S: Configuration data for component 'MYBROKER' is not usable by this product version (level -1; should be 8).

Each component has configuration data associated with it, and this data is versioned to ensure that the component can only be run under a product version that supports this level. The component level is -1 and the current code level only supports 8.
com.ibm.broker.config.proxy.ConfigManagerProxyLoggedException: BIP8846S: Configuration data for component 'MYBROKER' is not usable by this product version (level -1; should be 8).

Each component has configuration data associated with it, and this data is versioned to ensure that the component can only be run under a product version that supports this level. The component level is -1 and the current code level only supports 8.
    at com.ibm.broker.config.proxy.PipedBrokerConnectionParameters.getSender(PipedBrokerConnectionParameters.java:163)
    at com.ibm.broker.config.proxy.LocalBrokerConnectionParameters.getSender(LocalBrokerConnectionParameters.java:172)
    at com.ibm.broker.config.proxy.BrokerProxy.<init>(BrokerProxy.java:426)
    at com.ibm.broker.config.proxy.BrokerProxy.getInstance(BrokerProxy.java:1056)
    at com.ibm.broker.config.proxy.BrokerProxy.getLocalInstance(BrokerProxy.java:962)
    at com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.v7.MBTreeConfigMain.getBrokerNameFromBrokerProxy(MBTreeConfigMain.java:594)
    at com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.v7.MBTreeConfigMain.readMQBrokerListProperties(MBTreeConfigMain.java:444)
    at com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.v7.MBTreeConfigMain.<init>(MBTreeConfigMain.java:168)
    at com.wily.powerpack.websphereMQ.agent.MQMonitor.MQMonitor.main(MQMonitor.java:298)
    at com.wily.powerpack.websphereMQ.agent.MQMonitor.MQMonitor.main(MQMonitor.java:221)
7/17/18 10:09:25 AM BST [FATAL] [com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.v7.MBTreeConfigMain] Broker MYBROKER broken connection!


Then you need to ensure that the environment in which the agent is being run has had the msqiprofile executed (sourced prior to starting the agent) and that the user running the agent is a member of the mqbrkrs group.