Number of retries of receiver adapter

Hi there,
for some testing purposes I need to limit the number of retries of an outgoing RFC adapter. If the RFC connection of this receiver communication channel fails, the message should get the status "system error" immediately and the adapter engine should not run any furhter retries of sending the message.
Has anybody an idea how to limit the retry count for the RFC adapter?
Help is higly appriciated, tahnks in advance.
Cheers,
Matthias

Hi,
Check these replies help.
Retries
Note 791379 - XI Adapter service properties documentation
Note 791655 - Documentation of the XI Messaging System Service Properties
blog:
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Thanks,
Vijaya.

Similar Messages

Maximum number of retries in the Adapter Engine

Hi guys!
I have a question for you, I have many JDBC Receiver CC that for a bad data in their queries cannot be executed correctly in the target DB, and they remain in the Message Monitoring retring (e.g. one of them is in his retry #1700) and they always keep in TBDL status, not changing to System Error. I saw this in the Audit Log tab.
In the Message Data tab I See these parameters:
- Number of Retries 3
- Failed: 1700
- Retries 300000
I don't know why that "number of retries" parameters always stays on ' 3 ' value, so I'd like to know where is the real parameter that sets the ammount of times that the message will try to be sent (the correct way in these cases would be no more than 3 tries).
As an additional data I can tell you that in the definition of the CC I set the parameter in Advanced Mode -> Additional Parameters -> Nunber of retries of Database Transaction on SQL Error = 0.
Thanx in advance!

This retry information could be found at Visual Admin->server->services-> SAP XI Adapter: XI. You may also change it from here.
Regards,
Prateek

Payload at Adapter for System Errors - SOAP receiver adapter

Hi Everybody,
I am working on an Idoc to SOAP asynchronous scenario.
There are connection issues between SOAP adaper and the target webservice.
I need to capture the Idoc number from the message payload for the Erroneous messages at the adapter for the System errors.
Is there any way of capturing field values from the payload (Say, Idoc number) at the SOAP receiver Adapter level.
Helpful answers will be rewarded points.
Thanks & Regards,
Zabiulla

Hey,
I think you need to implement a module inorder to get the payload at receiver adapter module.
As far i concern you can not directly refer the payload in adapter in receiveer communication channel unless you have your own module, which gets the payload. Check the Modules tab in the communication channel and also regarding how to get the payload for error information, follow the steps mentioned in the below link, which gets the payload in file. hop it will resolve your issue.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/writepayloadtoafilefromAdapter+Module
Regards..
Prasanna..

Number of retries in Adapter Engine not working ok in SP18

Hi
We recently upgraded to SP18 from SP13 on our XI 3.0 Dev env. After upgrade , the number of error retries on the adapter engine is set to the default values as
xiadapter.inbound.numberRetries.default = 3
xiadapter.inbound.retryInterval.default = 300000 [ms]
xiadapter.outbound.numberRetries.default = 3
xiadapter.outbound.retryInterval.default = 300000 [ms]
In RWB, we find that the number of retries in case of a database update error - goes up to two hours - instead of ending at 15 minutes -
The number of retries - gets incremented to 2 in the sixth minute, but remains at 2 for nearly 2 hours - and then turns to 3 and ends .
Anybody face this problem in XI 3.0 SP18 - any known OSS notes applied to fix this issue - Correct answers to be rewarded rightaway.

Have you seen alreay these notes:
<a href="https://service.sap.com/sap/support/notes/791379">Note 791379 - XI Adapter service properties documentation</a>
<a href="https://service.sap.com/sap/support/notes/791655">Note 791655 - Documentation of the XI Messaging System Service Properties</a>
Regards,
Sandro

Service Number/Port Number in HTTP receiver adapter

Dear Experts,
I have a scenario where I am to do HTTP Post to a 3rd party web application via a url in the following format:
https://x.y.info/abc/sap/customer.cgi
The HTTP Post data is submitted to the CGI script which is then processed further by the web application. The URL works ok via IE or even PI soap receiver adapter is able to post XML message to the URL but using SOAP.
But I have to do only HTTP Post and now my problem is that the URL dont have a so called port number that I can fill in the "Service Number" field in HTTP receiver channel or in SM59.
Does SAP always need a service number or how to deal with this case where server doesnot expose the port.
Thanks in advance.
Br
Suman

Hello,
The HTTP Post data is submitted to the CGI script which is then processed further by the web application. The URL works ok via IE or even PI soap receiver adapter is able to post XML message to the URL but using SOAP.
By definition, the SOAP Adapter is also using HTTP POST as its HTTP method the only difference is that there is a SOAP Envelope that is being sent.
But I have to do only HTTP Post and now my problem is that the URL dont have a so called port number that I can fill in the "Service Number" field in HTTP receiver channel or in SM59.
Service number is the port number of the URL that you will be connecting to, if it is not shown, it is assumed that it is 80 for http and 443 for https (as Gzegorz mentioned). Since you are using HTTPs, you should use HTTP Destination that points to an SM59 configuration.
Hope this helps,
Mark

Maximum size of XML files and number of IDocs for IDoc receiver adapter

Hi Guys,
We have an XML file to IDoc scenario where XI picks up an XML file with multiple Customer records in it, it does a simple mapping and creates one DEBMAS06 IDoc per record in the XML file. All IDocs are sent in a single file in XML-IDOC format to IDoc adapter which then posts the separate DEBMAS IDocs to R/3.
a) What is the maximum size of XML files that XI can handle with mapping involved ?
b) What is the maximum number of IDocs in a single file that the receiver IDoc adapter can handle ?
The first time this interface runs almost 200,000 Customer records will be exported in one XML file.
Thank you.

