Performance issue with XI interfaces - Help Needed

[Former Member]

Hi all,

We are having idoc->xi->file. We have the design of collecting the idocs as the standard example BpmPatternCollectTime.

We have given the collection time of say 5minutes after the first idoc hits the BPM process. The issue is that the idoc messages are getting missed when we are sending 1000 idocs. Also after applying the note 898131 for the correction of missing idocs we got the problem of the timeout exception not being triggered and workflow instance is waiting for a longtime until all the messages are getting into BPM and is getting struck in the queue.

We are into XI 3.0 SP13. Can anyone provide some help in optimizing the interfaces/server settings/etc..

Thanks in advance.

Jayakrishnan

[Former Member]

Jay,

Is there a specific reason why you did this as a time dependent one? Instead why can't the BPM wait for specific number of messages?

Regards,

Ravi

[Former Member]

Hi Ravi,

We are having the scenarios like a particular interface will trigger 4 files a day at a time interval of say 6 hrs. So the triggering of the outbound idocs were scheduled at the same interval from ISU system.

Michal: We tried the same. As i mentioned above we cannot make the scenario message count dependent as the no of messages may vary depending on the inbound idocs posted from the legacy.

Thanks & regards,

Jayakrishnan

[Former Member]

Hi all,

We have seen in the message performance header that for DB_ENTRY_QUEUING the messages are taking more time here to get assigned to the queues. Is there any way that we can optimize the same?

Thanks & regards,

Jayakrishnan

[Former Member]

Hi Jayakirshnan,

check if this helps, whether you have optimal number of dialog processes.

see theselinks as well

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/sap exchange infrastructure tuning guide xi 3.0.pdf

http://help.sap.com/saphelp_erp2005/helpdata/en/42/e7bb8f7c9d3ee0e10000000a1553f6/content.htm

Regards

Vishnu

[Former Member]

Hi Vishnu,

Thank you for the help. We went thru the thread and our dialog work process is set as 25 as the server load is expected to be high.

Also based on the tuning guide and also on the help link, we have check the performance header of the message. We noticed that DB_ENTRY_QUEUING is taking more time in our case. Any pointers to optimize this part...

Coz in our case the mapping is taking hardly 25-30 seconds for 100-500 messages into the flat structure and we are struck up in the queue waiting for our number.

Thanks & regards,

Jayakrishnan

[MichalKrawczyk]

Hi,

have you tried using IDOC packages?:

/people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages

Regards,

michal