[esb-issues] [JBoss JIRA] Commented: (JBESB-1174) Invalid Hibernate.cfg.xml in jbpm.esb

[Burr Sutter (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-1174?page=comments#action_12382342 ] 
            
Burr Sutter commented on JBESB-1174:
------------------------------------

FYI, to verify that all is well follow these steps (based on build of SVN trunk on Oct 13 and the ESB Server generated by ant dist):
1) Update the login-config.xml in server\default\conf to include the following:
    <application-policy name = "jbpm">
       <authentication>
         <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule"
                       flag="required">
           <module-option name="dsJndiName">java:/JbpmDS</module-option>
           <module-option name="principalsQuery">
             SELECT PASSWORD_ FROM JBPM_ID_USER WHERE NAME_=?
           </module-option>
           <module-option name="rolesQuery">
             SELECT g.NAME_ ,'Roles' 
             FROM JBPM_ID_USER u,
                  JBPM_ID_MEMBERSHIP m,
                  JBPM_ID_GROUP g
             WHERE g.TYPE_='security-role'
               AND m.GROUP_ = g.ID_
               AND m.USER_ = u.ID_
               AND u.NAME_=?
           </module-option>
         </login-module>
       </authentication>
    </application-policy>

2) go to http://localhost:8080/jbpm-console and login as admin, admin
3) If this is the first time you've run these steps then you'll have no deployed processes
4) you can deploy a process definition in three ways:
 4.a) Deploy a PAR:
 - Using RHDS, add bpm_orchestration2 as a project, on the Deploy tab select Save Process Archive Locally, pick a location that you'll rememer and then click on Save Without Deploying...
 - in the jbpm admin console, select Deploy Process and use the browse button to select the par file generated in the previous step
 4.b) Deploy via RHDS/jBPM Graphical Process Designer:
 - Using RHDS (or jBPM Graphical Process Designer), select the Deploy tab, click on Test Connection, click on Deploy Process Archive
 - in the jbpm admin console, click on "Processes" or just refresh the page, to see "bpm_orchestration2Process" in the list.  Note: if you tried 4.a OR if you had run this more than once then you'll see the process definition listed multiple times but with different version numbers.
 4.c) Deploy via an ESB Service
  - from the bpm_orchestration2 quickstart folder, run "ant deploy" and "ant deployProcess"
  Note: this technique doesn't deploy the process image, therefore it better to try to get 4.a or 4.b working
5) if you have not done so already, go to bpm_orchestration2 quickstart folder, run "ant deploy", you might double check that it is in your deploy folder as an exploded archive
6) from the  bpm_orchestration2 quickstart folder run "ant startProcess"
you should see the process executing on the server console
7) using the jbpm admin console, drill down into the process definitions to review the instances, you should see them "Running" (in a green font).   This is because the Shipment Notice node is using an async call back into the ESB service and will wait until signaled.  
8) Drill down into the tokens and signal the Shipment Notice node so that it transitions to the end state and therefore the whole process instance is completed.

There is an error randomly produced by the Results Service (tied to the Shipment Notice node) that I have been unable to track down.

> Invalid Hibernate.cfg.xml in jbpm.esb
> -------------------------------------
>
>                 Key: JBESB-1174
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1174
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Process flow
>    Affects Versions: 4.2.1 IR1
>            Reporter: Burr Sutter
>         Assigned To: Mark Little
>            Priority: Critical
>             Fix For: 4.2.1 IR2
>
>
> hibernate.cfg.xml in deploy\jbpm.esb is using an in-memory database, it should be using the DataSource instead.  

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira