If you see Lotus Expeditor installation, you'll see many bundles, Here your guide to identifying the micro broker related bundles.
- com.ibm.micro.bridge.mq.jms_XXX.jar or package com.ibm.micro.bridge.mq.jms contains the classes that you need for connecting to WebSphere MQ using MQJMSConnectionDefinition from the micro broker bridge
- com.ibm.micro.bridge.jndi.jms_XXX.jar or package com.ibm.micro.bridge.jndi.jms contains the classes required for the miro broker bridge to connect to a JNDI enabled JMS provider using JNDIConnectionDefinition.
- com.ibm.micro.gettingstarted_XXX.jar contains sample broker. If deployed and started, it runs a broker at port 1883
- com.ibm.micro_XXX.jar This contains all the micro broker core classes
- com.ibm.micro.utils_XXX.jar This contains all the utility classes that are needed by the core micro broker
- com.ibm.mqttclient.jms_XXXX.jar This contains all the classes that are needed for a micro broker JMS client
- com.ibm.mqttclient_XXX.jar This contains the classes needed fot a normal MQTT java client
- Bundles ending with nl1, nl2, nl3 are fragments that are needed for NLS support.
If your deploying on a device, you can install only the required jars in the device environment. For example, com.ibm.mqttclient_XXX.jar is enough if you are running a MQTT client only, if you are running a micro broker with a MQTT bridge only the core bundles com.ibm.micro_XXX.jar and com.ibm.micro.utils_XXX.jar are sufficient.
Neeraj Krishna and Vijay