Deployed Process not appearing in Wildfly 8.2

[Niall Deehan]

Hi Guys,

I'm asking this on behalf of someone else - I wasn't able to come up with an answer myself, so hoping you guys can help....

I've downloaded the standalone EE WildFly war file from:

http://camunda.org/enterprise-release/camunda-bpm/jboss/nightly/7.3.0-alpha3/camunda-webapp-ee-jboss-standalone-7.3.0-alpha3-ee.war

With a plain vanilla version of WildFly 8.2.0, I've followed the instructions at http://docs.camunda.org/latest/guides/installation-guide/jboss/#bpm-platform-install-the-platform-on-a-vanilla-wildfly to merge the modules directory from the pre-made WildFly distro with our plain vanilla version and updated the standalone.xml file. After deploying the camunda-webapp-ee-jboss-standalone-7.3.0-alpha3-ee.war war file, Camunda loads up fine except for one thing. When deploying a built process application war file (e.g. the loan approval app from the getting started guide), Cockpit does not show that process application (after refreshing the page of course).

When using the WildFly 8 Full Distribution package, we are able to see the process application in Cockpit after deploying it into WildFly.

So we're having a problem getting process applications to load in a plain vanilla WildFly app server with a Standalone Web Application distribution war file installed.

Thanks,

Niall.

[thorben....@camunda.com]

Hi Niall,

The standalone webapplication contains its own process engine configuration therefore its own database configuration. You'll have to make sure this configuration matches the configuration of your process application's engine configuration. See [1] for a similar thread and the configuration location.

Note that you don't need the standalone webapp if you are using a shared engine on the same application server. Then you can also install the web application as described at [2] (which points to different WAR artifacts for the webapp). Following that procedure, you should end up with the exact setup as the distribution.

Cheers,
Thorben

[1] https://groups.google.com/forum/#!topic/camunda-bpm-users/mVKUiWdOMwY
[2] http://docs.camunda.org/latest/guides/installation-guide/jboss/#web-applications-install-camunda-cockpit-and-tasklist

[Sebastian Menski]

Hi Niall,

if you use the webapp standalone you don't have to merge modules. There is a separate installation guide for it [1]. You problem is that the webapp standalone uses an

embedded process engine. Which means your process application can't be deployed to it. As you mentioned you also adjusted the standalone.xml so I assume you

configured also a shared process engine which picks up your process application.

Cheers,

Sebastian

[1] http://docs.camunda.org/7.2/guides/installation-guide/standalone/#installation