Unfortunately, jBPM 7.5.0 does not have an official pre-packaged WAR distribution specifically for Tomcat. As you noticed, the official download page only provides binaries and WildFly-focused installers—this is because jBPM's official support at that version was primarily centered on WildFly (formerly JBoss AS).

But don't worry, you can still get jBPM running on Tomcat 8 by manually setting it up. Here's how to go about it:

• Start with the jBPM 7.5.0 binary package
  Download the official binary distribution from the jBPM website. This package contains all the core libraries, process engine components, and example projects you'll need.

• Prepare your Tomcat 8 environment

  • Ensure you're running a compatible JDK version (jBPM 7.5.0 requires JDK 8, so make sure Tomcat is configured to use it).
  • Configure a database datasource in Tomcat's conf/context.xml. jBPM needs a database to store process definitions, instances, and related data—common choices are H2 (for testing) or MySQL/PostgreSQL (for production).
  • Adjust Tomcat's memory settings (in bin/catalina.sh or bin/catalina.bat) to allocate enough heap space, as jBPM can be memory-intensive.

• Build or assemble a Tomcat-compatible WAR
  You have two main paths here:

  1. Use Maven to build a WAR from jBPM's sample projects: The binary package includes example projects that you can modify to target Tomcat. Exclude any WildFly-specific dependencies (like JBoss modules) and include Tomcat-compatible equivalents.
  2. Manually assemble the WAR: Gather all required jBPM libraries, your process definitions, and web application resources, then package them into a standard WAR file. Make sure to include a proper web.xml that configures the jBPM servlet context and filters.

• Deploy and test
  Drop your assembled WAR into Tomcat's webapps directory, start Tomcat, and monitor the logs/catalina.out file for any deployment errors. You may need to tweak dependencies or configuration settings if you run into classpath issues or missing components.

A few things to keep in mind: Some advanced jBPM features (like clustering, certain integration with enterprise services) might require extra configuration to work on Tomcat, since they're optimized for WildFly. It's worth checking the official jBPM 7.5.0 documentation for deployment best practices specific to non-WildFly application servers.

内容的提问来源于stack exchange，提问作者Juan Nieve