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

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.

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

Help to do RFC Sender -- XI -- WebService escenario using XSL mapping

Hello Guys!.
We have a WSDL definition that requires use header fields. For do this, in other forums, we see that is good, use an XSL mapping without the estandar message mapping.
The objective is:
1 - Interface begins when RFC is called in R/3 system then..
2 - Parameters TELEFONO and BODY of the RFC are passed to wsdl message called Sendmessage. We need pass header parameters too, user, account and password. This parameters not appear in this message.
Someone can help us, how can implement this using XSLT message.
Whe have now this one but, i don´t know if it´s good.
Best regards.

<<<<In your Receiver SOAP adapter, select option "Do Not use SOAP Enevelope".
Selecting this option implies that SOAP adapter will not add its own SOAP Envelope and the output of mapping will be passed to the target system / webservice.<<<<<
I have done exactly what has been suggested but XI is still generating the SOAP document along with the payload(my payload has SOAP envelop, header and body).
I want to supress/remove SOAP document and send only my payload to the webservice.
Does any one has any idea where it needs to be set?
Thanks in advance for your help.
Venkat
[email protected]

Rfc sender to soap recever (sync comunication in sender and recever side)

this scenario is from RFC sender(synchronous) to SOAP receiver adapter(synchronous)
RFC sender adapter (synchronous): r3 will send some details as request and it will get back 3 new fields as response.
SOAP receiver adapter(synchronous): webservice receve the details and it will send newly created 3 new fields in SQL database.
1) i am sending product details from R3 to xi using RFC sender adapter.
2) Details will be send From XI to webservice using receiver SOAP adapter.
3) The purpose of providing webservice by SQL database team : they want to receive the details from webservice to SQL database, once data base receves details through webservice, it will create the 3 new fields , then these fields will be returned to webservice . IS IT POSSIBLE?
4) Response(3 newly created fields by SQL database) will be send back to SOAP adapter by webservice
5)Xi sends these 3 new fields to the RFC sender adapter(responce), with the help of RFC adapter 3 new fields will be posted into R3
Thanks,
siva

Siva,
I think it is depending on approach...both approach sounds good.
But if databse team providing you webservice..i think you can go with this.
Anyway future would be webservice for all communication..:)
Nilesh

R/3 to PI using RFC Sender Adaptor as Asynchronous scenario

Hello Folks,
RFC Adp. SOAP Adp.
ECC-->XI--
>ARIBA
I am new to PI and doing a scenario mention above. we are using RFC sender adaptor to send the data to XI in asynchronous process.
I have config the Sender comm. channel as below.
Appl. Server(Gateway): My Ecc Server host name
Appl. Server Service (Gateway) : My Ecc server
Program Id : XYZ.
Note : while creating the the Service interface and Message mapping and Operation mapping I am using the RFCname.respone message type is that ok in asynchronous process?
And then I went to ECC in Tcode SM59 and created a RFC destination of type TCP/IP
and put the same information as given above and test the connection which is working fine.
I have created a FM at ECC end make it remote enabled. and calling the FM in back ground task using destination in a Work flow code.
When I run the Work flow code It ran successfully but i went to XI side there is no msg in the SXMB_MONI.
Then i went to the component monitoring->Adatptor engine>Comm. channnel Monitoring and found that under my RFC sender comm. channel there is an error msg saying
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'BS_ECC', toParty '', toService '', interface 'YFPS_MM_I_0242_PO_APPROVAL_OUT', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_0242_PO_Approval_RFC_Sender' (channelId 19585252a58335ee871e4c3a771b027f)
Where as i have checked that in the sxi_cache t-code there is a sender agreement for my scenario under the sender agreement tab.
Please Help me in this to resolve the above error. I am totally stuck at this point.I would really appreciate a quick answer.

Appl. Server Service (Gateway) : My Ecc server
Confused with this statement.....
it should have the format sapgwXX ....
XX is the system number which comes from the j2ee port mentioned in the XI homepage URL
http://<hostName>:5XX00:rep/start/index.jsp
How to configure sender RFC adapter...check this blog:
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1438
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException:
senderAgreement not found:
Sender Agreement is Expected in this communication which does not seem to be present in ID....create sender agreement using the RFC communication channel....
Regards,
Abhishek.
Edited by: abhishek salvi on May 2, 2009 1:24 AM

BPM- scenario RFC - XI - receive file - - SOAP - return answer to RFC

Hello everybody,
I have the scenario
RFC call a BPM
In the BPM, I have to receive information from a file ( generated by another system 4 times in a day)
Mix the data of the file with the data of RFC
Send them a SOAP
send the reply to the RFC
My problem is : how to receive the file on demand because in file adapter ( sender ), the definition is only by interval of time?
Is there anybody who can help me?
Thanks in advance and best regards.
Eric.

