1. To start the kie-config-cli tool in online mode, navigate to the kie-config-cli-6.MINOR_VERSION-redhat-x-dist directory where you installed the tool and then execute the following command.
2. In a Unix environment run:

   ./kie-config-cli.sh

   In a Windows environment run:

   ./kie-config-cli.bat

1. Navigate to the kie-config-cli-6.MINOR_VERSION-redhat-x-dist directory where you installed the tool.
2. In a Unix environment, run:

   ./kie-config-cli.sh offline

   In a Windows environment, run:

   ./kie-config-cli.bat offline

1. Download the migration tool by logging in at the Red Hat Customer Portal and then navigating to Red Hat JBoss BPM Suite Software Downloads section. Click on Red Hat JBoss BPM Suite Migration Tool to download the zip archive.
2. Unzip the downloaded zip archive in a directory of your choice, navigate to this directory in a command prompt and then run the following command:

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

1. Start JBoss Developer Studio.
2. Start the Red Hat JBoss BPM Suite server (if not already running) by selecting the server from the server tab and click the start icon.
3. 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 Existing local repository and click next.
5. Select the repository that is to be configured from the list of available repositories.
6. Import the project as a general project in the next window and click next. Name this project and click Finish.

1. Set the system property jbpm.v5.id.strategy to true in the BPMS standalone.xml:

   <property name="jbpm.v5.id.strategy" value="true"/>
   

2. Load the KieSession like the following:

   KieSession ksession = JPAKnowledgeService.loadStatefulKnowledgeSession(sessionID, kbase, sessionConf, env);
   

3. Continue the normal execution of the process using KieSession methods:

   ksession.signalEvent("SomeEvent", null);

Procedure 5.1. Changing Database

1. Install the database driver on JBoss (refer to JBoss driver documentation).
2. Create an empty database and a JBoss data source which connects to the database driver.
3. Modify the file dashbuilder.war/WEB-INF/jboss-web.xml:

   <jboss-web>
      <context-root>/dashbuilder</context-root>
      <resource-ref>
          <res-ref-name>jdbc/dashbuilder</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <jndi-name>java:jboss/datasources/myDataSource</jndi-name>
      </resource-ref>
      ...
   

4. Replace the jndi-name parameter value by the JNDI path of the JBoss data source you've just created.
5. Modify the file dashbuilder.war/WEB-INF/jboss-deployment-structure.xml
6. Add the following snippet of configuration inside the deployment tag, where jdbcDriverModuleName is the name of the JBoss JDBC driver module:

     <dependencies>
         <module name="jdbcDriverModuleName" />
     </dependencies>
   

Procedure 6.1. Creating a New Repository

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

   Figure 6.1. Create Repository Pop-up

4. Enter the mandatory details:
   • Repository name.

     Note

     Note that the repository name should be a valid filename. Avoid using a space or any special character that might lead to an invalid folder name.
   • Select an organizational unit in which the repository is to be created from the Organizational Unit drop-down option.
5. Click Create
6. A confirmation prompt with an OK button is displayed which notifies the user that the repository is created successfully. Click OK.

Procedure 6.2. Cloning a repository

1. Open the Administration perspective.
2. On the Repositories menu, select Clone repository.
3. The Clone Repository pop-up window is displayed.
   

   Figure 6.2. Clone Repository Pop-up

4. In the Clone Repository dialog window, enter the repository details:
   1. Enter the Repository Name to be used as the repository identifier in the Asset repository and select the Organizational Unit it should be added to.
   2. Enter the URL of the GIT repository:
      • For a Local Repository: file:///path-to-repository/reponame
      • For a Remote or preexisting Repository: git://hostname/reponame

      Note

      The file protocol is only supported for 'READ' operations. 'WRITE' operations are not supported.
   3. If applicable, enter the User Name and Password to be used for authentication when cloning the repository.
5. Click Clone.
6. A confirmation prompt with an OK button is displayed which notifies the user that the repository is created successfully. Click OK.

Procedure 6.3. Changing System Properties

