ServiceMix Chinese Course

http://blog.csdn.net/neusoftware_20063500/article/details/4047253

Link: http://blog.csdn.net/juset/archive/2006/12/18/1447626.aspx

1.http-binding (ServiceMix)

1.4 The process of passing message flows between components is as follows:

1. The Httpclient:http client runs a separate Java client program that connects the Request.xml file to the http://localhost:8912 through the URLConnection class in which it is sent to the port.

2. Httpreceiver: On the HTTP server (HTTP server), Httpreceiver gets this message by listening on the http://localhost:8912 port.

3. Httpreceiver sends this message through NMR to the corresponding StockQuote service according to the information in the Destinationservice (target service) attribute of the message.

4. StockQuote again sends this message to another service--soapendpoint to process.

5. After soapendpoint processing, the response message is returned to StockQuote.

6. StockQuote sent the corresponding message to httpreceiver through NMR.

7. Httpreceiver sends the corresponding message to the http://localhost:8912 port.

8. HttpClient reads the response message from the port.

9. The final response message is in the console output.

2.jms-binding (ServiceMix)

The 2.4 message flow connects to a topic called "Demo.org.servicemix.source" and sends a text message through the various components: JMSClient, through Activemqconnectionfactory. Jencks (JCA resource adapter) listens for messages on port 61616 inputreceiver Jencks Subscribe to the "Demo.org.servicemix.source" topic and receive JMS messages Inputreceiver normalizes the JMS message and sends it to the Outputsender Outputsender Outputsender by normalizing the message router (NMR) to marshal the normalized message as a JMS message. and use Jmstemplate to publish the message on the "Demo.org.servicemix.result" topic. Jmstemplate publishes a message on the "Demo.org.servicemix.result" topic, using Jmsfactory to obtain a connection to the resulting theme. JMSClient, "Demo.org.servicemix.result," another subscriber to the subject receives the message. The response is printed on the console.

 

3.BPEL Example (servicemix)

3.5 Logical flow of programs:

1. JMSClient, connected to a theme called "Demo.org.servicemix.source" via Activemqconnectionfactory, and sends a containing MESSAGE.SOAP A text message for file.

2. mycomponent, "Demo.org.servicemix.source," a subscriber to the subject, receives the message.

3. the MyComponent implementation class, Jmsservicecomponent, sends a message to Pxebpelengine via the ServiceMix bus and executes its onmessage () method. Destinationservice attribute to the destination of the message. Note: The Destinationservice property is in the file servicemix.xml.

4. Pxebpelengine sends a response to MyComponent via ServiceMix bus and NMR.

5. MyComponent Use the jmstemplate bean to publish the message.

6. Jmstemplate uses jmsfactory beans to get a to and JMS topic "Demo.org.servicemix.source." Connection to the associated port. This message is posted on the "Demo.org.servicemix.source" topic.

7. JMSClient, "Demo.org.servicemix.source," the subject of the Subscriber, receive this message.

8. The response is printed on the console.

4.rss-binding (ServiceMix)

 

5.File binding (ServiceMix)

5.4 Logical flow of programs:

1. Filepoller per 1000ms Retrieve inbox directory find one file at a time

2. Once a file is found in the Inbox directory, Filepoller obtains a thread from the Workmanager. This thread is used to process this file.

3. Filepoller creates a normalized message containing the file to be transmitted, which sends the normalized message to the NMR. NMR routes this message to the Filesender component.

4. Filesender converts the normalized message to a file and "sends" (puts) to the Outbox directory.

Log information is written to the console during file transfer.

6.Basic (ServiceMix)

The 6.4 message flow passes through the various components in the following ways:

1. The Timer component sends a message to Inputsender through normalized message routing (NMR).

2. Inputsender the message conversion (marshals) as a JMS message, and then publishes the message with the Jmstemplate bean.

3. Jmstemplate uses Jmsfactorybean to obtain a and JMS theme "Demo.org.servicemix.source." Connection to the associated port. This message is posted on the "Demo.org.servicemix.source" topic.

4. Jencks (the JCA resource adapter) listens for messages on port 61616

5. Inputreceiver subscribe to the "Demo.org.servicemix.source" topic and receive JMS messages via Jencks

6. Inputreceiver normalizes the JMS message and sends it to Outputsender via NMR

7. Outputsender Marshal the normalized message as a JMS message and uses Jmstemplate to publish the message on the "Demo.org.servicemix.result" topic.

8. Jmstemplate publishes a message on the "Demo.org.servicemix.result" topic, using Jmsfactory to obtain a connection to the resulting subject.

9. Jencks listens for messages on port 61616.

Jmstrace subscribes to the "Demo.org.servicemix.result" topic and receives JMS messages through Jencks.

Jmstrace converts a JMS message to a normalized message and sends it to trace via NMR.

Trace converts normalized messages into a string and logs them on the console.

Write a log on the console every 5 seconds, as well as information from the trace component. Note that in future Ggers&apos, the property value is "First Name" "My sample Work" group, "ServiceMix" is displayed with a timestamp.

7.quartz-binding (ServiceMix)

http://servicemix.apache.org/