Page History

Documentation Overview

The following diagrams and notes Following diagrams are my understanding of part of the ServiceMix architecture based on a study of the source code . Enjoy – PS.– PS

Contents

• NMR flow types
  • st
  • seda
  • jms
  • jca

...

• There are a number of flow implementations. For example: STFlow, SedaFlow, JMSFlow, JCAFlow

goto top

Broker send sequence diagram

...

JMSFlow

Uses JMS for message routing among a network of remote containers.

"remote" just means separate. In fact, it makes no difference if the JMSFlow containers are on the same or separate machines.TODO

JMSFLow classes and JMS Destinations

...

• There is one single Topic across all containers. This is created during JMSFlow init. A ConsumerAdvisor configured for this Topic allows container to be "aware" of each other. Special messages sent to this Topic allow broadcasting of you components to other containers in the network.

• There is one Queue per container. This is created during JMSFlow init. This Queue is for sending request MEs to.

• There is one Queue per sender component. This is created when a component is activated. These Queue is for sending response MEs to.

• The JMSFlow is a JMS MessageListener (ie it implements onMessage Method) for the Topic and all Queues

• The JMSFlow is also an ActiveMQ ConsumerAdvisoryEventListener for the Topic. This means all JMSFlow instances will be aware of remote container startup/shutdown

goto top

Notification of remote component state changes

• TODO add more notesfix diagram

• I have shown a "local" and "remote" JMSFLow instance for clarity although they may be the same instance

• A container needs to be made aware when the state of a remote container's components changes. JMSFlow uses an ActiveMQ ConsumerAdvisoryEvent to detect a change in status of a remote Consumer of the Topic.

• • If remote Topic Consumer activated - eg container started
    • Information of all (local) components are re-broadcast to the Topic so the new container can lern about them

• • If remote Topic Consumer is deactivates - eg container shutdown
    • All (local) knowledge of the remote container's components is removed

• Conversely, a remote container needs to be made aware if there is some state change with any component of the local container. JMSFlow is a JMS MessageListener on the Topic

• • If a component state changes a ComponentPacketEvent (which container component state information) is serialized and sent as a JMS ObjectMessage to the Topic.
    • All remove JMSFlows receive this message and adjust their knowledge of our component accordingly
  • If the component is becoming activated, then a Queue is created (for remote containers to send response MEs to)

goto top

JMSFlow send ME sequence diagram

• I have shown a "local" and "remote" JMSFLow instance for clarity although they may be the same instance

• The ME is serialized and sent as a JMS ObjectMessage

• Requests are sent to a generic Queue on the remote container

• Responses are sent back to a specific Queue for the component that sent the request exchange (because the sender may have done a synchronous send and is awaiting a response)

• The JMSFlow is a MessageListener for both Queues

• When the MessageListener's onMessage is triggered the ObjectMessage content is deserialized. If the deserialized Object is a ME then it is routed to the destination component.

goto top

JCAFlow

• TODOTODO add more notes

goto top