One of the most used artifacts in IBM ODM is the decision table. In this post I will show how to populate your Decision Table in the Rule Designer with external data sources like a .txt file or an excel spreadsheet. Business users can have their logic in multiple sources (mostly in Excel files), that they need to dump in a decision table to create rules and business logic behavior in IBM ODM. We are going to achieve this by using a combination of Java, Ant builds and ilog rule designer-plug ins embedded in our suite. This is a very technical tutorial and it might be a little difficult to get it done quickly but feel free to contact me with any problems or if you get stuck at some point.
- Setting up environment
- Create a new folder (in my case “dt-populate”) in your Rule project with a “data” subfolder and with an Ant Build file.
- Tip: You can also create and manage the ant and data configuration in a new external Java project.
- Create an environment variable ECLIPSE_HOME with the location of your IBM ODM installation.
- Insert the txt or the excel file with the data you want to import in the data folder. In my example I am using both, please have this considerations:
- Creating the Ant Build file
- Add the project tag with a name, basedir and a default target attributes.
- Tip: For more about Ant Tasks review my previous post here.
- Inside the project tag we are going to add the properties, conditions, echo messages, definitions and our targets. For each of you will be different depending in your environment and ODM installation.
- Tip: Remember to change the values according to your workspace and installation folders.
- Now let’s add the definitions the includes the properties and connection parameters.
- Finally, we add the targets.
- Remember to change the values according to your environment and also review the excel file extension.
- Running the Ant build file targets
I hope you enjoy this tutorial, there are many more automation and integration to be done with Ant Tasks, please let me know what you wish to see next, and as always feel free to comment or contact me with any feedback or support! Thank you!
In this post I will show a new way to start your Rule Projects, using a new IBM Bluemix Business Rules service feature called “Decision Composer”. This is currently in experimental mode but you can start to fully utilize its main features and see if it helps you in your organization. The decision composer is a new way to model your rules using the Decision Modeling Notation (learn more about DMN here), it is also very useful to business users with no ODM technical skills to define and model Rule Projects.
- Creating a Decision Composer project
- First we need to access our IBM Bluemix account and select our Business Rules Service. If you don’t have an account or the Business Service installed please refer to my previous Bluemix post here.
- Click on the “Open Decision Composer”
- Click “New Project”, give it a name and click “Create Project”. For this sample I will create a simple recruitment eligibility rule.
- Tip: You can import your XOM schema from a file or URL too
- Modeling rules in the Decision Composer
- By default we get a decision “Hello World” with a message, we can simply erase these 2 artifacts.
- Create a “data node”, it will create a square box representing a Decision Node. Click on it to modify it’s properties on the left panel. For my sample the output is a Boolean (true or false).
- Now that we have our Decision Node we need to add the Input data that will determine the rule outcome. Hover over decision node, click the + symbol and select “Input Data”.
- Do the same for each data field you need in your rule, in my sample I will need the age and sex of the candidate.
- Tip: Remember you can specify default values for each data
- Now we need to edit our business logic. Select the decision node and click “Edit decision logic” on the left panel. We can work with rule actions or decision tables. In this sample I will use a simple decision table to specify some rules:
- Set a default value for the outcome variable:
- Save your changes.
- Testing and deploying our Decision project
- Return to the main project screen, click “Run” and test the different scenarios of your rules:
- Now you can deploy your project to your Bluemix Business Rules RES. Return to the project selection screen, hover over your decision project and click “Deploy”
- Input the Bluemix RES URL, username and password. Your rule is ready to use on the cloud.
- Integrating the project with IBM ODM Rule Designer
- A great feature is that you can download this project and import it to your Rule Designer Eclipse workspace.
- In the same options list, click “Download”.
- In your Rule Designer workspace select File – Import – Existing projects into Workspace. Search for the files by viewing all file types and that’s it!
Let me know if you want to see more content like this and explore with the Decision Composer and DMN more. I hope you enjoy this tutorial and as always please feel free to contact me for any feedback or questions! Thank you!
Given the positive feedback from previous post we will continue to work further on with the ODM API and discover new possibilities and features to implement in our Rule projects. In this tutorial we will see how to create a custom log file, focusing on obtaining the values from Deployments of Decision Services within the Business Console.
To understand the basics of the IBM ODM, please refer to my previous post about the IBM ODM API here.
- Creating a custom log file
- In our Java ODM API project let’s create a global variable to define the output file.
- Now create a constructor method to add the values you want in your custom log file. In this example we are obtaining the deployment time stamp when a business user deploys a Decision Service from the Business Console:
- Tip: Remember we need to throw an IOException class for our constructor.
- We can continue adding the values we require in our outfile variable. In this code example we are getting the following values:
- Tip: Remember to format the log file with methods like newLine() and flush().
- Now we need to repackage and reinstall the teamserver.ear with our custom jar file and it will automatically start generating the log file when we make a Decision Service deployment. I will make a post explaining this process in detail in the future.
If we did not specify an output location for the log file you will find it in <Your WAS Installation Path>\logs. I hope you enjoy this tutorial it helps you, please feel free to contact me with any feedback or questions! Thank you!
To deploy RuleApps to Rule Execution Server, automate managerial tasks within Decision Center, and run many of the samples, you must have Ant installed on your computer. IBM ODM comes with Ant in the <InstallDir>/shared/tools/ant path. In this tutorial I will show how to use Ant tasks to automate RuleApp management tasks, including reading a specified RuleApp archive from the RES console, create a well-formed RuleApp archive with all its mandatory execution resources and deploy a RuleApp archive to a running Rule Execution Server instance.
First of all we need to set up our environment to automate processes, please follow the steps in this link.
- Downloading RuleApp instances from RES
- Create an Ant Build file, you can this directly in your Rule project in Eclipse:
- Define your project and property variables values.
- Tip: You can define properties for your common values like hostname, destfile, userid and password.
- Please find the next sample as a demonstration of a working Ant build file:
- The target res-fetch command extracts a specific Ruleapp value, the res-fetch-all will generate a .war file with all the Ruleapps present in the RES
- Deploying into RES with Ant Tasks
- Now that we have our jar file ready, we can automate the deployments with Ant Tasks by using the res-deploy command.
- You will need to add a new target to your build ant file or create a new one, this command requires the login credentials, jar path and hostname.
- Please refer to the following example:
After running our deploy command we see our Ruleapp deployed in the RES:
There are many more automation and integration to be done with Ant Tasks, please let me know what you wish to see next, and as always feel free to comment or contact me with any feedback or support! Thank you!
IBM Bluemix is a cloud platform that helps you solve real problems and drive business value with applications, infrastructure and services. There are other powerful cloud services like AWS, Azure or Google Cloud platform but IBM Bluemix comes with pre-designed services for your IBM software solutions. In this article we will see how the Business Rules service allows us to deploy our Decision Operations from Rule Designer or Decision Center console directly to IBM Bluemix cloud. In order to test this you will need to create a IBM Bluemix account that comes with 30 days free trial.
- Creating the Business Rules service
- Login to your IBM Bluemix account.
- Click “Catalog” and search for “Business Rules”
- Tip: This service gives you 1,000 API calls free per month that is more than enough for dev purposes, you can cancel the service at any time.
- Click “Create” and give a proper name.
- Navigate to the “Connection Settings” tab and you should be able to see the connection details like this:
- Tip: Click “Open Console” and navigate just like in your RES local installation.
- Configuring the Deployment
- Now that our Business Rules service on IBM Bluemix is ready, let’s configure and deploy the Rule project.
- Open Rule Designer and navigate to the deployment folder of the Rule project.
- If you have a previous deployment configuration already set up you can just add the new IBM Bluemix RES server target:
- Insert the Bluemix connection details and test the connection.
- Deploy the Decision Operation Ruleapp and verify the deployment by accessing the IBM Bluemix RES console.
- The Ruleapp should appear like this:
- Testing our Rule web service in SoapUI
- Navigate to the Ruleset view by clicking on the Ruleapp Name and then the Ruleset name in the RES console.
- Click the “Retrieve HTDS Description File” option:
- Download the SOAP HTDS file or click view and copy the WSDL URL.
- Open SoapUI and create a New SOAP project.
- Insert the wsdl URL, username and password.
- Now you have the request ready, the only thing missing is the security authorization. Click the “Auth” option and select Basic, type the Bluemix Business Rules service username and password.
You are ready to call your Rules from anyplace, anywhere. Just share your WSDL url with the client application and give the proper authorization. Having the Rule Execution Server on the cloud is a great way to test your rules in development without depending on your local Sample Server.
I hope you enjoy this tutorial and as always please feel free to contact me for any feedback or questions! Thank you!
The XOM (Execution Object Model) and BOM (Business Object Model) are key artifacts of our Rule project. The execution object model (XOM) is the model against which you run rules, it references the application objects and data, and is the base implementation of the business object model (BOM). For more information about XOM/BOM visit the IBM Knowledge Center here.
We can generate our BOM entries from a XOM (Java or XSD) and get the objects we will verbalize for our rules. A very common requirement in a project is to work with Lists and return a populated List with values from a Rule Action or Decision Table. You will notice that after you create your BOM entry from an XOM with Lists (maxOccurs=”unbounded”) you will get an object of type java.util.Vector but with no direct relationship between the elements. Please review the following problem example and a workaround on how to fix it and implement Lists correctly.
Let’s say you have an XSD with an element like this:
<element name=”recruits” type=”tns:Recruit” maxOccurs=”unbounded” minOccurs=”0″></element>
After you create the BOM entry, you will get an object like this:
With no proper verbalization and without a way to use it in a Rule Action, Decision Table or Decision Tree correctly. In this example we want to add objects of type Recruit to our RecruitsList and display this list in the output of our Decision Service. Follow the steps below to implement a workaround and accomplish our goal.
- Creating a new Method member
- Let’s remove this verbalization and navigate to the Class tab.
- We are going to create a new method to add our Objects. Click “New…” in the Members section.
- Select “Method”, give a proper Name and “void” for Type.
- Now add Arguments according to the Object you are going to add to your list, in our example the Recruit’s attributes. At the end you should have something like this:
- Tip: Remember that the types have to match, if you are using a virtual value assign the corresponding type like the example. For more information about dynamic domains and virtual values read my previous post here.
- Now we need to create a proper verbalization for our new method and implement the BOM to XOM Mapping logic.
- Navigate to the Member Verbalization section and click “Create”. Modify the Action phrase according to your Object. In this sample:
- The last and most important step is to define our BOM to XOM Mapping logic. We need to map our method arguments with the attributes of our Object, in this sample with the Recruit’s age, country, name and sex:Tip: Don’t forget to initialize the response list variable in your ruleflow or variableSet.
Now we are ready to use our method in any Rule and return a list structure schema in our Decision Service response!
Decision Table demonstration sample:
After we test our rules we will see this list structure in the response (Testing with SoapUI):
Please feel free to comment or contact me with any doubts or feedback. Thank you!
There are many ways to test our rules, we can use Excel DVS testsuites, decision operations, web services applications like SoapUI and more, but sometimes we need to debug our ruleflow to find a particular bug that is preventing us to continue. When developing a new rule project in Rule Designer we often need to see the output of our rules without having to deploy our solution and see the behavior of the ruleflow to compare the variables values.
In this article I am going to show how to debug a simple ruleflow using a decision operation to test your Rules.
Let’s assume we already have the ruleflow, variables and rules.
- Creating the Decision Operation
- Right click the “deployment” folder in your Rule Project and select New -> Decision Operation.
- Give a proper name, select the Rule Project and select the Ruleflow inside your Rule Project.
- Now open your Decision Operation and you should have one like this:
- Click “Define” or to the “Signature” tab.
- Expand your varible set and drag and drop the corresponding variables to the Input and Output Parameters.
- Tip: Is a good practice to name your input variable with “Request” at the end and “Response” for your output.
- Setting the breakpoints
- There a many places where we can define our breakpoints, it depends on what you need to test and where do you want the flow to stop execution. I will show some examples of places where you can put your breakpoints next.
- Action Rule:
- Decision Table:
- BOM member
- Ruleflow artifacts
- Creating the Debug Configuration
- Navigate to Run -> Debug Configurations… in your Rule Designer top bar.
- Locate the Decision Operation artifact, right click and select New.
- Give a proper name and Browse for your Decision Operation.
- Tip: The checkbox “Stop at first rule statement” guarantees you enter debug mode if you didn’t set any breakpoints.
- Now the most important step is to define the “Parameters and Arguments” for this configuration, select the tab and click “Edit Value”.
- You have to create and return a new object of your Input Parameter class, you can also assign testing values. Click “Function body” and add the proper code. Take a look at my sample:
- Click Apply and Debug.
Now you are in Debug mode, watch your variables and step through your code and rules!
I hope you enjoy this article, as always please feel free to contact me about any question or feedback. Thank you!
A very common requirement in a Rule development project is to manage some data objects with dynamic domains. But wait, what are domains? A Domain places a restriction for your BOM members, this includes attributes, method arguments and classes. For more information about domains click here.
There are many ways to use Domains, the easiest way is to use Static References to define the possible values. But what if we want to have an external source to manage and update our values frecuently? Well, that’s when Dynamic Domains come in handy. In this tutorial we will focus on creating dynamic domains from an excel file.
The IBM knowledge center provides an article about this topic but without some key details that can make you spend more time than neccesary.
- Creating the Domains Values Excel File
- The Excel file must have the structure defined by the Excel Domain Provider:
- Value column
- Label column
- BOM to XOM column
- Documentation and additonal labels/documentation for other locales (Optional)
- You can have multiple sheets, each one representing a Domain. Example: Countries, Cities, Streets, etc.
- Each row represents a value for that particular Domain, you cannot have merged cells.
- Here is an example of how your excel file should look like:
- Tip: If you want to have the option to send a blank value use “None” or “NA” in the Values and Label columns and return “”; in the BOM to XOM column. Check the example above.
- Save the Excel file in the resources folder or your BOM rule project.
- The Excel file must have the structure defined by the Excel Domain Provider:
- Creating the Dynamic Domains from the Domains Excel File
- It is recommended to have the Domain values in a separate BOM model, or at least in a separate package from your original objects. Here is a simple example:
- Create a class in your new BOM model for each Domain you have. In this example “CountryValues”.
- Open the new class and expand the BOM to XOM Mapping section. In the Execution name field you need to specify the type for your Domain values, for example java.lang.String:
- Now you are ready to create your dynamic domains, locate the Domain section and click Create.
- Select the Excel option under Dynamic Domains, click Next and then select your excel file.
- Select the correct sheet for the Domain you are working on and check the “Table with Header” option to see the column header values. Now map the columns to the appropiate field, here is how your final mapping should look like:
- The values should appear in the Domain section:
- You can update the values by modifying the Excel file and clicking “Synchronize” or at the BOM Entry level, clicking “Update”:
- Creating the virtual attribute
- Our first intention would be to change the type our attribute to our new virtual class but this would create a duplicate of the original member and a BOM to XOM conflict error. That is why we need to create a virtual member for each attribute that is going to use Domains.
- Create a new member in your Class editor and in the type field select the virtual class with the Domains. In this example we are going to create “countryVirtualName”:
- Verbalize the member accordingly. You will need to change Edit the subject to elaborate correct sentences for Action and Navigation fields. Remember to delete the original member verbalization.
- Check the “Ignore for DVS” option to avoid having the virtual value being added when testing with DVS Excel testsuites.
- And the last but most important step is to finish the BOM to XOM mapping. In Getter return the original member and in Setter assign the value to the original member. Example:
- Creating the Domains Values Excel File
Now you are ready to use Dinamyc Domains for your BOM members like in the Decision Table sample below:
Please feel free to contact me with any queries or feedback about this article. Thank you!