...
- From a command shell, go to the BPEL example directory:
whereCode Block cd [SM:servicemix_install_dir]\examples\bpel
servicemix_install_dir
is the directory in which ServiceMix was installed. - Then type:
Code Block [SM:servicemix_install_dir]\bin\servicemix servicemix.xml OR ..\..\bin\servicemix servicemix.xml
- 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.Tip title Handy Hint Add $SERVICEMIX_HOME\bin directory to $PATH variable to simplify execution of the example.
...
Code Block |
---|
ServiceMix ESB: 1.0 Loading ServiceMix from file: servicemix.xml [SM:INFO] XmlBeanDefinitionReader - -Loading XML bean definitions from file C:\exist\servicemix\servicemix-1.0.1\examples\bpel\servicemix.xml] [SM:INFO] CollectionFactory - -JDK 1.4+ collections available [SM:INFO] CollectionFactory - -Commons Collections 3.x available [SM:INFO] FileSystemXmlApplicationContext - -Bean factory for application context [SM:org.springframework.context.support.FileSystemXmlApplicationContext;hashCode=110 2920]: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [SM:jndi,broker,transactionManager,jmsFactory,jbi]; root of BeanFactory hierarchy[SM:INFO] FileSystemXmlApplicationContext - -5 beans defined in application context [SM:org.springframework.context.support.FileSystemXmlApplicationContext;hashCode=1102920] [SM:INFO] FileSystemXmlApplicationContext - -Unable to locate MessageSource with name 'messageSource': using default [SM:org.springframework.context.support.DelegatingMessageSource@18e2b22] [SM:INFO] FileSystemXmlApplicationContext - -Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using default [SM:org.springframework.context.event.SimpleApplicationEventMulticaster@13caecd] [SM:INFO] DefaultListableBeanFactory - -Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [SM:jndi,broker,transactionManager,jmsFactory,jbi]; root of BeanFactory hierarchy] [SM:INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean'jndi' [SM:INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'broker' [SM:INFO] SpringBrokerContainerFactory - -Loading ActiveMQ broker from configuration: class path resource [SM:activemq.xml] [SM:INFO] ActiveMQBeanDefinitionReader - -Loading XML bean definitions from class path resource [SM:activemq.xml] [SM:INFO] ActiveMQBeanFactory - -Creating shared instance of singleton bean 'broker' [SM:INFO] ActiveMQBeanFactory - -Creating shared instance of singleton bean 'memoryManager' [SM:INFO] ActiveMQBeanFactory - -Creating shared instance of singleton bean 'derby-ds' [SM:INFO] ActiveMQBeanFactory - -Creating shared instance of singleton bean 'mysql-ds' [SM:INFO] BrokerContainerImpl - -ActiveMQ 3.1-M6 JMS Message Broker (ID:el2tong-1095-1129854563062-0:0) is starting [SM:INFO] BrokerContainerImpl - -For help or more information please see: http://www.logicblaze.com [SM:INFO] JDBCPersistenceAdapter - -Database driver recognized: [SM:apache_derby_embedded_jdbc_driver] [SM: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 [SM: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 [SM: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 [SM: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 [SM:INFO] JournalPersistenceAdapter - -Opening journal. [SM:INFO] JournalPersistenceAdapter - -Opened journal: Active Journal: using 2 x 20.0 Megs at: ..\var\journal [SM:INFO] JournalPersistenceAdapter - -Journal Recovery Started. [SM:INFO] JournalPersistenceAdapter - -Journal Recovered: 0 message(s) in transactions recovered. [SM:INFO] TcpTransportServerChannel - -Listening for connections at: tcp://el2tong:61616 [SM:INFO] BrokerConnectorImpl - -ActiveMQ connector started: TcpTransportServerChannel@tcp://el2tong:61616 [SM:INFO] BrokerContainerImpl - -ActiveMQ JMS Message Broker (ID:el2tong-1095-1129854563062-0:0) has started [SM:INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'transactionManager' [SM:INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'jmsFactory' [SM:INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'jbi' [SM:INFO] ActiveMQConnection - -channel status changed: Channel: TcpTransportChannel: Socket[SM:addr=localhost/127.0.0.1,port=61616,localport=1096] has connected [SM:INFO] BrokerContainerImpl - -Adding new client: ID:el2tong-1095-1129854563062-5:0 on transport: TcpTransportChannel: Socket[SM:addr=/127.0.0.1,port=1096,localport=61616] [SM:INFO] JBIContainer - -ServiceMix JBI Container (http://servicemix.org/) name: defaultJBI running version: ServiceMix. [SM:INFO] JBIContainer - -Activating component for: [SM:container=defaultJBI,name=myComponent,id=myComponent] with service: {uri:fivesight.com/examples/AsyncProcessJBI}JmsService component: org.servicemix.components.jms.JmsServiceComponent@1b82d69 [SM:INFO] ComponentContextImpl - -Component: myComponent activated endpoint: {uri:fivesight.com/examples/AsyncProcessJBI}JmsService : myComponent |
...