...
This document describes how to run ServiceMix's BPEL example and provides details about what it does. For information on the business use case, please refer to: Use Case for BPEL.
The BPEL example illustrates the following:
- an example of declarative programming
- how to perform BPEL integration with ServiceMix
- shows the how to use of JmsTemplate for publishing and subscribing to ActiveMQ topics
...
This example has a client application (, JMSClient) , which sends a SOAP message to a JmsServiceComponent (myComponent) which ServiceMix binding component called myComponent. myComponent forwards the request to the PXE BPEL engine and waits for a response. The client is placing In other words, JMSClient places a book order and the ServiceMix binding component myComponent receives the order and then sends it to the Webservice that takes orders. The client, JMSClient, and the binding component (, myComponent) , communicate via JMS. The binding component (myComponent) ; this communication is external to the ServiceMix JBI. myComponent and the PXE BPEL service engine communicate internally over the Normalized Mesage Message Router (NMR). A simple JMS client is provided so that messages can sent and received from the JMSService. This example uses PXE integration to demonstrate the use of BPEL with ServiceMix.
Prerequisites to Run the BPEL Example
...
- Java Standard Edition 5.0
- Ant - http://ant.apache.org
.
- PXE - We support WS-BPEL via the PXE BPEL Engine from FiveSight.
Warning title Warning
...
NOTE: ServiceMix works on any Java SE 1.4 or later environment; however to use PXE
...
a Java SE 5 or later platform
...
is required. Before running this example, use Java 1.5 to
...
start up ServiceMix.
Running the BPEL Example
First, run ServiceMix with a JNDI context configured so that PXE can be deployed.
Before running this example, the following setup must be done. PXE has a JBI component and deployment unit, which can be auto-deployed in any JBI compliant container, in this case ServiceMix. To use PXE with ServiceMix put , the PXE deployment unit into must be placed in the install
directory in the BPEL example directory and the component so it will be auto-deployed in ServiceMix. This NOTE: The PXE deployment unit has already been done - look in placed into the install
directory under for you - take a look at the servicemix_install_dir\examples\bpel\install
directory to see the PXE jar file.
Perform the following steps to run the BPEL example:
- From a command shell, go to the BPEL example directory:
whereCode Block cd [servicemix_install_dir]\examples\bpel
servicemix_install_dir
is the directory in which ServiceMix was installed. - Then type:
Code Block [servicemix_install_dir]\bin\servicemix servicemix.xml OR ..\..\bin\servicemix servicemix.xml
You should now have PXE deployed with a JBI service engine together with a deployment unit for a specific BPEL process.
...
- To trigger the BPEL business process, send it some messages. To do this, compile and run a simple JMS client. The client is built and run from source code using Ant. Execute
...
- Ant from the BPEL
...
- directory
...
- :
servicemix_install_dir\examples\bpel
...
- . To run the JMS client type:
Code Block ant
Ant will compile and run the simple JMS client, JMSClient, which performs a JMS based request-response into the ServiceMix container before returning the results to the console.
Stopping the BPEL Example
To terminate the BPEL 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 logical flow of the program through the BPEL components.:
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
...
The logical flow of the program is:
- The JMSClient, through ActiveMQConnectionFactory, connects to the topic named "demo.org.servicemix.source" and sends a text message from containing the
message.soap
file. - myComponent, being a subscriber of the topic "demo.org.servicemix.source," , receives the message.
- 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 (. NOTE: the destinationService property is found in the
servicemix.xml
file. - PxeBpelEngine sends a response again through SericeMix back to myComponent through the ServiceMix bus, the NMR.
- myComponent uses the jmsTemplate bean to publish the message.
- 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.
- JMSClient, being a subscriber of topic "demo.org.servicemix.source," , receives the message.
- The response is printed on the console.
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:\exist\Program Filesservicemix\servicemix-1.0.1\examples\file-bindingbpel\servicemiservicemix.xml] [INFO] CollectionFactory - -JDK 1.4+ collections available [INFO] CollectionFactory - -Commons Collections 3.x available [INFO] FileSystemXmlApplicationContext - -Bean factory for application context [org.springframework.context.support.FileSystemXmlApplication ContextFileSystemXmlApplicationContext;hashCode=7486844110 2920]: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [workManager [jndi,broker,transactionManager,jmsFactory,jbi]; root of BeanFactory hierarchy [INFO] FileSystemXmlApplicationContext - -25 beans defined in application context [org.springframework.context.support.FileSystemXmlApplicationContext;hashCode=74868441102920] [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 xtcontext.support.DelegatingMessageSource@1d6776dDelegatingMessageSource@18e2b22] [INFO] FileSystemXmlApplicationContext - -Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using defaul tdefault [org.springframework.context.event.SimpleApplicationEventMulticaster@4fce71SimpleApplicationEventMulticaster@13caecd] [INFO] DefaultListableBeanFactory - -Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFDefaultListableBeanFactory actory defining beans [workManagerjndi,broker,transactionManager,jmsFactory,jbi]; root of BeanFactory hierarchy] [INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'workManagerjndi' [INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'jbi' Created MBeanServer with ID: 203c31:106bd250a5b:-7fff:Lisas:1broker' [INFO] SpringInitialContextFactorySpringBrokerContainerFactory - -Loading JNDIActiveMQ contextbroker from configuration: class path resource [jndiactivemq.xml] [INFO] XmlBeanDefinitionReaderActiveMQBeanDefinitionReader - -Loading XML bean definitions from class path resource [jndiactivemq.xml] [INFO] XmlBeanFactory ActiveMQBeanFactory - -Creating shared instance of singleton bean 'broker' [INFO] ActiveMQBeanFactory - -Creating shared instance of singleton bean 'memoryManager' [INFO] ActiveMQBeanFactory - -Creating shared instance of singleton bean 'derby-ds' [INFO] ActiveMQBeanFactory - -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 : fileSendermysql-ds' [INFO] BrokerContainerImpl - -ActiveMQ 3.1-M6 JMS Message Broker (ID:el2tong-1095-1129854563062-0:0) is starting [INFO] BrokerContainerImpl - -For help or more information please see: http://www.logicblaze.com [INFO] JDBCPersistenceAdapter - -Database driver recognized: [apache_derby_embedded_jdbc_driver] [INFO] DefaultJDBCAdapter - -Could not create JDBC tables; they could already exist. Failure was: CREATE TABLE ACTIVEMQ_MSGS(ID INTEGER NOT NULL, CONTAINER VARCHAR(250), MSGID VARCHAR(250), MSG BLOB, PRIMARY KEY ( ID ) ) Message: Table/View 'ACTIVEMQ_MSGS' already exists in Schema 'APP'. SQLState: X0Y32 Vendor code: 20000 [INFO] DefaultJDBCAdapter - -Could not create JDBC tables; they could already exist. Failure was: CREATE TABLE ACTIVEMQ_TXS(XID VARCHAR(250) NOT NULL, PRIMARY KEY ( XID )) Message: Table/View 'ACTIVEMQ_TXS' already exists in Schema 'APP'. SQLState: X0Y32 Vendor code: 20000 [INFO] DefaultJDBCAdapter - -Could not create JDBC tables; they could already exist. Failure was: CREATE TABLE ACTIVEMQ_ACKS(SUB VARCHAR(250) NOT NULL, CONTAINER VARCHAR(250) NOT NULL, LAST_ACKED_ID INTEGER, SE_ID INTEGER, SE_CLIENT_ID VARCHAR(250), SE_CONSUMER_NAME VARCHAR(250), SE_SELECTOR VARCHAR(250), PRIMARY KEY ( SUB, CONTAINER )) Message: Table/View 'ACTIVEMQ_ACKS' already exists in Schema 'APP'. SQLState: X0Y32 Vendor code: 20000 [INFO] DefaultJDBCAdapter - -Could not create JDBC tables; they could already exist. Failure was: ALTER TABLE ACTIVEMQ_MSGS ADD EXPIRATION BIGINT Message: Column 'EXPIRATION' already exists in Table/View 'APP.ACTIVEMQ_MSGS'. SQLState: X0Y32 Vendor code: 20000 [INFO] JournalPersistenceAdapter - -Opening journal. [INFO] JournalPersistenceAdapter - -Opened journal: Active Journal: using 2 x 20.0 Megs at: ..\var\journal [INFO] JournalPersistenceAdapter - -Journal Recovery Started. [INFO] JournalPersistenceAdapter - -Journal Recovered: 0 message(s) in transactions recovered. [INFO] TcpTransportServerChannel - -Listening for connections at: tcp://el2tong:61616 [INFO] BrokerConnectorImpl - -ActiveMQ connector started: TcpTransportServerChannel@tcp://el2tong:61616 [INFO] BrokerContainerImpl - -ActiveMQ JMS Message Broker (ID:el2tong-1095-1129854563062-0:0) has started [INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'transactionManager' [INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'jmsFactory' [INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'jbi' [INFO] ActiveMQConnection - -channel status changed: Channel: TcpTransportChannel: Socket[addr=localhost/127.0.0.1,port=61616,localport=1096] has connected [INFO] BrokerContainerImpl - -Adding new client: ID:el2tong-1095-1129854563062-5:0 on transport: TcpTransportChannel: Socket[addr=/127.0.0.1,port=1096,localport=61616] [INFO] JBIContainer - -ServiceMix JBI Container (http://servicemix.org/) name: defaultJBI running version: ServiceMix. [INFO] JBIContainer - -Activating component for: [container=defaultJBI,name=filePollermyComponent,id=filePollermyComponent] with service: filePoller{uri:fivesight.com/examples/AsyncProcessJBI}JmsService component: or gorg.servicemix.components.filejms.FilePoller@183e7deJmsServiceComponent@1b82d69 [INFO] ComponentContextImpl - -Component: filePollermyComponent activated endpoint: filePoller : filePoller [INFO] DeliveryChannel - -default destination serviceName for filePoller = fileSender |
...
{uri:fivesight.com/examples/AsyncProcessJBI}JmsService : myComponent
|
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 | ||
---|---|---|---|
jbi | jbi is the "id" of the JBI container and provides the basic infrastructure services for myComponent. During initialization, several singletons are instantiated: transactionManager, broker, jmsFactory, and jbi. Also, take note of the properties installationDirPath and deploymentDirPath defined in | ||
JMSClient | This Java standalone program, through the ActiveMQConnectionFactory, connects to topic "demo.org.servicemix.source." It then creates a text message from the file | ||
myComponent | This JMS service component subscribes to the "demo.org.servicemix.source" topic via its defaultDestinationName property specified on in the | ||
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 | This bean loads up | JNDI | Loads database and transaction manager resources, which will be used by the other components in the system. More importantly, the JNDI context must be configured so that PXE can be deployed. |
Pxe-install.jar | This jarfile is located in the | ||
AsyncProcess-sa.jar | This jarfile is located in the | ||
broker | The broker bean uses the | ||
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 in the jbi container. | ||
jmsFactory | This bean listens on port 61616 and provides a pooled ActiveMQ connection. |
Summarizing, when the ServiceMix container instantiates an MBean it firsts sets the property values if there are any, then calls the init() method of the class and its' parent classes, if applicable. Then it calls the start() method of the class. When a Spring bean starts up, the properties are set and then the afterPropertiesSet() method is called.
Related Documentation
For more information on the following topics please see: