Versions Compared

Old Version 26

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

Saved on

compared with

New Version 27

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

Saved on

Key

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

...

This is the component in which the JMS binding connects to. PXE is a runtime component for executing processes defined by the BPEL4WS 1.1 specification and forthcoming WS-BPEL 2.0 OASIS standard. PXE BPEL engine uses JMX to provide management and introspection functionality. Business Process Execution Language (BPEL) defines a notation for specifying business process behavior
based on Web Services.

Component or Bean ID

Description

myComponent

This JMS binding 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. When it receives a message, it sends it to PXE BPEL engine as specified on destinationService property

pxe:ProcessSVC

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.

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) |

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.

...