IBM Sterling B2B Integrator

Transcription

1 Sylvain Fontaine - Sterling B2B Integrator Technical Support Engineer September 2015 IBM Sterling B2B Integrator Business Process Design from a Performance Perspective 2009 IBM Corporation

2 IBM Presentation Template Full Version Introduction: About IBM Sterling B2B Integrator: The IBM Sterling B2B integrator is a complex business process execution engine. The architecture of the application contains several layers that each play a critical role in the availability of the service. For each phase in the implementation there are some "Best Practices" that should be followed to make the best possible use of the application. The Key Phases in a project are: Application Installation Application Development Move to Production IBM Corporation

3 Architecture overview Custom developments (Web Application / Custom Services) Custom Business Process ISBI Application Database Java Virtual Machine Operating System / Kernel Hardware Infrastructure Network Infrastructure IBM Corporation

4 Business Process Development Best Practices Define a naming convention for all types of ressources: business processes, maps, adapter and service configurations etc. Design reusable Sub Processes that complete specific tasks so they can be called from various Parent business processes. This avoids having to manage complexe Business Processes that are difficult to visualise in the graphical modelling tool. It also avoids duplicating code and bpml logic accross different business processes, Whenever possible, favour trigerring Business Processes from Adapters in Bootstrap mode. It avoids running schedules when there are no files to process, IBM Corporation

5 Business Process Development Best Practices Apply changes to bpml code incrementally, and test only one modification at a time to control and understand the impact of each modification. Use the Description field to specify what has changed in the BP. (Avoid using version numbers like «v015» in Descriptions) Avoid designing Business Processes that can Persist more than 1000 Steps to the Database in a single execution. Avoid creating Bpml Loops without controlling when to exit the loop. Always maintain the Process Data to a small or reasonable size, Use the Release Service to remove unnecessary parts of the Process Data when they are not needed anymore to keep the Process Data small. Use the Lock Service to avoid mutually excluding processes, IBM Corporation

6 Business Process Development Best Practices Use the most recent versions of Services and Adapters and avoid using Services or Adapters that are being deprecated. When Invoking business processes, avoid passing the entire Process Data to the Parent or Child bp. Use the "message_to_child" or "message_to_parent" xpath functions to pass selected parts of the Process Data to the parent or child bp. Make the appropriate choice betweeen using the Wait or the Sleep services The Wait Service will free u the executing thread for another bp. The Sleep Service holds on to the thread so it is not released for use by another BP IBM Corporation

7 Business Process Development Best Practices Use the On Fault Group to include Error Handling logic in the business process to determine what level of Alert should be raised in case of error. Use a unique name for each Sequence Start section in the bpml in order to be able to address multiple On Fault groups within the same bp. For Business Processes doing Client communication protocols such as HTTP(s), FTP, FTPS or SFTP, you should include a Connection Close condition in the On Fault group to graciously close connections for failed connections. Use Inline Invocation method for small bp's with few steps. Use the Asynchronous Invoke method for bp's with many steps. When invoking multiple Child processes from a Parent bp, preffer using the Asynhornous invoke method to run multiple threads in parallel IBM Corporation

8 Business Process Development Best Practices Restrain from reading information from the File System or from the Database. Try reading information from memory whenever possible, it is much faster. Avoid using Wildcards in xpath expressions, such as // For Xpath functions, it is much faster to use the full path rather than a relative path: /ProcessData/myService/myData/text() is much faster than //mydata/text() Avoid using advanced xpath functions for doing calculations or retrieving date stamps etc. It is usually much faster to do these operations in Services, Adapters or in SQL code IBM Corporation

9 Moving the Business Processes to Production Once the development phase is over you need to do unit testing and volume testing to optimize the business processes before moving them to Production. It is important to do volume tests to know what the behavior of the application will be when under heavy load. (The re-queuing of business processes may cause some surprises. Test the business processes by progressively reducing the persistence level and viewing what tracking information is available in the user interface. The Goal is to have the lowest possible persistence level for the most executed business processes but keeping the necessary level of tracking information in the user interface IBM Corporation

10 Moving the Business Processes to Production You need to define the appropriate Recovery Level for each bp (Auto Restart, Auto Resume, Manual or Terminate). Consider using Deadlines at the BP check in to prioritize the most critical workflows to meet their SLA's. Choose the appropriate execution Queue based on the type business process you are checking in. Consider changing some queue configuration parameters to better meet the requirements of the business processes placed in the queue IBM Corporation

11 Choose the appropriate execution Queue based on the type business process you are checking in. Test the business processes with the lowest possible Persistence Level and verify there is sufficient tracking information available in the user interface for your business needs IBM Corporation

12 Moving the Business Processes to Production Determine the appropriate Recovery Level for each bp (Auto Restart, Auto Resume, Manual or Terminate). Consider using Deadlines during the BP check in to prioritize the most critical workflow's to meet the Service Level Agreements IBM Corporation

13 Moving the Business Processes to Production Configure the retention period based on the criticality of the Business Process. Every bp in the system should not have the same default life span. It is recommended to Purge data directly when possible and only Archive sensitive or critical production data IBM Corporation

14 Moving the Business Processes to Production IBM Corporation

15 This Support Technical Exchange session will be recorded and a replay will be available on IBM.COM sites and possibly social media sites such as YouTube. When speaking, do not state any confidential information, your name, company name or any information you do not want shared publicly in the replay. By speaking in during this presentation, you assume liability for your comments IBM Corporation

16 Reférences additionnelles Learn about upcoming Support Technical Exchange webcasts, and access previously recorded presentations at: IBM Electronic Support Introduction Sign up to receive weekly technical My Notifications s: developerworks Forums, Communities and Technical Topics Quick Reference Guide for Using Service Request Tool IBM Support Assistant Access product show-me demos and tutorials by visiting IBM Education Assistant: IBM Corporation

17 THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM S CURRENT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION, NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO NOR SHALL HAVE THE EFFECT OF CREATING ANY WARRANTIES OR REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCT OR SOFTWARE. Copyright and Trademark Information IBM, The IBM Logo and IBM.COM are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks and others are available on the web under Copyright and Trademark Information located at IBM Corporation