Hi manas mahani ,
These r the details regarding Queues while handling file to idoc scenario:
Queues for Prioritized Message Processing
http://help.sap.com/saphelp_nw04/helpdata/en/04/827440c36ed562e10000000a155106/content.htm
Queue prioritization for XI processing queues uses a built in feature of qRFC. By specifying the maximum processing time for a queue, u can define how much processing time a specific queue will get(this works like a time-scheduling procedure, time slicing). U can use this feature to add queues for high-priority and low-priority messages(for inbound and outbound processing). These queues are then named, for example XBT1* or XBT9* for inbound EO processing and XBTA, XBTZ for outbound EO processing.
This function uses the message filter concept and can be configured in transaction SXMB_ADM. U can define message filters for specific message attributes such as sender/reciever service, interface and so on. A filter can also be dependent on the message size.
This function can also be useful in situations where a queue backlog needs to be processed, due to a system error or an error on the reciever side, for example. In this case, u can use a Prioritized queue for urgent messages that must be processed immediately, without having to process the whole back-log first.
How to prioritize XI messages on the integration server
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972...
The parameter QualityOfService specifies how the Integration Engine should process a message. The following values are permitted:
1)BE(Best Effort: synchronous processing). If QualityOfService is BE, the client is sent the final status for the processing.
2)EO(Exactly Once: asynchronous processing with guaranteed execution exactly once). If QualityOfService is EO,processing occurs asynchronously and the client only recieves a confirmation of reciept with HTTP status '200'.
3)EOIO(Exactly Once in Order: asynchronous processing using queues, that is, guaranteed execution exactly once and maintaining the sequence of successive messages). If QualityOfService is EOIO,processing occurs asynchronously and the client only recieves a confirmation of reciept with HTTP status '200'.
Since u had choosen EOIO ,You must also define a queue name for EOIO:
XI.QueueId=<QueueName>
This queue name is used in the Integration Engine to process messages in the same sequence that they arrived in.
This QueueName can consist of a maximum of 16 characters. If the first 8 characters contain 'SAP_ALE_', these r removed since this value is reserved by SAP and used internally.
If a value is not specified for QualityOfService , the default value 'BE' is used.
These r following websites which u wil find helpful:
http://help.sap.com/saphelp_nw04/helpdata/en/0d/00453c91f37151e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm
http://documentation.softwareag.com/crossvision/xie311/admin/config.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a8424011-0d01-0010-e19d-e5b...
cheers!
gyanaraj
****Pls reward points if u find this helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.