1. Go to the Red Hat Customer Portal and log in.
2. Click Downloads → Products Downloads.
3. In the Product Downloads page that opens, click Red Hat JBoss BRMS.
4. From the Version drop-down menu, select version 6.2.
5. Select Red Hat JBoss BRMS 6.2 Deployable for EAP 6.4 and then click Download.

1. Setup Location and Users

   Navigate to the folder where you downloaded the installer file in a command prompt and execute the following command.
   java -jar jboss-brms-6.2.0.GA-installer.jar

   Note

   When running the installer on Windows, you may be prompted to provide administrator credentials during the installation. To prevent this, add the izpack.mode=privileged option to the installation command: java -Dizpack.mode=privileged -jar jboss-brms-6.2.0.GA-installer.jar
2. The graphical installer will execute and display a splash screen and a license agreement page. Accept the license to proceed.
3. In the next screen, provide the parent location of an existing JBoss EAP where JBoss BRMS must be installed. The screenshot below depicts an example directory path:
   

   Figure 1.1. Red Hat JBoss BRMS Installer for EAP Directory Path

4. In the next two screens, create two users: the first one for the management console of the EAP (ManagementRealm) and the second one for managing JBoss BRMS itself (ApplicationRealm).
   Creation of the first user for the management console of JBoss EAP is optional and you may skip it if it is not required.
   Make a note of these usernames and passwords as you will need them to access the JBoss EAP server (if you do decide to create it) and the JBoss BRMS application respectively.

   Note

   The username that you create should not be the same as any of the pre-defined roles (See Section 1.8, “Defining Roles”).

   The passwords that you create must have at least 8 characters and must contain at least one number and one non-alphanumeric character (not including the character &).

   Note

   The application role assigned to the second user that you create is the admin role. This is the only role that can be assigned to this newly created user. You can create more users with narrow roles afterwards by using the command line.

5. Setup Security Environment

   Next, you will setup the security environment of your new JBoss BRMS install. Decide to enable or disable the Java Security Manager in this step by clicking on the check box. The Java Security Manager makes your system more secure but may downgrade performance. You need to make a decision based on your environment.
6. Choose whether you want to setup pure IPv6 configuration on the server that the installation is taking place. This will allow you to setup runtime IPv6 specific configurations later.

7. Configure Runtime Environment

   This step provides the option of using a default configuration or specifying an advanced configuration.

   • Default Configuration

     Choose default configuration for the runtime environment in the next step and click next to review the installation details. If you are happy with the details, click next to start the actual installation or click previous to go back and make changes.

   • Advanced Configuration

     Choose to enable advanced configuration options. Select "Perform advanced configuration" and choose the advanced configuration options you want to enable for your environment via the check boxes.
     

     Figure 1.2. Advanced Configuration Options

     • Configure Vault Password

       Vault passwords are used to obfuscate passwords in the various server descriptors using a java secret key generated during the installation process, or manually using the keytool. This prevents passwords from being stored as plain text in the descriptors. The iteration count and salt are both parameters to the encryption process.
       For more information about vault passwords, see the Red Hat JBoss EAP Security Guide.
       

       Figure 1.3. Configure vault password

     • SSL Security

       This screen allows you to add the <ssl> and <truststore> elements to the ManagementRealm security-realm using the provided keystore.

       • The <ssl> element causes the server to present the certificate within the keystore as its identity, which allows the user to apply their official certificate.
       • The <truststore> element enables "Client-Cert" authentication. This means that, if a remote client attempts to connect to any resource managed by the ManagementRealm, the client can present a certificate, and if an entry in the truststore matches, will be authenticated without needing to provide a username / password.

       The end result is an encrypted connection that is secure between the client and the server for the ManagementRealm.
       

       Figure 1.4. SSL Security Configuration

     • LDAP Security

       This step in the installer allows the user to define an LDAP server, which in turn defines users which should be allowed to authenticate with the ManagementRealm. This replaces the default configuration.
       The LDAP Connection screen allows users to define how to connect to the LDAP server.

       • The Distinguished Name(DN): the user that can connect to the LDAP server. Typically the DN will uniquely define a special user for this purpose.
       

       Figure 1.5. LDAP Connection Configuration

       LDAP Security (Management Console)

       The Management Console LDAP Configuration screen allows you to set up a security realm. This defines the <security-realm> element to be added to the descriptors, and utilizes the connection defined previously.
       

       Figure 1.6. Management Console LDAP Configuration

       • Base DN: Will typically define a 'base search' or 'root context' to begin searching for users.
       • Filter type: Tells JBoss EAP how to find the LDAP attribute that defines a user; it is can be a simple attribute, but can also be a complex "LDAP Filter".
       • Username attribute: The LDAP attribute which holds the username values. A username entered in this field is used for search queries as a value of the 'uid' attribute. If a user chooses 'LDAP syntax query' as a filter type, this query must be specified in this field.
       • Recursive directory search: If enabled, JBoss EAP will traverse the LDAP tree recursively, starting at Base DN. Otherwise, the search will be limited to Base DN.

       LDAP Security (Business Central)

       Most of the following fields are similar to the Base DN. Contexts are used to search for roles, which allows it to perform authorization in addition to authentication. Otherwise, the context fields are analogous to the Base DN from the previous, and attribute fields are analogous to Username attribute. The filters allow fine grained control over which values of the given attribute will be accepted.
       Input values from Business Central LDAP Configuration page are used to configure a new security domain, which make use of LdapExtended login module. This security domain is set as default for Business Central web application. For more information about security domains and login modules, see the Red Hat JBoss EAP Security Guide.
       

       Figure 1.7. Business Central LDAP Configuration

     • Security Domain and JSSE

       The Security Domain screen allows you to configure all of the elements of the <security-domain> security subsystem for managing security information, including JSSE configuration. For more detailed information about configuring security domains, see the Red Hat JBoss EAP Security Guide.
       

       Figure 1.8. Security Domain

       

       Figure 1.9. JSSE Configuration

