Queue handling for FTP?!

[Former Member]

Hi, well its the first time i have to handle with queues.

We have the scenario: File2IDoc

...where the files in the folder should be read EOIO and processed EOIO due to writing in R/3 Database.

How to handle this?!

br

[Former Member]

Hi,

Pls check this out..

http://help.sap.com/saphelp_nw70/helpdata/en/f0/02a63b9bb3e035e10000000a114084/frameset.htm

Regards,

Pratibha

[nisarkhan_n]

all you have to do is to maintain the QOS in the file adapter as EOIO and define the queue name

Message was edited by:

n Khan

[Former Member]

> all you have to do is to maintain the QOS in the file

> adapter as EOIO and define the queue name

>

> Message was edited by:

> n Khan

Hi, so do i have to maintain a queue name in module-paramters as decribed in posts before?! Is this working, when i have files in folder and these should be read one after another?! Or how can i control this....

br

[nisarkhan_n]

check this:

For delivering the messages the queue name is used it doesn't matter whatever u give as queue name

The queue name is nothing but it is an identifier for the message sender, every message is then send with the same queue name that means it will be persisted by the integration engine. XI uses QRFC functionality for this purpose.

try this and let us know else give queue specific for EOIO like XBQO*

[Former Member]

Hi have a look on the following

SMQ1 – qRFC Monitor for the outbound queue You can use this to monitor the status of the LUWs in the outbound queue.

SMQ2 – qRFC Monitor for the inbound queue. You can use this to monitor the status of the LUWs in the inbound queue.

SMQS – You can use the Outbound Queue Scheduler to register, deregister, and exclude destinations.

SMQR – You can use the Inbound Queue Scheduler to register and deregister queues

http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/eae2a889e711d2956500a0c94260a5/frameset.htm

You can use transaction SMOHQUEUE (Replication Queues Monitor) for displaying the

Replication Queue Monitor and information about.

http://www.realtech.com.sg/wDeutsch/software/application_manager/Applications/SAP/CRM_DC_WP_EN.pdf

http://documents.bmc.com/supportu/documents/92/28/59228/59228.pdf

Thanks

sudhir sharma

[Former Member]

Hi,

In addition to earlier replies check these two very imp blogs on queues in XI message processing:

XI Asynchronous Message Processing: Understanding XI Queues:

/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i

Introduction to queues in message mapping:

/people/venkat.donela/blog/2005/06/09/introduction-to-queues-in-message-mapping

Regards,

Subhasha

[Former Member]

Hi Carsten Heinrich ,

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...

Reward Points if u find it useful.

cheers!

gyanaraj

[Former Member]

&#9632; XI.QualityOfService=<QualityOfService>

Specifies how the Integration Engine should process a message. The following values are permitted:

&#9632; XI.QualityOfService=BE(Best Effort: synchronous processing)

&#9632; XI.QualityOfService=EO(Exactly Once: asynchronous processing with guaranteed execution exactly once)

&#9632; XI.QualityOfService=EOIO(Exactly Once in Order: means asynchronous processing using queues. This means guaranteed execution exactly once following the sequence of successive messages)

You must also define a queue name for EOIO:

&#9675; XI.QueueId=<QueueName>

This queue name is used in the Integration Engine to process messages in the same sequence that they arrived in.

http://help.sap.com/saphelp_nw04/helpdata/en/0d/00453c91f37151e10000000a11402f/frameset.htm