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 2.1. Unlocking assets

1. Open the asset.
2. Click on the Overview tab and open up the Metadata screen.
   If the asset is already being edited by another user, the following will be displayed in the Lock status field:
   Locked by <user_name>
3. To edit the asset locked by another user, click Force unclock asset button.
   The following confirmation popup message is displayed:
   Are you sure you want to release the lock of this asset? This might cause <user_name> to lose unsaved changes!
4. Click Yes to confirm.
   The asset goes back to unlocked state.

Procedure 3.1. Creating an organizational unit

1. Open the Administration perspective: on the main menu, click Authoring → Administration.
2. On the perspective menu, click Organizational Units → Manage Organizational Units.
3. In the Organization Unit Manager view, click on the Add button. The Add New Organizational Unit pop-up window opens.
   

   Figure 3.1. Add New Organizational Unit Pop-up

4. Enter the mandatory details:
   • Organizational unit name.
   • Owner.
5. Click OK to create the unit.

Procedure 3.2. 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 3.2. 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 Finish

Procedure 3.3. 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 3.3. 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.The repository will be indexed. Some workbench features may be unavailable until indexing has completed.

1. Open the Project Authoring perspective: on the main menu, click Authoring → Project Authoring.
2. In the Project Explorer, select the organizational unit and the repository where you want to create the project.
3. In the perspective menu, go to New Item → Project.
4. In the Create new Project dialog window, define the project details:
   1. In the Project text box, enter the project name.
      
5. The explorer refreshes to show a New Project Wizard pop-up window.
   
6. Define the Project General Settings and Group artifact version details for this new project. These parameters are stored inside the pom.xml Maven configuration file.
   • Project Name: The name for the project; for example MortgageProject
   • Project Description: The description of the project which may be useful for the project documentation purpose.
   • Group ID: group ID of the project; for example org.mycompany.commons
   • Artifact ID: artifact ID unique in the group; for example myframework. Avoid using a space or any special character that might lead to an invalid name.
   • Version ID: version of the project; for example 2.1.1
   The Project Screen view is updated with the new project details as defined in the pom.xml file. Note, that you can switch between project descriptor files in the drop down-box with Project Settings and Knowledge Base Setting, and edit their contents.

Procedure 3.4. Creating a new package

1. Open the Project Authoring perspective: on the main menu, click Authoring → Project Authoring.
2. In the Project Explorer view, do the following:
   • If in the Project view of Project Explorer, select the organizational unit, repository and the project where you want to create the package.
   • If in the Repository view of Project Explorer, navigate to the project root, where you want to create the package.
3. In the perspective menu, go to New Item → Package.
4. In the Create new Package dialog window, define the package details:
   1. In the Resource Name text box, enter the package name and click OK.
5. The new package is now created under the selected project.

1. Open the Project Editor for the given project:
   1. In the Project Explorer view of the Project Authoring perspective, open the project directory.
   2. Click on the button to open the project view.
2. In the Project Screen view, select in the Project Settings drop-down box the Dependencies item.
3. On the updated Project Screen, click the Add button to add a maven dependency or click the Add from repository button to add a dependency from the Knowledge Store (Artifact repository):
   • When adding a maven dependency, a user has to define the Group ID, Artifact ID and the Version ID in the new row which is created in the dependency table.
   • When adding a dependency from the Knowledge Store, select the dependency in the displayed dialog box: the dependency will be added to the dependency table.
4. To apply the various changes, the dependencies must be saved.

1. Click Authoring → Project Authoring and navigate to your project.
2. In the Project Explorer window, click Open Project Editor.
3. Click Project Settings: Project General Settings → Knowledge bases and sessions. This view provides a user interface for changing kmodule.xml.
4. Click Add to define and add your bases.
   1. After you enter a name for your Knowledge Base, add Packages. For including all packages, click Add below Packages and enter asterisk *.
