IBM Sterling Integrator Business Process Modeling Best Practices

List of SI business process modeling best practices documentation is designed to provide information that can be a helpful reference in t... thumbnail 1 summary

List of SI business process modeling best practices documentation is designed to
provide information that can be a helpful reference in the following situations:

business process GPM


1.While planning your business process models' structure

2.While modifying existing business process models

3.While troubleshooting problems caused by the structure and configuration of
your process models

The documentation assumes that you are generally familiar with terms used in
relation to working with IBM® Sterling B2B Integrator


Using Your Company's Naming Conventions Consistently

Naming different versions of the same business process model brings special
considerations. 


Retaining Service Names in Graphical Process Models

Although you can change the names of services in your graphical process models to make them more descriptive, a good practice is to retain the service name within your new name, so that for future reference you can easily see which service you used for that step (changing the name of a service in the GPM changes the display name shown in the workspace for that service, but it does not rename the service configuration used in the process model).

Retaining the name of the service is particularly helpful so that when you need to update multiple business process models to use a new service (such as when one that you have been using is retired), you can see the service name in the process model. This saves research time.


Designing Reusable Business Processes

Whenever possible, create business processes that you can reuse so that you canavoid the work involved in creating new ones and maintain consistency in your process models.


Using Predefined Business Processes

Whenever possible, use predefined process models provided with Sterling B2B
Integrator, to save work.


Configuring Bootstrap Adapters Outside Business Process Models

Sterling B2B Integrator 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 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.


Keeping 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.


Making Modifications Incrementally 

Make incremental modifications to your business processes, and thoroughly test each change before making additional changes. This approach can save you a great deal of time because incremental changes are easier to troubleshoot than an entire business process.


Naming Versions Meaningfully

Sterling B2B Integrator stores each version of a business process model that you check in, which enables you to revert to using a previous version should the need arise. Therefore, you should employ a strategy for using the description field to differentiate business process models as you check them in to Sterling B2B Integrator, so that you can easily identify a previous version. For example, you might add a version number or identify the change made to the process.


Using the Lock Service

Use the lock service when you have a business process or resource within a
business process that should never have more than one instance running at a time.

The Lock service will need to be included twice in the business process. The first
instance to lock the resource and the second instance to unlock the resource.
Generally the lock duration is set to 2-3 times what the estimated time of execution will be so that the lock does not time-out before the business process reaches the unlock step.