Components that can be administered: XPD621
Use the broker interface to access the micro broker components.
Accessing the broker administration interface: XPD621
Access to the administration interface is gained by way of a BrokerFactory, an instance of which can easily be obtained as shown in the examples that follow. From an administrative perspective, there are two types of broker. These are referred to as local and remote brokers, respectively and represented by their corresponding LocalBroker and RemoteBroker Java objects.
Creating and starting a broker: XPD621
Use this example to create and start a default broker.
Using the bridge
Connect to other messaging servers.
The bridge provides a framework for users to create and run their own transformations. These add-ons have to be defined and registered with the bridge.
Adding JNDI security properties: XPD621
This section describes how to add JNDI security properties.
Connecting to a broker: XPD621
This section describes how to connect to a broker.
Administering listeners: XPD621
Create a listener to listen for and accept connections from clients.
Administering queues: XPD621
Application queues can be created on the Messaging Engine component for use with point-to-point messaging.
Migration information: XPD621
Bundles which use the micro broker administrative API, and which also use the "Require-Bundle" header in the manifest, will need to be updated to use the "Import-Package" header instead. The administrative API is now in the bundle com.ibm.micro.admin
. It is considered a best practice to manage imports at the package level, as it makes dependencies less brittle to bundle changes.