1. Edit the file $JBOSS_HOME/domain/configuration/host.xml
2. Locate the XML elements server that belong to the main-server-group and add a system property, for example:

   <system-properties>
    <property name="org.uberfire.nio.git.dir" value="..." boot-time="false"/>
    ...
   </system-properties>
   

1. Open the Project Authoring perspective (Authoring → Project Authoring).
2. In Project Explorer (Project Authoring → Project Explorer), navigate to the project where you want to create the Process definition (in the Project view, select the respective repository and project in the drop-down lists; in the Repository view, navigate to REPOSITORY/PROJECT/src/main/resources/ directory).

   Note

   It is recommended to create your resources, including your Process definitions, in a package of a Project to allow importing of resources and their referencing. To create a package, do the following:

   • In the Repository view of the Project Explorer, navigate to the REPOSITORY/PROJECT/src/main/resources/ directory.
   • Go to New Item → Package.
   • In the New resource dialog, define the package name and check the location of the package in the repository.
3. From the perspective menu, go to New Item → Business Process.
4. In the New Processes dialog box, enter the Process name and click OK. Wait until the Process Editor with the Process diagram appears.

1. In the Project Explorer, select a Project and the respective package to which you want to import the Process definition.
2. Create a new Business Process to work in by going to New Item → Business Process.
3. In the Process Designer toolbar, click the Import icon in the editor toolbar and pick the format of the imported process definition. Note that you have to choose to overwrite the existing process definition in order to import.
4. From the Import window, locate the Process file and click Import.
   

   Figure 7.1. Import Window

Procedure 7.1. Exporting a business process

1. Open the Project Authoring perspective: on the main menu, click Authoring → Project Authoring.
2. Select the business process which is to be exported, to view it in the Process Designer.
3. Click on the ( ) button of the process designer toolbar and select View Process Sources from the drop-down options.
4. The Process Sources window is displayed
5. Click on the Download BPMN2 button and save the business process at the desired location.

1. Clone the git repository where you have saved the BPM Suite project by running this command:

   git clone http://localhost:8001/REPOSITORY_NAME

2. On the command line, move into the folder that contains the project.
3. Follow the instructions in Red Hat JBoss Fuse Service Works 6 Development Guide, Volume 3: Governance, section Deploying to S-RAMP. Use the URL from the example below:

   <distributionManagement>
     <repository>
       <id>local-sramp-repo</id>
       <name>S-RAMP Releases Repository</name>
       <url>sramp://S-RAMP_SERVER_URL/s-ramp-server/</url>
     </repository>
     <snapshotRepository>
       <id>local-sramp-repo-snapshots</id>
       <name>S-RAMP Snapshots Repository</name>
       <url>sramp://S-RAMP_SERVER_URL/s-ramp-server/</url>
     </snapshotRepository>
   </distributionManagement>

   With these settings, Maven deployments are sent directly to the S-RAMP repository using the S-RAMP API. Note that artifacts are added to the S-RAMP repository with an artifact type based on the Maven type of the project. You can override this behavior by adding a query parameter to the repository URL in the pom.xml file. For example:

   <distributionManagement>
     <repository>
       <id>local-sramp-repo</id>
       <name>S-RAMP Releases Repository</name>
       <url>sramp://S-RAMP_SERVER_URL/s-ramp-server/?artifactType=KieJarArchive</url>
     </repository>
   </distributionManagement>
   

   The above example causes the Maven artifact to be uploaded with an S-RAMP artifact type of KieJarArchive.
4. Amend the maven plug-in in file pom.xml and add a dependency to it as follows in case the project does not contain decision tables:

   <plugins>
       <plugin>
         <groupId>org.kie</groupId>
         <artifactId>kie-maven-plugin</artifactId>
         <version>6.0.2-redhat-6</version>
         <extensions>true</extensions>
         <dependencies>
             <dependency>
                 <groupId>org.jbpm</groupId>
                 <artifactId>jbpm-bpmn2</artifactId>
                 <version>6.0.2-redhat-6</version>
             </dependency>
         </dependencies>  
        </plugin>
       </plugins>
   

   If the project contains decision tables, use this dependency for the kie-maven-plugin instead:

   <plugins>
       <plugin>
         <groupId>org.kie</groupId>
         <artifactId>kie-maven-plugin</artifactId>
         <version>6.0.2-redhat-6</version>
         <extensions>true</extensions>
         <dependencies>
             <dependency>
                  <groupId>org.drools</groupId>
                  <artifactId>drools-decisiontables</artifactId>
                  <version>6.0.2-redhat-6</version>
              </dependency>
         </dependencies>  
        </plugin>
       </plugins>
   