8. The installer will go through the steps to install JBoss BRMS and will perform post installation configuration steps when you click next. The installer will also start the JBoss BRMS server and connect to it to validate the installation. Click next to get to the last screen where you can generate the installation script and properties file. Click done to quit the installer.

1. Navigate to the folder where you downloaded the installer file in a command prompt and execute the following command.

   java -jar jboss-brms-6.2.0.GA-installer.jar -console

2. The command-line interactive process will start and display the End-User license agreement. You will be prompted to select an option at the end of this license:

   press 1 to continue, 2 to quit, 3 to redisplay.
   
   

3. Enter 1 to begin the installation and type in the parent directory of an existing EAP installation.

   The location below must specify the JBOSS_HOME of an existing EAP installation.
   
   [/home/user/BRMS-6.2.0/jboss-eap-6.4]
   
   

   The installer will verify the location of the JBoss EAP installation at the provided location.

   press 1 to continue, 2 to quit, 3 to redisplay.

   Enter 1 to confirm and continue.
4. Create an administrative user

   Create an administrative user
   This user will be added to the host container's management realm for administrative purposes. It can be used to access the management console, the management CLI or other applications secured in this realm.
   
   The password must be at least eight characters long, with one alphabetic character, one digit, and one non-alphanumeric character not including &.
   
   Create an administrative user.
   0  [x] Skip new administrative user creation.
   1  [ ] Create a new administrative user.
   
   

5. Create and confirm a password for the user of the EAP management console:

   Admin password: []
   **********
   Confirm admin password: [**********]
   **********
   

6. After the passwords have been entered, choose an option from the prompt below:

   press 1 to continue, 2 to quit, 3 to redisplay.
   
   

7. Enter 1 then create a JBoss BRMS user:

   Create a Business Rules Management System Admin User
   Create a BRMS admin user. The user will be added to the ApplicationRealm, and can be used to access the Business Central Console. The User will be assigned the 'admin' application role. The BRMS username cannot be any of the following: 'admin', 'analyst', 'user', 'manager' or 'developer'.
   
   The password must be at least eight characters long, with one alphabetic character, one digit, and one non-alphanumeric character not including &.
   
   BRMS username: [brmsAdmin]
   
   

8. Create and confirm a password for the JBoss BRMS user:

   BRMS password: []
   **********
   Confirm BRMS password: [**********]
   **********
   
   

9. After the passwords have been entered, choose an option from the prompt below:

   press 1 to continue, 2 to quit, 3 to redisplay.
   
   