Hi Eric,
in sender file adapter, we just have polling interval - so in your receive step in BPM you have to wait for the source file.....
i do not think any other workaround will be feasible for your this case
Regards,
Rajeev Gupta

Multiple clients for a RFC sender to SOAP scenario

All,
We have a RFC to SOAP scenario in our Development server and is working.
The problem we are having is - we only have one XI server available. But there are different clients in Dev that want to use this scenario now. Though we create the new BS for each of these clients, the issue i see is in the RFC sender communication channel. it needs to have the program id.
Right now we are creating a new program id for each of the clients(which translates to different RFC destination names on the ABAP side)... but that is causing a problem on the ABAP side - since the calling function is the same and they need some logic to change the RFC destination based on the client..
Are we missing something or is there a simpler way to this?
Thanks.

we created the exact same way you told... just add another business system. complete the receiver determination, interface determination and sender agreement.
It works every other time. When we checked the communcation channel monitoring - it will go to the client 210 once, and it would work. when we call the next time - it will error with a short dump in ABAP - but the error will appear on the communication channel for 250 (though we are calling from 210).
Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'UD1CLNT250'/'RFC_UD1CLNT250', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'UD1#210' returned party/service of ''/'UD1CLNT210')
Any thoughts?

How to send back the soap fault message without details tag to the sender

Hello Expert,
Is it possible to send the soap fault message(fault String element value) without details tag as shown below to the sender in synchrounous scenario.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soapenv:Body>
          <soapenv:Fault>
               <faultcode>soapenv:Client</faultcode>
               <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.arrayOtrosTributos.otroTributo(1).codigo - El Código de Tributo es obligatorio.</faultstring>
               <detail></detail>
          </soapenv:Fault>
     </soapenv:Body>
</soapenv:Envelope>
I have to send the faultstring element value in one of the element in response message back to sender? Is it possible using BPM?The above fault response does not have a fault payload (no detail element) and would result in a system error message.So how to handle this?
If yes .Please tell me the BPM design
faultstring value will be dynamic.
Thanks in advance

Thanks Yzanagi,
I have gone through the index.htm file.
In my scenario that is RFC -PI-soap(using http(Axis) protocol).when the webservice provider is sending the soap fault as.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soapenv:Body>
          <soapenv:Fault>
               <faultcode>soapenv:Client</faultcode>
               <faultstring>autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1</faultstring>
               <detail></detail>
          </soapenv:Fault>
     </soapenv:Body>
</soapenv:Envelope>
In PI sxmb_moni it is converting to the error (system not application error)as shown below when using receiver soap adapter with https(Axis) transport protocol and Message protocol:Axis.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1></SAP:P1>
<SAP:P2></SAP:P2>
<SAP:P3></SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: autorizarComprobanteRequest.comprobanteCAERequest.numeroComprobante - El Número de Comprobante debe ser mayor o igual a 1.</SAP:AdditionalText>
<SAP:Stack></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
As my requirement was (I have mentioned in my first question) that I want to pass
SAP:AdditionalText tag
value back to sender in one of the elements of response message payload or handle using fault message mapping if this error could be converted to application error and map to the RFC exception but unfortunately which is not possible even using AXIS adapter.
so other option to inform the sender RFC is mentioned here http://help.sap.com/saphelp_nw70/helpdata/en/22/0425e0488911d189490000e829fbbd/content.htm
but while handling the SYSTEM_FAILURE exception from PI at sender in report program and displaying the msg variable ,I am not getting complete error message..It is getting truncated.Is there a limit to the no of character the msg variable contains which is set by system.Even if we declare msg variable with more length(for example char length 500) it is just displaying part of the error message from PI.
Any Idea to read complete system error message from PI in report program at RFC sender..
Kind Regards,
Kubra fatima

RFC Sender configuration

Trying to configure webservice(SOAP)-->XI->R/3(RFC) scenario.
Created a z_fun_mod and made it remotely enabled in R/3.
Trying to create a destination of type T in XI for R/3. As I need to specify 'ProgramID' for 'Registered Server Program', I specified a 'sdnweblogs' as per Michal's blog /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step . When I test this connection, got the connection error saying 'program sdnweblogs not registered' in my R/3 host/gateway.
How do I register the programID?
Is this 'sdnweblogs' supposed to be a function module in R/3 client that calls my z_fun_mod ?
As per michal's blog, the programID is later needs to be specified while configuring the RFC Sender.
TIA,
Steve.

