Servicemix testing
From PTAGISWiki
Testing Apache Servicemix on snapper.
- downloaded apache servicemix 3.2 http://servicemix.apache.org/download.html
used the pre-compiled binaries for linux and not the source
- installed on snapper at /var/www/html/sm
- started with command bin/servicemix
[root@snapper apache-servicemix-3.2]# bin/servicemix java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pxi32devifx-20070806 (SR5a)) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20070426 (JIT enabled) J9VM - 20070420_12448_lHdSMR JIT - 20070419_1806_r8 GC - 200704_19) JCL - 20070725 IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20070426 (JIT enabled) Starting Apache ServiceMix ESB: 3.2 Loading Apache ServiceMix from servicemix.xml on the CLASSPATH INFO - ConnectorServerFactoryBean - JMX connector available at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi INFO - JBIContainer - ServiceMix 3.2 JBI Container (ServiceMix) is starting INFO - JBIContainer - For help or more informations please see: http://incubator.apache.org/servicemix/ INFO - ComponentMBeanImpl - Initializing component: #SubscriptionManager# INFO - jetty - Logging to org.apache.servicemix.http.jetty.JCLLogger@4d804d8 via org.apache.servicemix.http.jetty.JCLLogger INFO - DeploymentService - Restoring service assemblies INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-http to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-http INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-cxf-bc to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-cxf-bc INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-script to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-script INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-lwcontainer to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-lwcontainer INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-eip to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-eip INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-bean to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-bean INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-wsn2005 to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-wsn2005 INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-drools to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-drools INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-jsr181 to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-jsr181 INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-xmpp to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-xmpp INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-cxf-se to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-cxf-se INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-truezip to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-truezip INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-saxon to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-saxon INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-jms to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-jms INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-ftp to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-ftp INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-quartz to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-quartz 1 name = quartz.properties INFO - SimpleThreadPool - Job execution threads will use class loader of thread: main 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 - QuartzScheduler - Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-file to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-file INFO - ComponentMBeanImpl - Setting running state for Component: servicemix-camel to Started INFO - ComponentMBeanImpl - Initializing component: servicemix-camel INFO - ServiceAssemblyLifeCycle - Starting service assembly: wsdl-first-sa INFO - ServiceUnitLifeCycle - Initializing service unit: wsdl-first-jsr181-su INFO - ServiceUnitLifeCycle - Initializing service unit: wsdl-first-http-su INFO - ServiceUnitLifeCycle - Starting service unit: wsdl-first-jsr181-su INFO - ServiceUnitLifeCycle - Starting service unit: wsdl-first-http-su INFO - jetty - jetty-6.1.5 INFO - jetty - Started SelectChannelConnector@0.0.0.0:8192 INFO - JBIContainer - ServiceMix JBI Container (ServiceMix) started INFO - JDBCAdapterFactory - Database driver recognized: [apache_derby_embedded_jdbc_driver] INFO - LogTask - Logging system reconfigured using file: file:/var/www/html/apache-servicemix-3.2/conf/log4j.xml
- tried to follow the quickstart tutorial, but the instructions quickly deviated from my experience. For instance, they give these instructions for deploying the sample app under linux:
cp components/servicemix-shared-*.zip install cp components/servicemix-http-*.zip install cp components/servicemix-jsr181-*.zip install cp examples/wsdl-first/wsdl-first-sa-*.zip deploy
But there is no "components" directory and no install or deploy directory. Searching for files that match that pattern in the installation shows that they already exist in the hotdeploy directory.
If the deployment is done, then this URL should be live: http://snapper.psmfc.org:8192/PersonService/main.wsdl And it is. So the next step is getting the deployed application to work.
getting an application to work
This URL is now live: http://snapper.psmfc.org/sm/examples/wsdl-first/client.html But when clicking on submit, I get a send error.
Looking through every other file in the examples directory does not reveal any working samples. The few other clickable pages in the examples directory yield similar connection error pages.