10. Configure the Java Security Manager

    A Java security manager offers JVM level security beyond what is provided by the application container. It enforces access rules at the JVM runtime based on one or more security policies.
    
    This installer will place two security policies in the installation directory with the filenames 'security.policy' and 'kie.policy' regardless of choice. Those policies will be enabled at runtime if the option below is selected.
    
    Please note that a security manager imposes a significant performance overhead when enabled. It is suggested the included policies be applied in production if user requirements call for a stronger measure than what is already provided by the application container's authentication and authorization mechanism.
    
    Please see the JBoss Business Rules Management System administrative documentation for further details and consideration.
      [ ] Enable the Java security manager
    Input 1 to select, 0 to deselect:
    
    

11. After the Java Security Manager choice, choose an option from the prompt below:

    press 1 to continue, 2 to quit, 3 to redisplay.
    
    

12. Next, select whether to enable the IPv6 configuration.

    IPv6 configuration
    
    If this computer is using a pure IPv6 configuration, please check the box below. A pure IPv6 setup requires additional configuration at runtime to ensure the proper bindings of the management and http interfaces.
      [ ] Enable pure IPv6 configuration
    Input 1 to select, 0 to deselect:
    
    

13. After the IPv6 configuration choice, choose an option from the prompt below:

    press 1 to continue, 2 to quit, 3 to redisplay.
    
    

14. Configure the runtime environment by either choosing the default configuration or inputting advanced options.

    Configure runtime environment
    Red Hat JBoss Business Rules Management System can be further customized at this time.
    0  [x] Perform default configuration
    1  [ ] Perform advanced configuration
    Input Selection:
    
    

    If you select 1, "Perform advanced configuration," complete the following configurations:

    •   [ ] Install password vault
      Input 1 to select, 0 to deselect:

    •   [ ] Enable SSL security
      Input 1 to select, 0 to deselect:

    •   [ ] Secure EAP Management Console with LDAP
      Input 1 to select, 0 to deselect:

    •   [ ] Secure Business Central with LDAP
      Input 1 to select, 0 to deselect:

    •   [ ] Add a security-domain
      Input 1 to select, 0 to deselect:

15. Next, choose an option from the prompt below:

    press 1 to continue, 2 to quit, 3 to redisplay.
    
    

16. The .jar file will begin to unpack and configure.
17. After a successful installation, the command-line will ask you if you would like to generate an automatic installation script and properties file.

    Installation has completed successfully.
    Application installed on /home/user/BRMS-6.2.0/jboss-eap-6.4
    Would you like to generate an automatic installation script and properties file?
    (y/n) [n]:
    

18. If you select [ y ], provide a path for the automatic installation script:

    Select path for the automatic installation script: [/home/user/BRMS-6.2.0/jboss-eap-6.4/<auto script filename>]
    
    

    This generated script will allow the user to run the installer in the following way for future installations:

    java -jar jboss-brms-6.2.0.GA-installer.jar <auto script filename>

    Note

    Running the installer in this way will result in an installation identical to the installation from which the auto script was generated. Note that sensitive values, such as passwords, will need to be provided from an external file or provided at auto installation time. The optional argument below allows the user to provide these values automatically:

    -variablefile <variable filename>

    Sensitive values can also be provided using the following argument:

    -variables key1=value1,key2=value2

19. The command-line will provide the following message upon a successful auto script creation and/or console installation:

    XML written successfully.
    [ Console installation done ]
    [BRMS_Installer]$
    

20. Start JBoss EAP by running standalone.sh in the jboss-eap-6.4/bin directory.

    ./standalone.sh

21. Navigate to http://localhost:8080/business-central in a web browser.
22. Login with the correct username/password as given to the JBoss BRMS user in the "Create and confirm a password for the JBoss BRMS user" step.

1. Move the downloaded zip archive to the parent directory of the Red Hat JBoss Enterprise Application Platform home directory (EAP_HOME; the jboss-eap-6.4 directory).
2. Unzip the downloaded zip archive: make sure it is merged into the EAP_HOME directory (jboss-eap-6.4).

   Warning

   This step must be performed by the same user account that was used to install EAP. This account must not be a superuser account.
3. It is necessary to overwrite the files that already exist in the EAP_HOME directory with their versions from the downloaded zip archive. When prompted to do so, accept overwriting the original files.

