Page History

...

This document describes how to run the Qaurtz example and provides details about what it does. For information on the business use case, please refer to: Use Case for BasicQuartz.

The Basic Quartz example illustrates the following:

...

The source code for the Quartz example is located in the ServiceMix installation directory under the examples\quartz-binding directory in the servicemix.xml file. It is recommended that you refer to the source code while reading this document.

This example shows how to use Quartz component that sets to set off a trigger to send that sends messages to a trace component. The trace component logs the messages to the console as they arrive

Running the

...

Quartz Example

From a command shell, go to the Basic Quartz example directory:

cd [servicemix_install_dir]\examples\basicquartz-binding

Then type:

[servicemix_install_dir]\bin\servicemix servicemix.xml

where servicemix_install_dir is the directory in which ServiceMix was installed.

Stopping the

...

Quartz Example

To terminate the Basic example type "CTRL-C" in the command shell in which it is running and answer "y" to the "Terminate batch job (y/n)?" question.

...

The diagram below illustrates the flow of messages through the Basic Quartz components.

Messages flow through the components as follows:

1. The For every 5 seconds the timer component sends a message to inputSender trace through the Normalized Message Router (NMR).
2. inputSender converts the message (marshals it) into a JMS message, then uses the jmsTemplate bean to publish the message.
3. jmsTemplate uses the jmsFactory bean to get a connection to the port associated with the JMS topic called "demo.org.servicemix.source." The message is published on the "demo.org.servicemix.source" topic.
4. jencks (the JCA resource adapter) listens on port 61616 for messages.
5. inputReceiver subscribes to the "demo.org.servicemix.source" topic via jencks and receives the JMS message.
6. inputReceiver normalizes the JMS message and sends it to outputSender via the NMR.
7. outputSender marshals the normalized message to a JMS message and uses jmsTemplate to publish the message on the "demo.org.servicemix.result" topic.
8. jmsTemplate publishes it on the "demo.org.servicemix.result" topic using jmsFactory to get a connection to the result topic.
9. jencks listens on port 61616 for messages.
10. jmsTrace subscribes to the "demo.org.servicemix.result" topic and receives the JMS message via jencks.
11. jmsTrace converts the JMS message into a normalized message and sends it to trace via the NMR.
12. trace transforms the normalized message into a string and logs it to the console.
    

...

1. .

...

1. 
   
   

   Code Block

...

1. [INFO] TraceComponent - -Exchange: org.servicemix.jbi.messaging.InOnlyImpl@4fdf11 received IN message: org.servicemix.jbi.messaging.NormalizedMessageImpl@1be0369{properties: {org.servicemix.jms.message=ACTIVEMQ_TEXT_MESSAGE: id = 0 ActiveMQMessage{ , jmsMessageID = null, bodyAsBytes = org.activemq.io.util.ByteArray@1d1fc02, readOnlyMessage = true, jmsClientID = 'ID:Lisas-2828-1126207917359-23:0' , jmsCorrelationID = 'null' , jmsDestination = demo.org.servicemix.result, jmsReplyTo = null, jmsDeliveryMode = 2, jmsRedelivered = false, jmsType = 'null' , jmsExpiration = 0, jmsPriority = 4, jmsTime stamp = 1126207938593, properties = {}, readOnlyProperties = true, entryBrokerName = 'ID:Lisas-2828-1126207917359-0:0' , entryClusterName = 'default' , consumerNos = [0], transactionId = 'null' , xaTransacted = false, consumerIdentifer = 'ID:Lisas-2828-1126207917359-14:0' , messageConsumed = false, transientConsumed = true, sequenceNumber = 7, deliveryCount = 1, dispatchedFromDLQ = false, messageAcknowledge = org.activemq.ActiveMQSession@1de7497, jmsMessageIdentity = null, producerKey = ID:Lisas-2828-1126207917359-29: }, text = <?xml version="1.0" encoding="UTF-8"?> <timer><name>My Example Job</name><group>ServiceMix</group><fullname>ServiceMix.My Example Job</fullname><description/><fireTime> Thu Sep 08 12:32:18 PDT 2005</fireTime></timer>}}

Details

The following table provides more details about the function of each component and bean in the servicemix.xml file.

...