1 Reply Latest reply on Jun 9, 2014 12:18 AM by Cameron Smith

    [JBPM 6] How to start JBPM without ant start.demo.noeclipse ?

    jeudi0506 Newbie

      hello,

      We try to launch JBPM but we have some constraints and we can't simply do "ant start.demo.noeclipse" to do it.

      To avoid those constraints, we want to launch JBPM without "ant start.demo.noeclipse."

       

      We first try to launch standalone.bat in Jboss/bin, in order to be « similar” with redhat but there are problem of parsing (ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-t hreads - 1) JBAS014654: Composite operation was rolled back 13:55:55,571 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Stepsthat failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jbpm-console.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jbpm-console.war\".PARSE: Failed to process phase PARSE of deployment \"jbpm-console.war\""}}}} )

       

       

      Which is file to launch JBPM without ant command? (standalone?? .bat ??)

      Or what exactly does the command “ant start.demo.noeclipse” (which is the script launched )

       

      regards.

        • 1. Re: [JBPM 6] How to start JBPM without ant start.demo.noeclipse ?
          Cameron Smith Newbie

          The ant script will load what it needs to do from the build.xml file.

           

          As such, the start.demo.noeclipse target points to the following:

          <target name="start.demo.noeclipse" depends="start.h2,start.jboss" />

           

          This means that in order to run start.demo.noeclipse it will first run start.h2 and start.jboss. So, now look at those targets to see what they do:

          <target name="start.h2" depends="start.h2.check" if="start.h2.db">

          + This seems to start h2 database and check that it worked.

          <target name="start.jboss">

              <property name="jboss.full.path.win" location="${jboss.home}/bin/standalone.bat" />

              <exec executable="${jboss.full.path.win}" spawn="yes" osfamily="windows">

                <env key="JAVA_OPTS" value="-XX:MaxPermSize=256m -Xms256m -Xmx512m" />

                <arg value="-b" />

                <arg value="${jboss.bind.address}" />

                <arg value="--server-config=standalone-full.xml" />

                <arg value="-Dorg.kie.demo=true" />

                <arg value="-Dorg.kie.example=false" />

              </exec>

              <property name="jboss.full.path.linux" location="${jboss.home}/bin/standalone.sh" />

              <exec executable="${jboss.full.path.linux}" spawn="yes" osfamily="unix">

                <env key="JAVA_OPTS" value="-XX:MaxPermSize=256m -Xms256m -Xmx512m" />

                <arg value="-b" />

                <arg value="${jboss.bind.address}" />

                <arg value="--server-config=standalone-full.xml" />

                <arg value="-Dorg.kie.demo=true" />

                <arg value="-Dorg.kie.example=false" />

              </exec>

              <waitfor maxwait="5" maxwaitunit="minute" checkevery="10"

                       checkeveryunit="second" timeoutproperty="jboss.timeout">

                <socket server="${jboss.bind.address}" port="8080" />

              </waitfor>

              <fail if="jboss.timeout" message="JBoss application server did not start within 5 minutes"/>

            </target>

          + This starts jboss using the standalone.bat batch file with a whole host of options, those options depending on which os you are running.

           

          So, if you want to emulate this I guess you need to start the h2 database, and then run the standalone batch file with similar options. However, I do not understand why you couldn't just run the ant version?