...
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 property properties installationDirPath and deploymentDirPath defined in |
JMSClient | This Java standalone program, through the ActiveMQConnectionFactory, connects to topic "demo.org.servicemix.source." . It then create 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 the |
JNDI | This bean loads up 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 |
AsyncProcess-sa.jar | This jarfile is located in the examples/bpel/deploy directory. It contains a jbi.xml file, which references 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. |
...