Tag: odm

  • IBM Digital Business Automation and Blue Prism Integration

    By integrating IBM Business Automation Workflow and RPA, enterprises can address their business requirements by leveraging people, systems, content and bots in end-to-end workflows. IBM Business Automation Workflow (BAW) traditionally relies on APIs to integrate services and systems. However, applications are often not built for integration and therefore don’t have APIs or their source code […]

  • IBM Digital Business Automation and UiPath Integration

    IBM Digital Business Automation and UiPath Integration

    By integrating IBM Business Automation Workflow and RPA, enterprises can address their business requirements by leveraging people, systems, content and bots in end-to-end workflows. IBM Business Automation Workflow (BAW) traditionally relies on APIs to integrate services and systems. However, applications are often not built for integration and therefore don’t have APIs or their source code […]

  • Decision service lifecycle on IBM Cloud Private

    By ODM technical leads: Rachel Orti and Laurent Grateau Introduction When you work on an ODM project, it is more than likely that you’ll need a number of different ODM instances to support the promotion of a decision service all the way into production. The need for a well-defined workflow is important if you plan […]

  • A practical guide on using the Decision Center archive repository tool

    By performance architect Nicolas Peulvast What does the archive repository tool do? The goal of the archive tool is to reduce the size of the in-use schema by removing the records that are inactive. A smaller schema can improve the overall performance of Decision Center. Active database records are in use by the current rule […]

  • If a DSI cluster is unstable try changing the heartbeat policy

    Diagnosis and treatment of a heartbeat failure in a DSI cluster If a Decision Server Insights cluster stops processing events or stops communicating with clients, add the -Xverbosegclog JVM parameter to the jvm.options file in your runtime servers. You can then check in the logs to see if the garbage collection (GC) pause times are […]

  • A checklist to improve the performance of Decision Center

    By ODM performance architects: Pierre-Andre Paumelle and Nicolas Peulvast Use this checklist to improve the scalability of Decision Center, and configure it for the right number of users. The checklist is divided into sections to help you locate where the optimization is done. Java virtual machines Set the initial heap size to 8 gigabytes per […]

  • A checklist to improve the performance of Rule Execution Server

    By ODM performance architects: Pierre-Andre Paumelle and Nicolas Peulvast There are significant performance gains to be had by tuning certain aspects of Rule Execution Server. The decision engine improvements made in 8.9 has much better performance compared to previous releases, and especially compared to the classic rule engine. If you switch to the decision engine […]

  • Top ten tips to improve performance of ODM on ESX

    By ODM performance architects: Pierre-Andre Paumelle and Nicolas Peulvast ESX server is an enterprise-class hypervisor developed by VMware for deploying and serving virtual computers. With ESX, a single physical server can run several virtual machines simultaneously. If you are using ESX to streamline your ODM server hardware or to deploy new servers and maintain existing […]

  • A dozen design tips to improve decision service performance

    By ODM performance architects: Pierre-Andre Paumelle and Nicolas Peulvast The following design and development tips might help you to better meet your service level agreement (SLA). Tip 1: Choose a XOM type with performance requirements in mind One of the first and most important steps when building your application is to choose which XOM type […]

  • High Availability for ODM Rule Execution Server Console using VIPA

    or most customers, having high availability (HA) for the RES console is not critical. This is because users who notice an absence of the console could ask a system administrator restart it. Furthermore, the RES console is not required for rules to run, so the rules will still execute even if the RES console is down. Also, the deployed rules won’t change, because the console could not have been used to update them; therefore, XUs will not miss any important rule updates. However, because there may be a high cost associated with a delay to rule updates, some business environments require reliable live changes. The configuration described in the following sections can help ensure high availability.