3.2. The generic deployable bundle installation

Install the transaction manager.

1. Define users and roles in $TOMCAT_DIR/conf/tomcat-users.xml. Note that Business Central requires users to have the roles specified as admin and/or analyst (for more information about user and role definitions, refer to the Tomcat 7 documentation).
   The program listing below shows an example of how these two roles would be added and how a user named bpmsadmin will be assigned these roles.

     <role rolename="admin"/>
     <role rolename="analyst" />
     <user username="bpmsadmin" password="P@ssw0rd" roles="admin,analyst"/>
   
   

   Copy to Clipboard Toggle word wrap
2. Copy kie-tomcat-integration-VERSION.jar from $TOMCAT_DIR/webapps/business-central/WEB-INF/lib/ to $TOMCAT_DIR/lib/.
3. Copy jaxb-api-VERSION.jar from $TOMCAT_DIR/webapps/business-central/WEB-INF/lib/ to $TOMCAT_DIR/lib/.
4. In $TOMCAT_DIR/conf/server.xml, add the Tomcat Valve declaration in the relevant <host> element:

   <Valve className="org.kie.integration.tomcat.JACCValve" />
   

   Copy to Clipboard Toggle word wrap
5. In $TOMCAT_DIR/webapps/business-central/WEB-INF/web.xml, uncomment entries marked with the TOMCAT-JEE-SECURITY comments.
6. Set up the tomcat authentication source: in the $TOMCAT_DIR/webapps/business-central/WEB-INF/classes/META-INF/services/ directory, rename the following files: org.uberfire.security.auth.AuthenticationSource to org.uberfire.security.auth.AuthenticationSource-ORIGIN and org.uberfire.security.auth.AuthenticationSource-TOMCAT-JEE-SECURITY to org.uberfire.security.auth.AuthenticationSource:

   # Example command if you run this from $TOMCAT_DIR/webapps directory 
   $ mv business-central/WEB-INF/classes/META-INF/services/org.uberfire.security.auth.AuthenticationSource business-central/WEB-INF/classes/META-INF/services/org.uberfire.security.auth.AuthenticationSource-ORIGIN
   $ mv business-central/WEB-INF/classes/META-INF/services/org.uberfire.security.auth.AuthenticationSource-TOMCAT-JEE-SECURITY business-central/WEB-INF/classes/META-INF/services/org.uberfire.security.auth.AuthenticationSource
   

   Copy to Clipboard Toggle word wrap
7. In $TOMCAT_DIR/webapps/business-central/WEB-INF/beans.xml, uncomment JAASUserGroupInfoProducer and comment org.jbpm.kie.services.cdi.producer.DefaultUserGroupInfoProducer (optional). The alternatives part of this file should now look like this:

     <alternatives>
       <!--    <class>org.jbpm.kie.services.cdi.producer.DefaultUserGroupInfoProducer</class> -->
       <!-- uncomment JAASUserGroupInfoProducer when using JEE security on Tomcat -->
       <class>org.jbpm.kie.services.cdi.producer.JAASUserGroupInfoProducer</class>
     </alternatives>						
   					
   
   

   Copy to Clipboard Toggle word wrap

1. In business-central/META-INF/context.xml, replace the datasource JNDI name in the <Resource> element. The uniqueName attribute refers to the resource.ds1.uniqueName property set in resources.properties:

   <Resource name="jdbc/myDatasource" uniqueName="jdbc/jbpm" auth="Container" removeAbandoned="true" factory="bitronix.tm.resource.ResourceObjectFactory" type="javax.sql.DataSource"/>
   

   Copy to Clipboard Toggle word wrap
2. In business-central/WEB-INF/web.xml, replace the datasource JNDI name in the <res-ref-name> element with your datasource name:

   <resource-ref>
           <description>Console DS</description>
           <res-ref-name>jdbc/myDatasource</res-ref-name>
           <res-type>javax.sql.DataSource</res-type>
           <res-auth>Container</res-auth>
   </resource-ref>
   

   Copy to Clipboard Toggle word wrap
3. Change business-central/WEB-INF/classes/META-INF/persistence.xml.
   In this file, change the name of the hibernate dialect used for your database, if using a different database other than H2. The code below demonstrates the original database information for persistence.xml:

   <property name="hibernate.dialect" value="org.hibernate.dialect.H2Dialect"/>
   

   Copy to Clipboard Toggle word wrap
   This information can be updated in the following manner (as demonstrated with MySQL database below):

   <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
   

   Copy to Clipboard Toggle word wrap

   Note

   The dialect for DB2 is org.hibernate.dialect.DB2Dialect, for DB2 on AS/400 is org.hibernate.dialect.DB2400Dialect, for Oracle is org.hibernate.dialect.Oracle10gDialect and for Microsoft SQL Server is org.hibernate.dialect.SQLServerDialect
4. Change business-central/WEB-INF/classes/META-INF/persistence.xml file so that BPMS process engine can use the new database.
   The code below demonstrates the original datasource information for persistence.xml:

   <jta-data-source>java:comp/env/jdbc/jbpm</jta-data-source>
   

   Copy to Clipboard Toggle word wrap
   Change this value to the datasource defined earlier:

   <jta-data-source>java:comp/env/jdbc/myDatasource</jta-data-source>
   

   Copy to Clipboard Toggle word wrap

1. Run startup.sh in the $TOMCAT_HOME/bin directory.

   ./startup.sh

   Copy to Clipboard Toggle word wrap
2. Navigate to http://localhost:8080/business-central in a web browser.
3. Login with the correct username/password as given in the tomcat-users.xml file where you defined user roles.

1. In dashbuilder/META-INF/context.xml, replace the datasource JNDI name in the <Resource> element. The uniqueName attribute refers to the resource.ds1.uniqueName property set in resources.properties:

   <Resource name="jdbc/dashbuilderDS" uniqueName="jdbc/jbpm" auth="Container" removeAbandoned="true" factory="bitronix.tm.resource.ResourceObjectFactory" type="javax.sql.DataSource"/>
   

   Copy to Clipboard Toggle word wrap

   Note

   Depending upon your database, you may need to define some other properties here as well. For example, in an Oracle environment, this entry may look like the following listing.

   <Resource name="jdbc/jbpm" uniqueName="jdbc/jbpm" auth="Container"  removeAbandoned="true" factory="bitronix.tm.resource.ResourceObjectFactory" type="javax.sql.DataSource" username="username" password="password"  driverClassName="oracle.jdbc.xa.client.OracleXADataSource" url="jdbc:oracle:thin:YOUR-URL:1521:YOUR-DB" maxActive="8" />
   
   

   Copy to Clipboard Toggle word wrap
2. In dashbuilder/WEB-INF/web.xml, add the datasource JNDI name in the <res-ref-name> element with your datasource name:

   <resource-ref>
       <description>Dashboard Builder Datasource</description>
       <res-ref-name>jdbc/dashbuilderDS</res-ref-name>
       <res-type>javax.sql.DataSource</res-type>
       <res-auth>Container</res-auth>
   </resource-ref>
   

   Copy to Clipboard Toggle word wrap
3. In dashbuilder/META-INF/context.xml, define the transaction factory:

    <Transaction factory="bitronix.tm.BitronixUserTransactionObjectFactory"/>
   

   Copy to Clipboard Toggle word wrap
4. Update the datasource JNDI name in dashbuilder/WEB-INF/etc/hibernate.cfg.xml in the <session-factory> element:

   <property name="connection.datasource">java:/comp/env/jdbc/dashbuilderDS</property>
   

   Copy to Clipboard Toggle word wrap