1. On the command line, move into the $SERVER_HOME/bin/ directory.
2. In a Unix environment run:

   ./standalone.sh

   In a Windows environment run:

   ./standalone.bat

1. On the command line, move into the $SERVER_HOME/bin/ directory.
2. In a Unix environment run:

   ./standalone-secure.sh

   In a Windows environment run:

   ./standalone-secure.bat

1. Open Business Central in your web browser (if running locally http://localhost:8080/business-central) and log in as a user with the admin role (helloworlduser).
2. Create an organizational unit in the Artifact repository:
   1. Go to Authoring → Administration.
   2. On the perspective menu, click Organizational Units → Manage Organizational Units.
   3. In the displayed Organizational Unit Manager view, click Add.
      In the displayed Add New Organizational Unit dialog box, define the unit properties and click Ok:
      • Name: helloworld
      • Owner: helloworlduser
3. Create a new repository in the helloworld organizational unit:
   1. Go to Authoring → Administration.
   2. On the perspective menu, click Repositories → New repository.
   3. In the displayed Create Repository dialog box, define the repository properties:
      • Repository Name: helloworldrepo
      • Organizational Unit: helloworld
4. Go to Authoring → Project Authoring.
5. In the Project Explorer in the organizational unit drop-down box, select helloworld, and in the repository drop-down box select helloworldrepo.
   

   Figure 4.1. Selecting the helloworldrepo repository in the helloworld organizational group in Project Explorer

6. Create a project in the helloworld repository:
   1. On the perspective menu, go to New Item → Project
   2. In the displayed Create new Project dialog box, define your Project properties:
      • Resource Name (project name): HelloWorld
   3. In the New Project Wizard dialog, define the maven properties of the Project:
      • Group ID: org.bpms
      • Artifact ID: HelloWorld
      • Version ID: 1.0
   4. Click Finish.

1. Display the Project Authoring perspective (Authoring → Project Authoring).
2. In the Project Explorer view on the left, select the helloworld organizational unit, the helloworldrepo repository, and the HelloWorld project.
3. On the perspective menu, click New Item → Business Process and define the Process definition details:
   • Enter the name of the Business Process as HelloWorld.
   • Select the org.bpms.helloworld package. This defines the location in the Artifact repository, where you will create your Business Process definition.

     Note

     Make sure to select the package org.bpms.helloworld. Selection of an incorrect package causes the deployment to fail.
4. Click Ok.

1. Expand the Object Library palette with Process Elements: click the double-arrow button ( ) in the upper left hand corner of the Business Process designer tab.
2. A Start Event element appears on the canvas.
3. Click the Start Event element: the quick linker items appear around the node. Click the Task ( ) icon to create an outgoing Sequence Flow and a Task element connected to the Start Event.
4. Create a Timer Event: from the palette, drag-and-drop the Timer (under Catching Intermediate Events) and connect the Task to the Timer Element using the quick linker menu.
5. Create the End Event element connected to the Timer Event element (either using the quick linker feature or dragging it from the palette).

1. Click the double-arrow ( ) in the upper right hand corner to expand the Properties tab.
2. Click anywhere on the canvas. The Properties tab displays the properties of the HelloWorld Process. The required properties are pre-defined; however, you can change their values if necessary.
3. The Start Element and End Element have only optional properties. However, Task Elements need their type and then type-specific properties defined: click the Task element and define the required properties:
   • Name: ScriptTask
   • Task Type: Script
   • Script Language: java
   • Script: System.out.println("Hello World!");
     Click OK.
   You have defined a Task that will perform a script on execution. The script is defined in Java and executes the method System.out.println("Hello World!");, that means it will write Hello World! to the standard output of the server (by default, the standard output of the server is the console the server was started in).
4. You still need to define properties of the Timer Event to make the process wait on runtime, so you can inspect its execution: click the Timer Element and define the time it will wait for execution:
   • Edit Time Duration: 1m and press Enter.
     The Process will therefore wait for 1 minute on the Timer Event after it executes the Script Task.
5. Give the Timer Event a name via the properties, and then save your Process: open the Save menu ( ) and click Save.
6. A Save this item prompt is displayed. Enter the Check-in comment and click Save.

   Note

   The check-in comment would be a short description of the kind of change you made and has to be entered every time an asset is saved.
7. Click the ( ) button on the toolbar of the Process Designer with the Process to make sure the defined Process is valid. The outline of any element with one or multiple validation mistakes turns orange (refer to the Red Hat JBoss BPM Suite User Guide for information on the validation feature).

1. On the main menu of Business Central, go to Authoring → Project Authoring.
2. In the Project Explorer, locate the Hello World project.
3. Open the Project in the Project editor: in the Project Explorer, click the Open Project Editor button.
4. Check that the correct Project details are displayed on the Project Screen and click the Build → Build & Deploy in the upper right hand corner of the Project Screen view.
   

   Figure 5.2. Project editor with the HelloWorld project properties.

1. Click Process Management → Process Definitions on the main menu.
2. On the displayed Process Definitions tab, locate the Hello World process. You might need to click the Refresh button to have the deployment displayed on the list.
3. Click the Start( ) button next to the Process definition entry and in the Form dialog box, click the Submit button to confirm that you want to instantiate the process.
   The Process is instantiated with the currently logged-in user as the process owner and the process form is displayed (the form can serve to request input from a user on Process instantiation if defined; refer to the Red Hat JBoss BPM Suite User Guide).

1. In Project Explorer, select the helloworld organizational unit, the helloworldrepo repository, the HelloWorld project, and the default package.

   Note

   Make sure to select the default package. Selection of an incorrect package causes the deployment to fail.
2. Create the DRL file:
   1. On the perspective menu, click New Item → DRL file.
   2. In the Create new DRL file dialog box, define the resource name as helloworldrule and check that the Package option is set to <default>.
   3. Click OK.
3. In the displayed DRL editor with the helloworldrule.drl file, define the rule:

   rule "helloworldrule"
   ruleflow-group "helloworldgroup"
   when
   then
   	System.out.println("Hello World!");
   end
   

   This rule does not define any when condition, that is, it will always be true when fired (called to execute) and the Hello World! phrase will be printed.
4. Click Save.
5. A Save this item prompt is displayed. Enter the Check-in comment and click Save.

   Note

   The check-in comment would be a short description of the kind of change you made and has to be entered every time an asset is saved.

1. Open your Business Process in Process Designer: in Project Explorer, select the HelloWorld project, click on the BUSINESS PROCESSES and select the HelloWorld process.
2. In the displayed Business Process designer with the helloworld process, expand the Object Library palette with Process Elements: click the double-arrow button ( ) in the upper left hand corner of the Business Process designer tab.
3. Expand the Tasks menu and drag-and-drop the Business Rule task to the canvas on the right.
   Adjust flow connections so as to integrate the task into the workflow.
4. Select the Business Rule Task and define its properties in the Properties panel:
   • Name: BusinessRule
   • Ruleflow Group: helloworldgroup
     The Ruleflow Group property defines the group of rules that should be fired when the Task is being executed. In this example, only one rule, the helloworldrule rule defined in the helloworldrule.drl file, is present in the helloworldgroup group.
   

   Figure 6.1. The HelloWorld process with the Business Rule Task and its properties.

5. Save the changes by clicking the Save button in the upper left corner.

1. On the main menu of Business Central, go to Authoring → Project Authoring.
2. In the Project Explorer, locate the HelloWorld project.
3. Open the Project in the Project editor: in the Project Explorer, click the Open Project Editor button.
4. Check that the correct Project details are displayed on the Project Screen. Change the version number of the Project and click the Save button.
5. Click the Build → Build & Deploy in the upper right hand corner of the Project Screen view.

1. Click Process Management → Process Definitions on the main menu.
2. On the displayed Process Definitions tab, locate the HelloWorld. You might need to click Refresh to have the deployment displayed on the list.
3. Click the Start( ) button next to the Process definition entry and in the Form dialog box, click the Submit button to confirm that you want to instantiate the process.
   The Process is instantiated with the currently logged-in user as the process owner and the process form is displayed (the form can serve to request input from a user on Process instantiation if defined; refer to the Red Hat JBoss BPM Suite User Guide).

Procedure 8.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 8.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 8.3. Configure jBPM Runtime

1. From the JBoss Developer Studio menu, select Window and click Preferences.
2. Select jBPM → Installed jBPM Runtimes.
3. Click Add...; provide a name for the new runtime, and click Browse to navigate to the directory where the runtime is located.
4. Click OK, select the new runtime and click OK again. If you have existing projects, a dialog box will indicate that you have to restart JBoss Developer Studio to update the Runtime.

Procedure 8.4. Configure the Server

1. Open the view by selecting Window → Open Perspective → Other and select 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 installed.
6. Provide a name for the server in the Name field, make sure that the configuration file is set, and click Finish.

Procedure 8.5. 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 8.2. 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 8.6. 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 8.3. 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 8.4. Wizard for Project Import

Procedure 8.7. Creating a New Red Hat JBoss Developer Studio Project

1. From the main menu, select File → New → Project.
   Select Drools → Drools Project and click Next.
2. Enter a name for the project into the Project name: text box and click Next.

   Note

   JBoss Developer Studio provides the option to add a sample HelloWorld Rule file to the project. Accept this default by clicking Next to test the sample project in the following steps.
3. Select the Drools runtime (or use the default).
4. Select code compatible with Drools 6.0.x. Enter a GroupID, an ArtifactID, and Version, and click Finish.
5. To test the project, right click the Java file that contains the main method and select Run → run as → Java Application.
   The output will be displayed on the console tab.

Procedure 8.8. Creating a New JBoss BPM Suite project inRed Hat JBoss Developer Studio

1. From the main menu, select File → New → Project.
   Select jBPM → jBPM Project and click Next.
2. Enter a name for the project into the Project name: text box and click Next.

   Note

   JBoss Developer Studio provides the option to add a sample HelloWorld Rule file to the project. Accept this default by clicking Next to test the sample project in the following steps.
3. Select the jBPM runtime (or use the default).
4. Select generate code compatible with jBPM 6 or above, and click Finish.
5. To test the project, right click the Java file that contains the main method and select Run → run as → Java Application.
   The output will be displayed in the console tab.

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 BPM Suite.
4. From the Version drop-down menu, select version 6.1.0.
5. Select Red Hat JBoss BPM Suite 6.1.0 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.