There is only a single micro broker instance per platform. The micro broker instance is created programmatically by using the administration APIs.
The micro broker instance once created will be started automatically by the com.ibm.micro bundle. Since the com.ibm.micro bundle will be lazy started as a result of calling the administrative APIs on the micro broker, the only bundle that needs to be added to the platform or application lifecycle is your application bundle that checks for existence of or creates a micro broker instance. See Managing life cycle
for more information.
To begin initial prototyping using the micro broker, a Lotus® Expeditor micro broker Getting Started feature is provided on the updates\platform update site. This feature is not installed by default and must be installed using one of the provisioning mechanisms. To use this feature, either add the com.ibm.micro.gettingstarted plug-in to the platform life cycle to perform the initial configuration of the micro broker instance, or use the platform console to manually start this plug-in. The micro broker instance is named FirstBroker
. This plug-in is for evaluation and initial prototyping use and provides a very basic configuration. You may need to create your own broker instance specific to your application requirements, configuring capabilities such as connections and connection types, persistence, connection factories and more.
For more information, refer to Configuring and administering micro broker components
for more details.
Parent topic: Extending the platform: XPD621