1. Download the zip archive and prepare to manually merge files into the Red Hat JBoss Enterprise Application Platform home directory (EAP_HOME; the jboss-eap-6.4 directory).
2. Unzip the downloaded zip archive; however, do not overwrite all of the files. Manually merge the following files into the EAP_HOME directory (jboss-eap-6.4):
   • jboss-eap-6.4/domain/configuration/*
   • jboss-eap-6.4/standalone/configuration/*
   • jboss-eap-6.4/modules/layers.conf
   • jboss-eap-6.4/bin/product.conf

   Warning

   Make sure this step is performed by the same user account that was used to install EAP. This account must not be a superuser account.
3. Ensure the target EAP does not include a deployment with a colliding name. Copy the folder jboss-eap-6.4/standalone/deployments into the EAP_HOME directory from the JBoss BRMS distribution.
4. Make sure no EAP module layer is already called JBoss BRMS and copy the folder jboss-eap-6.4/modules/system/layers/brms into the EAP 6.4 folder.

Procedure 1.1. Installing the Generic Deployable Package

1. Download and Extract

   To download the generic deployable package zip file from the Red Hat Customer Support Portal, go to https://access.redhat.com and log in.
2. Click Downloads.
3. In the Product Downloads page that opens, click Red Hat JBoss BRMS.
4. From the Version drop-down menu, select version 6.2
5. Select Red Hat JBoss BRMS 6.2 Deployable for All Supported Containers package and then click Download.
   Also select and download the Red Hat JBoss BRMS Engine files.
6. Extract business-central.war and kie-server.war from the generic deployable archive and copy to tomcat7/webapps/ folder.
7. Remove the .war extensions from the business-central.war and kie-server folders.
8. Move the kie-tomcat-integration-VERSION.jar file from business-central/WEB-INF/lib in JBoss BRMS distribution to tomcat7/lib.

9. Setup Users

   Define the users and the roles in tomcat7/conf/tomcat-users.xml as shown below. Make sure that username and roles do not conflict. For example, you should not create a user with the username of admin as that is a defined role. See Section 1.8, “Defining Roles” for a list of defined roles.

     <role rolename="admin"/>
     <role rolename="analyst"/>
     <user username="user" password="password" roles="admin,analyst"/>

10. Install the transaction manager.

    Warning

    Please note that the following section describes the setup of a transaction manager, Bitronix that is not officially supported by Red Hat.
    Copy the following transaction manager jar libraries from the lib folder to $TOMCAT_DIR/lib/ directory:
    • btm-VERSION.jar
    • btm-tomcat55-lifecycle-VERSION.jar
    • jta-VERSION.jar
    • slf4j-api-VERSION.jar
    • slf4j-jdk14-VERSION.jar
    In addition, download the following library and copy it into the $TOMCAT_DIR/lib/ folder as well:
    • javax.security.jacc-api.jar
11. Create the transaction manager configuration files in $TOMCAT_DIR/conf/:
    • btm-config.properties

      bitronix.tm.serverId=tomcat-btm-node0
      bitronix.tm.journal.disk.logPart1Filename=${btm.root}/work/btm1.tlog
      bitronix.tm.journal.disk.logPart2Filename=${btm.root}/work/btm2.tlog
      bitronix.tm.resource.configuration=${btm.root}/conf/resources.properties
      

    • resources.properties (the resource.ds1.uniqueName defines the datasource name used in tomcat resource definition later - make a note of this value).

      Example 1.1. H2 datasource definition

      resource.ds1.className=bitronix.tm.resource.jdbc.lrc.LrcXADataSource
      resource.ds1.uniqueName=jdbc/jbpm
      resource.ds1.minPoolSize=10
      resource.ds1.maxPoolSize=20
      resource.ds1.driverProperties.driverClassName=org.h2.Driver
      resource.ds1.driverProperties.url=jdbc:h2:file:~/jbpm
      resource.ds1.driverProperties.user=sa
      resource.ds1.driverProperties.password=
      resource.ds1.allowLocalTransactions=true

      Example 1.2. MySQL 5.5 datasource definition

      resource.ds1.className=com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
      resource.ds1.uniqueName=jdbc/jbpm
      resource.ds1.minPoolSize=0
      resource.ds1.maxPoolSize=10
      resource.ds1.driverProperties.URL=jdbc:mysql://localhost:3306/sampledb
      resource.ds1.driverProperties.user=dbuser
      resource.ds1.driverProperties.password=dbpassword
      resource.ds1.allowLocalTransactions=true

      Example 1.3. DB2 Type 4 datasource definition

      resource.ds1.className=com.ibm.db2.jcc.DB2Driver
      resource.ds1.uniqueName=jdbc/jbpm
      resource.ds1.minPoolSize=0
      resource.ds1.maxPoolSize=10
      resource.ds1.driverProperties.URL=jdbc:db2://localhost:50000/sampledb
      resource.ds1.driverProperties.user=dbuser
      resource.ds1.driverProperties.password=dbpassword
      resource.ds1.allowLocalTransactions=true

      Example 1.4. Oracle datasource definition

      resource.ds1.className=oracle.jdbc.xa.client.OracleXADataSource
      resource.ds1.uniqueName=jdbc/jbpm
      resource.ds1.minPoolSize=0
      resource.ds1.maxPoolSize=10
      resource.ds1.driverProperties.URL=jdbc:oracle:thin:@//localhost:1521/bpms
      resource.ds1.driverProperties.user=dbuser
      resource.ds1.driverProperties.password=dbpassword
      resource.ds1.allowLocalTransactions=true

      Example 1.5. Microsoft SQL Server datasource definition

      resource.ds1.className=com.microsoft.sqlserver.jdbc.SQLServerDriver
      resource.ds1.uniqueName=jdbc/jbpm
      resource.ds1.minPoolSize=0
      resource.ds1.maxPoolSize=10
      resource.ds1.driverProperties.URL=jdbc:sqlserver://localhost:1433;databaseName=bpms;
      resource.ds1.driverProperties.user=dbuser
      resource.ds1.driverProperties.password=dbpassword
      resource.ds1.allowLocalTransactions=true

12. Set up the transaction manager listener in $TOMCAT_DIR/conf/server.xml to start and stop Bitronix on container startup and shutdown.
    Add the following element as the last <Listener> element into the <Server> element:

    <Listener className="bitronix.tm.integration.tomcat55.BTMLifecycleListener" />

13. Define the btm.root system property and location where bitronix config file is placed in:
    $TOMCAT_DIR/bin/, create a readable setenv.sh file with the following content:

    CATALINA_OPTS="-Xmx512M -XX:MaxPermSize=512m -Djava.security.auth.login.config=$CATALINA_HOME/webapps/business-central/WEB-INF/classes/login.config -Dbtm.root=$CATALINA_HOME -Dbitronix.tm.configuration=$CATALINA_HOME/conf/btm-config.properties -Dorg.jbpm.designer.perspective=RuleFlow -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchronizationRegistry"

    The property org.jbpm.designer.perspective is set to RuleFlow to allow the default perspective for the designer to be RuleFlow rather than Full. Grant the file execute permissions if applicable.

    Important

    On Microsoft Windows systems, replace the $CATALINA_HOME value in the content of the file with the equivalent environment variable name or use the absolute path and add the values in setenv.bat file as shown here in the following example:

    set "CATALINA_OPTS=-Xmx512m -XX:MaxPermSize=512m -Djava.security.auth.login.config=C:\apache-tomcat\webapps\business-central\WEB-INF\classes\login.config -Dbtm.root=C:\apache-tomcat -Dbitronix.tm.configuration=C:\apache-tomcat\conf\btm-config.properties -Dorg.jbpm.designer.perspective=RuleFlow -Djbpm.tsr.jndi.lookup=java:comp/env/TransactionSynchronizationRegistry"

14. Install the Driver to Your Database

    Copy the jar file with the relevant database driver to $TOMCAT_DIR/lib/.

    Note

    If using the embedded H2 database, the driver is available in business-central/WEB-INF/lib/.

15. Start Server and Test

    Start JBoss Web Server by running startup.sh in the tomcat7/bin directory.

    ./startup.sh

    Wait a few minutes and check the server log ($TOMCAT_DIR/tomcat7/logs) for any errors. If there are no errors, proceed to the next step.
16. Navigate to http://localhost:8080/business-central in a web browser.
17. Login with the username/password defined in the tomcat-users.xml file.

1. Download and extract the Red Hat JBoss BRMS 6.2.0 Deployable for EAP 6 ZIP file from Red Hat Customer Portal and copy the following directories into the installation of EAP 6.4:
   • bin
   • domain
   Skip the standalone directory.
2. On the command line, move to the /bin directory and start the domain as follows:
   In a Unix environment, run:

   ./domain.sh

   In a Windows environment, run:

   ./domain.bat

3. Deploy the archive either via ${jboss-eap-home}/bin/jboss-cli.sh / ${jboss-eap-home}/bin/jboss-cli.bat, or via management web UI (localhost:9990/):

   Note

   The web application business-central.war supplied in the EAP deployable binaries in the /standalone/deployments directory is a directory, but for deployment into the domain, you have to use a WAR archive. To create it, zip the content of the business-central.war directory.
   1. To deploy the archive via ${jboss-eap-home}/bin/jboss-cli.sh or ${jboss-eap-home}/bin/jboss-cli.bat, move into the ${jboss-eap-home}/bin directory and deploy the WAR file:
      In a Unix environment, run:

      ./jboss-cli.sh

      In a Windows environment, run:

      ./jboss-cli.bat

      Then run:

      deploy location_of_business-central.war_file

   2. To deploy the archive via management web UI (localhost:9990/):
      • to create an EAP management account, add a Management User from the /bin directory as follows.
        On a Unix system, run:

        ./add-user.sh

        In a Windows environment, run:

        ./add-user.bat

        (refer to Section 1.9, “Creating users” and Section 1.8, “Defining Roles”).
      • log in using your EAP management account
      • select Domain -> Manage Deployments -> Content Repository -> Add
      • select the web archive from the file system, upload the web archive
      • select the deployment, click the Assign button
      • select the server group

1. Run ./add-user.sh on a Unix system or add-user.bat on a Windows system from the bin directory.
2. Enter b to select an Application User at the type of user prompt and press Enter.
3. Accept the default Realm (ApplicationRealm): by pressing Enter.
4. At the username prompt, enter a user name and confirm. For example: helloworlduser.

   Note

   Make sure that the usernames don't conflict with any known groups. For example, if there is a group called admin, you should not create a user with the username admin.
5. Create the user's password at the password prompt and reenter the password. For example: Helloworld@123.

   Note

   The password should be at least 8 characters in length and should contain upper and lower case alphabetic characters (e.g. A-Z, a-z), at least one numerical character (e.g. 0-9) and at least one special character (e.g. ~ ! @ # $ % ^ * ( ) - _ + =).
6. Enter a comma separate list of roles the user will need at the roles prompt (refer to Section 1.8, “Defining Roles”).
   Business Central users need to have the analyst or the admin role.
7. Confirm you want to add the user.
8. Enter yes at the next prompt (this is to enable clustering in the future if required).

Procedure 2.1. Cloning a repository

1. Open the Administration perspective: on the main menu, click Authoring → Administration.
2. On the perspective menu, click Repository → Clone repository.
3. The Clone Repository pop-up window is displayed.
   

   Figure 2.1. Clone Repository Pop-up

4. Enter the mandatory details:
   • Repository name.
   • Select an organizational unit in which the repository is to be created from the Organizational Unit drop-down option.
   • Enter the GIT URL.
   • Enter Username and Password.
5. Click Clone

1. Download the migration tool from Red Hat Customer Portal and unzip the downloaded zip archive.
2. For production databases, copy the JDBC driver for the database that is used by the JCR repository into the libs directory of the migration tool.
3. On the command line, move into the bin/ directory of the exploded zip archive.
   In a Unix environment, run:

   ./runMigration.sh -i <source-path> -o <destination-path> -r <repository-name>

   In a Windows environment, run:

   ./runMigration.bat -i <source-path> -o <destination-path> -r <repository-name>

   Where:
   • <source-path> is the path to the source JCR repository.
   • <destination-path> is the path to the destination git VFS.
   • <repository-name> is an arbitrary name for the new repository.
   The repository is then migrated to the specified location.

1. Navigate to http://localhost:8080/business-central in a web browser. If the user interface has been configured to run from a domain name, substitute localhost for the domain name. For example http://www.example.com:8080/business-central.
2. Log in with the user credentials that were created during installation. For example: User = helloworlduser and password = Helloworld@123.

Procedure 6.1. 

1. Download the following ZIP archives containing the required repositories:
   • https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downloadType=distributions&product=brms&version=6.2.0
2. Unzip the downloaded ZIP files into an arbitrary location in a local file system.
3. Add entries for the unzipped repositories to Maven's settings.xml file. The following code sample contains a profile with the repositories, configuration of authentication for access to the repositories, and an activation entry for the profile:

   <?xml version="1.0" encoding="UTF-8" standalone="no"?>
   <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/xsd/settings-1.0.0.xsd">
     <localRepository/>
     <profiles>
       <!-- Profile with local repositories required by JBoss BRMS/JBoss BPM Suite -->
       <profile>
         <id>brms-bpms-local-profile</id>
         <repositories>
           <repository>
             <id>jboss-brms-bpmsuite-repository</id>
             <name>BRMS/BPMS 6.2.0 GA Repository</name>
             <url>file://<!-- path to the repository -->/jboss-brms-bpmsuite-6.2.0.GA-redhat-5-maven-repository/maven-repository</url>
             <layout>default</layout>
             <releases>
               <enabled>true</enabled>
               <updatePolicy>never</updatePolicy>
             </releases>
             <snapshots>
               <enabled>false</enabled>
               <updatePolicy>never</updatePolicy>
             </snapshots>
           </repository>
         </repositories>
         <pluginRepositories>
           <pluginRepository>
             <id>jboss-brms-bpmsuite-repository</id>
             <name>BRMS/BPMS 6.2.0 GA Repository</name>
             <url>file://<!-- path to the repository -->/jboss-brms-bpmsuite-6.2.0.GA-redhat-5-maven-repository/maven-repository</url>
             <layout>default</layout>
             <releases>
               <enabled>true</enabled>
               <updatePolicy>never</updatePolicy>
             </releases>
             <snapshots>
               <enabled>false</enabled>
               <updatePolicy>never</updatePolicy>
             </snapshots>
           </pluginRepository>
         </pluginRepositories>
       </profile>
     </profiles>
   
     <!-- Configuring pre-emptive authentication for the repository server -->
     <server>
       <id>brms-bpms-m2-repo</id>
       <username>admin</username>
       <password>admin</password>
       <configuration>
         <wagonProvider>httpclient</wagonProvider>
         <httpConfiguration>
           <all>
             <usePreemptive>true</usePreemptive>
           </all>
         </httpConfiguration>
       </configuration>
     </server>
   
     <!-- Alternative to enabling pre-emptive authentication - configuring
          the Authorization HTTP header with Base64-encoded credentials
     <server>
       <id>brms-bpms-m2-repo</id>
       <configuration>
         <httpHeaders>
           <property>
             <name>Authorization</name>
             <value>Basic YWRtaW46YWRtaW4=</value>
           </property>
         </httpHeaders>
       </configuration>
     </server>
     -->
   
     <activeProfiles>
      <!-- Activation of the JBoss BRMS/JBoss BPM Suite profile -->
      <activeProfile>brms-bpms-local-profile</activeProfile>
     </activeProfiles>
   </settings>

Procedure 6.2. Configuring Maven to Use the Online Repositories

1. Add entries for the online repositories and configuration of authentication for accessing them to Maven's settings.xml file as in the code sample below:

   <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
   
     <profiles>
       <!-- Profile with online repositories required by BRMS/BPMS -->
       <profile>
         <id>brms-bpms-online-profile</id>
         <repositories>
           <repository>
             <id>jboss-ga-repository</id>
             <url>http://maven.repository.redhat.com/techpreview/all</url>
             <releases>
               <enabled>true</enabled>
             </releases>
             <snapshots>
               <enabled>false</enabled>
             </snapshots>
           </repository>
         </repositories>
         <pluginRepositories>
           <pluginRepository>
             <id>jboss-ga-plugin-repository</id>
             <url>http://maven.repository.redhat.com/techpreview/all</url>
             <releases>
               <enabled>true</enabled>
             </releases>
             <snapshots>
               <enabled>false</enabled>
             </snapshots>
           </pluginRepository>
         </pluginRepositories>
       </profile>
     </profiles>
   
     <!-- Configuring pre-emptive authentication for the repository server -->
     <server>
       <id>brms-bpms-m2-repo</id>
       <username>admin</username>
       <password>admin</password>
       <configuration>
         <wagonProvider>httpclient</wagonProvider>
         <httpConfiguration>
           <all>
             <usePreemptive>true</usePreemptive>
           </all>
         </httpConfiguration>
       </configuration>
     </server>
   
     <!-- Alternative to enabling pre-emptive authentication - configuring
          the Authorization HTTP header with Base64-encoded credentials
     <server>
       <id>brms-bpms-m2-repo</id>
       <configuration>
         <httpHeaders>
           <property>
             <name>Authorization</name>
             <value>Basic YWRtaW46YWRtaW4=</value>
           </property>
         </httpHeaders>
       </configuration>
     </server>
     -->
   
     <activeProfiles>
       <!-- Activation of the BRMS/BPMS profile -->
       <activeProfile>brms-bpms-online-profile</activeProfile>
     </activeProfiles>
   
   </settings>

2. If you modified the settings.xml file while JBoss Developer Studio was running, you must refresh Maven settings in the IDE. From the menu, choose Window → Preferences. In the Preferences Window, expand Maven and choose User Settings. Click the Update Settings button to refresh the Maven user settings in JBoss Developer Studio.
   

   Figure 6.2. Update Maven User Settings

Procedure 7.1. Install the Drools JBoss Developer Studio Plug-in

1. Start JBoss Developer Studio.
2. Select Help → Install New Software.
3. Click Add to enter the Add Repository menu.
4. Give the software site a name next to Name field and add the following url in the Location field: https://devstudio.jboss.com/updates/8.0/integration-stack/
5. Click OK.
6. Select the JBoss Business Process and Rule Development feature from the available options and click Next and then Next again.
7. Read the license and accept it by selecting the appropriate radio button, and click Finish.
8. After installation of the plug-ins has completed, restart JBoss Developer Studio.

Procedure 7.2. Configure JBoss BRMS Runtime

1. Extract the runtime jar files located in the jboss-brms-VERSION-engine.zip archive that you can download from Red Hat Customer Portal.
2. From the JBoss Developer Studio menu, select Window and click Preferences.
3. Select Drools → Installed Drools Runtimes.
4. Click Add...; provide a name for the new runtime, and click Browse to navigate to the directory where you extracted the runtime files in step 1. Click OK to register the selected runtime in JBDS.
5. Mark the runtime you have created as the default Drools runtime by clicking on the check box next to it.
6. Click OK. If you have existing projects, a dialog box will indicate that you have to restart JBoss Developer Studio to update the Runtime.

Procedure 7.3. Configure the Server

1. Open the Drools view by selecting Window → Open Perspective → Other and select Drools and click OK.
2. Add the server view by selecting Window → Show View → Other... and select Server → Servers.
3. Open the server menu by right clicking the Servers panel and select New → Server.
4. Define the server by selecting JBoss Enterprise Middleware → JBoss Enterprise Application Platform 6.4+ and clicking Next.
5. Set the home directory by clicking the Browse button. Navigate to and select the installation directory for JBoss EAP 6.4 which has JBoss BRMS installed.
6. Provide a name for the server in the Name field, make sure that the configuration file is set, and click Finish.

Procedure 7.4. Cloning a Remote Git Repository

1. Start the Red Hat JBoss BRMS/BPM Suite server (whichever is applicable) by selecting the server from the server tab and click the start icon.
2. Simultaneously, start the Secure Shell server, if not running already, by using the following command. The command is Linux and Mac specific only. On these platforms, if sshd has already been started, this command fails. In that case, you may safely ignore this step.

   /sbin/service sshd start

3. In JBoss Developer Studio, select File → Import... and navigate to the Git folder. Open the Git folder to select Projects from Git and click Next.
4. Select the repository source as Clone URI and click Next.
5. Enter the details of the Git repository in the next window and click Next.

   

   Figure 7.1. Git Repository Details

6. Select the branch you wish to import in the following window and click Next.
7. To define the local storage for this project, enter (or select) a non-empty directory, make any configuration changes and click Next.
8. Import the project as a general project in the following window and click Next. Name the project and click Finish.

Procedure 7.5. Importing a Local Git Repository

1. Start the Red Hat JBoss BRMS/BPM Suite server (whichever is applicable) by selecting the server from the server tab and click the start icon.
2. In JBoss Developer Studio, select File → Import... and navigate to the Git folder. Open the Git folder to select Projects from Git and click Next.
3. Select the repository source as Existing local repository and click Next.
   

   Figure 7.2. Git Repository Details

4. Select the repository that is to be configured from the list of available repositories and click Next.
5. In the dialog that opens, select the radio button Import as general project from the Wizard for project import group and click Next. Name the project and click Finish.

   

   Figure 7.3. Wizard for Project Import

1. Navigate to the Red Hat Customer Portal and log in with your user credentials.
2. Select Downloads → Product Downloads.
3. In the Product Downloads page that opens, click Red Hat JBoss BRMS.
4. From the Version drop-down menu, select version 6.2.
5. Select Red Hat JBoss BRMS 6.2 Business Resource Planner and then click Download.

1. On the command line, move into the examples/ directory.
2. In a Unix environment, run the following command:

   ./runExamples.sh

   In a Windows environment, run the following command:

   ./runExamples.bat

3. Pick an example from the Examples GUI application that opens and run it in your favorite IDE.