5. Below Knowledge Sessions, click Add and enter the name of your session.
6. Mark it Default and select appropriate state.
   For Red Hat JBoss BRMS, you can choose between stateful and stateless sessions. Use stateless if you do not need iterative invocations of the facts. Otherwise, use stateful session.
7. Click Save in the top right corner once you are done.

1. Open the repository view for your project.
   

   Figure 3.4. Changing to Repository View

2. Navigate to /src/main/resources/META-INF. Click on kmodule.xml to edit the file directly.
3. Define your kbases and ksessions. For example:

   <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <kbase name="myBase" default="true" eventProcessingMode="stream" equalsBehavior="identity" packages="*">
       <ksession name="mySession" type="stateless" default="true" clockType="realtime"/>
     </kbase>
   </kmodule>
   

4. Click save in the top right corner.

1. In the Project Authoring perspective, click New Item → Data Object on the perspective menu. Enter the name and the location (the name has to be unique across the package, but it is possible to have two data object with the same name in two different packages). Uncheck the Persistable box to prevent the Data Object from being made persistable. Press the Ok button.
2. Create fields of the data object:
   1. By clicking add field button in the main editor window, you can add a field to the object with the attributes Id, Label and Type. Required attributes are marked with *.
      • Id: field ID unique within the data object
      • Label: label to be used in the Fields panel (optional)
      • Type: data type of the field
      
   2. Click the Create button (the new field is created and the New field window closes) or the Create and continue button (the new field is created and the New field window remains open, so it is possible to continue adding more fields).
   Attributes can be edited selecting the attribute and editing the fields using the general properties screen to the right.

Procedure 5.1. Creating a Persistable Data Object

1. When creating a persistable Data Object, the Identifier field id will be generated automatically, along with the @Entity annotation.
   
   Selecting the List option changes a property to have multiple values. For example, it can enable an attribute Name, to have a list of strings with multiple names.
2. Create fields of the data object:
   1. By clicking add field button in the main editor window, you can add a field to the object with the attributes Id, Label and Type. Required attributes are marked with *.
      • Id: field ID unique within the data object
      • Label: label to be used in the Fields panel (optional)
      • Type: data type of the field
      
   2. Click the Create button (the new field is created and the New field window closes) or the Create and continue button (the new field is created and the New field window remains open, so it is possible to continue adding more fields).
   Attributes can be edited selecting the attribute and editing the fields using the general properties screen to the right.

Procedure 6.1. Creating a new rule

1. In the Project Explorer view, do the following:
   • If in the Project view of Project Explorer, select the organizational unit, repository and the project where you want to create the rule.
   • If in the Repository view of Project Explorer, navigate to src/main/resources/ and the SUBFOLDER/PACKAGE where you want to create the project folder for the rule template.
2. In the perspective menu, go to New Item → Guided Rule.
3. In the Create new Guided Rule dialog window, define the package details:
   1. In the Resource Name text box, enter the Guided Rule name and click OK.
4. The new Guided Rule is now created under the selected project.

Procedure 9.1. Creating a new Test Scenario

1. Open the Projects view from the Project Authoring menu.
2. Select the project where the test scenario is to be created.
3. From the New Item dropdown menu on the toolbar, select Test Scenario from the listed options.
4. Enter the Test Scenario name in the pop-up dialog box and click OK.
5. You will be presented with the Test Scenario edit screen.
   

Procedure 9.2. Importing a model for the Test Scenario

1. Use the tabs at the bottom of the screen to move between the Test Scenario edit screen and the Config edit screen.
2. The Config screen allows you to specify the model objects that you will be using in this Test Scenario.
3. Data objects from the same package are available by default. For example, if you have a package structure org.company.project, and you have a data object Fact1 in package org.company and a Fact2 in package org.company.project, you will not have to import model objects for Fact1 if you want to create a Test Scenario in package org.company; however, you will need to import Fact2 if you want to use it.
4. To import the data objects that are required for your Scenario, click on the New Item button in the Config screen.
5. These imports can be specific to your project's data model or generic ones like String or Double objects.