Hi,
Well it is difficult to find out the maximum Size of xml messgaes that can be processed by XI and also Maximum number idocs an recevier Idoc adapter can handle.
This totally depends on your production system loads and the limits can be set totally on trail & error basis..
In my heavy loaded production system, i found out that the maximum size of the successfull messages after processing by XI is around 75 MB (seen in transaction SXMB_MONI). Whereas messages with size around 100 MB went into error.
I havent encounter any such limits with respect to Idocs.
I would suggest that you divide your data into smaller chunks and sent it part by part instead of sending it all once since you data size is huge.
You can vary your batch size as per your system load.
Regards,
- Deepak.

'number of retries allowed & retry interval in seconds' does not working

Hi Guys,
Is there a way to schedule a report to run,and if the report job fail for whatever reason, retry the job again immediately, and automatically?
I've tried use 'number of retries allowed' and 'retry interval in seconds', but it doesn't work.
Is there any setup that we missed?
note:
i can receive notification [failed/success] through email without any problem..

Hi,
I think, for adapter engine, you can do it in Visual Admin.
Refer this blog-
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Moorthy

Filename from payload - FTP receiver adapter

Hello everyone!
I have a scenario wherein I need to get the value from a field coming from an IDOC and then give that value as the "filename" of the file that is saved in the FTP folder.
IDOC > XI > FILE
For example, if /ORDERS05/IDOC/E1EDK02/BELNR = 620000123
then I want the name of the file to be saved in the FTP folder to be 620000123.xml
I understand you may use the 'variable substitution' property in the FTP receiver adapter, but subsequent attempts at trying to configure that property have resulted in errors. Can anyone help me out?
Warm regards,
Glenn

do u have recordset name (root message)
For Ex: If you want to refer to the field which is bold
below is your variable substuition:
payload:root,1,e1,1,e2,2
<?xml version="1.0" encoding="UTF-8" ?>
<root>
<dummy>
     <e1>
        <e2>Data_1</e2>
        <f/>
       <g attr="abc">text</g>
        <e2>Data_2</e2>
     </e1>
</dummy>
<e1>
     <e2>illegal/value</e2>
     <f/>
     <g attr="abc">text</g>
     <e2 attr="fghij">Example Value</e2>
   </e1>
</root>
Similarly
for your strucutre:
<MS_MT>
<order>
      <number>
