Rule set execution statistics are provided for each thread (XU) in the cluster. The Ruleset in Statistics View displays an array that contains information about the execution of rule sets, both for each thread (XU) in the configuration and for the entire cluster. If it takes a long time to run the rule set, consider reducing both the analysis time and the actual execution time. A good indication that you should focus on reducing crawl time for rule sets is if you notice a long response time to the first rule set request, if rule execution slows down intermittently, or if the server takes a long time to start. If you receive timeout error messages when you run rules, try to reduce both the analysis of rule sets and the actual execution time. The statistics table for the rule set contains the following columns: Executing the metric and rule set. The rows in the statistics table contain the following information. The duration is expressed in milliseconds. In many companies, you have many rules that you have to work with in your daily activities. Banks will apply rules to find the right balance between granting excessive risk loans and not lending to keep their business afloat. Insurance companies will use rules to determine a rate based on an incredible variety of factors, such as .
B a potential customer`s driving record of where they live, the type of car they own. even credit scores! Even retailers can use rules to determine if a coupon can be used for certain types of products, brands, etc. If it takes a long time to run your rules, you should first rule out any other factors that might affect performance, such as searches in . B database and network latency. You can view rule set statistics for a rule application on the rule execution server/decision server verwenden_to rule set statistics for a rule application. An exception can occur in rule criteria or rule actions for several reasons, of which NullPointerException (NPE) is common. NPE occurs with reference data types, such as class and string objects. Therefore, all required items must be checked for NULL from the beginning of the flow. However, there are many other types of exceptions that we may not even be aware of. Hard code: Yes, if something can be created in a rules engine, it can be written as pure code in almost any language. Granted, there`s an incredible amount of control, but at the end of the day, the result is hard-to-manage code.
This code can be difficult to learn and understand, even for another programmer, let alone a professional user. Are business users directly involved in maintenance? Forget it! The gap between business and IT is especially dangerous when you consider that something could be misunderstood, or even completely overlooked, between developing, writing, reading, interpreting, and executing business needs. Rule set execution time = Rule set parsing time + Actual rule set execution time database: If you deal with many rules in similar formats, you can put everything in a database. This can give business users CRUD (Create, Read, Update, Delete) features, but there still needs to be a lot of code behind the scenes to run the process and go through each table – code that encounters the same issues described above. This is also to the detriment of flexibility: the rules must respect the rigid structure defined in the tables. In addition, the resources devoted to creating a decent frontend can be significant, especially if this front-end is designed to be reasonably flexible. To be clear, ODM rules are far from the only rules engine that exists today. There are others that exist on a variety of platforms.
However, ODM rules are distinguished by their user-friendly features, including developer and testing tools and governance features. These features not only improve business participation, but also reduce the time it takes to implement these changes. ODM Rules is also very flexible. Although it is based on a Java platform, it is most often run as a SOAP or REST web service that can run on virtually any major platform, including Microsoft`s .NET. For implementations that require it, there is also a version of the ODM rules for z/OS. (READ: ODM Rule Components) When they hear about a new product, many have an initial instinct of skepticism – sometimes to their advantage, sometimes not. Especially when introducing a brand new product, it is difficult to get rid of old habits – which is often very understandable. However, without a business rules engine, options for implementing business rules are limited, likely to one of the following alternatives. An example of a rule written in the ODM Rules business rules language When we work on business applications, we often encounter circumstances in which the company says that only a subset of rules should be applied to the data in the request if the request meets certain conditions. In other words, the rules engine has to decide which rule to run based on the agenda, and the rest has to be ignored. In other words, the effectiveness of the rules depends on the date of request received by the calling application, and we call this selection a dynamic rule.
However, we can still capture the exception in other algorithms and at the rule flow level using the IlrContext.setRuleflowExceptionHandler method, but execution stops. .