Procedure 9.3. Providing Test Scenario Facts

1. After you have imported the data objects, come back to the Test Scenario screen and enter the variables for your Scenario.
2. At the minimum, there are two sections that require input: GIVEN and EXPECT
   • GIVEN: What are the input facts for this Test Scenario?
   • EXPECT: What are the expected results given the input facts from the GIVEN section?
3. GIVEN these input parameters, EXPECT these rules to be activated or fired. You can also EXPECT facts to be present and to have specific field values or EXPECT rules not to fire at all.
   If the expectations are met, then the Test Scenario has passed and your rules have been created correctly. If the expectations are not met, then the Test Scenario has failed and you need to check your rules.

Procedure 9.4. Providing Given Facts

1. To add a new fact, click on the green + button next to the GIVEN label. This will bring up the New Input dialog box. Provide your fact data in this window based on the data models that you have imported in the Config screen.
   
   You can select a particular data object from the model and give it a variable name (called Fact Name in the window), or choose to activate a rule flow group instead. If you choose to activate a rule flow group, you are allowing rules from a rule flow group to be tested by activating the group in advance. If you want to add a given fact and activate a rule flow group, you have to add the given fact, click the green + button again, and then add the activation.
2. Depending upon the model that you select, you will be able to provide values to its editable properties as part of your GIVEN fact. For example, if your model was a Product, you might have properties like itemID, productName and price. You get to these properties by clicking on the text Insert Product.
   
   By clicking on the pencil icon next to the property, you can edit the property to provide either a literal value for that property that should form part of your GIVEN fact data or you can provide advanced fact data. See Section 9.3, “Additional Test Scenario Features” for more information.

Procedure 9.5. Providing Expected Rules

1. Once you are satisfied with the Given rule conditions, you can expect that rules that will be fired if the Given rule conditions are met when the Test Scenario is run.
2. To do so, click on the green + button next to the EXPECT label. A New expectation dialog box will come up.
   
3. You can provide one of three expectations given the set of data that was created in the Given section. You can:
   • Either type in the name of a rule that is expected to be fired or select it from the list of rules and then click the OK button.
   • Expect a particular instance of a model object (and one or more of its properties) to have a certain value by selecting that instance from the drop down in the Fact Value field. For example, product1 shown in the figure, which is an instance of the fictitious Product model created in the Given section. You specify the property values by first adding that instance by clicking the Add button and then clicking a green arrow to bring up the fields to add. Once you have selected the field to add, you can provide a literal value for that field.
   • Expect a fact model to match your Given facts by selecting it from the Any fact that matches drop down. Instances of data objects are in the working memory, rather than matching what has been set up in the Given section. Rules may change the contents of working memory for example, some facts may be retracted, others inserted, and some will have their properties changed.
     In the figure shown above, you can mandate that instances of the Product's one or more properties match the Given rule conditions.

Procedure 9.6. Reviewing, Saving, and Running a Scenario

1. Once you are satisfied with your Test Scenario's facts, you can save it by clicking the Save button in the upper right corner. Ensure you regularly save and review your scenarios.
2. You can now run your Test Scenario by clicking the Run scenario button at the top of the Test Scenario screen. The results are displayed at the bottom of this screen in a new panel called Reporting.
   
3. Once you have a bunch of Test Scenarios for a particular package, you can run all of them together by accessing the All Test Scenarios tab and then clicking the Run all scenarios button.

Procedure 9.7. Calling Methods

1. Call Method - allows you to call a method on an existing fact in the beginning of the rule execution. This feature is accessed by clicking on the green plus sign next to the CALL METHOD feature. This opens up a new input box like the following:
   

   Figure 9.2. Call Method

2. After selecting an existing fact from the drop-down list, click the Add button. The green arrow button allows you to call a method on the fact.
   

   Figure 9.3. Invoke a Method

Procedure 9.8. Adding Globals

