Versions Compared

Old Version 3

changes.mady.by.user Unknown User (lmalgeri)

Saved on

compared with

New Version 4

changes.mady.by.user Unknown User (lmalgeri)

Saved on

Key

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

...

This document is under development and will be completed when the underlying code is ready. In the meantime, the ServiceMix on Geronimo deployment shown here is of the servicemix-web.war file. The war file uses lightweight components, which are those components defined in a servicemix.xml file. Ultimately, the ServiceMix deployment on Geronimo will use heavyweight components. Heavyweight components accept service unit deployments, such as PXE. If you are interested in this topic and how it progresses, please "watch" this page for future changes.

...

The following guide explains how to deploy ServiceMix 2.0.x on the Apache Tomcat Geronimo application server. This guide provides instructions specifically for the ServiceMix 2.0.x release. For ServiceMix 1.1 and ServiceMix 2. 0 instructions, refer to Tomcat Integration for ServiceMix 1.1 and 2.0.

Pre-Installation Requirements

...

  • Windows XP
  • Tomcat 5.5
  • Java 5
  • ServiceMix 2.0.x

Deploying ServiceMix on

...

Geronimo

Execute the following steps to deploy ServiceMix on Apache TomcatGeronimo. NOTE: This procedure will work on Unix platforms, as well as the Windows platform, with the appropriate substitutions, such as using the backslash ( / ) instead of the forward slash ( \ ).

  1. Apache Tomcat Geronimo must be downloaded and installed. For instructions please see the Tomcat Geronimo web site.
  2. In the Geronimo release of geronimo-1.0-M5 or greater, Tomcat is integrated with Geronimo. By default, Tomcat uses port 8080. It is important to note if your Tomcat installation is on another port, such as port 80; this information will be used in a later step.
  3. Download the ServiceMix source code. Please see the Getting Started guide for instructions.
  4. Create the WAR file:
    Code Block
    cd [servicemix_install_dir]\tooling\servicemix-web
maven war
    where servicemix_install_dir is the directory in which ServiceMix was downloaded and installed.
  5. To deploy the WAR file, servicemix-web.war, copy it to the Tomcat webapps directory. For example, on a Windows system:
    Code Block
    cd [servicemix_install_dir]\tooling\servicemix-web\target
copy servicemix-web.war [tomcat_install_dir]\webapps
    where tomcat_install_dir is the directory in which Tomcat was installed.
  6. To deploy the ServiceMix WAR file , stop and start Tomcaton Geronimo, use the Geronimo deployer.jar tool found in the bin directory of the Geronimo base directory.
    The output in the Tomcat console window should show ServiceMix starting. Output will be similar to the following:
    Code Block
    INFO: Deploying web application archive servicemix-web.war
Nov 1, 2005 11:03:54 AM org.springframework.web.context.ContextLoader initWebApplicationContext
INFO: Root WebApplicationContext: initialization started
Nov 1, 2005 11:03:54 AM org.springframework.beans.factory.xml.XmlBeanDefinitionReader loadBeanDefinitions
INFO: Loading XML bean definitions from ServletContext resource [/WEB-INF/applicationContext.xml]
Nov 1, 2005 11:03:55 AM org.springframework.core.CollectionFactory <clinit>
INFO: JDK 1.4+ collections available
Nov 1, 2005 11:03:55 AM org.springframework.core.CollectionFactory <clinit>
INFO: Commons Collections 3.x available
Nov 1, 2005 11:03:55 AM org.springframework.context.support.AbstractRefreshableApplicationContext refreshBeanFactory
INFO: Bean factory for application context [Root WebApplicationContext]: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [jencks,broker,transactionManager,jmsFactory,jbi]; root of BeanFactory hierarchy
Nov 1, 2005 11:03:55 AM org.springframework.context.support.AbstractApplicationContext refresh
INFO: 5 beans defined in application context [Root WebApplicationContext]
Nov 1, 2005 11:03:55 AM org.springframework.context.support.AbstractApplicationContext initMessageSource
INFO: Unable to locate MessageSource with name 'messageSource': using default [org.springframework.context.support.DelegatingMessageSource@1049d3]
Nov 1, 2005 11:03:55 AM org.springframework.context.support.AbstractApplicationContext initApplicationEventMulticaster
INFO: Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using default [org.springframework.context.event.SimpleApplicationEventMulticaster@14a7a12]
Nov 1, 2005 11:03:55 AM org.springframework.ui.context.support.UiApplicationContextUtils initThemeSource
INFO: No ThemeSource found for [Root WebApplicationContext]: using ResourceBundleThemeSource
Nov 1, 2005 11:03:55 AM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [jencks,broker,transactionManager,jmsFactory,jbi]; root of BeanFactory hierarchy]
Nov 1, 2005 11:03:55 AM org.springframework.beans.factory.support.AbstractBeanFactory getBean
INFO: Creating shared instance of singleton bean 'jencks'
Nov 1, 2005 11:03:56 AM org.springframework.beans.factory.support.AbstractBeanFactory getBean
INFO: Creating shared instance of singleton bean 'broker'
...
    NOTE: The console output is also logged in tomcat_home_dir\logs\catalina.xxxx-xx-xx.log.

...