...
- Geronimo must be downloaded and installed. For instructions please see the Geronimo web site. In the Geronimo release of geronimo-1.0-M5 or greater, Tomcat is integrated with Geronimo. By default, Tomcat uses port 8080. This information will be used later.
- Download the ServiceMix source code. Please see the Getting Started guide for instructions.
- Create the WAR file:
Code Block |
---|
cd [servicemix_install_dir]\tooling\servicemix-web
maven war
|
Wiki Markup |
---|
where {{servicemix_install_dir
}} is the directory in which ServiceMix was downloaded and installed. The war file can be found in {{\[servicemix_install_dir
\]\tooling\servicemix-web\target\servicemix-web.war
}}. - To deploy the ServiceMix WAR file on Geronimo, use the Geronimo
deployer.jar
tool found in the bin
directory of the Geronimo base directory.
From a command shell: Code Block |
---|
cd [geronimo_install_dir]
java -jar bin/deployer.jar --user system --password manager deploy [servicemix-2.0.x_install_dir]\tooling\servicemix-web\target\servicemix-web.war
|
You will see output similar to this: Code Block |
---|
Deployed servicemix-web @ http://Lisas:8080/servicemix-web
|
The output in the Geronimo console window should show ServiceMix starting. Output will be similar to the following. This WAR file was not developed for use on Geronimo, but for use on Tomcat stand-alone, therefore, it does not contain a geronimo-web.xml deployment plan. For using the servicemix-web.war
file on Tomcat, please see Tomcat Integration. Code Block |
---|
...
Geronimo Application Server started
13:13:17,062 WARN [JettyModuleBuilder] Web application does not contain a WEB-INF/geronimo-web.xml deployment plan. This may or may not
a problem, depending on whether you have things like resource references that need to be resolved. You can also give the deployer a sep
te deployment plan file on the command line.
|
If Geronimo is restarted the console log will show ServiceMix starting, as shown below. Note: Geronimo does not need to be restarted to deploy the WAR file. Code Block |
---|
Booting Geronimo Kernel (in Java 1.5.0_05)...
Starting Geronimo Application Server
[*****************] 100% 45s Startup complete
Listening on Ports:
1099 0.0.0.0 RMI Naming
1527 0.0.0.0 Derby Connector
4201 0.0.0.0 ActiveIO Connector EJB
4242 0.0.0.0 Remote Login Listener
8019 0.0.0.0 Tomcat Connector AJP
8080 0.0.0.0 Jetty Connector HTTP
8090 0.0.0.0 Tomcat Connector HTTP
8443 0.0.0.0 Jetty Connector HTTPS
8453 0.0.0.0 Tomcat Connector HTTPS
61616 0.0.0.0 ActiveMQ Message Broker Connector
Started Application Modules:
EAR: org/apache/geronimo/Console/Jetty
WAR: org/apache/geronimo/applications/Welcome/Jetty
WAR: servicemix-web
Web Applications:
http://Lisas:8080/
http://Lisas:8080/console
http://Lisas:8080/console-standard
http://Lisas:8080/servicemix-web
Geronimo Application Server started
|
NOTE: The console output is also logged in geronimo_install_dir\var\log\deployer.log
.
...
These steps were performed with a source distribution of ServiceMix 2.0.2 on Windows XP. The existing quartz binding example is modified in this example to turn it into a deployement unit.
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.- Create a directory elsewhere, such as \temp\JBIcomponent
- Copy servicemix.xml to \temp\JBIcomponent
- cd \temp\JBIcomponent
- 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.apache.servicemix.components.util.TraceComponent" />
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
</sm:serviceunit>
</beans>
|
This file will be used in a later step.
- 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
. - 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>
|
- 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 *
|
- 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. - 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 *
|
Wiki Markup |
Deploy the two jar 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 |
---|
ServiceMixComponent: deploy
ServiceMixComponent: init: SU_1 path: C:\tmp1\servicemix-1.1-SNAPSHOT\target\servicemix-1.1-SNAPSHOT\bin\servicemix-1.1-SNAPSHOT\bin\..\wdir
\defaultJBI\components\servicemix-component\serviceunit\SU_1
[INFO] XmlBeanDefinitionReader - -Loading XML bean definitions from URL [file:C:/tmp1/servicemix-1.1-SNAPSHOT/target/servicemix-1.1-SNAPSHOT
/bin/servicemix-1.1-SNAPSHOT/bin/../wdir/defaultJBI/components/servicemix-component/serviceunit/SU_1/servicemix.xml]
...
[INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'jbi'
ServiceMixComponent: start: SU_1
[INFO] JBIContainer - -Activating component for: [container=defaultJBI,name=timer,id=timer] with service: {http://servicemix.org/demo/}timer
component: org.servicemix.components.quartz.QuartzComponent@1ecfe07
[INFO] SimpleThreadPool - -Job execution threads will use class loader of thread: main
[INFO] RAMJobStore - -RAMJobStore initialized.
[INFO] StdSchedulerFactory - -Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.pr
operties'
[INFO] StdSchedulerFactory - -Quartz scheduler version: 1.4.0
[INFO] ComponentContextImpl - -Component: timer activated endpoint: {http://servicemix.org/demo/}timer : timer
[INFO] JBIContainer - -Activating component for: [container=defaultJBI,name=trace,id=trace] with service: {http://servicemix.org/demo/}trace
component: org.servicemix.components.util.TraceComponent@8b8a47
[INFO] ComponentContextImpl - -Component: trace activated endpoint: {http://servicemix.org/demo/}trace : trace
[INFO] DeploymentService - -Deployed ServiceUnit SU_1 to Component: servicemix-component
[INFO] AutoDeploymentService - -Unpacked archive C:\tmp1\servicemix-1.1-SNAPSHOT\target\servicemix-1.1-SNAPSHOT\bin\servicemix-1.1-SNAPSHOT\
bin\..\deploy\comp.jar to C:\tmp1\servicemix-1.1-SNAPSHOT\target\servicemix-1.1-SNAPSHOT\bin\servicemix-1.1-SNAPSHOT\bin\..\wdir\defaultJBI\
tmp\comp.0.tmp
[INFO] XmlBeanDefinitionReader - -Loading XML bean definitions from URL [file:/C:/tmp1/servicemix-1.1-SNAPSHOT/target/servicemix-1.1-SNAPSHO
T/bin/servicemix-1.1-SNAPSHOT/bin/../wdir/defaultJBI/tmp/comp.0.tmp/META-INF/jbi.xml]
...
[INFO] DefaultListableBeanFactory - -Creating shared instance of singleton bean 'jbi'
[INFO] AutoDeploymentService - -Unpacked archive C:\tmp1\servicemix-1.1-SNAPSHOT\target\servicemix-1.1-SNAPSHOT\bin\servicemix-1.1-SNAPSHOT\
bin\..\deploy\sa_quartz.jar to C:\tmp1\servicemix-1.1-SNAPSHOT\target\servicemix-1.1-SNAPSHOT\bin\servicemix-1.1-SNAPSHOT\bin\..\wdir\defaul
tJBI\tmp\sa_quartz.0.tmp
[INFO] XmlBeanDefinitionReader - -Loading XML bean definitions from URL [file:/C:/tmp1/servicemix-1.1-SNAPSHOT/target/servicemix-1.1-SNAPSHO
T/bin/servicemix-1.1-SNAPSHOT/bin/../wdir/defaultJBI/tmp/sa_quartz.0.tmp/META-INF/jbi.xml]
[INFO] FileSystemXmlApplicationContext - -Bean factory for application context [org.springframework.context.support.FileSystemXmlApplication
[INFO] JBIContainer - -ServiceMix JBI Container (http://servicemix.org/) name: defaultJBI running version: ServiceMix.
[INFO] DeliveryChannel - -default destination serviceName for timer = {http://servicemix.org/demo/}trace
[INFO] QuartzScheduler - -Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
[INFO] TraceComponent - -Exchange: org.servicemix.jbi.messaging.InOnlyImpl@a7dd39 received IN message: org.servicemix.jbi.messaging.Normaliz
edMessageImpl@acdd02{properties: {org.servicemix.quartz.context=JobExecutionContext: trigger: 'ServiceMix.My Example Job job: ServiceMix.My
Example Job fireTime: 'Thu Dec 08 14:15:06 PST 2005 scheduledFireTime: Thu Dec 08 14:15:05 PST 2005 previousFireTime: 'null nextFireTime: Th
u Dec 08 14:15:06 PST 2005 isRecovering: false refireCount: 0, org.servicemix.quartz.detail=JobDetail 'ServiceMix.My Example Job': jobClass
: 'org.servicemix.components.quartz.ServiceMixJob isStateful: false isVolatile: false isDurable: false requestsRecovers: false, org.servicem
ix.component=org.servicemix.components.quartz.QuartzComponent@1ecfe07}}
[INFO] TraceComponent - -Body is: <?xml version="1.0" encoding="UTF-8"?><timer><name>My Example Job</name><group>ServiceMix</group><fullname
>ServiceMix.My Example Job</fullname><description/><fireTime>Thu Dec 08 14:15:06 PST 2005</fireTime></timer>
[INFO] TraceComponent - -Exchange: org.servicemix.jbi.messaging.InOnlyImpl@19ecd80 received IN message: org.servicemix.jbi.messaging.Normali
zedMessageImpl@c5aa00{properties: {org.servicemix.quartz.context=JobExecutionContext: trigger: 'ServiceMix.My Example Job job: ServiceMix.My
Example Job fireTime: 'Thu Dec 08 14:15:06 PST 2005 scheduledFireTime: Thu Dec 08 14:15:06 PST 2005 previousFireTime: 'Thu Dec 08 14:15:05
PST 2005 nextFireTime: Thu Dec 08 14:15:06 PST 2005 isRecovering: false refireCount: 0, org.servicemix.quartz.detail=JobDetail 'ServiceMix.M
y Example Job': jobClass: 'org.servicemix.components.quartz.ServiceMixJob isStateful: false isVolatile: false isDurable: false requestsReco
vers: false, org.servicemix.component=org.servicemix.components.quartz.QuartzComponent@1ecfe07}}
[INFO] TraceComponent - -Body is: <?xml version="1.0" encoding="UTF-8"?><timer><name>My Example Job</name><group>ServiceMix</group><fullname
>ServiceMix.My Example Job</fullname><description/><fireTime>Thu Dec 08 14:15:06 PST 2005</fireTime></timer>
|
...