3 Replies Latest reply on Nov 16, 2011 5:38 AM by Mauricio Salatino

    Running jBPM in Standalone Tomcat 5+

    Michael Renzi Newbie

      Hi - Just started looking into jBMP.  Is there a version (or way to build a version) that can run stand-along in Tomcat 5 or higher?  Running it on JBoss is not an option for me in this case.

       

      Thanks

      -Mike Renzi

        • 1. Re: Running jBPM in Standalone Tomcat 5+
          Mauricio Salatino Master

          Yes sure,

          jBPM5 is agnostic to the environment and you can set it up in any container or outside a container as well.

          Which features of the project do you want to use? the jBPM5 core can also be embedded inside your application and used without any of the provided tooling.

          Cheers

          • 2. Re: Running jBPM in Standalone Tomcat 5+
            Michael Renzi Newbie

            Ok, but more info would be helpful.  You say jbpm is agnostic to the environment.  Are these the core libraries:

             

            *   jbpm-flow

            *   jbpm-flow-builder

            *   jbpm-bpmn2

             

            And, does any documentation exist that explains the various "other" non-jboss deployments (just core, core + tools, etc...)? 

             

             

             

            • 3. Re: Running jBPM in Standalone Tomcat 5+
              Mauricio Salatino Master

              Those that you mention are the core libs.

              All of them are maven projects, that means that you can easily manage and get the dependency tree for all of them in order to check the dependency requirements.

               

              For the tooling you need to know that most of the tooling is being built using GWT and can be deployed in any container, but it's not up to the jBPM5 project specify all the other containers deployment requirements. Most of the project is built using standard technologies that helps the deployment process.

               

              Imagine the core of jBPM5 as Hibernate, that you can use it everywhere, doesn't make sense to write a document for each container, it will be good if as a community effort we can coordinate a wiki to share our experiencies with different containers.

               

              Cheers