My workspace

Most often after deploying new business rules in BRES, we have to redeploy IlrSession beans with our custom beans(XOM). Also developing new client for the business rules is time consuming work. Bres(Business rules execution server) provide rmi protocol and some web service support(Decision service) to invoke rules in bres. Deployed rules will be exposed only when you add your domain class(XOM) in the jrules-bres-ootbds.ear and redeploy it again in application server. All the life cycle is too time consuming to manage the whole project. However, often business analyst (Most of time, project mangers require such thing to fulfill customers demand) requires expose business rules through web service for solving business requirement with customer. In today's post i will show a agile way to expose business rules through web service and run it into jdk 6 embedded http server. We have one web service with a few methods, every method expose one business rules as a web method. For developing...

Apache tucsany provides a framework for developing SOA solution that is based on Service Component Architecture (SCA) standard. Tucsany offers following advantages: 1) Provides a model for creating composite applications by defining the services in the fabric and their relationships with one another. 2) Enables service developers to create reusable services that only contain business logic. 3) Existing applications can work with new SCA compositions. This allows for incremental growth towards a more flexible architecture, outsourcing or providing services to others. Tucsany implemented in java and c++ programming language. For more information visit apache tucsany site . In the growing uses of business rules in SOA, on the current post i decide to make a laboratory work to show how to use business rules in SCA SOA solution. For more information to get benifit from business rules please consider my some previous post about Ilog business rules. On the current tutorial we are goin...

Ilog Jrules define decision service as a ordinary web service with management capabilities using JMX MBeans. Through protocol SOAP, it's easy to invoke business rules rather than any other protocol like rmi. More information about decision services should find here. From the view of ilog jrules, there are two types of decision services: 1) Hosted transparent decision services 2) Monitored transparent decision services All of them drives rule execution and enables users to access Rule Execution Server through a Web service, rather than accessing it directly. Hosted transparent decision services: Using a hosted transparent decision service, Rule Execution Server automatically exposes any deployed rule set as web services, that uses an XML schema or a Java XOM with simple types. The decision service automatically generates Web Services Description Language (WSDL) file for each deployed ruleset archive and the decision service MBean is able to retrieve execution statistics. These rule...

Documentation which supplied with Ilog Jrules is very much helpfull to write business rules. However, to write better business rules on Ilog Jrules, we might follow some best practice, which will help us to write and manage our rules. In the current post i would like to share my experince with Ilog Jrules as a best practice guide: 1) Follow java naming conventions when creating java class which will converted to BOM. Best approach will be create class with all its functionality. 2) Use rule packages, because on ruleflow you can use rule packages to contol running business rules effectively. However by default all rules under one package will run, you can use dynamic rule selection to select and run any particular business rules. 3) Use ruleflow task to initialize any global variables, it's not good idea to auto generate variable for any bom. 4) Also it's very usefull to use task for rule packages to intialize bom which will prticipate in the current package. 5) In many ca...

With Ilog Jrules default distribution, Jboss application sever is default. But customers might choose any application server to use Jrules. In these circumstances, customers should deploy all the necessary components manually. The task is not so straight forward because Jrules consists of a few independent web components. In the following i will describe briefly how to install Ilog Jrules in OAS 10.1.3.3. Jrules consists of following three main web components: 1) RES 2) TEAM SERVER 3) SCENARIO MANAGER We follow step by step to install and deploy all the components in the OAS. 1) Install RES: 1.1) First we should create data base user and schema in Oracle DB for component Res. 1.2) Run the script in sqlplus or any other oracle sql client to create new data base objects from the following place <ILOG_HOME>\JRules672\executionserver\databases\oracle\schema_oracle.sql 1.3)Create a new oc4j instance in the OAS named Ilog_bres 1.4)Create new connection pool and data sourc...

Material of this post was published on oracle magazine (russian edition), see the following link to read the article . From the last few weeks i am working with Oracle OSB. In this post i want to share my some experince to apply Business rules engine to message broking in OSB. The full article has been written in Russian language for Oracle Magazine and will add the link soon after publish. From the few years we have been familliar with Business rules and java rules engine API(JSR-94) and successfully usees business rules on many project. From the view of OSB - sometimes it's very important to separate the business logic or policy implementions from the OSB proxy service. In any corporate business logic or business policy could change often, specially in tele-communication sector and stock exchanges. This post is not to discuss about when and why to use Business rules engine rather than how to use it with OSB to implement and separate business policy for message broking. Here i...

Last couple of months i have worked with Ilog Jrules. These BRMS has lot of functionality to use business rules effectively in any project. Sometimes it's very usefull to get some additional meta data from database to execute business rules. In Ilog jrules documentation is not so useful to know how to use JPA, however in documentation you should found a few information with bunch of code. This post will explain how to use JPA in ilog jrules project and save a couple of hours for new comm er in BRMS. At first in jrules we have to build XOM(Execution object model), which will execute all the business logic. After that we define BOM (Business object model) from XOM to write business logic's in project. For using JPA we will make a class which will get all the CRUD operations and delegate every thing to the DAO layer. Class diagram is as follows: Here implemention of the IDAOService interface is a basic implemention of the DAO pattern and initialize session manager to manage all th...

Business Rules execution server allowed management throw JMX. All the bres functionality could invoked by JMX. See jmx client sample code for getting help.

Last week we configured Ilog jrules version 6.7.2 in the OAS version 10.1.3.3. Ilog Jrules consist of three main web components as follows: 1)Rules execution server 2)Team server 3)Scenario manager First we had to define the number of oc4j instance to create and fix all the data sources. We created 1 extra oc4j instance for team server, create datasources and deploy the teamserver. One classloader problem occurred for commons-logging.jar. Just edit application.xml to unregistered shared library. Next we defined another two data source for the BRES, SCM and deploy these application on home. IrlSessionRule session bean we also deployed in home along with BRES. Next we have to define all the role and user on home instance and on the instance for the teamserver. Just never forget to assign rmi role in the user bres. Next our mission to use identity management for authorization and authentication. We also plan to clustered all the oc4j instance to solve load balancing.