Versions Compared

Old Version 1

changes.mady.by.user Gert Vanthienen

Saved on

compared with

New Version 2

changes.mady.by.user Gert Vanthienen

Saved on

Key

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

...

However, the console output seems to indicate that something is not right with this service assembly. Can you figure out what is happening?

No Format

INFO  - AutoDeploymentService          - Directory: deploy: Archive changed: processing bridge-sa-3.2-incubating-SNAPSHOT.zip ...
WARN  - AutoDeploymentService          - Components servicemix-jms, servicemix-saxon, servicemix-eip are not installed yet: the service assembly bridge-sa deployment is suspended and will be resumed once the listed components are installed
INFO  - AutoDeploymentService          - Directory: deploy: Finished installation of archive:  bridge-sa-3.2-incubating-SNAPSHOT.zip

Components

ServiceMix tells you to install additional components. This example requires additional features from the ESB, so you will need to install these as additional JBI components:

...

No Format
INFO  - AutoDeploymentService          - Directory: install: Archive changed: processing servicemix-jms-3.2-incubating-SNAPSHOT-installer.zip ...
INFO  - ComponentMBeanImpl             - Starting component: servicemix-jms
INFO  - ComponentMBeanImpl             - Initializing component: servicemix-jms
INFO  - AutoDeploymentService          - Directory: install: Finished installation of archive:  servicemix-jms-3.2-incubating-SNAPSHOT-installer.zip
INFO  - AutoDeploymentService          - Directory: install: Archive changed: processing servicemix-eip-3.2-incubating-SNAPSHOT-installer.zip ...
INFO  - ComponentMBeanImpl             - Starting component: servicemix-eip
INFO  - ComponentMBeanImpl             - Initializing component: servicemix-eip
INFO  - AutoDeploymentService          - Directory: install: Finished installation of archive:  servicemix-eip-3.2-incubating-SNAPSHOT-installer.zip
INFO  - AutoDeploymentService          - Directory: install: Archive changed: processing servicemix-saxon-3.2-incubating-SNAPSHOT-installer.zip ...
INFO  - ComponentMBeanImpl             - Starting component: servicemix-saxon
INFO  - ComponentMBeanImpl             - Initializing component: servicemix-saxon
INFO  - ServiceAssemblyLifeCycle       - Starting service assembly: bridge-sa
INFO  - ServiceUnitLifeCycle           - Initializing service unit: bridge-http-su
INFO  - ServiceUnitLifeCycle           - Initializing service unit: bridge-eip-su
INFO  - ServiceUnitLifeCycle           - Initializing service unit: bridge-xslt-su
INFO  - ServiceUnitLifeCycle           - Initializing service unit: bridge-jms-su
INFO  - ServiceUnitLifeCycle           - Starting service unit: bridge-http-su
INFO  - ServiceUnitLifeCycle           - Starting service unit: bridge-eip-su
INFO  - ServiceUnitLifeCycle           - Starting service unit: bridge-xslt-su
INFO  - ServiceUnitLifeCycle           - Starting service unit: bridge-jms-su
INFO  - AutoDeploymentService          - Directory: install: Finished installation of archive:  servicemix-saxon-3.2-incubating-SNAPSHOT-installer.zip

Service assembly

Not only does the logging show you that ServiceMix started the three components you just installed, it also continued the deployment of the bridge-sa-<version>.zip service assembly automatically. If you point your browser at http://localhost:8192Image Added now, you should see that the additional service is now also available.

Testing and verifying the result with JMX

You can now go ahead and test this service assembly. The distribution also comes with an HTML page to help you test this service assembly. You find this page in <servicemix_home>/examples/bridge/client.html. If you click the send button in the left side of the page, you should get an message STATUS: 202 in the right side, indicating that the request has completed successfully.

The message has been sent to ActiveMQ, the embedded JMS server in ServiceMix. If you connect to ServiceMix using JMX, you can also use the MBean view to navigate to the ActiveMQ Queue information. The attributes for the bridge.output queue show the number of messages that have been received by this queue. Verify that the queue has received your message.
Image Added

While you are using the JMX console, try to find the JBI components and service assembly you have just installed in there. We have learned how to do so in 1.4. Tutorial - Using JMX to look inside the ESB.Now that all required components have been installed on the JBI container, you can deploy the

Further reading