1. globals - validate the global field values. Globals are named objects that are visible to the rule engine but are different from the objects for facts. Accordingly, the changes in the object of a global do not trigger the reevaluation of rules. This feature is accessed by clicking on the green plus sign next to the (globals) feature.
   

   Figure 9.4. New Global

2. After selecting an existing global from the drop-down list, click the Add button. Clicking on the newly selected global allows you to assign values to fields of the global variable.
   

   Figure 9.5. Apply Field

3. After selecting an existing field from the drop-down list, click the OK button. Once you have selected the field, you will be able to set its value. By clicking on this icon, you will be able to edit the field values.
   

   Figure 9.6. Field Values

Procedure 9.9. Configuring Rules

1. Configuring rules - allows the user to determine additional constraints on the firing of rules by providing the following options:

   • Allow these rules to fire: - allows you to select which rules are allowed to fire.
   • Prevent these rules from firing: - allows you to prevent certain rules from firing for the test scenario.
   • All rules may fire - will allow all the rules to fire for the given test.
   

   Figure 9.7. Configuration

2. If you select Allow these rules to fire: or Prevent these rules from firing:, you will be supplied with an empty field where you can select the rules which pertain to the configuration by clicking the green plus sign next to the empty field. This will open a dialog to select which rules are affected by the condition.
   

   Figure 9.8. Selecting rules

3. Choose a rule from the drop-down list and click the OK button. The selected rules will appear in the field next to the rules configuration option. You can add as many rules as you like to this field.

Procedure 9.10. Date and Time Configuration

1. Use real date and time - the real time is used when running the test scenario.
   

   Figure 9.9. Real Date and Time

2. Use a simulated date and time - this option allows you to specify the year, month, day, hour, and minute associated with the test scenario run.
   

   Figure 9.10. Title

Procedure 9.11. Advanced Fact Data

1. After providing values to editable properties as part of your created fact, the Field value dialog box will appear where you can edit literal values or provide advanced fact data.
   

   Figure 9.11. Advanced Options

2. Within the Advanced Options section, you will be provided with various choices depending on the type of fact created and the model objects used for the particular Test Scenario.
   • Bound variable - sets the value of the field to the fact bout to the selected variable. The field must be of the right type.
     

     Figure 9.12. Bound Variable

   • Create new fact - allows you to create a new fact. By clicking on the Create new fact button, a new fact will appear as the value of the field. By clicking on that fact, you will be supplied with a drop down of various field values, and these values may be given further field values.
     

     Figure 9.13. Create New Fact

Procedure 9.12. Adding More Sections

• The Test Scenario edit screen allows you to add Given, Call Method, and Expect sections to the scenario by clicking the More button below the EXPECT section. This will open a block encompassing all three sections that can be removed by clicking the delete item button.

Procedure 9.13. Modifying or Deleting an Existing Fact

• • Modifying an existing fact - allows the editing of a fact between knowledge base executions.
  • Delete an existing fact - allows the removing of facts between executions.
  

  Figure 9.14. Modifying and Deleting Existing Facts

1. Once you have deployed the WAR file (or if you have it deployed on the same web container where JBoss BRMS is deployed), create a user with the role of kie-server in this web container.
2. Test that you can access the decision engine by navigating to the endpoint in a browser window: http://SERVER:PORT/kie-server/services/rest/server/ with the web container running. You will be prompted for your username/password that you created in the previous step.
3. Once authenticated, you will see an XML response in the form of engine status, similar to this:

   <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
   <response type="SUCCESS" msg="Kie Server info">
    <kie-server-info>
     <capabilities>BPM</capabilities>
   	<capabilities>KieServer</capabilities>
   	<capabilities>BRM</capabilities>
   	<location>http://localhost:8230/kie-server/services/rest/server</location>
   	<name>KieServer@/kie-server</name>
   	<id>15ad5bfa-7532-3eea-940a-abbbbc89f1e8</id>
   	<version>6.3.0.Final-redhat-5</version>
   	</kie-server-info>
   </response>