Versions Compared

Old Version 33

changes.mady.by.user Unknown User (lmalgeri)

Saved on

compared with

New Version 34

changes.mady.by.user Unknown User (lmalgeri)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The JMSClient through ActiveMQConnectionFactory connects to topic "demo.org.servicemix.source" and sends a text message from containing the message.soap file.
  2. myComponent, being a subscriber of the topic "demo.org.servicemix.source", receives the message.
  3. The myComponent implementation class, JmsServiceComponent, sends the message over the ServiceMix bus to the PxeBpelEngine by executing its onMessage method. The destinationService property defines the destination of the message (destinationService is found in the servicemix.xml file).
  4. PxeBpelEngine sends a response again back to myComponent through the SericeMix bus, the NMR.
  5. myComponent uses the jmsTemplate bean to publish the message.
  6. 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.
  7. JMSClient being a subscriber of topic "demo.org.servicemix.source", receives the message.

Logginginformation Logging information is written to the console as files are transmitted. Typical output looks like the following:

Code Block
 
 
ServiceMix ESB: 1.0.1

Loading ServiceMix from file: servicemix.xml
[INFO] XmlBeanDefinitionReader - -Loading XML bean definitions from file [C:\Program Files\servicemix-1.0.1\examples\file-binding\servicemi.xml]
[INFO] FileSystemXmlApplicationContext - -Bean factory for application context [org.springframework.context.support.FileSystemXmlApplication
Context;hashCode=7486844]: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [workManager,jbi]; root of BeanFactory hierarchy
[INFO] FileSystemXmlApplicationContext - -2 beans defined in application context 
[org.springframework.context.support.FileSystemXmlApplicationContext;hashCode=7486844]
[INFO] CollectionFactory - -JDK 1.4+ collections available
[INFO] CollectionFactory - -Commons Collections 3.x available
[INFO] FileSystemXmlApplicationContext - -Unable to locate MessageSource with name 'messageSource': using default [org.springframework.conte
xt.support.DelegatingMessageSource@1d6776d]
[INFO] FileSystemXmlApplicationContext - -Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using defaul
t [org.springframework.context.event.SimpleApplicationEventMulticaster@4fce71]
[INFO] DefaultListableBeanFactory - -Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanF
actory defining beans [workManager,jbi]; root of BeanFactory hierarchy]
[INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'workManager'
[INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'jbi'
Created MBeanServer with ID: 203c31:106bd250a5b:-7fff:Lisas:1
[INFO] SpringInitialContextFactory - -Loading JNDI context from: class path resource [jndi.xml]
[INFO] XmlBeanDefinitionReader - -Loading XML bean definitions from class path resource [jndi.xml]
[INFO] XmlBeanFactory - -Creating shared instance of singleton bean 'jndi'
RMIConnectorServer started at: service:jmx:rmi://lisas/jndi/rmi://localhost:1099/defaultJBIJMX
[INFO] JBIContainer - -ServiceMix JBI Container (http://servicemix.org/) name: defaultJBI running version: ServiceMix.
[INFO] JBIContainer - -Activating component for: [container=defaultJBI,name=fileSender,id=fileSender] with service: fileSender component: org.servicemix.components.file.FileWriter@b1cc87
[INFO] ComponentContextImpl - -Component: fileSender activated endpoint: fileSender : fileSender
[INFO] JBIContainer - -Activating component for: [container=defaultJBI,name=filePoller,id=filePoller] with service: filePoller component: or
g.servicemix.components.file.FilePoller@183e7de
[INFO] ComponentContextImpl - -Component: filePoller activated endpoint: filePoller : filePoller
[INFO] DeliveryChannel - -default destination serviceName for filePoller = fileSender

...

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

Component or Bean ID
Description
 myComponent 
 This JMS service component subscribes to the "demo.org.servicemix.source" topic via its defaultDestinationName property specified on the servicemix.xml configuration file. Through its template property, it uses JmsFactory to listen on port 61616 via ActiveMQConnectionFactory. It is implemented by the JmsServiceComponent that has an onMessage method which is called by ActiveMQ when a message arrives on the topic. This method creates a NormalizedMessagenormalized message, which is sent over the servicemix ServiceMix bus to the PxeBpelEngine as specified on its destinationService property.
 JMSClient 
 This program through ActiveMQConnectionFactory connects to topic "demo.org.servicemix.source". It then create a text message from the file message.soap and publish it to the topic "demo.org.servicemix.source" at the same time requesting for a response. It eventually prints the response to the console.
 JNDI 
 Loads database and transaction manager resources, which will be used by the other components in the system.
 Pxe-install.jar 
 This jarfile is located in the examples/bpel/install directory. It contains many jarfiles, which contain the classes that implement the PXE BPEL engine. It also contains a jbi.xml file, which is used by servicemix to install the PXE BPEL engine as a servicemix service-engine component. Note that in this file, the component type is "service-engine" and the component name is "PxeBpelEngine." When processes are deployed to the PXE (see next section with AsyncProcess-sa.jar), it exposes them as services on the jbi, which can be referenced by other components as destinationService(s), with destinationEnpoint(s) (see the servicemix.xml file) 
 AsyncProcess-sa.jar 
 This jarfile is located in the examples/bpel/deploy directory. It contains a jbi.xml file, which refences the PxeBpelEngine. This ties the processes to the PXE ENGINE described in the previous section. The jbi.xml file also references the AsyncProcess-su.zip file, which is also contained in the AsycnProcess-sa.jar file. This zipfile contains other configuration files and WSDL files (i.e. pxe-system.xml and resource_X.stream), which describe the services deployed on the PXE.
 broker 
 The broker bean uses the activemq.xml file to configure the message broker, which handles the JMS messages for the components that require JMS messaging services. 
 transactionManager 
 This bean is configured to be the default transaction manager for the jbi container. jencks is configured to use the default transaction manager. This transaction manager provides transactional services between the resource adapter (in this case the ActiveMQ resource adapter provided by the jencks JCA container) and components the jbi container. 
 jmsFactory 
 This bean listens on port 61616 and provides a pooled ActiveMQ connection. 
...