Page History

...

1. Wiki Markup
   Modify the quartz binding {{servicemix.xml}} file to change it into a service unit. The {{servicemix.xml}} file is located in {{\[servicemix_src_install_dir\]\assembly\target\servicemix-2.0.2\bin\servicemix-2.0.2\examples\quartz-binding}}, where \[servicemix_src_install_dir\] is the directory in which the source distribution of ServiceMix is located.

2. Create a directory elsewhere, such as \temp\JBIcomponent
3. Copy servicemix.xml to \temp\JBIcomponent
4. cd \temp\JBIcomponent
5. Edit the servicemix.xml file. Change the "container" tags to "serviceunit" and save the file. The file should match the following:

   Code Block

   <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://xbean.org/schemas/spring/1.0" xmlns:spring="http://xbean.org/schemas/spring/1.0" xmlns:sm="http://servicemix.org/config/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xbean.org/schemas/spring/1.0 ../../conf/spring-beans.xsd http://servicemix.org/config/1.0 ../../conf/servicemix.xsd" xmlns:my="http://servicemix.org/demo/"> <!-- the JBI container --> <sm:serviceunit spring:id="jbi"> <sm:activationSpecs> <!-- lets kick off a timer every 5 seconds --> <sm:activationSpec componentName="timer" service="my:timer" destinationService="my:trace"> <sm:component> <bean xmlns="http://xbean.org/schemas/spring/1.0" class="org.servicemix.components.quartz.QuartzComponent"> <property name="triggers"> <map> <entry> <key> <bean class="org.quartz.SimpleTrigger"> <property name="repeatInterval" value="5000" /> <property name="repeatCount" value="-1" /> </bean> </key> <bean class="org.quartz.JobDetail"> <property name="name" value="My Example Job" /> <property name="group" value="ServiceMix" /> </bean> </entry> </map> </property> </bean> </sm:component> </sm:activationSpec> <!-- Route the event to a trace component that just outputs the event to the console --> <sm:activationSpec componentName="trace" service="my:trace"> <sm:component> <bean xmlns="http://xbean.org/schemas/spring/1.0" class="org.servicemix.components.util.TraceComponent" /> </sm:component> </sm:activationSpec> </sm:activationSpecs> </sm:serviceunit> </beans>

   This file will be used in a later step.

1. Two jar files must be created. These jar files will be copied into the ServiceMix deploy directory. The first jar file will contain the service component jbi.xml file. When this is copied to the deploy directory it deploys the ServiceMixComponent component. The second jar file will contain the service assembly and the jbi.xml descriptor file. When it is copied to the deploy directory of ServiceMix it deploys the service unit (Quartz) to the previously deployed component, ServiceMixComponent.
   1. The file service component jbi.xml file should contain:

      Code Block

      <jbi xmlns="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/jbi" version="1.0"> <component type="service-engine"> <identification> <name>servicemix-component</name> <description>A ServiceMix Component that can be used to deploy servicemix.xml artifacts.</description> </identification> <component-class-name>org.servicemix.components.servicemix.ServiceMixComponent</component-class-name> <component-class-path/> </component> </jbi>

   2. Put jbi.xml in an empty META-INF directory and put that into a jar file:

      Code Block
      mkdir META-INF copy jbi.xml META-INF jar cvf service-component.jar *

   3. Create a zip file of the servicemix.xml file you modified above. The zip file should contain the servicemix.xml file and it should be called su1.zip to match the name it is called in the jbi.xml file. See the artifacts-name tag in the jbi.xml file for the name of the zip file.
   4. Create the second jar file--this is the service assembly jar file. It will contain another jbi.xml file that is used for the service assembly and it will also contain the zip file, su1.zip in the following structure:
      The service assembly jbi.xml should be match the following:

      Code Block

      <jbi xmlns="http://java.sun.com/xml/ns/jbi" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/jbi" version="1.0"> <service-assembly> <identification> <name>AU_1</name> <description>Sample AU</description> </identification> <service-unit> <identification> <name>SU_1</name> <description>Sample</description> </identification> <target> <artifacts-zip>su1.zip</artifacts-zip> <component-name>servicemix-component</component-name> </target> </service-unit> </service-assembly> </jbi>

      Copy the jbi.xml file to an empty META-INF directory, then create the jar file:

      Code Block
      In a directory which contains these files, create the jar file: META-INF/jbi.xml su1.zip jar cvf sa_quartz.jar *

2. Wiki Markup
   Deploy the two jar

   files. only this file to the deploy directory on 2.0.3-SNAPSHOT and get:

   Code Block
   [INFO] JBIContainer - Activating component for: [container=defaultJBI,name=servicemix-component,id=servicemix-component] with service: null component: org.servicemix.components.servicemix.ServiceMixComponent@1a1bc40 ServiceMixComponent: init [INFO] AutoDeploymentService - Directory: deploy: Finished installation of archive: service-component.jar

   Then I copy the sa_quartz.jar file in: Code Block

3. Wiki Markup
   Finally, to *deploy*, copy sa_quartz.jar and service-component.jar to the {{deploy}} directory of ServiceMix. The deploy directory is located in {{\[servicemix_install_dir\]\deploy}}, where {{\[servicemix_install_dir\]}} is the location in which ServiceMix was installed.

4. If ServiceMix is already running, look at the console window output to see the deployment. If ServiceMix has not been started, start it and monitor the console window output.

Deploying Components on servicemix-web.war

Deploying JBI Components on Geronimo Using the Geronimo Deployment Tool

...

1. files. Copy {{service_component.jar}} and {{sa_quartz.jar}} to {{\[servicemix_src_install_dir\]\assembly\target\servicemix-2.0.\bin\servicemix-2.0.2\deploy}}. This can be done while ServiceMix is running or while ServiceMix is not running. In the second case, run ServiceMix to see the deployment. Output will be similar to:

   Code Block

   h3. Deploying Components on servicemix-web.war This section is on hold until the Jira issue: is fixed. h3. Deploying JBI Components on Geronimo Using the Geronimo Deployment Tool This section discusses using the Geronimo deployment tool to deploy components. This is separate from the previous sections dealing with the servicemix-web.war file. When the deployment tool is fully developed this will be the preferred method. Currently only geronimo-1.0-SNAPSHOT can be used to perform this method.

...

1. The JBI spec describes in detail how to create a valid JBI deployment unit. In essence, it is a jar file with a META-INF/jbi.xml with other resource jars inside it. Please see [Deployment Units] for more information.

...

1. # Make sure that your geronimo server is running.

   # Run the geronimo deploy tool against your deployment unit (in this case jbcomponent.jar):
   Code Block

   java -jar geronimo-1.0-SNAPSHOT/bin/deployer.jar --user system --password manager deploy jbcomponent.jar

   Code Block
   That should deploy the component to geronimo. To check, just take a look at the geronimo logs for a message similar to:

...

...

1. 11:44:24,865

...

1. INFO

...

1. Configuration

...

1. Started

...

1. configuration

...

1. example-engine-1

...

1. 
   11:44:24,869

...

1. INFO

...

1. ServiceMixDeployment

...

1. Starting:

...

1. /Users/chirino/sandbox/geronimo/modules/assembly/target/geronimo-1.0-SNAPSHOT/config-store/20/META-INF/jbi.xml

...

1. 
   ...

...

1. 
   11:44:25,783

...

1. INFO

...

1. DefaultListableBeanFactory

...

1. Creating

...

1. shared

...

1. instance

...

1. of

...

1. singleton

...

1. bean

...

1. 'jbi'

...

1. Code Block

Related Documentation

• Geronimo
• Tomcat Integration.

...