5. Run a clean Maven deployment using the following command:

   mvn -s sramp-settings.xml deploy

   .

1. In a web browser, navigate to http://localhost:8080/s-ramp-ui/. 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/s-ramp-ui/.
2. Click on Artifacts.
3. In the Manage Artifacts section, select Import.
4. Locate the kie archive you want to deploy. In the dialog that opens, fill out KieJarArchive as the type, and select Import.
5. The deployment then creates these entries in the S-RAMP repository:
   KieJarArchive, from which it derives:
   • KieXmlDocument (if the archive contains kmodule.xml)
   • BpmnDocument (if the archive contains bpmn definitions)
   • DroolsDocument (if the archive contains drl definitions)

1. Map the Log classes to the data source, so that the given data source accepts the log entries. On Red Hat JBoss EAP, edit the data source properties in the persistence.xml file.

   Example 11.1. The ProcessInstanceLog, NodeInstanceLog and VariableInstanceLog classes enabled for processInstanceDS

   <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
   <persistence  version="1.0"  xsi:schemaLocation=
       "http://java.sun.com/xml/ns/persistence
        http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd
        http://java.sun.com/xml/ns/persistence/orm
        http://java.sun.com/xml/ns/persistence/orm_1_0.xsd"
     xmlns:orm="http://java.sun.com/xml/ns/persistence/orm"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns="http://java.sun.com/xml/ns/persistence">
   
     <persistence-unit name="org.jbpm.persistence.jpa">
       <provider>org.hibernate.ejb.HibernatePersistence</provider>
       <jta-data-source>jdbc/processInstanceDS</jta-data-source>
       <class>org.drools.persistence.info.SessionInfo</class>
       <class>org.jbpm.persistence.processinstance.ProcessInstanceInfo</class>
       <class>org.drools.persistence.info.WorkItemInfo</class>
       <class>org.jbpm.process.audit.ProcessInstanceLog</class>
       <class>org.jbpm.process.audit.NodeInstanceLog</class>
       <class>org.jbpm.process.audit.VariableInstanceLog</class>
   
       <properties>
         <property name="hibernate.dialect" value="org.hibernate.dialect.H2Dialect"/>
         <property name="hibernate.max_fetch_depth" value="3"/>
         <property name="hibernate.hbm2ddl.auto" value="update"/>
         <property name="hibernate.show_sql" value="true"/>
         <property name="hibernate.transaction.manager_lookup_class"
                   value="org.hibernate.transaction.BTMTransactionManagerLookup"/>
       </properties>
     </persistence-unit>
   </persistence>
   

2. Register a logger on your Kie Session.

   Example 11.2. Import the Loggers

   import org.jbpm.process.audit.AuditLogService;
   import org.jbpm.process.audit.AuditLoggerFactory;
   import org.jbpm.process.audit.AuditLoggerFactory.Type;
   import org.jbpm.process.audit.JPAAuditLogService;
   ...
   

   Example 11.3. Registering a Logger to a Kie Session

   @PersistenceUnit(unitName = PERSISTENCE_UNIT_NAME)
     private EntityManagerFactory emf;
   
     private AuditLogService auditLogService;
   @PostConstruct
     public void configure() {
     
     auditLogService = new JPAAuditLogService(emf);
     ((JPAAuditLogService) auditLogService).setPersistenceUnitName(PERSISTENCE_UNIT_NAME);
     
     if( emf == null ) { 
     ((JPAAuditLogService) auditLogService).setPersistenceUnitName(PERSISTENCE_UNIT_NAME);
     }
     
     RuntimeEngine runtime = singletonManager.getRuntimeEngine(EmptyContext.get());
     KieSession ksession = runtime.getKieSession();
     AuditLoggerFactory.newInstance(Type.JPA, ksession, null);
   
     }
   

