File to file scenario: EOIO queue name?

hi forum,
i have file to file system, in the sender file communication channel,
i need to use qualit_of_service as "EOIO", but for that i need to use a Queue Name, what should i give as the name of the queue, for test purpose i gave the name of the queue as "xyz", but it works........
but i dont know how it worked

hI SUMIT,
i have a question for long,
i have a typical file BPM file scenario,
when the scenario run....i can see two rows in the MONI, one from sender service to the BPM, and the other from BPM to the Receiver service,
in the moni there is a column called Queue Id,
as i mentioned .... the row in MONI corresponding to Sener service to BPM, the queue ID is always XBQO* ....... as far as i have read, 'Q' in XBQO signifies that it is queue RFC, and it is so even if my file sener sends it using EO(transactional RFC), means no matter how i configure my sender file channel(EO or EOIO), it shows the Queue Id as XBQO*,
i assume that XBQO* means queue-RFC
and XBTO* means Transactional RFC,
pls help

Similar Messages

EOIO queue name change

Hi All,
any possibility EOIO queue name can be changed in Message mapping??
Thank You,
Madhav

Hi Madhav,
Similar to:
public String setVariable(Container container){
String variable = "Test";
java.util.Map map;
// get constant map
map = container.getTransformationParameters();
// get value
//variable = (String) map.get(StreamTransformationConstants.QUEUE_ID);
// set value
map.put( StreamTransformationConstants.QUEUE_ID, variable );
return variable;
See Context Object Names in:
[Technical Context Objects|http://help.sap.com/saphelp_nw04/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/content.htm]
Regards,
Pedro Baroni

Different / multiple senders to the same EOIO queue name.

Hello,
I'd like to know if it is possible to send from different senders, different messages to different receivers but using always same EOIO queue?
Scenarios are:
1) SOAP SENDER -> PI -> SOAP RECEIVER A
2) IDOC SENDER -> PI -> SOAP RECEIVER B
3) PROXY ABAP -> SOAP RECEIVER C.
All messages need to be processed by receivers in the same order they were sent from the different senders.
How this scenario should be implemented?
Thanks in advance.

Hi Michal. Thanks for response!
As far as I know,
1- Proxy Sender adds a prefix by defaul. Is it posible to change this behaviour?
2- By Following note 856597, I understand that you can set your own queue name in parameter &QueueId=xxxxxxxxxxxxxxxx. So there should be no problem.
3- In Idoc Adapter, you can set a queue name by using a Function Module, but I dont know whether this adds or not a prefix. Will it add a prefix to the queue name?
So, in case I want to use for all this adapters the same queue, then I need to set in the Soap queueId param, and in the Idoc function module, the same queue name that is generated automatically in Proxy Sender (since this is fixed queue name based on Prefix + custom queue suffix).
4- Is that true? Can I guarantee that from IDOC I can use same queue as used by Proxy and IDOC won't add a prefix?
Thanks again.

How to enqueue a XML file into a JMS AQ Queue

Hi guys:
I have a XML file in a directory 'X' and need to enqueue it into a queue of obejct type 'SYS.AQ$_JMS_MESSAGE'.
How can I do this?
XML File => 'c:\xml_odi_files\enqueue_file.xml'
Queue Name => Podesc_Queue
Queue Table => Podesc_Queue_Table
I took a look into the dbms_aq but didn't found a solution reading directly from a XML file.
I'm using Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
Regards.
Luiz Araujo

