...
The following guide explains how to deploy ServiceMix 23.0.x on the Apache Tomcat application server. This guide provides instructions specifically for ServiceMix 23.0.x release. For ServiceMix 1.1 and ServiceMix 2.0.1 instructions, refer to Tomcat Integration for ServiceMix 1.1 and 2.0.1.
Pre-Installation Requirements
- Java Developer Kit (JDK) 1.45.x or greater to run ServiceMix (to build ServiceMix, JDK 1.5.x or greater is required)
- The JAVA_HOME environment variable must be set to the directory where the JDK is installed, e.g.
c:\Program Files\Java\jdk1.5.xx
. - Maven 12.0.2 4 or greater (required when installing source or developer releases).
- Apache Tomcat version 5.5
- ServiceMix 23.0.x
The following platform was used to produce this deployment guide:
- Windows XP
- Tomcat 5.5
- Java 5
- ServiceMix 23.0.x
Deploying ServiceMix on Tomcat
...
- Apache Tomcat must be downloaded and installed. For instructions please see the Tomcat web site.
- 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.
- Download the ServiceMix source codedistribution. Please see the Getting Started guide for instructions.
- Create the WAR file:
whereCode Block cd [servicemix_install_dir]\toolingexamples\servicemix-web mavenmvn warinstall
servicemix_install_dir
is the directory in which ServiceMix was downloaded and installed.Warning title For ServiceMix 3.0 If you use ServiceMix 3.0, you need to modify the
pom.xml
file in the \examples\servicemix-web directory.
Lines 79-83 should be modified as following:Code Block lang xml <dependency> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty</artifactId> </dependency>
For ServiceMix 3.0.1 or later, this step is not necessary.
- To deploy the WAR file,
servicemix-web-xxx.war
, copy it to the Tomcatwebapps
directory. For example, on a Windows system:
whereCode Block cd [servicemix_install_dir]\toolingexamples\servicemix-web\target copy servicemix-web-*.war [tomcat_install_dir]\webapps
tomcat_install_dir
is the directory in which Tomcat was installed. - Start Tomcat if it was not already running To deploy the ServiceMix WAR file, stop and start Tomcat.
The output in the Tomcat console window should show ServiceMix starting. Output will be similar to the following:
NOTE: The console output is also logged inCode Block INFO: Deploying web application archive servicemix-web-3.0-incubating.war NovSept. 129, 20052006 1119:0349:54 AM40 org.springframeworkapache.webcatalina.contextloader.ContextLoaderWebappClassLoader initWebApplicationContextvalidateJarFile INFO: validateJarFile(c: 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' ...
tomcat_home_dir\logs\catalina.xxxx-xx-xx.log
\java-bin\apache-tomcat-5.5.20\webapps\servicemix-web-3.0-incubating\WEB-INF\lib\servlet-api-2.5-6.0.0rc4.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class INFO - jetty - Logging to org.apache.servicemix.http.jetty.JCLLogger@628704 via org.apache.servicemix.http.jetty.JCLLogger INFO - JBIContainer - ServiceMix 3.0-incubating JBI Container (ServiceMix) is starting INFO - JBIContainer - For help or more informations please see: http://incubator.apache.org/servicemix/ INFO - ConnectorServerFactoryBean - JMX connector available at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi INFO - ComponentMBeanImpl - Initializing component: #SubscriptionManager# INFO - DeploymentService - Restoring service assemblies INFO - ComponentMBeanImpl - Initializing component: servicemix-http INFO - ComponentMBeanImpl - Initializing component: echo INFO - ComponentMBeanImpl - Initializing component: timer INFO - SimpleThreadPool - Job execution threads will use class loader of thread: ContainerBackgroundProcessor[StandardEngine[Catalina]] INFO - QuartzScheduler - Quartz Scheduler v.1.5.2 created. INFO - RAMJobStore - RAMJobStore initialized. INFO - StdSchedulerFactory - Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties' INFO - StdSchedulerFactory - Quartz scheduler version: 1.5.2 INFO - ComponentMBeanImpl - Initializing component: inputSender INFO - ComponentMBeanImpl - Initializing component: inputReceiver INFO - ComponentMBeanImpl - Initializing component: outputSender INFO - ComponentMBeanImpl - Initializing component: jmsTrace INFO - ComponentMBeanImpl - Initializing component: trace ERROR - ClientFactory - Cound not start ClientFactory: javax.naming.NamingException: Context is read only. INFO - QuartzScheduler - Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. INFO - JBIContainer - ServiceMix JBI Container (ServiceMix) started
Info | ||
---|---|---|
| ||
The log will display an error. Do not worry, this error will not affect ServiceMix. |
Testing the ServiceMix Deployment on Tomcat
...
- Check the Tomcat console output or the Tomcat log files (see above) to confirm that the servicemix-web is starting without errors.ServiceMix's default port is 1099. From another window run netstat and search for port 1099.
From a Windows console, type: code ORnetstat -an|find "1099"
From a Unix command shell, type:
Run the ServiceMix JMX Console. To do this, enter the following URL in a web browser: http://localhost:8080/servicemix-web-3.0-incubating/Code Block netstat -an|grep 1099
. Note: your installation of Tomcat may not be running on port 8080. If that is the case, replace 8080 with the correct port number in the previous URL.
Try using the JMX console. For example, perform the following steps. Note: this is optional.- Click on "Catalina".
- Click on "Unknown".
- Click on the "JMXServlet WebModule" to get monitoring information about the JMX Servlet itself:
- An http binding example is supplied. To run the example program perform the following steps:
- From a browser, enter the URL http://localhost:8080/servicemix-web-3.0-incubating/examples
. NOTE: If Tomcat is using a different port, such as port 80, substitute the correct port number for 8080 in the URL.
- Enter a name or some text in the text box (shown above) and click the Submit button. You will see:
- From a browser, enter the URL http://localhost:8080/servicemix-web-3.0-incubating/examples