Frequency of Message Sending for HTTP/SOAP Receiver

hi,
is there a way to schedule a message for a particular time/situation until we get the response from the receiver?
Say i am connecting to a https://test.com/OrderReceive, for some reason the receiver has failed to receive the message.
Is there a way for HTTPS/SOAP like how we have for a FILE adapter to poll the message at a regular interval until we get a success response?
Thanks,
Tirumal

Hi Tirumal,
you can build a business process with a synchronous sendstep. In case of error you jump into an exception branch. There is an endless loop with a wait step and the same send step. In case of success you raise another exception which can end the process.
Sounds more complex than it is
Regards,
Udo

Similar Messages

R3 (rfc-sender) - XI - Webservice ( soap-receiver)

Hi,
I am getting below error whenever webservice(target system) is unavailable.
HTTP 404 Not Found
Then RFC got failed in R3, due to this error in XI
R3 (rfc-sender) <-> XI <-> Webservice ( soap-receiver) Synch
User will enter the request data in R3 and waiting for the response, but webservice is down(i.e not available)
Request is reached to XI box and XI is trying to send data when webservice is down( i,e not available), RFC is waiting for the response from XI box.
how we will handle this kind of situation,how should i give response back to RFC( because RFC sent the request and waiting for the response, XI could not send any response back as Webservce is down, Please advice me how should XI inform to the end user r R3 abt webservice.
I am getting this error to my mail box as i have configured ALERTS. i do not want to change existing RFC.
is there any chance to send response to R3 even webservice is down, please can any one suggest.
Thanks,
SIva
Edited by: Siva Grandhi on Jun 18, 2008 1:12 PM

Hi siva,
check this blog on HTTP errors.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
May be the URL you have given in SOAP at receiver adapter is wrong.Check that once.
Error: 404 Not Found
Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404
u2022 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
u2022 Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
u2022 If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
u2022 If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.
Thanks,
Vijaya.

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

Message setup for HTTP adapter

If the http plain adapter is used, you use the URL to post the XML file to. What I was wondering is what the complete string looks like that is send, so URL including the XML message itself? In other words, what's between the http URL (http://...&language=EN) and the XML message itself (<?xml%20...).

Alexander
If I understand your question right, you are wondering what is in between the URL and the XML message. If yes, you need to understand how data exchange happens using HTTP.
When data need to be exchanged between systems (Client and Server), there are various protocols. For e.g., FTP is used for transferring data as OS files between systems. Similarly HTTP is a protocol that is use for exchanged data between systems in the form of 'Request;Response' cycle. As with any protocol there are certain rules and structure.
In case of HTTP, you should note the following
1. There is a URL which is used for identifying where the request should be sent, which port it should hit and other related information. You can pass some information in the URL (In case of XI HTTP adapter, maximum of 200 characters long) as well and in case of XI it will contain information specific to interface.
2. Then there is HTTP header which will give information to the server (the system receiving the request) about various attributes like mime type of the data etc.
3. Then there is HTTP body that actually has the data that needs to be sent to the system. In your case the body contains the XML message. Note that the body can also contain form elements instead of XML in which case you need ABAP or Java mapping in XI to parse the data.
To come back to your question, what is in between the URL and XML? answer is nothing, because these are two different entities within HTTP. And no, you cannot embed the XML within the URL. An analogy in real world would be when you sending mails using post. The envelope you use is like a HTTP header, the address you write on the envelope is the URL and the actual letter inside the envelope is the HTTP body.
Please refer http://en.wikipedia.org/wiki/HTTP to understand more on what HTTP is about.
Thanks
KK

Message Interface for HTTP to JDBC synchronous scenario

Hi Experts,
Could you please explain the Message Interface from the below blog. Actually, I am confused with the Outbound Interface. Is it correct?
/people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response
1. LoginData_Sync_OUT_MI
Input Message : Role_MT
Output Message : LoginData_MT
2. LoginData_DB_Sync_IN_MI
Input Message : LoginData_DB_DT
Output Message : Dummy_DT
Regards
Sara

Hi All,
Here is my Interface mapping's problem details.
Scenario : I have to pass EmpId as a request from webservice to JDBC, If we have the EmpId address in the JDBC then we have to return the address of the employee as a response to Webservice.
Please find the below datatype, message type and etc., which I have used it for the scenario.
1. Data Types:
a) DT_REQUEST ( Webservice to XI request)
 1. EmpId
