cancel
Showing results for 
Search instead for 
Did you mean: 

Quality of Services "Exactly Once in Order"

Former Member
0 Kudos

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.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I think it found that leaves the iDOCS with Quality of Services "Exactly Once in Order." The iDOCS arriving from R/3 of my set to arrive only by 1 tail in the SMQ2

/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter

This apparently means that iDOCS run in a serializable

http://help.sap.com/saphelp_nw04/helpdata/en/bd/277264c3ddd44ea429af5e7d2c6e69/content.htm

Former Member
0 Kudos

Mi scenary is:

R/3 (IDOC) --> XI --> DATABASE (JDBC)

Former Member
0 Kudos

Julian,

I don't understand what is your problem now.. Do you WANT or NOT to maintain order of messages..?

Peter

Former Member
0 Kudos

Peter,

I want to pass messages to the engine J2EE with the Quality of Service "Exactly Once."

Regards.

Juliá

Former Member
0 Kudos

Remove serialization from your outbound IDocs.

Peter

Former Member
0 Kudos

Hi

To do this make sure the check box for maintain order on the interface determination of your interface is not checked as it will make the QOS to be EOIO.

Hope it works for you

Nikhil

Former Member
0 Kudos

So this set.

The problem was because I had configured on the table IDXQUEUE (/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter) a single queue entry into XI, and now removed the parameter if fall with the Quality of Service Exactly Once.

Best Regards.

Julian

Former Member
0 Kudos

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.

Former Member
0 Kudos

Julian, your rquest is not clear.

What is your scenario? IDocs are outbound or inbound?

Peter