Installing Camunda Tomcat on Amazon EC2

[joet...@googlemail.com]

Hello folks,
just tried to install Camunda Tomcat Server 7 from http://camunda.org/download/ on my Amazon EC2 instance.
Installation seems to be successfull and I was able to start the server.
In the process list the tomcat server shows up as java proceess.
Everything looks pretty normal. But when I am trying to access the welcom page via http://myinstancenumberhere.compute.amazonaws.com:8080/camunda-welcome/index.html I only get a blanke page.
Am I doing something wrong?
Cheers
Josef

[Sebastian Menski]

Hi Josef,

could you attach the tomcat log?

Cheers,

Sebastian

[joet...@googlemail.com]

Hi,
the localhost log:

May 06, 2015 7:33:14 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
May 06, 2015 7:33:14 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
May 06, 2015 7:33:14 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: attributeAdded('org.apache.jasper.compiler.TldLocationsC$

[joet...@googlemail.com]

An here the last 20 lines of the catalina log:
INFO: Deployment summary for process archive 'camunda-invoice':

invoice.png
invoice.bpmn

May 06, 2015 7:33:33 AM org.camunda.bpm.engine.impl.application.ProcessApplicationManager logRegistration
INFO: ProcessApplication 'camunda-invoice' registered for DB deployments [332c8c57-f3c2-11e4-8db1-067fd98b34ba]. Will execute process definitions

invoice[version: 1, id: invoice:1:3350dd3a-f3c2-11e4-8db1-067fd98b34ba]
Deployment does not provide any case definitions.
May 06, 2015 7:33:33 AM org.camunda.bpm.example.invoice.DemoDataGenerator createUsers
INFO: Generating demo data for invoice showcase
May 06, 2015 7:33:34 AM org.camunda.bpm.container.impl.RuntimeContainerDelegateImpl deployProcessApplication
INFO: Process Application camunda-invoice successfully deployed.
May 06, 2015 7:33:34 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
May 06, 2015 7:33:34 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
May 06, 2015 7:33:34 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 30842 ms

[Sebastian Menski]

Hi Josef,

the last 20 lines aren't really informative. Does your log contains any exceptions? And exists a line like:

INFO: Deploying web application directory /camunda/webapps/camunda-welcome

Are the webapps directly accessible (Tasklist, Cockpit)?

http://myinstancenumberhere.compute.amazonaws.com:8080/camunda/app/tasklist/

http://myinstancenumberhere.compute.amazonaws.com:8080/camunda/app/cockpit/

Cheers,

Sebastian

[webcyberrob]

Hi Josef,

I would first remote desktop to your AWS host and confirm on the local host that all is ok, ie use the browser on the remote host. If all is ok, I suspect its an access control issue. With AWS instances, you need to setup an access policy if you want remote access.

regards

Rob

[joet...@googlemail.com]

Hello,
thanks for your reply.
The server log contains the line with the comunda welcome.
There are no exceptions. I will paste the complete log under this post.
Concerning the remote desktop suggestion: i am running a linux instance of which i am not even sure if a gui is installed. I actually would prefer to work via console.

The log:
May 06, 2015 7:33:02 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
May 06, 2015 7:33:03 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
May 06, 2015 7:33:03 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
May 06, 2015 7:33:03 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1183 ms
May 06, 2015 7:33:04 AM org.camunda.bpm.container.impl.tomcat.deployment.TomcatParseBpmPlatformXmlStep lookupBpmPlatformXmlFromCatalinaConfDirectory
INFO: Found camunda bpm platform configuration in CATALINA_BASE/CATALINA_HOME conf directory [/usr/share/server/apache-tomcat-7.0.50/conf/bpm-platform.xml] at file:/usr/share/server/apache-tomcat-7.0.50/conf/bpm-platform.xml
May 06, 2015 7:33:04 AM org.camunda.bpm.engine.impl.jobexecutor.JobExecutor start
INFO: Starting up the JobExecutor[org.camunda.bpm.engine.impl.jobexecutor.RuntimeContainerJobExecutor].
May 06, 2015 7:33:04 AM org.camunda.bpm.engine.impl.jobexecutor.SequentialJobAcquisitionRunnable run
INFO: JobExecutor[org.camunda.bpm.engine.impl.jobexecutor.RuntimeContainerJobExecutor] starting to acquire jobs
May 06, 2015 7:33:04 AM org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl invokePreInit
INFO: PLUGIN ProcessApplicationEventListenerPlugin activated on process engine default
May 06, 2015 7:33:04 AM org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl invokePreInit
INFO: PLUGIN SpinProcessEnginePlugin activated on process engine default
May 06, 2015 7:33:04 AM org.camunda.bpm.engine.impl.cfg.ProcessEngineConfigurationImpl invokePreInit
INFO: PLUGIN ConnectProcessEnginePlugin activated on process engine default
May 06, 2015 7:33:06 AM org.camunda.bpm.engine.impl.db.sql.DbSqlSession executeSchemaResource
INFO: performing create on engine with resource org/camunda/bpm/engine/db/create/activiti.h2.create.engine.sql
May 06, 2015 7:33:07 AM org.camunda.bpm.engine.impl.db.sql.DbSqlSession executeSchemaResource
INFO: performing create on history with resource org/camunda/bpm/engine/db/create/activiti.h2.create.history.sql
May 06, 2015 7:33:07 AM org.camunda.bpm.engine.impl.db.sql.DbSqlSession executeSchemaResource
INFO: performing create on identity with resource org/camunda/bpm/engine/db/create/activiti.h2.create.identity.sql
May 06, 2015 7:33:07 AM org.camunda.bpm.engine.impl.db.sql.DbSqlSession executeSchemaResource
INFO: performing create on case.engine with resource org/camunda/bpm/engine/db/create/activiti.h2.create.case.engine.sql
May 06, 2015 7:33:07 AM org.camunda.bpm.engine.impl.db.sql.DbSqlSession executeSchemaResource
INFO: performing create on case.history with resource org/camunda/bpm/engine/db/create/activiti.h2.create.case.history.sql
May 06, 2015 7:33:07 AM org.camunda.bpm.engine.impl.SchemaOperationsProcessEngineBuild checkHistoryLevel
INFO: No historyLevel property found in database.
May 06, 2015 7:33:07 AM org.camunda.bpm.engine.impl.SchemaOperationsProcessEngineBuild dbCreateHistoryLevel
INFO: Creating historyLevel property in database with value: full
May 06, 2015 7:33:07 AM org.camunda.bpm.engine.impl.ProcessEngineImpl <init>
INFO: ProcessEngine default created
May 06, 2015 7:33:07 AM org.camunda.bpm.container.impl.tomcat.TomcatBpmPlatformBootstrap deployBpmPlatform
INFO: camunda BPM platform sucessfully started on Apache Tomcat/7.0.50.
May 06, 2015 7:33:07 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
May 06, 2015 7:33:07 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.50
May 06, 2015 7:33:07 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/server/apache-tomcat-7.0.50/webapps/host-manager
May 06, 2015 7:33:11 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/server/apache-tomcat-7.0.50/webapps/examples
May 06, 2015 7:33:14 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/server/apache-tomcat-7.0.50/webapps/h2
May 06, 2015 7:33:16 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/server/apache-tomcat-7.0.50/webapps/manager
May 06, 2015 7:33:19 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/server/apache-tomcat-7.0.50/webapps/camunda
May 06, 2015 7:33:22 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/server/apache-tomcat-7.0.50/webapps/ROOT
May 06, 2015 7:33:25 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/server/apache-tomcat-7.0.50/webapps/docs
May 06, 2015 7:33:27 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/server/apache-tomcat-7.0.50/webapps/engine-rest
May 06, 2015 7:33:30 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/server/apache-tomcat-7.0.50/webapps/camunda-welcome
May 06, 2015 7:33:32 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /usr/share/server/apache-tomcat-7.0.50/webapps/camunda-invoice
May 06, 2015 7:33:33 AM org.camunda.bpm.application.impl.ServletProcessApplicationDeployer onStartup
INFO: Detected @ProcessApplication class org.camunda.bpm.example.invoice.InvoiceProcessApplication
May 06, 2015 7:33:33 AM org.camunda.bpm.container.impl.deployment.ParseProcessesXmlStep parseProcessesXmlFiles
INFO: Found process application file at file:/usr/share/server/apache-tomcat-7.0.50/webapps/camunda-invoice/WEB-INF/classes/META-INF/processes.xml
May 06, 2015 7:33:33 AM org.camunda.bpm.container.impl.deployment.DeployProcessArchiveStep logDeploymentSummary

[webcyberrob]

Hi,

It looks to me like all is ok. I would suggest go to your AWS console and look at the security group. Look at the inbound and outbound protocols allowed. Tomcat will starat on port 8080 and thus access may not be enabled by default. If this is not a production machine, you could allow all protocols to all ports from all hosts as a brute force way to get going...

regards

Rob

[joet...@googlemail.com]

Hello,
thank you ver much.
This was exactly the problem.
I had to set an inbound rule for 8080.
It is actually not a Comunda problem at all.
Thanks all very much for your help and adive.
Regards
Josef