Tag: business_process_manager_express

  • Good practice – Plan for disaster recovery

    By Chris Richardson Many factors, ranging from human error to natural disasters, could compromise the capability of the hardware infrastructure that runs your IBM® Business Process Manager (BPM) system. To preserve business continuity when an entire data center is lost, it is important to have a disaster recovery plan. This plan describes the operational procedures […]

  • Good practice – Back up your IBM BPM data regularly

    By Meng Wang Back up your IBM® Business Process Manager (BPM) data regularly, particularly after you make discrete configuration changes, such as installing a new system, applying interim fixes, deploying applications, and changing the topology, which you would do for vertical or horizontal scaling. It is also especially important before purging any data. The more […]

  • Good-practice resource – Use the IBM Business Process Manager Interactive Installation and Configuration Guide or the Interactive Migration Guide

    By Dave Hay The IBM Business Process Manager Interactive Installation and Configuration Guide takes you through the steps for installing and configuring IBM Business Process Manager (IBM BPM) by using installation and configuration rules and considerations that are described in other topics in the documentation. If you are migrating business data and applications from a […]

  • Good-practice resource – Tune your IBM BPM performance

    It is imperative to your success that you read and follow the advice in the appropriate IBM Redpaper™ for your release: IBM Business Process Manager V8.5 Performance Tuning and Best Practices IBM Business Process Manager V8.0 Performance Tuning and Best Practices IBM Business Process Manager V7.5 Performance Tuning and Best Practices Also see 5 Things to Know […]

  • Good practice – Avoid excessive use of server-side JavaScript

    By Phil Coulthard Avoid large server-side JavaScript blocks within BPDs and services, because JavaScript is interpreted and therefore is slower to process than other compiled mechanisms, such as Java™ code. Furthermore, large JavaScript scripts often indicate that too much integration logic is being placed in the business process layer instead of having that logic encapsulated […]

  • Good practice – Turn off auto-tracking in BPDs if it is not required

    By Phil Coulthard Auto-tracking in IBM® WebSphere Lombardi Edition and IBM Business Process Manager is important for many business process definitions (BPDs) because it helps you gather, track, and report key business metrics. However, an additional cost comes with auto-tracking because these events are processed by the Performance Data Warehouse and persisted in the database. […]

  • Good practice – Use efficient SQL statements

    By Andy Garratt When you write SQL statements directly in IBM® Business Process Manager, such as from server-side JavaScript in a service, ensure that you use typical SQL good practices for performance and resiliency. Avoid using ‘SELECT * from ‘ When you use ‘SELECT * ‘ all the fields from the table or view are […]

  • Good practice – Place Process Center near where your Process Designer users are physically located

    By Phil Coulthard If you have a geographically disperse business process management (BPM) development team, it is better to have regional IBM® Process Centers than to have a single shared Process Center that is accessed by remote Process Designer authoring clients. The Process Designer interacts frequently with the Process Center for authoring tasks. For this […]

  • Good practice – Avoid multiple sequential system lane activities

    By Phil Coulthard In IBM® Business Process Manager, minimize the extra resources that are needed for multiple system lane transitions. Each system lane activity is considered a new Event Manager task, which adds a task transition in IBM Process Server. These task transitions are expensive. If your business process definition (BPD) contains multiple system lane […]

  • Good practice – Avoid mutually dependent toolkits

    By Phil Coulthard In IBM® Business Process Manager, design toolkit hierarchies to avoid mutual dependencies by factoring out common content into its own toolkit so that the other toolkits can refer to it independently. If you update the dependency on a child toolkit, you need to take a new snapshot of that parent toolkit for […]