-
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 […]