the variable substuition would be
payload:MS_MT,1,order,1,number,1
you have to give complete XML to arrive to this value.

Adapter-specific message attributes for the JMS Receiver adapter

Dear SAP Community,
We are trying to activate some parameters at message level when SAP XI sent an interface (XML data) to IBM Websphere MQ. Programmaticaly, this is done the following way:
       TextMessage outMessage = session.createTextMessage();
       MQQueue replyToQ = new MQQueue("TESTQM01","SYSTEM.ADMIN.ACTIVITY.QUEUE");
       Destination replyTo = (Destination) replyToQ;
       outMessage.setJMSReplyTo(replyTo);
       outMessage.setIntProperty("JMS_IBM_Report_Exception", MQC.MQRO_EXCEPTION);
       outMessage.setIntProperty("JMS_IBM_Report_Expiration", MQC.MQRO_EXPIRATION);;
       outMessage.setIntProperty("JMS_IBM_Report_COA", MQC.MQRO_COA);
       outMessage.setIntProperty("JMS_IBM_Report_COD", MQC.MQRO_COD);
       outMessage.setIntProperty("JMS_IBM_Report_Discard_Msg", MQC.MQRO_DISCARD_MSG);
This code is working fine.
Since the documentation about this feature (Adapter-specific message attributes) is very light, We am not sure about the interpretation we made.
First, we defined the following attributes: MS_IBM_Report_Exception, JMS_IBM_Report_Expiration, JMS_IBM_Report_COA, JMS_IBM_Report_COD, JMS_IBM_Report_Discard_Msg. All of them are with type int.
Then we changed the mapping (XSL) to pass the value to the dynamic configuration, using the technical names (DCJMSMessageProperty0, ..., DCJMSMessageProperty4) and the value of the constants. We also specified a value in the Reply To Queue parameter of the adapter. As a test, We also change another parameter via the mapping (the correlation ID, to use the idoc number) and according to the log of the processed message, every thing is finde. According to the trace of the JMS adapter, everything is fine to. However, this has no impact on the message, only the correlation ID is changed.
The JMS server is IBM Websphere MQ (v6.0.2.1). It is already in production and working fine. This is a change we have been asked to implement.
Has anyone experience with the JMS receiver adapter-specific message attrbitutes ? What have we done wrong ?
Any help is greatly appreciated.
Regards,
Gregory PFISTER
SAP XI Analyst - Holcim

Hi Neha,
pls do chk the below links for SOAP adapter message attributes
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst38.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/webservices/webservices16.htm
Regards
Sampath

Configuring a Seeburger FTP Receiver Adapter

Hello,
I am trying to build a scenario where SAP ECC 6 sends an invoice to a customer via EDI.
We are using ECC 6.0 and PI 7.0 and the Generic Seeburger EDI Adapters. The VAN is a GEIS EDISWITCH VAN (Eircom in Ireland).
I am able to successfully send an IDoc from ECC 6 and into PI where a Seeburger map converts the message to EDI-XML format. I can use a file adapter to create a file in normal EDI format. But I can't get the Seeburger FTP adapter to work with the VAN.
I have configured the correct IP, port, username and password but I keep getting the following message when the communication channel tries to send the message:
<h6>Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: >> Description: com.seeburger.jftp.app.exception.FtpExceptionSoftProcessingError: Unexpected reply: 501-Syntax errors in parameter. usage: %[recipient id]%[APRF] where either [recipient] or [APRF] can be omitted. (to change your current default SEND relationship). %% (places you in your 'HOME' TR). &['s'|'single'] ('get' command gets single file). &['m'|'multiple'] ('get' command gets multiple files). >> </h6>
The FTP session is expecting a PUT command with the recipient id and APRF as parameters but these are not getting passed. I suspect this is because I am not passing the correct variables to the receiver adapter but I don't know what variables it expects and where they should be specified. And I can't find the answers in the documentation.
Can anyone shed some light on what I need to do?
Thanks,
Ben

