Configure Bootstrap Adapters Outside Business Process Models
Application includes several bootstrap adapters – adapters that can start processes dynamically without being part of the process model. When building your business process models, do not include these adapters as the first step in a business process model. Using bootstrap adapters in this way is preferable because your goal is to reuse components whenever possible, for easier maintenance of your process models. If you create Design Guidelines for Business Process Models Sterling Commerce, Inc. 6 an adapter configuration specific to the business process, you are less likely to be able to reuse the adapter configuration to start other business processes.
Keep Subprocesses Manageable
Keep each subprocess to a manageable size. If the subprocess performs multiple activities, consider splitting it into multiple, smaller subprocesses. This approach enhances reusability and simplifies maintenance. Another consideration is how you intend to invoke subprocesses. If you are using inline invocation of subprocesses, the impact on performance is relatively small, whereas asynchronous invokes can have a more marked negative effect on performance. If you need to use asynchronous invokes for your subprocesses, consider building the steps into the parent process instead.
Performance Differences of Invocation
Asynchronous invocation will cause you to fire off a subprocess as another WFD_ID.� This means that� the business process will be returned to the queue by the ops controller for another listener in that queue to execute the business process. The parent wil not wait for the child to complete to continue to the next steps.
Synchronous invocation will cause the parent to fire off a subprocess as another WFD_ID as well.� This means that� the business process will be returned to the queue by the ops controller for another listener in that queue to execute the business process.� The parent will wait for the child to complete to continue to the next steps
Inline invocation will cause the parent to invoke the subprocess as part of the same WFD_ID.� This mean the business process will not have to be returned to the queue and will continue as part of the same process. �
Keeep your business process and subprocesses manageable. Refractoring and breaking processes into smaller units of work allows you reduce overhead.
Inline performs the best because you don't have to return the business process to a queue.� An inline process will inherit it's parents queue setting.� Refer to "when to use what invocation" for determining what subprocess invoke method is best for you.