-
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 – Mark system tasks for deletion when you create them
By Phil Coulthard For system tasks in your business process definitions (BPDs), select the Delete task on completion check box on the Implementation tab of the properties in IBM Process Designer. With this option selected, tasks are automatically deleted when they complete, which can save a significant amount of data from being persisted. Note that the […]
-
Good practice – Purge data regularly
By Michael Scheible If your IBM® Business Process Manager data grows without bounds, it can over time lead to disk space issues and to performance issues as database queries take longer and longer to process. Therefore, it is important to have a policy of continuously removing older data. There are a number of places within […]
-
Good practice – Avoid large business objects in a process or service
By Andy Garratt Business processes in IBM® Business Process Manager should store only the data that is needed for the process or a service in the process as the process runs. Avoid large “cargo” object data being carried through the process because that data needs to be persisted as process instance state. When large amounts […]