0 Replies Latest reply on May 13, 2016 4:43 AM by Jaime Izuzquiza Suárez-Inclán

    Correct approach for several jBoss BPM Suite installations in different enterprise environments

    Jaime Izuzquiza Suárez-Inclán Newbie

      The company I work for wants to integrate jBoss BPM Suite for business process management with all his current applications (Liferay). They have three environments: Development, Certification and Production. The Java code (basically portlets, themes and layouts) is storaged in a SVN repository. The steps that everybody follows in order to release any incident are the following:

      1. Developers code and test in their local environment. Next, they commit the code to SVN Snapshots Branch, build the project and install the resulting .war in the first Liferay environment, the Development one. They can run that application in the first server.
      2. Developers check that everything works OK in the Development environment. They do integration tests and the code is committed to the SVN Release Branch. Again, they build the .war with Release code and they install it in the second Liferay environment, the Certification one. Business users can test the functonality of the deliverable. Obviously, this environment has a different Liferay instance and a different database from the Development one.
      3. When users check that everything works fine, code is commited to master branch and the war is installed in production environment.

      Here is my question:

      I don't know how to integrate jBoss BPM Suite with all these environments in order to promote processes and other assets from one environment to next one. The first idea was something like this: one jBoss BPM Suite installation and jbpm-schema per Liferay environment, and one shared git repository between all jBoss BPM Suite installations:


      Does anyone know what is the correct approach in order to promote assets/adapt the out-of-the-box jBPM approval process of managed repositories to the technical environment I exposed early?

      Thank you very much.