Quality of Services "Exactly Once in Order"

Hi,
I have several integration using iDOC output R / 3.
This integration into the Integration Builder them removed brand "Maintain Order At runtime" (Quality of Services - Interface Determination) to be executed in parallel, but when they reach the engine J2EE appear with the Quality of Services as "Exactly Once in Order."
Why this happens with iDOCs? . With RFC do not have this problem.
Best Regards
Julian.

Hi
I have been reviewing the integrations that run in parallel and gave the impression that really do not run in parallel (Quality of Services "Exactly Once"), but that the channel receiver is taken so that the previous interface ends of inserting data into the receiver.
If open the message and revise the log, the first message that arrives is in this state:
"JDBC adapter receiver channel JDBC_XXX_YYY_Receiver: started processing; Party, service ZZZ_BS "
But the following is not enough to reach this state and it is with this log:
"Receiver JDBC adapter: started processing; QoS required: ExactlyOnce "
One step before the first message, only runs the next step when the first message ends to be processed by the adapter.

Similar Messages

RFC Exactly once in order

I deployed EJB to enable RFC Sender Adapter to work in exactly once in order
this is the code I used :
package com.netafim;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import javax.ejb.CreateException;
import com.sap.aii.af.mp.module.ModuleContext;
import com.sap.aii.af.mp.module.ModuleData;
import com.sap.aii.af.mp.module.ModuleException;
import com.sap.aii.af.ra.ms.api.DeliverySemantics;
import com.sap.aii.af.ra.ms.api.*;
@ejbLocal <{com.netafim.EOIORfcLocal}>
@ejbLocalHome <{com.netafim.EOIORfcLocalHome}>
@stateless
@transactionType Container
public class EOIORfcBean implements SessionBean {
        public void ejbRemove() {
        public void ejbActivate() {
        public void ejbPassivate() {
        public void setSessionContext(SessionContext context) {
                myContext = context;
        private SessionContext myContext;
Create Method.
        public void ejbCreate() throws CreateException {
                // TODO : Implement
        public ModuleData process(ModuleContext moduleContext,ModuleData inputModuleData, String queueName)
                throws ModuleException {
                        try {
                        Message msg = (Message)inputModuleData.getPrincipalData();
                        msg.setDeliverySemantics(DeliverySemantics.ExactlyOnceInOrder);
                        msg.setConversationId(queueName);
                        inputModuleData.setPrincipalData(msg);
                } catch (Exception e) {
//                 raise exception, when an error occurred
                ModuleException me = new ModuleException(e);
                throw me;
//                 return XI message
                return inputModuleData;
when I excute the function I get the following error in the comuunicatin chanel monitoring : no paramter was found.
in the paramters in the adapter modules tab I just wrote the queue name
for example : ( its supposed to be a string )
RFC******************queueName************XBIO_0001
still the module doesnt reconzie it.
Is the code above will add the functionaly of Excatly once in Order to the RFC Sender Adatper ? whats wrong with the paramters ?
thx,Shai

Hi,
<i>
data is sent "exactly once in order".</i>
>>>I am not sure about this document which assures it is always EOIO.
I am sure that using proxy communication u can do the quality of service as EOIO.
To maintain the sequence in the client ABAPproxy with ABAP code-http://help.sap.com/saphelp_nw2004s/helpdata/en/65/40c9a4a1fa476288ac61b5fcc6bbde/content.htm
Regards,
Moorthy

Exactly Once In Order ..in File adapter ???

Hi Xi friends..
in my file to idoc ..
i am getting files as wear*.xml .
i think , i have to use Exactly once in Order in Communication Channel to process multiple files in order starting with wear*.xml
if i select Exactly Once In Order..
i have to give Queue Name..
please tell me which queue name to be given here..
please tell me how to use this Exacly Once in Order option..
thanks and regards
Ram

Hi Ram,
The XI supports Synchronous and Asynchronous delivery; in XI terms, these
are described with a Quality of Service (QoS) descriptor. The XI supports
QoS Best Effort (BE), Exactly-once (EO), and Exactly-once-in-order (EOIO).
These are equivalent to RFC types Synchronous RFC (sRFC), Transactional
RFC (tRFC), and Queued RFC (qRFC), respectively.
EOIO (Exactly Once In Order):
Messages are delivered with the same queue names (supplied by the application) in the same sequence that they were sent from the sender system. Message processing is asynchronous in this case.
In the case of quality of service BE, an error occurs if more than one receiver is determined for a message. In the case of delivery types EO and EOIO, the message is copied correspondingly and sent to the individual receivers.
Ckeck this link
http://help.sap.com/saphelp_nw04/helpdata/en/41/b714fe5ffc11d5b3ea0050da403d6a/frameset.htm

FTP - Sender File Adapter - Exactly Once In Order

We are running SP10 on PI7.0
I have a file (FTP - content conversion) to idoc scenario and this works well apart from the communication channel picking up the files in the wrong order.
I have set to Exactly Once In Order, and the nuemrically file is being picked up in the correct order, however we wish to pick the file up by time and date stamp.
If I flag the Adapter Specific Message Attributes - and Source File Time Stamp, will this then process the files by timestamp instead of by File name?
How else can we get the files to process by time created?

but this option is valid for NFS transport protocol
http://help.sap.com/saphelp_nw70/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
●      Processing Sequence (for transport protocol File System (NFS))
If you used placeholders when specifying the file name, define the processing sequence of the files:
○       By Name: Files are processed alphabetically by file name.
○       By Date: Files are processed according to their time stamp in the file system, starting with the oldest file.
Message was edited by:
        Prabhu S

Exactly once in order in adapter engine

We have a user case that requires using R/3>XI>adapter-->back end system. There is requirement for maintain the message in exactly the order comes in.
the issue is, when the adapter or back end system part has some kind of error, we can see in the run time workbench the messages will repeat trying for several times before turning to "system error". Seems to me during the re-send process by adapter engine, the order of the original message get easily be lost. and we do not want this.
Any input on how to solve this?

normally the quality of service for a message is set in the sender (refer to http://help.sap.com/saphelp_nw04/helpdata/en/41/b714fe5ffc11d5b3ea0050da403d6a/content.htm). Did you check, if this is set correctly in the incoming message in XI? (in sxmb_moni, entry SOAP Header:ReliableMessaging has a tag <SAP:QualityOfService>) Only if this is really set to EOIO the receiver adapter will handle the message in one queue. What happens then, is that if the queue fails with one message, all later messages are blocked because the erroneous message blocks the complete queue.
best regards
Christine

Changing Exactly-Once-in-Order Processing in the Adapter Engine

During some issues with hanging messages in some communication channels I noticed that messages for other receivers were also on hold. So adapter engine was processing all messages EOIO while Integration Server does that per receiver.
I found the [solution in the SAP Help |http://help.sap.com/saphelp_nw04/helpdata/en/45/13b942f14d29efe10000000a114a6b/content.htm] but I am not able to access the mentioned link: http://<host><port>/MessagingSystem/migration.jsp
Error message I got is: 404 not found.
Looks like something changed! I checked some simular links like http://<host>:50000/MessagingSystem/monitor/monitor.jsp and that works fine.
(I also checked the role SAP_XI_ADMINISTRATOR_J2EE was included in my userprofile)
Please help me finding what I do wrong...or what has changed.

Hi Sunil,
ok, but do you know how what happened with the
http://<host>:50000/MessagingSystem/migration.jsp
I need that link to change the EOIO processing in the adapter engine.
Regards,
Michel

Need some clarifications on Quality-of-services

Hi Everybody.
I need some clarification on Quality-of-services.the question is which one is better in Quality-of-services (Exactly-Once or Exactly-Once-In-order)?why?wht is the differenc between them?

Hi Narayana
refer the below Urls
make the QOS of file as EO or EOIO and then use this blog,
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
It depends upon the Adapter,Can you please spicific
http://help.sap.com/saphelp_erp2005vp/helpdata/en/41/b714fe5ffc11d5b3ea0050da403d6a/content.htm
Check these blogs written on QoS:
XI Asynchronous Message Processing: Understanding XI Queues
How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework
EO = Exactly Once ( Used in Asynchronous Communication)
EOIO = Exactly Once In Order ( Used in Asynchronous Communication)
BE = Best Effort ( Used in Synchronous Communication)
Best Effort --> Used for Synchronous Calls.
EO and EOIO --> Asynchronous Calls.
EOIO --> Asynchronous with Sequential Processing Guranteed.
http://help.sap.com/saphelp_nw04/helpdata/en/41/b714fe5ffc11d5b3ea0050da403d6a/frameset.htm
For the QOS, u can refer the following library links .
http://help.sap.com/saphelp_nw04/helpdata/en/41/b714fe5ffc11d5b3ea0050da403d6a/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm
For receiver channels QoS BE (Best Effort) will result in a
synchronous call (sRFC) , QoS EO (Exactly Once) will create a
transactional call (tRFC) to the BC. For sender channels a synchronous
call (sRFC) will result in a message with QoS BE, a transactional call
(tRFC) will result in a message with QoS EO.
QoS EOIO is not supported by the BC-Adapter.
SAP XI term Quality of service describing how the transmission and process-ing of messages is to be handled. Possible values are:
BE = BestEffort (synchronous call, no transactional guarantees for transmission and processing)
EO = ExactlyOnce (asynchronous call, guarantee for local transactional handling, exactly-once transmission and exactly-once processing)
EOIO = ExactlyOnceInOrder (as for EO but with serialization guarantee on a given queue name).
<b>Pls reward if useful</b>

Changing Quality of Service in Receiver Adapter

Hi,
We have a scenario where hundreds of messages for the same interface is sent to XI and written to one file on the receiver side. We do not want to change the QOS (Quality of Service) to EOIO (Exactly Once in Order) on the sender side nor do we want to use BPM due to performance issues.
Is there any way to change the QOS to EOIO after the mapping is complete?
I tried changing the QOS (DeliverySemantics) using a adapter module on the receiver adapter. In the audit log, I can see that the QOS has been changed to EOIO and assigned to the correct ConversationId, but the messages does not follow the EOIO process.
Any help is great appreciated.
Thanks.
Best Regards,
Duke

Here is more detail on the scenario.
Hundreds of messages come into XI from R/3. One message is split into multiple messages by using the Extended Interface Determination. These messages are written to a file (each message has its own file). The file adapter is set to append.
The issue we are facing is that when hundreds of messages are processed simultaneously, it triggers an error when attempting to write to the file (locking issues). It then has to wait and retry, which adds to total processing time. Due to the time sensitivity of these interfaces and the errors that are raised, we would like to change the QOS to EOIO on the receiver side (when it writes to the file) so that it does not have to wait and retry.
The Maintain Order at Runtime is checked in the Interface Determination. Once it gets to the adapter framework to write to the file, it has a QOS of Exactly Once, which is carried over from the sender.
We do not want to change the QOS on the sender side, but only on the receiver side.
Any thoughts?
Thanks.
Best Regards,
Duke
Edited by: Duke on May 29, 2008 5:11 PM

Exactly once(option) in QOS filesender

hi.
i want to know the difference between EXACTLYONCE,EXACTLY ONCE IN ORDER,BEST EFFORT options in quality of service.
waiting for your response.
cheers.
seeta ram.

hi michal.
thanks for your answer.
but i just want clear my doubt.
here in my scenarion iam testing file to bapi by putting exactly once in(QOS)Of file sender adapterand the procesing mode of sender file adapter as test.
but i forgot to deactivate file sender adapter and now iam getting ptoblems with ICM IN MESSAGE MONITORING(SXMB_MONI)
ITS SHOWING IN XMLPAYLOAD AS
400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
wat would be the reason for this.
waiting for yur answer.
cheers.
seeta ram.

Quality fo service to receivers.

do we have the quality fo service to receivers.I mean EO,EOIO,BE

Hi,
do we have the quality fo service to receivers.I mean EO,EOIO,BE
No.
BE (Best Effort):
The message is sent synchronously. The sender waits for a response before it continues processing.
EO (Exactly Once):
The message is sent asynchronously. The sender does not wait for a response. The Integration Engine Extern guarantees that the message is sent and processed exactly once.
EOIO (Exactly Once In Order):
Messages are delivered with the same queue names (supplied by the application) in the same sequence that they were sent from the sender system. Message processing is asynchronous in this case.
In the case of quality of service BE, an error occurs if more than one receiver is determined Seite 468 for a message. In the case of delivery types EO and EOIO, the message is copied correspondingly and sent to the individual receivers.
Synchronous Message Processing (BE)
The message is not persisted by the Integration Engine. Once a message has been processed in the target system it performs an implicit database commit.
Asynchronous Message Processing (EO, EOIO)
The message is persisted by the Integration Engine at a predefined time and scheduled for processing using the queued RFC Extern (qRFC).
Thanks
Vikranth

EOIO Quality of Service

Hi guys,
We have developed a File-XI-Idoc scenario, which works fine.
The problem is that we want each file that is found in the folder where XI reads files, to be processed first and the corresponding Idoc that is produced from the mapping to be posted in receiver R/3 system first.
In order to achieve that we have used EOIO QoS in processing parameters of sender file communication channel. Although, files are processed by XI one by one, since they are put in the same queue, it is not guaranteed that Idocs are posted to R/3 in the same sequence,
We had a case that Idocs were posted exactly at the same time in receiver R/3 system and the one that should be processed second was processed first. The second Idoc (that should be processed first) was locked due to concurrent modification of the same material.
Is there something else that I can do in receiver Idoc adapter, for example??
Evaggelos

Use the Queue Processing option of the receiver Idoc channel
Queue Processing
If the function module IDOC_INBOUND_IN_QUEUE is to be used, set the relevant indicator. It is used for IDocs that are serialized by queues (quality of service is EOIO). This module is only available in SAP Web AS 6.40 and higher. If it is not available, the function module IDOC_INBOUND_ASYNCHRONOUS is called. The indicator only takes effect in SAP systems Releases 4.0 and higher. Calls for the queue processing function module are placed in the qRFC queue.
Regards,
Prateek

RFC TO SOAP - Quality of Service

Hi,
i see that my RFC to SOAP test functioning properly. But in Exactly Once mode. In RFC Sender adapter and SOAP Receiver adapter there is no configuration tab to change "Quality of service".
Is it possible to change the mode?
Kind Regards,
PM

It is not possible to set the QoS at Channel leve for RFC receiver.
Have a look at this thread: tRFC & qRFC
for SOAP, look at this discussion: Re: In what QOS does the receiver SOAP adapter work BE or EO?
Regards
Ramesh
Edited by: Ramesh P on Dec 30, 2011 1:17 PM

Quality of Service and Jitter issues

I am having poor quality of service (36%) and Jitter issues (36ms). I called Verizon Fios technical support and was told that my connection is fine and that it must be a vendor issue. Only vendor I'm having an issue with is Verizon. If I can't get someone from Verizon that knows what QoS and Jitter is on the phone to help me troubleshoot this issue I'm going to have to cancel my service and find a provider that has someone technical providing tech support.

Upstream jitter
35.7 ms
Downstream jitter
6.0 ms
Upstream packet loss
0.8 %
Downstream packet loss
0.0 %
Upstream packet order
100.0 %
Downstream packet order
100.0 %
Packet discards
5.1 %
MOS
3.4

Quality of service in Receiver file/ftp adapter (SAP PI 7.1)?

Hi,
    We are building an IDoc to File scenario in SAP PI 7.1, where a single incoming idoc will create three different output files. Also files must be created in target server in a specific order.
    Our first idea to ensure that files would be created following a specific order was that Message mapping (in Java) build target payload with all three files following expected sequence.
    In addition, receiver file/ftp adapter is setup with a dynamic variable to create each file with a different filename adding also timestamp.
    Testing the scenario, we see that three files are created in target server but when we sort them by creation date, it seems they don't follow always same sequence.
    Sometimes adapter creates File1, File2, File3; next time it created File2, File1, File3 and so on.
    Our problem is that files must be created always with a specific order and we cannot use BPM. Does anyone know if a receiver file/ftp adapter can be setup to create files following specific sequence (EOIO)?
    I know that sender file/ftp adapter can be setup with a quality of service, but I didn't find anything similar for Receiver file/ftp adapter.
    Suggestions will be welcome.
Kind Regards,
Aitor

Hi,
     First, thanks all of you for your quick answers. They were helpful because we learnt a new configuration setting.
     We tried your suggestions but they didn't really fix our problem.
     Finally interface has been re-designed and we will not have to apply this logic, so no issue from our side.
     However, let me continue with this topic in case that somebody else will have the same issue, then it will be able to review this thread.
     When adapter created the files in the target directory (windows server), files had the expected timestamp in each filename. However, if we sorted windows directory contents by "Date Creation", files were sorted different that timestamp shows in the filename.
     For example, adapter created following files:
File1_20090325-115117-169
File2_20090325-115117-174
File3_20090325-115117-180
     But when we sorted windows folder contents, files were sorted as follows:
File2_20090325-115117-174
File1_20090325-115117-169
File3_20090325-115117-180
     It seems that timestamp was pre-assigned by the adapter, but when adapter created the files, it did it with a temporary name and finally assigns the filename. If a file size was bigger than other, maybe it takes more time and windows creation date is higher.
     If so, it means that adapter is not following same instructions as itu2019s indicated in "maintain order at runtime" checkbox.
     Do you know if there is any way where we can push also the order in the adapter as we did in interface determination?
Regards,
Aitor

How to Resend OR Cancel Exactly Once Messages

Dear all,
I have nearly 20 messages with status "Holding" under adapter engine message monitor.
These interfaces are Exactly Once type. I am trying to Resend or cancel them. Nothing worked here.
When i check the error reason for the Holding status message, it says warning " Empty document found. Proceed without sending message"
Referred this weblog /people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
Please suggest me how to deal with these...
Regards
Edited by: Bhavana Ch on Feb 14, 2011 5:56 PM

Hi Bhavana,
I came to a similar error situation when whether restarting nor canceling was possible and I was looking for an solution instead of restarting the whole java stack.
We restart the messaging service of the java engine and this solves the error, canceling or restart was possible afterwards. The correct service should be XPI Service: Messaging System in Netweaver Adminstrator -> Operation Management -> Systems -> Start&Stop -> Java EE Service, unfortunately I lost my remarks of this error situation, so you have just to try it.
If this will not solve the issue, I think you have to go for restarting the whole java server.
please let me know if this solve the error.
Regards,
Jochen

Quality of Services "Exactly Once in Order"

Similar Messages

Maybe you are looking for