on 01-19-2009 10:06 PM
Hello All,
I am trying to get more information on load balancing Central Advance Adapter Engine for SAP PI 7.1. How do I configure and load balance Advance Central Adapter Engine to handle more volume? Should I added extra non-central adapter engines to achieve this? If yes, How do I do this i.e. configuration etc? If not, then what is the best practice on load balancing the Central Advance Adapter Engine?
Thank you for replying,
Mayur
closing it without any resolution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I just post your Q&A here.
Cheers,
Aaron
I have few follow up questions regarding your answers.
1. For options 1 and 2, could you elaborate or point me some documentation on sap.help or somewhere else which talks more about these options?
=========================================
Basically you have more power with more processes (Instances or Server node) to process your messages in the Adapter Engine. That's the way to improve the system throughput.
For more information, please refer to SAP PI tuning guide (I could not find the guide for 7.1, but the principle is still the same)
https://websmp102.sap-ag.de/~sapidb/011000358700000592892005E.PDF
=========================================
2. For option 3, add non central adapter engine and configure scenarios.
1. So, do I have to run non-central adapters on separate servers?
====================
Yes. It is recommended to run non-central adapter enging on separate server to minimize the reciprocal impact in terms of resource contention.
==============
2. Do I need web dispatcher to do the load balancing between central and non-central adapter engine?
========
No. this is also not possible since the below is true.
=========
I somehow think that if I am selecting the non-central adapter engine when creating the communication channel then it won't be "load balancing" because I will be sending a particular interface to the non-central engine at design time instead of runtime.
Thank you for taking time and replying to my questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Aaron and Alok for replying. You answers have been very helpful. I have some further question more specific a the JMS adapter. How do I load balance the JMS adapters connected to IBM MQ?
1. What is the recommended practice?
2. Does PI automatically scale itself to pull the messages off the MQ queue?
OR
3. Configure multiple JMS sender adapters connected to same queue where the messages are arriving
4. If multiple JMS sender adapters are configured, then should I be distributing the adapters across multiple Adapter Engines?
Thank you for replying,
Mayur
Hi,
Please have a look at these points:
1. PI should use three-tier system architecture to improve resource balancing.
2. Where IDoc adapter is involver and message size is high then use IDoc packaging at sender and receiver side and do not post immediately at receiver site. Always prefer to post in groups to minimize ABAP processing and reduce the number of database commit operations.
3. If there is a continuous flow of messages sent to the Integration Server. Every second a message will arrive. To optimize resources, instead of processing each message individually, we should package them up into 30 messages per package. In order to do so, we will wait up to 60 seconds for the messages to build up in the queue.
4. In case of Asynchronous scenarios, a bulk of messages can be processed in one service call and thus context switches for mapping, routing, reading message header etc. can be reduced and mass operations on the database are possible.
5. Install Http load Balancer for IS pipeline entry processing, and AE inbound processing. Different components can be used for Http Load Balancer like: SAP Web Dispatcher, Hardware Load Balancer, and Web Switch.
BR,
Alok Sharma
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mayur,
to scale up your Adapter Engine, you have serveral options,
1. Add Additional J2EE server nodes
2. Install Additional Dialog Instance ( could be combined with 1), you will need to have http loadbalancer (e.g., SAP Web Dispatcher) to distribute the http load to different instances
3. Add non-central Adapter Engine, in this case you can configure your specific scenarios to run on this non-central adapter engine by selecting the adapter engine when creating a communication channel.
Cheers,
Aaron
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.