b) DT_JDBC_REQUEST ( XI to JDBC request)
 1. EmpId ,2. EmpName, 3. Company,4. AddressLine1
 5. AddressLine2,6. City,7. State
c) DT_JDBC_RESPONSE (JDBC to XI response)
 1. EmpId ,2. EmpName, 3. Company,4. AddressLine1
 5. AddressLine2,6. City,7. State
d) DT_RESPONSE (XI to Webservice response)
 1. EmpId ,2. EmpName, 3. Company,4. AddressLine1
 5. AddressLine2,6. City,7. State
2. Message Type created according to the Data Type.
3. Message Interface:
a) MI_Outbound
Output Message : MT_REQUEST
Input Message : MT_JDBC_RESPONSE
b) MI_Inbound
Input Message : MT_JDBC_REQUEST
Output Message : MT_RESPONSE
4. Message Mapping:
a) MM_REQUEST[EmpId mapping]
Source Message : MT_ REQUEST
Target Message : MT_JDBC_REQUEST
b) MM_RESPONSE [Mapping for all the fields]
Source Message : MT_JDBC_RESPONSE
Target Message : MT_RESPONSE
5. Interface Mapping
IM_WEB_DB
Source Interface : MI_Outbound
Target Interface : MI_Inbound
Request :
Source Message : MT_REQUEST
Target Message : MT_JDBC_REQUEST
Response :
Source Message : MT_RESPONSE
Target Message : MT_JDBC_RESPONSE
Here the source Message should be MT_JDBC_RESPONSE and the Target Message should be MT_RESPONSE. But when I tried to create the Interface Mapping I am getting the above bolded Response Messages automatically populated by XI.
Actually, I have followed Siva's blog to do this scenario. Finally confused with the Interface Mapping's response messages. So, please help me out with this scenario steps.
Regards
Sara

R3 (rfc-sender) - XI - Webservice ( soap-receiver) Alert monitoring

Hi,
I am getting multple(two times) alerts for same message id when interface got failed, i am getting total 4 e-mails to my Inbox mail. Any one can plese suggest me to get single message for entire interface when it gets failed.
Thanks,
Siva

hI,
Check the fix receipient tab in ALRTCATDEF transaction for the receipient.
refer this thread,
Bunch of problems with ALERTING in SP14!
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
Thanks
Virkanth

IDoc to SOAP Receiver Fault Message Handling?

Hi,
I am working on IDoc to SOAP Scenario (IDoc -> PI -> SOAP). It is in async mode without BPM. This works fine as long as there is no error on the SOAP receiver side. How to handle the falut message raised by the SOAP receiver and send it back the SAP ECC.
Do I need to use ALEAUD IDoc for this? If Yes, how to configure this to handle fault message? Is there any other way of doing it?
Could you please give steps to handle the fault message?
Thank you.
Regards,
Cdr.

Have a look into the below threads -
How to capture SOAPFault in an Async/Sync Scenario without BPM
Acknowledgement Handling in IDoc to SOAP Scenario in PI 7.3

HTTPS config in SOAP receiver adapter ?

Hi Guys,
I have configured the soap receiver adapter with the URL
*https://xxxx.abcd.com/xyzv/bbbb.asmx with the user authentication *
I have tested the url and the user and pw in the browser and they are working fine but the messages are failing the soap receiver adapter with the 401 unautorized error as the message from the Audit log in the RWB.
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 401 Unauthorized. Setting message to status failed.
Do i need to configure the Java Stack for HTTPS ? The communicaion is between the XI system and a third part system internally.
any help would be appreciated ?
Thanks,
Srini