You want a R/3 -(RFC)-> XI -(SOAP)-> Webservice scenario, then? It's different from what you had previously informed (webservice -> XI -> R/3).
Anyway, for R/3 to send data to XI through a RFC, you need:
1. to configure a RFC Destination, inside R/3 (TX SM59), using type T (TCP/IP), activation type "registered server program", informing a Program ID, and informing the R/3 gateway host and gateway service (sapgwXX, where XX is your instance number). It's kinda confusing to use R/3 informations inside R/3 itself, but that's how it is.
2. to create a sender RFC Adapter, which will get the data from R/3 and send to XI. There, you'll need to inform the RFC Server (gateway) host and service again. The Program ID must be the same you used in RFC Destination above. And finally you need the info for the metadata repository. Generally, it's the same R/3 instance that runs the RFC server, so just input it again, but this time you'll need the client number, a language and a user authentication to the system (just like you'd configure a SAPGUI entry).
I spent quite a long time trying to understand this configuration scenario, but the best that I could come up with was this: A metadata repository is linked to a application that consumes the metadata through a RFC server. So, in your metadata repository, you'll need the information of this RFC Server (done in SM59) and in your application you'll need to reference both the RFC server and the metadata repository (both done on the adapter configuration). But in most of the cases the RFC server and the metadata repository are the same (R/3, for example), and so you'll need to reference R/3 in R/3 (in SM59) and reference it twice to XI (in adapter configuration).
hehehe, it was the only explanation that made any sense to me.

RFC Send could not be resolved against SAP system because its metadata could not be obtained...EXCEPTION FU_NOT_FOUND RAISED

Hello,
I am getting the following error in sending IDOC to SAP via WCF-SAP adapter in BizTalk Server 2009. I have the SOAP header in the adapter mentioned below. Also, wondering what is the convension for Action URL? Is it always "http://Microsoft.LobServices.Sap/2007/03/Rfc/"
+ Operation name mentioned in the Orchestration? I would appreciate if anyone could help me resolve this error.
The adapter failed to transmit message going to send port "SendReceive_PO_IDOC_TO_SAP" with URL "sap://CLIENT=111;LANG=EN;@a/123.456.789.101/00?GWHOST=123.456.789.101&GWSERV=sapgw00&ListenerProgramId=ABCDEF111&RfcSdkTrace=False&AbapDebug=False".
It will be retransmitted after the retry interval specified for this Send Port. Details:"Microsoft.ServiceModel.Channels.Common.MetadataException: RFC Send could not be resolved against SAP system because its metadata could not be obtained. ---> Microsoft.Adapters.SAP.RFCException:
Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=EXCEPTION FU_NOT_FOUND RAISED. AdapterErrorMessage=An error occurred while determining the function interface of the RFC Send.
at Microsoft.Adapters.SAP.RFCException.HelperThrow(Int32 retCode, String additionalErrorMessage)
at Microsoft.Adapters.SAP.RfcClientConnection.GetRfcFunctionInterface(String rfcName)
at Microsoft.Adapters.SAP.InternalRfcMetadata..ctor(String originalRfcName, SAPConnection sapConnection)
at Microsoft.Adapters.SAP.SAPMetadataContract.ResolveOperationMetadata(String operationId, TimeSpan timeout, TypeMetadataCollection& extraTypeMetadataResolved)
at Microsoft.ServiceModel.Channels.Common.Design.MetadataCache.GetOperationMetadata(String uniqueId, Guid clientId, TimeSpan timeout)
at Microsoft.ServiceModel.Channels.Common.MetadataLookup.GetOperationDefinition(String operationId, TimeSpan timeout)
at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadataUsingSdk(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper
timeoutHelper)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
SOAP Header:
<BtsActionMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Operation Name="Send" Action="http://Microsoft.LobServices.Sap/2007/03/Rfc/Send" />
</BtsActionMapping>
Thanks,
Tarun

Hello Morten,
The Send is actually just the name of the operation in Orchestration and it does not exist in SAP. Hence, do I really need to have the SOAP header in WCF-SAP adapter or can I send the IDOC without any SOAP header info? When I try to send without
SOAP header I get the following error. Can you help me resolve this?
The adapter failed to transmit message going to send port "SendReceive_PO_IDOC_TO_SAP" with URL "sap://CLIENT=111;LANG=EN;@a/123.456.789.101/00?GWHOST=123.456.789.101&GWSERV=sapgw00&ListenerProgramId=ABCDEF111&RfcSdkTrace=False&AbapDebug=False". It
will be retransmitted after the retry interval specified for this Send Port. Details:"System.ArgumentNullException: Value cannot be null.
Parameter name: key
at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.CreateChannelFactory[TChannel](IBaseMessage bizTalkMessage)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.InitializeValues(IBaseMessage message)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2..ctor(IBaseMessage message, WcfTransmitter`2 transmitter)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfTransmitter`2.GetClientFromCache(String spid, IBaseMessage message)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfAsyncBatch`2.BatchWorker(List`1 messages)".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Thanks,
Tarun