OK, then something like this :
- load the file into a CLOB, using DBMS_LOB package or DBMS_XSLPROCESSOR.READTOCLOB procedure (a very convenient wrapper)
- build a new AQ$_JMS_MESSAGE object of type JMS_TEXT_MESSAGE
- set the CLOB content
v_msg        sys.aq$_jms_message;
v_payload    clob;
BEGIN
v_payload := dbms_xslprocessor.read2clob(
                 'XML_DIR'                  -- Oracle directory object pointing to the physical location of the file
               , 'test.xml'                 -- Filename
               , nls_charset_id('AL32UTF8') -- Encoding of the file (ex. UTF-8), default is DB charset
v_msg := sys.aq$_jms_message.construct(DBMS_AQ.JMS_TEXT_MESSAGE);
v_msg.set_text(v_payload);
-- Enqueueing...
DBMS_AQ.Enqueue(
);

Change Queue name in Message mapping

Hi
We want to change the queue name dynamically in the message mapping.
We refered the post
Re: EOIO queue name change
http://help.sap.com/saphelp_nw04/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/frameset.htm
But as said in it, we are not able to access the parameter QUEUE_ID or QUALITY_OF_SERVICE.
Other than these two parameters, we can access all parameters.
Below is the code to access one of them.
while compiling, the message mapping gives error as below.
cannot find symbol
symbol : variable QUEUE_ID
Any pointers.
///// CODE
MappingTrace trace;
String constant;
java.util.Map map;
trace = container.getTrace();
// get constant map
map = container.getTransformationParameters();
constant = (String) map.get(
StreamTransformationConstants.QUEUE_ID);
trace.addInfo("QUEUE ID:" + constant);
return constant;
Regards
Anandan

Hi Anandan,
As given in help you can only get queue Id if you have Quality of service as ExactlyOnceInOrder. So make sure you have selected that option.
http://help.sap.com/saphelp_nw04/helpdata/en/6e/ff0bf75772457b863ef5d99bc92404/content.htm
Regards,
---Satish

In case of EOIO , then QUEUE NAME in File Adapter

Hi
   I'm using File Adpater in the Sender side   (FTP ).. and in the processing parameters if i choose the Quality of Service : EOIO   then system was asking as next parameter is Queue Name .--?
   Here   what can we give as queue name.. Is that is the new name.. Or any existed queue name... how we can identify that particular queue   name..
helpful answers will be appriciated
regards
Jain

>    I'm using File Adpater in the Sender side   (FTP ).. and in the processing parameters if i choose the Quality of Service : EOIO   then system was asking as next parameter is Queue Name .--?
>
>    Here   what can we give as queue name.. Is that is the new name.. Or any existed queue name... how we can identify that particular queue   name..
Go through this...
XI Asynchronous Message Processing: Understanding XI Queues -Part I

File -- MQ scenario; Define EOIO queue.

All,
I have several file2MQ interfaces, all have EOIO (Exactly Once In Order) as "Quality of Service" and therefore must have a "Queue Name". Obviously, EOIO queue should not be shared by more then one communication channel (in order to minimize the risk/penalty in case a message is being stuck in queue). my question:
I have 20 scenarios (20 EOIO senders), should i use queues XBTOM___0001 - XBTOM___0020 (does this queue actualy exists)?
should i refer other technical issues?
Regards
Uri

Hi,
Queue name will be only XBT or other queue, but the sequence like different queue from 001 to 020 will come dynamically(depends on load) and is defined by system.
For more details check this useful blog on queue.
XI Asynchronous Message Processing: Understanding XI Queues -Part I
Thanks!

Where to define third party logical system name in file to idoc scenario

Hi Friends,
I am shalini shah.
I have one doubt, where I can define the logical system name in File to Idoc scenario.
I created Logical system for R/3 system in SALE t.code, but where to define the Third party logical system ,
In SALE or any where.
Please give me solution.
Warm Regards,
Shalini Shah

Hi Shalini,
You need to create Business system in SLD and import the business system in ID.Then u will start with the configuration.
Just refer the below link for configurations with step by step solution.
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag

File name to be read in mapping - File to SOAP Scenario

Hi all,
its a file to soap scenario. i need to send the file name also to target system. how can i get the file name in the mapping? is there a way to read the header information in mapping?
Regards,
Rashmi

You need to check for Adapeter specific Message Attributes of your File adapter.Then write user defined function to set Dynamic_configuration. So that you can get the file name in the header(u can chk this in SXMB_MONI after implementing the UDF, it will create one section for dynamic_configuration.)
Manisha

File to RFC scenario want to read file name

Hi All,
I am having file to RFC scenario in which i am having file name in format text_yyyymmdd.txt.
i want to read this file name and by separating the date in file name i have to pass this to one of the RFC date parameter.
please help me to sort out this.
Thanks
Swapnil

Hi,
By writing simple UDF in your mapping you can Acheive this
Try this Once
DynamicConfiguration dynamicconfiguration = (DynamicConfiguration)param.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File", "FileName");
String MyFileName = dynamicconfiguration.get(key);
String str[] = MyFileName.split("_");
return str1[1];
Map this to the date parameter(RFC) in the mapping .
Thank & Regards,
Deepthi
Edited by: Deepthi Muppasani on Sep 23, 2011 8:17 AM

File to file scenario - output name files based on input

Hi experts,
i have the following scenario : file to file with no mapping
the only requirement is that if the file name from the source is lets say XXX then the output name should be abc and if the source file is YYY then it should be def
can i do that in 1 scenario?
Thanks a lot
any help would be greatly appreciated
Jamal

the only requirement is that if the file name from the source is lets say XXX then the output name should be abc and if the
source file is YYY then it should be def
AnySourceNode --> DynamicUDF --> AnyTargetNode
DynamiUDF will be:
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String SourceFileName = conf.get(key);
if (SourceFileName.equals("XXX"))
{ String TargetFileName = abc;
conf.put(key, TargetFileName);
if (SourceFileName.equals("YYY))
{String TargetFileName = def;
conf.put(key, TargetFileName);
return "";
The above code may require some (syntax) corrections!
Regards,
Abhishek.

File adapter with QoS=EOIO Is there any filesize limitation?

Dear Experts,
I'm using a File/FTP Sender adapter with Quality of Service = EOIO (Exactly Once In Order) to keep the polled order of the files.
In the processing parameters I defined a queue name and everything is working well for small (~1 MByte) files.
But if I want to transfer bigger (~25 MByte) files, the whole Java stack collapses and the system has to be restarted.
Is there any size limitation for this own defined queues?
Have you any experience with this kind of processing?
Any comments / experiences are welcome!
Best regards,
Andras

Hello,
there are several files to poll, we have to keep the alphabetical order of them.
It seems, that we have this issue only with EOIO. (EO works good)
After the system has restarted, the first file from the queue was processed, but with a n error message "Could not delete file 'filename.dat' after processing: java.lang.NullPointerException"
(the delete option is on after the transfer)
Is there any possibility to check the mentioned "QuicSized" settings?
I just wanted to know, if there is an "unofficial" size limit of these queues.
Thank you!

Help me please with File-to-RFC scenario

Hi, I'm a beginner with XI and I have as problem with an interface.
This interface is a file-to-RFC scenario an it was working correctly a few days ago. Suddenly, the interface doesn´t work and we haven´t error message in sxi_monitor transaction. The queues are fine and we haven´t any sign that why the interface doesn´t work.
If someone´s had a similar problem and know how to solve it or someone can teld me a clue, please, help me!!
Thank you

HI,
You can monitor the Communication Channel in RWB.
Go Component Monitoring in Runtimework Bench and click on Adapter Engine and select the Communicaiton Channel and select your channel name.
You can find any whether it is in active or not?
Also check the Message monitoring in RWB.
Regards
Sridhar Goli

File-to-file scenario: unable to trace cause of error

hi
i m new to Xi..
i have made a file -> XI -> file scenario, with a BPM having one receive and two send steps, sending message to two receiver-business-service.
the sender of the file is a sender-business-service, file adapter is using FTP.
the file is being picked up, but it is not put to the two destinations.
in SXMB_moni...i cant trace the error...
but in the respnse xml i cant see the payload...
pls tell me how to see where the error is.
pls help me....coz any scenario i make the main problem i face is to trace the error(file not being put to the destination directories),

hi sreeram and rajeev,
this is the trace from the response xml from the sxmb_moni enrty for the message send from the BPM to the final receiver-business-service through the send step(asynchronously).
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">COMMIT is expected by application !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = XIT</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2007-03-13T16:14:45Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 5922E409A745CA4BAE129D025CA22AE6</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XIT</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2007-03-13T16:14:45Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO60__0002</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = XIT</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2007-03-13T16:14:48Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="1" type="T">No mapping required</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="1" type="T">system-ID = XIT</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2007-03-13T16:14:48Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

XI 3 File to IDoc scenario - Still referencing Old Logical system

Hi
Dont know if you can help. I have a file to idoc scenario using XI 3 to R/3 4.6c system.
I had the interface working from a third party system XMLHUB to SAP R/3. The Logical system name for the XMLHUB was XMLHUB01 in the SLD which I have set up as a partner profile in R/3. I have recently changed the logical system name to XMLHUBDEV01 in the SLD and created that logical system in R/3 and changed the partner profile to XMLHUBDEV01.
Unfortunately in the sender information of the IDoc the partner number is still XMLHUB01 and not XMLHUBDEV01. I don't understand where this partner is sent from to get into the control record of the IDoc.
I have cleared the SLD cache in both the Repository and the directory. Is there somewhere else I should be looking? Any help would be appreciated.
Regards
Daniel

hi daniel...
this thread wud answer ur query....
Re: IDOC Payload
regards..
vishal

File to file scenario: EOIO queue name?

Similar Messages

Maybe you are looking for