3. Optionally, call the method addFilter on the logger to filter out irrelevant information. Only information accepted by all filters appears in the database.
4. Logger classes can be viewed in the Audit View:

   <dependency>
   	<groupId>org.jbpm</groupId>
   	<artifactId>jbpm-audit</artifactId>
   	<version>6.0.1.Final</version>
   </dependency>
   

1. Log into the dashbuilder after the server has been successfully started by navigating to http://localhost:8080/dashbuilder in a web browser.
2. Select the language of your choice by clicking on the available locales on the top center of the dashbuilder user interface to change the language.

Procedure 12.1. Setting the default language as French

1. Navigate to jboss-eap-6.1/standalone/configuration and define the following in the standalone.xml file.

   <system-properties>
       <property name="org.jboss.dashboard.LocaleManager.installedLocaleIds" value="en,es,de,fr,ja,pt,zh"/>
       <property name="org.jboss.dashboard.LocaleManager.defaultLocaleId" value="fr"/>
   </system-properties>
   

2. The default user interface language of the dashbuilder is now set to French.

Procedure 12.2. Defining the installed locale

• Navigate to jboss-eap-6.1/standalone/configuration and define the following in the standalone.xml file.

  <system-properties>
      <property name="org.jboss.dashboard.LocaleManager.installedLocaleIds" value="en,es,de,fr,ja,pt"/>
      <property name="org.jboss.dashboard.LocaleManager.defaultLocaleId" value="fr"/>
  </system-properties>
  

Procedure 15.1. Copying the JBoss BRMS plug-in JAR files

1. Extract the JBoss BRMS plug-in pack archive to a temporary location. This creates a subdirectory with the name jon-plugin-pack-brms-bpms-3.2.0.GA. For example:

   [root@server rhq-agent]# unzip jon-plugin-pack-brms-bpms-3.2.0.GA.zip -d /tmp

2. Copy the extracted BRMS plug-in JAR files from the jon-plugin-pack-brms-bpms-3.2.0.GA/ directory to the JBoss ON server plug-in directory. For example:

   [root@server rhq-agent]# cp /tmp/jon-plugin-pack-brms-bpms-3.2.0.GA/*.jar /opt/jon/jon-server-3.2.0.GA1/plugins

3. Start the JBoss Operations Network server to update the BRMS plug-in.

Procedure 15.2. Uploading the BRMS plug-in through GUI

1. Start the JBoss Operations Network Server and Log in to access the GUI.
2. In the top navigation of the GUI, open the Administration menu.
3. In the Configuration area on the left, select the Server Plugins link.
4. At the bottom of the list of loaded server plug-ins, click the Upload a plugin button and choose the BRMS plugin.
5. The BRMS plug-in for JBoss Operations Network is now uploaded.

Procedure 16.1. Accessing Workspace Permissions

1. Log into Business Dashboards from Business Central (as described in the Accessing Red Hat JBoss BPM Suite Dashbuilder topic).
2. Select the appropriate Dashboard from the Wokspace drop-down.
   

   Figure 16.1. Dashbuilder Workspace

3. Click the Edit selected workspace properties button to access the Workspace Dashboard.
4. Click the Permissions label to view the permission management screen.
   

   Figure 16.2. Permissions Screen

1. To access Page permissions, locate the Pages drop-down under the jBPM Dashboard (or whatever Dashboard you selected).
2. After expanding Pages, expand the Process dashboard option.
3. Select the Page permissions option.

1. To access the Panel permissions page, expand the Panel instances option under the jBPM Dashboard (or whatever Dashboard you are using).
2. Expand the Dashboard option and then expand the Process dashboard.
3. Expand the Panels choice and select the appropriate process.
4. Open the Panel permissions page.