RFC Sender Adapter - MP: exception caught

Hi Friends,
We have one RFC to SOAP scenario in our PRD system.
When we execute an RFC in the R/3 side, the sender RFC CC receives the message. (The message id is generated). But, the message is not entered into SXMB_MONI.
When we checked the audit log. The error is as below:
RfcAdapter received sRFC for Z_RFC_SUPER_ACK from P88/300. Trying to send message synchronously.
MP: entering1
MP: processing local module localejbs/RfcAFBean
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection RFC_http://sap.com/xi/XI/System is currently not started.
We have checked Program ID, RFC Connections in R/3 system. It is correct. The standard module " localejbs/RfcAFBean - Local Enterprise Bean " is used in the sender CC, only this module.
We have few RFC receiver communication channels, all are working fine.
Only this Sender RFC CC, we are facing this problem.
We found the similar thread "RFC-Connection not started ?". The same problem we are facing. They suggested to bounce the system and restart.
Since it is PRD system, it is not able to do that immediately. Since all RFC receivers are working fine, we feel that it is not required to bounce.
Can you kindly help me friends, how to solve this problem.
Thanking you,
Kind regards,
Jegathees P.

Hi Sabarish
The RFC sender cc is active in ID and started.
The status of the channel in CC monitoring is red. (due to this error).

RFC Sender Adapter in XI..Possible??

Hi All,
I am trying to send data from XI using RFC Sender Adapter.
Have done all the configuration, ie created a tcp/ip destination in SM59 and then in the RFC adapter mentioned the program name.
In Adapter monitoring i can see the adapter working fine.
When i execute the Function Mouldule i get the following error in SM58.
parameter JCO.Request was <null> (server: RfcServer[CC_RFC_TX1_OUT]1)
Can anyone please lemme know if we can send data from XI box using RFC sender adapter.
Regards,
Sumit

Sumit,
Technically specking this should be possible.. I Havent tried it though..
So, you are using a Sender RFC to send data from XI to XI itself uh?
I have tried configuring a Receievr RFC adapter pointing to XI and it has worked fine.
Also, take a look at these blogs if your config is correct,
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Regards,
Bhavesh

SOAP to Synch JMS(Websphere MQ) without BPM

Hi
i have created an interface for SOAP to Synch JMS (Websphere MQ)without BPM.
I have reffered the SAP Note 1086303 - XI JMS Adapter and IBM Websphere MQ (Que : 4).
Since JMS adapter is a Asynchronous adapter with EO & EOIO, how to proceed with this interface.
I am in PI 7.11 .....
Sender : Soap Adapter
Receiver : Created 2 JMS channels....1) Receiver(for Request Queue) 2) Sender(Response Queue)
I am testing through soap Ui....
Please let me know if someone has done this interface..
Regards
Reema

I have done the configuration using integrated configuration where sender is Portal & receiver is receiver JMS channel.
Not sure how it works in case of Integrated Configuration...may be you can first try with the normal procedure (including IE) and then check if the flow is working.
what should be the sender service portal or JMS MQ?
The sender would be the JMS service....the response soming from the JMS will be posted to the waiting response part of the original sender (in your case SOAP).

Problems in RFC Sender adapter

Hello
I am having a scenario where I am sending the message through RFC sender. The message is getting posted on integration server but its giving error in SXMB_MONI.
The error says
"HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)" in call adapter.
I checked some notes mentioning about poll parameter of sap af messaging in visual admin but still the problem is same.
Thanks in advance.
Regards
Rajeev

Udo,
I checked the file adapter but the status is green which says "No message processing till now" and also it is not listed in Message monitoring.
Also as described in note mentioned by shekhar I tried to change the Visual Admin poll interval. also i tried that URL which gave "Messaing servlet is active"
<?xml version="1.0" encoding="UTF-8" ?>
- <scenario>
<scenname>MSG_SCEN</scenname>
<scentype>SERV</scentype>
<sceninst>MSG_001</sceninst>
<scenversion>001</scenversion>
- <component>
<compname>SERVLET</compname>
<compdesc>Messaging System</compdesc>
<comphost>localhost</comphost>
<compinst>MSG_001</compinst>
- <message>
<messalert>OKAY</messalert>
<messseverity>100</messseverity>
<messarea>QR</messarea>
<messnumber>801</messnumber>
<messparameter>na</messparameter>
<messtext>MessagingServlet is active.</messtext>
</message>
</component>
</scenario>

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

Similar Messages

Maybe you are looking for