Download PDF (1.3 MB) - IBM Redbooks

Minimizing the number and size of Business Process Execution
Language variables and business objects
Use the following guidelines when you define BPEL variables and BOs:
► Use as few variables as possible and minimize the size and the number of BOs used. In
long-running processes, each commit saves modified variables to the database (to save
context), and multiple variables or large BOs make this process costly. Smaller BOs are
also more efficient to process when emitting monitor events.
► Specify variables as data type variables. This specification improves runtime performance.
► Use transformations (maps or assigns) to produce smaller BOs by mapping only fields that
are necessary for the business logic.
3.2.7 Human task considerations
Follow these guidelines when developing human tasks for BPEL business processes:
► Use group work items for large groups (people assignment criterion: Group) instead of
individual work items for group members (people assignment criterion: Group Members).
► Use native properties on the task object rather than custom properties where possible. For
example, use the priority field instead of creating a custom property priority.
► Set the transactional behavior to commit after if the task is not part of a page flow. This
setting improves the response time of task complete API calls.
3.2.8 Business process and human tasks client considerations
Consider the following information when developing effective BPEL business process and
human task clients:
►
►
►
Do not frequently call APIs that provide task details and process details, such as
htm.getTask(). Use these methods only when required to show the task details of a single
task, for example.
Do not put too much work into a single client transaction.
– In servlet applications, a global transaction is typically not available. If the servlet calls
the Human Task Manager (HTM) and Business Flow Manager (BFM) APIs directly,
transaction size is typically not a concern.
– In Enterprise JavaBeans (EJB) applications, make sure that transactions are not too
time-consuming. Long-running transactions create long-lasting locks in the database,
which prevent other applications and clients to continue processing.
Choose the protocol that best suits your needs.
– In a J2EE environment, use the HTM and BFM EJB APIs. If the client application is
running on a Business Process Manager server, use the local EJB interface.
– In a Web 2.0 application, use the REST API.
– In an application that runs remote to the process container, the web services API is
an option.
Chapter 3. Development best practices 37