Hi Guys,
I have solved the problem and NTLM works with PI 7.0 but we need to configure soap axis adapter
The Windows NTLM authentication is supported by Axis's CommonsHTTPSender handler and consequently it is supported by the Axis adapter's corresponding handler com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender. Read about How Can I use CommonsHTTPSender as the transport handler? if CommonsHTTPSender is not enabled on your system. Once it is enabled, you can use com.sap.aii.adapter.axis.ra.transport.http.CommonsHTTPSender instead of default com.sap.aii.adapter.axis.ra.transport.http.HTTPSender as the transport handler in the module configuration and set the authentication setting to NTLM and enter usename as domain\username in the channel configuration
To use CommonsHTTPHandler, the optional Jakarta-Commons-Net, Jakarta-Commons-HttpClient, Jakarta-Commons-Codec libraries are required. Make sure that these libraries are available for the Axis adapter at the deployment check page If these components are not available, you will need to include the corresponding jar files (commons-codec-1.3.jar, commons-httpclient-3.0.jar, and commons-net-1.0.0-dev.jar from the Axis 1.4 release) in aii_af_axisprovider.sda and deploy this archive (see How to prepare aii_af_axisprovider.sda?).
The provider.xml file must include the jar-name entries for these jar files, as shown in:
 <jars>
 <jar-name>commons-net-1.0.0-dev.jar</jar-name>
 <jar-name>commons-codec-1.3.jar</jar-name>
 <jar-name>commons-httpclient-3.0.jar</jar-name>
 </jars>
Once you do all the above settings, NTLM works fine
Thanks,
Srini

SOAP receiver problems

Hi Folks,
I am sending data to the webservice using SOAP receiver. In the runtime workbench I can see the message as successfull, but the end user is claiming that , he didn't get the data from XI.
What could be the possible reason for this?
Where might the message lost?
And for one message which is using SOAP receiver as communication channel , In the audit log I can see the steps as below:
SOAP: request message entering the adapter with user J2EE_GUEST
SOAP: completed the processing
SOAP: continuing to response message
SOAP: sending a delivery ack
SOAP: sent a delivery ack
The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
MP: Leaving module processor
The message status set to DLVD.
For other message I can see the log as :
SOAP: request message entering the adapter with user J2EE_GUEST
SOAP: completed the processing
SOAP: continuing to response message
SOAP: sending a delivery ack ...
SOAP: sent a delivery ack
MP: Leaving module processor
The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.
The message status set to DLVD.
Both are using same communication channel. still u can see the difference in the steps that are exicuted (check leaving module processer line in both).
Is it mandatory that the series of steps should be same for all the messages?
I have 2 queries, please answer both......
Thanks SPMD

HI
As a first test , import the wsdl shared by third party in soap uI/MS infopath/xml spy , fill in the test data (preferably same which you are trying to post now) and do a test :- doing this you will get to know if there is any problem in the WS iteslf. if you get http 200 ok then posting happened and ask the third party to check if they got any request.
If you have sync soap then you will be getting the desired response back to soap ui .
Also check if you need to put soap action also check the content type if its text/xml or app/xml some WS dont accept App/xml u may need to use message transformation bean in modules tab.
if there is any connectivity at ntwrk level then please try if you can trouble shoot using this blog
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
Regards
$rinivas

Set dynamic URL in SOAP receiver adapter

Hi,
Is this possible ? I have managed to do this with the HTTP adapter but the this time it is a Web service I am integrating to that requires SOAP 1.1 over HTTP to be used.
Thx.
Colin.

Hi Stefan,
Basically the full URL I want to send the message to via the SOAP receiver is within the payload.
I can see the Target URL can be set in the communication channel but I want to override this with detail from the payload.
I have managed to use dynamic URL setting with the HTTP adapter but am a little stumped on how/if this can be done on the SOAP adapter.
Can you please expand on your comments a little please ?
Kind regards
Colin.

Inconsistency of Status (SOAP Receiver)

Hi Experts,
Currently we have a design in PI 7.1 ehp1 sending messages to partners via SOAP (receiver). The first issue I've encountered is ChainLinkVerifier for SSL cert. Then it was resolved by uploading the RootCA of systems in TrustedCAs Keystore. If i send 1 message, the status is successful. But when I'm sending let say 5 messages, alternatively the status is Successful, System Error, Successful..etc etc.
What would be an alternative way to make those message all Successful. Do I have to add timeout settings?
Regards,
R-jay

