See: Description
Interface | Description |
---|---|
AdminInterface |
AdminInterface is an interface that can be added to the OutputConnector or the EventInputConnector to provide administration to the system being connected to.
|
Class | Description |
---|---|
ByteArrayInputRecord |
ByteArrayInputRecord allows a record to be created that is based on a byte array.
|
ConnectorFactory |
ConnectorFactory is the base class which must be extended to implement a connector which can run in WebSphere Message Broker.
|
ContainerServices |
ContainerServices gives access to key functions provided by the container, such as tracing and logging.
|
ElementInputRecord | |
Event |
Event is the base class which must be extended to implement the receiving of an event from the system.
|
EventInputConnector |
EventInputConnector is the base class which must be extended to implement a connector which can receive events from the system.
|
InputRecord | |
OutputConnector |
OutputConnector is the base class which must be extended to implement a connector which can send data to a system.
|
OutputInteraction | |
OutputRecord |
A Connector is a component designed to connect message broker nodes to a particular system.
To implement a set of Connectors to interact with an end system you first need to implement a ConnectorFactory. This is then called by message broker to create connectors for nodes to use to interact with that particular system. To uses a connector in a message flow you first need to create a java user defined node definition in the message broker toolkit. You do not need to construct a java MbNode classes just define a node for the type of connector you require: