Page History

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 NormalizedMessage, which is sent over the 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.