QOS in File scenario

[GabrielSagaya]

In Sender File CC has QOS as BE, EOIO, EO => can be asynchronous as well as synchronous

but in Receiver CC has QOS as EOIO, EO but not have BE==> not synchronous at receiver side.

Why???

[prabhu_s2 · Accepted solution]

recv CC of file adapter doesnt support sync comm

[ranjit_deshmukh · Accepted solution]

Do we really have a QOS for receiver adpt?

I am not sure. I am having SP12 PI7.0

I cant see any QOS in Receiver adpt

Ranjit

[Former Member]

Hello

We don't use sync communication using file adapters. BE is for sRFC syncronous communications, EO is for tRFC asyncronous, and EOIO is for qRFC in asyncronous .

[Former Member]

hi gabriel,

>>Receiver CC has QOS as EOIO, EO

receiver cc doznot have QOS. it takes qos from integration engine (the one that is specified for sender's side)

file interface can only be asynch and never synch. althoh u have an option of specifying it as BE (at sender side)...even if u do it ur response scenario will fail as file will never send a response and at other side will never wait for a response!!

[reward if helpful]

regards,

latika.

[aashish_sinha]

it supports only Async communication for file adapter , thats why EOIO/EO.

Regards

Aashish Sinha

PS : reward points if helpful