Hi,
I did similar requirement (PI 7.0) but i didn't get any problem and no poll intervel. I think somwhere configuration settings is problem better to recheck again meanwhile configure certificate on java stack.

QoS - EOIO in RFC and http/SOAP adapters

Hi all,
I need to have the QoS as EOIO in my interface where I am using RFC Sender adapter and HTTP/SOAP receiver adapter and using BPM Integration process.
I have seen in the adapter attributes that these 2 adapters support the EOIO. I don't know how to specify this service in the adapters.
Is there any special way of specifying this?
Any help in this regard is highly appreciated.
My interface is async and we are at SP 14.
Thanks
Kalyan

Hi Kalyana,
Check these..
2 scenarios with 1 Rfc-queue does it work ??
RFC synch/asynch
Queues for RFC-Destination
cheers,
Prashanth
P.S Please mark helpful answers

R3 (rfc-sender) - XI - Webservice ( soap-recever) Synch : error handlng

R3 (rfc-sender) <-> XI <-> Webservice ( soap-receiver) Synch
User will enter the request data in R3 and waiting for the response, but webservice is down(i.e not available)
Request is reached to XI box and XI is trying to send data when webservice is down( i,e not available), RFC is waiting for the response from XI box.
how we will handle this kind of situation,how should i give response back to RFC( because RFC sent the request and waiting for the response, XI could not send any response back as Webservce is down, Please advice me how should XI inform to the end user r R3 abt webservice down.
Pleae help me out on this.
Thanks,
Dhanush.

Hi,
Normally, the Web service should provide a fault message back to XI and the RFC should also have an exception defined that will trigger a fault message mapping and that way the application error is sent back to R3.
But if the web service does not provide u with a fault message then XI will trigger the System Error back to R3.
The functionality of checking the DB status and propagating meaningful errors to XI as fault messages should lie with the web service.
Thanks
Vikranth

SOAP Receiver sync call timeout

Hi guys, I need to increase the sync call timeout value for SOAP adpter as my receiver system has vaery slow response time. Which parameter to set? Currently is the message valid for 3 minutes.
Thanks, Andrzej

Hello
XI.Timeout can be used with the SOAP sender, and XMBWS.Timeout for the SOAP receiver.
There are further details in note - 856597
Q: Can I increase the default timeout value for the sender
adapter?
A: Yes. The default timeout value for synchronous calls is 5
minutes. You can increase this value by setting parameter
XI.Timeout in the module parameter table of the SOAP adapter.
Q: Can I configure the timeout value of my receiver adapter?
Sarah

Specific logon Group for Http logins

Hi
I just wondering whether we can have Logon group in SMLG specifically for http logins to use only 3 app server out of 6.
In my case,we have given one of the app server in the Iviews so all http logins goes to it, But as I see this server is idle most of the times and my other app servers are overloading and hanging sometimes so to allow GUI users on this and distribute http logins to use only 3 servers.
And If I use the generic load balancing then all the request would come to Central instance and then go to app server,which I don't want because I restricted any users login to central instance .so What I am looking is, to distribute Http logins to 3 app servers only .
Can this be acheived???
Any ideas are welcome.
Thanks

Hello,
you can create a logon group in SMLG with those 3 application servers, then set the flag ""Ext. RFC-enabled" in SMLG.
If you use the Message server for Http load balancing you should activate the services sap/public/icf_info/logon_groups and sap/public/icf_info/urlprefix in SICF transaction.
You could as well assign specific logon groups to url's in transaction SICF.
There are some restrictions when using the message server for Http load balancing (depending of your scenario), see SAP Note 1040325. That's the reason is recommended to use SAP Webdispatcher
http://help.sap.com/saphelp_nw04/helpdata/EN/de/89023c59698908e10000000a11402f/frameset.htm
Kind regards,
Mercedes

Frequency of Message Sending for HTTP/SOAP Receiver

Similar Messages

Maybe you are looking for