Procedure 2.2. Installing the Deployable Package

1. Download the deployable package zip file from the Red Hat Customer Support Portal at https://access.redhat.com.
   Select Downloads → Download your software → BRMS Platform, and then select the version and choose the deployable package.
   Users installing to JBoss Enterprise Application Platform 6 should download the package that includes EE6 as part of the filename. All other users should download the package that does not include EE6 as part of the filename.
2. Extracting the downloaded archive creates the following zip archives:
   • jboss-brms-engine.zip
   • jboss-brms-manager.zip
   • jboss-jbpm-console.zip
   • jboss-jbpm-engine.zip
   • modeshape.zip
   Modeshape is a Java Content Repository (JCR) that is included in JBoss Enterprise BRMS 5.3.1 as a technical preview; see the BRMS Administration Guide for further details.
3. Extract jboss-brms.war from the jboss-brms-manager.zip archive and copy to the application server's deploy directory.
   The deploy directories are as follow:
   • JBoss Enterprise Application Platform 5.x:
     jboss-as/server/profile/deploy/
   • JBoss Enterprise Application Platform 6.0:
     jboss-eap-6.0/standalone/deployments/
   • JBoss Enterprise SOA Platform:
     jboss-esb/server/profile/deploy/
   • JBoss Enterprise Web Server 1:
     tomcat6/webapps/
   • JBoss Enterprise Web Server 2:
     tomcat7/webapps/
4. Extract business-central.war, business-central-server.war, designer.war, and jbpm-human-task.war from the jboss-jbpm-console.zip archive and copy to the application server's deploy directory as above.
5. JBoss Enterprise Web Server users must remove the .war extension from the name of the war archives. After the archives have been renamed the webapps/ directory should contains the following subdirectories:
   • jboss-brms
   • business-central
   • business-central-server
   • designer
   • jbpm-human-task
6. JBoss Enterprise Application Platform 6 users must create the following empty files in the jboss-eap-6.0/standalone/deployments/ directory:
   • jboss-brms.war.dodeploy
   • business-central.war.dodeploy
   • business-central-server.war.dodeploy
   • designer.war.dodeploy
   • jbpm-human-task.war.dodeploy
7. Extract the jboss-jbpm-engine.zip directory and copy the netty.jar file from jboss-jbpm-engine/lib/ into a directory that will be on the classpath.
   • JBoss Enterprise Application Platform 5:
     common/lib/
   • JBoss Enterprise SOA Platform 5.x:
     common/lib/
   • JBoss Enterprise Web Server 1:
     tomcat6/lib/
   • JBoss Enterprise Web Server 2:
     tomcat7/lib/

   Note

   Both JBoss Enterprise Application Platform 5.x and JBoss Enterprise SOA Platform include a netty.jar file; however, JBoss Enterprise BRMS requires the specific version of netty.jar that is included with the JBoss Enterprise BRMS download.
   JBoss Enterprise Application Platform 6 users do not need to extract netty.jar from the jboss-jbpm-engine.zip directory. Instead, edit the jboss-eap-6.0/standalone/configuration/standalone.xml file so that the application server will load the required netty library.
   Update the "urn:jboss:domain:ee:1.1" subsystem property to match the following code snippet:

   <subsystem xmlns="urn:jboss:domain:ee:1.1">
      <global-modules>
   	  <module name="org.jboss.netty" slot="main"/>
      </global-modules>
      <spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>
      <jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>
   </subsystem>
   

8. When deploying to JBoss Enterprise Web Server, copy the antlr, common-collections, dom4j, javassist, jta, hibernate, log4j, and slf4j jar files from the jboss-jbpm-engine/lib/ directory to the application server's lib directory.
   • JBoss Enterprise Web Server 1:
     tomcat6/lib/
   • JBoss Enterprise Web Server 2:
     tomcat7/lib/
9. The default configurations use embedded databases that are not suitable or supported for production environments. Before deploying into a production environment, this configuration must be changed to a supported database. Please refer to the BRMS Administration Guide for database configuration instructions.