[esb-issues] [JBoss JIRA] Work started: (JBESB-735) Documentation for the jBPM 3.2.1 Admin Console with the ESB is needed

Trevor Kirby (JIRA) jira-events at lists.jboss.org
Sat Sep 1 16:36:18 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBESB-735?page=all ]

Work on JBESB-735 started by Trevor Kirby.

> Documentation for the jBPM 3.2.1 Admin Console with the ESB is needed
> ---------------------------------------------------------------------
>
>                 Key: JBESB-735
>                 URL: http://jira.jboss.com/jira/browse/JBESB-735
>             Project: JBoss ESB
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: BPM
>    Affects Versions: 4.2 Milestone Release 2
>            Reporter: Burr Sutter
>         Assigned To: Trevor Kirby
>             Fix For: 4.2.1
>
>         Attachments: hibernate.cfg.xml, jbpm-console.war, jbpm-ds.xml, jbpmDB.properties, jbpmDB.script, login-config.xml
>
>
> My notes on how to make it run with AS 4.2 with Java 5 are here:
> http://jboss.org/index.html?module=bb&op=viewtopic&t=112908
> And here:
> Steps (for AS 4.2 + Messaging 1.3 + ESB 4.2MR3)
> 1. Deploy attached hypersonic databases to the server\messaging\data\hypersonic director. jbpmDB.properties, jbpmDB.script
> 2. Deploy attached datasource - jbpm-ds.xml into the server\messaging\deploy directory
> 3. Deploy attached jbpm-console.war - created from CVS because the one in the jBPM3.2.1 suite do not work with Java 5
> 4. Modify the conf\login-config.xml be inserting 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>
> 5. Modify the server\messaging\deploy\jbpm.esb\hibernate.cfg.xml so that it uses the DS defined in step 2.
> The result should look something like the following:
>     <property name="hibernate.dialect">org.hibernate.dialect.HSQLDialect</property>
>     <!-- JDBC connection properties (begin)
>     <property name="hibernate.connection.driver_class">org.hsqldb.jdbcDriver</property>
>     <property name="hibernate.connection.url">jdbc:hsqldb:mem:jbpm</property>
>     <property name="hibernate.connection.username">sa</property>
>     <property name="hibernate.connection.password"></property>
>     <property name="hibernate.hbm2ddl.auto">create</property>
>      JDBC connection properties (end) -->
>     
>     <property name="hibernate.cache.provider_class">org.hibernate.cache.HashtableCacheProvider</property>
>     
>     <!-- DataSource properties (begin) === -->
>     <property name="hibernate.connection.datasource">java:/JbpmDS</property>
>     <!-- ==== DataSource properties (end) -->
>     
> 6. Start your server with run -c messaging    
> N . http://localhost:8080/jbpm-console

-- 
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

        



More information about the esb-issues mailing list