Hi Prateek,
Thanks for your comments. The channel is set to GEIS(GeMarkIII). There is nowhere to specify a directory or filename. The settings I have used are as follows:
Adapter Type: FTP (http://seeburger.com/xi)
Receiver
Transport Protocol: FTP
Message Protocol: GEIS/GeMarkIII
Adapter Engine: Integration Server
Host name: <IP address of VAN server>
port: 21
User Id: <Our mailbox number>
Password: <Correct password>
Host path/VAN Partner ID: <blank>
Script file: <blank>
Transfer type: ASCII
Connection mode: Passive
Use keep alive: <Not checked>
Security Mode: None
Proxy Mode: none
Resource ID: <blank>
Deliver transmission report: <not checked>
Payload mode: Attachment
Attachment ID: SeeburgerMain
Channel status: Active
Use dynamic attributes: <Checked>
Use non-empty attributes: <Checked>
Request displayed report: <Not checked>
Request dispatched report: <Not checked>
Report timeout (minutes): 720
Handle received reports: Refer reports to XI system
There is nowhere in the communication channel configuration that allows me to specify the receiver ID or the APRF. The documentation say this is read from the EDI data and the relevant fields are populated.
Any ideas?
Thanks,
Ben

Wrong port in FTP receiver adapter - no errors in message monitoring?

Hello all
We're on XI 3.0 SP16 and have created / configured a HTTP XML -> XI -> FTP Server scenario. In the receiver comm. channel (ftp) we had specified a wrong port number and always wondered, why we never got errors in message monitoring. Everything seemed to be processed correctly... but no file arrived on the FTP server (receiver) side!
After correcting the wrong FTP port number in the receiver FTP comm. channel everything went fine.
We now encountered a similar problem with a RFC receiver adapter. We're using it in another scenario HTTP XML -> XI -> RFC to SAP R/3 (4.7).
For some reason it died (red status in adapter monitor) and it was no more possible to do RFC calls from XI to SAP R/3 (normal RFC adapter, NO proxies).
In XI message monitor everything seemed to be ok but no message arrived till SAP R/3. Nothing in any queue...
After deactivating and reactivation the RFC receiver comm. channel it worked again BUT ALL PREVIOUSLY SENT messages seem to be lost.
Is it really the way it works? Does XI integration engine at runtime NOT catch whether or not a RFC or FTP receiver adapter died, thus is not able to tell somewhere in message monitor that a message could not be delivered at all?
I'm really confused here but hopefully I simply don't understand some easy principles to take into account...
Our SAP R/3 is on rel. 4.70 with Web AS 6.20. The XI 3.0 plugin is not installed. Do we need to go with server proxies there and use QOS = best effort?!?
Thanks for some suggestions.
Best regards,
Renaud

Hi Michal
Thanks... works great for normal XML based messages!
Now, what if I wanted to pass binary files from one ftp server via BPM to another ftp server in order to enable the transport acknowledgment?
The files polled from ftp server using the ftp sender adapter are all in binary format (ARJ). No xml data in there. How should the message format look like in BPM for the receiving step? Or: how to make sure not to loose the binary content when passing through BPMs?
I need this sort of scenario because of the tansport acknowledgment and because I need to have some sort of message splitting (send the binary file over to a second ftp server and additionally send some kind of info message to SAP R/3 regarding thin binary file).
BTW: in the MessagingSystem/monitor/monitor.jsp I do not see sender / receiver information. Is this normal? It's quite of a bad thing to look inside each message in order to find out what message I'm having in front of me...
Thanks a lot for your support and patience!
Kind regards,
Renaud

Dynamic URL in SOAP Receiver adapter

Hi all,
I have a scenario where I am using a SOAP receiver adapter to send a cXML document to some vendors. I need to change the URL based on the vendor number (passed by sender SRM system). So I have created a user-defined function and used in message mapping to assign the right URL to the variable TServerLocation. But the communication channel still prompts for a static URL which appears to be a mandatory field. Even though the DynamicConfiguration tab in Message Monitoring shows that the TServerLocation was correctly assigned, the scenario does not work when I put some dummy in the static URL field like 'dummy' or '*'. Any ideas on how to make the communication channel go for the dynamic URL field and ignore the static URL field? I have already selected the'Use Adapter Specific Message attributes' and 'Variable Transport Binding' check boxes. Am I referring to the correct variable that references the target URL? Also other than the two checkboxes that I mentioned, I am not displayed anything else under "Adapter Specific Message Attributes" section in the comm. channel.
Thanks

James,
I ve just been digging into SAP help, and have tried it too ... Looks like it doesnt work the way it is supposed to.
Anotheer point i found was, in the FILE ADAPTER, when we say ADAPTER SPECIFI ATTRIBUTES , we can select the attirbutes.. This is not possible in a SOAP adapter...
Maybe, we can only access the ADAPTER SPECIIFC ATTIRIBUTES of a SOAP adapter, but cannot set them dynamically.
Let me know if you find something on this issue.
Regards,
Bhavesh

JDBC Sender/Receiver Adapter Configuration with key fields in SAP XI

Hi All,
Good evening.
Please let me know, what are the settings required for key fields when configuring both sender and receiver Adapter?
In My IDOC-XI-File Scenario, when i am sending an IDOC from R/3, I got Mapping Runtime exception error? So, How to send the same IDOC after correcting the error?
Thanks to all in advance.
Regards,
Nagarjuna.

HI Nagarjuna,
If my understanding is correct, When you trigger the Idoc from R/3 it thrown the error in XI.
If you want to send the same Idoc then go to WE19 in R/3 system enter the same Idoc number and execute the scenaio. It send the Idoc to XI system, but the message number will change.
Regards
Goli Sridhar

HTTP Receiver Adapter payload as single line plain text with out any tags.

Hi PI experts,
I have a strange problem in http receiver adapter.
Sender RFC (SAP) Receiver: HTTP.
Receiver system expects the output from XI in the below format in a single line plain text with out any tags in the payload. and the content type should be application/x-www-form-urlencoded
Group=Test&Sentinel=Web%20Server&Facility=5345&Order Number=XT-XWHM-Y-NA&Serial Number=123456&@LABEL_QUANTITY=5&@LABEL_NAME=111114_Q
Is there any way to achieve this using http receiver adapter. Business is not ready to accept the output from XI not even in a single element instead they only need it as a JUST a plain text.
Appreciate early response on this.
Thanks in Advance,
Jitender

Dear Ola,
Could you elaborate how you achieved in catching the response data from the receiver in case of HTTP receiver adapter?
The target service is not a WebService but some python script that must to receive some paramters via POST request.
HOW can I post this parameters?
Here you entered the fields of the message type of the request in the header parameters of the receiver adapter? Thats fine.
But what about the message type and vice versa of the response from the receiver?
Regards
Rebecca

JMS Receiver Adapter to MQ - additional message property error

Hi,
I'm trying to add addional message properties to a Receiver JMS message for MQ Server queue. Creating the message in the MQ queue only works when I don't try to
add additional message properties. As soon as I try to add additional message properties the XI-Monitor says it's OK but there is no message in the queue.
Our system constellation is a bit odd cause we implemented the JMS/MQ classes of release 5.3 in XI/J2EE.
Our actual used MQ Server is on release 5.1 due to compatibilty reasons of other productive software.
Is there a need to use a MQ server of release 5.3 ?
Has anybody a step by step description for implementing a JMS receiver Adapter for MQ with with additional message property (f.ex. mesType = salesOrder) in the MQ header?
Thanx a lot in advance
Hans

Hi,
You also might want to look at sap note 856346...for this ..
2.6) I am connecting to a JMS provider using JNDI mode. How do I add pass an extra name,value property pair while setting up the JNDI initial context?
Answer: Assuming that your property value is a string, please add the following name, value pair in "JMS Additional properties" table of your channel configuration:
JNDI.InitialContext.property.X=java.lang.String propertyName, java.lang.String propertyValue
where X is a number, the LHS part needs to be put in the name column and the RHS part in the value column of the table respectively.
This note covers frequently asked questions that arise during the installation, configuration or administration of the XI JMS Adapter from the Adapter Framework (AF).
Other terms
JMS - Java Message Service
AF - Adapter Framework
AE - Adapter Engine
SP - Service Pack
Reason and Prerequisites
This note clarifies the frequently asked questions on the XI/PI JMS adapter for released 3.0, 7.0 and 7.1 in the form of an FAQ. References to external information is provided at the end.
Solution
1. Documentation
1.1) Where do I find the JMS adapter documentation?
Answer: In the SAP online help. Go to http://help.sap.com and select SAP Netweaver-> SAP Netweaver 7.1 or SAP NetWeaver 7.0 (2004s) or SAP Netweaver 2004. This opens up SAP Library topic page for that release.
For releases 3.0 and 7.0:
Select SAP Netweaver Library -> SAP Netweaver by Key capability-> Process Integration by Key Capability -> SAP Netweaver Exchange Infrastructure -> Runtime -> Connectivity -> Adapters -> JMS Adapter.
For releases 7.1:
Select SAP Netweaver Process Integration 7.1 -> SAP Netweaver Process Integration Library -> Function Oriented View > Advanced Adapter Engine.
In the topic page click on the JMS Adapter link.
Alternatively, you may simply enter the search string "JMS adapter" and navigate to the documentation page directly from the relevant search results. This is much faster.
1.2) Which JMS providers are supported?
Answer: The JMS Adapter supports JMS 1.02b and 1.1. JMS providers that also claim to be compatible with JMS 1.02b or 1.1 can be accessed using the JMS Adapter.
Furthermore, SAP makes no assertions as to whether a particular JMS provider is tested or can be recommended, because SAP has not set up a certification or testing process.
2. Functions and architecture
2.1) Does the JMS Adapter support JMS topics (publish&subscribe)?
Answer: No. Currently the JMS Adapter works with JMS queues because 100% Exactly Once (In Order) service quality can only be guaranteed with JMS queues. However, this capability might be planned for introduction at a future release. (no planned time estimate)
2.2) I have JMS message properties that are of significant. How do I get this data into XI? How do I get this data out of XI?
Answer:
A feature generically referred to as XI adapter-specific message properties was introduced in the adapter framework. This allowed additional adapter information to be attached to a XI message which can be used the routing, mapping and BPE. The message properties of different adapters are differentiated by namespaces.
If you are on XI 3.0 support pack 18 onwards, the JMS adapter allows you to copy JMS message properties into these XI adapter specific message properties (at the sender JMS channel), and to copy the values of XI adapter specific message properties back into JMS message properties (at the receiver JMS channel).
The JMS adapter currently supports upto 10 JMS message properties to be copied into the XI message properties with the name DCJMSMessageProperty0 to DCJMSMessageProperty9. The configuration details of how to achieve this are explained in the sub-topic pages of the JMS adapter documentation. (See sub topics: "Configuring the Sender JMS adapter", "Configuring the Receiver JMS adapter")
JMS Message properties can have values belonging to types: boolean, byte, short, int, long, float, double, and String (defined in the specification). These are all normalized to strings when converted to the their respective XI message properties at the sender JMS channel.
However, in the receiver JMS channel configuration, you can enter specific JMS message property types, such that these normalized XI message properties may be coerced back into their original types (or any compatible JMS message property type) when translating a XI message into a JMS message.
Transfer of custom JMS Message properties from/to XI adapters-specific message attributes is only supported for JMS compliant messages, i.e. this feature will not work for Websphere MQ in legacy mode.
Deprecated Information on this feature
Between support pack 14 to support pack 18, the JMS adapter allowed the allowed you append only up to two JMS string properties to the XI message in the sender channel, which could then be analyzed in XI routing, mapping and BPE. In the JMS receiver channel, the XI adapter-specific message attributes could be read, and up to two JMS string properties could be set. The names of the (now deprecated) XI message properties were DCJMSStringProperty1 and DCJMSStringProperty2.
Regards
Ravi Raman

Number of retries of receiver adapter

Similar Messages

Maybe you are looking for