Synchronous JMS RFC scenario

Similar Messages

Synchronous HTTP - RFC Scenario: Timeout

Hello together,
I have just implemented a synchronous HTTP --> RFC scenario. When I test the implementation using the HTTP testing tool within the Runtime Workbench everything works fine.
However when I use an external HTTP Client I get a timeout exception. This is also raised in the XI Message Monitoring: "Timeout condition of pipeline reached"
Do you know any reason for this?
Thank you very much.

Hello,
this problem is solved now. It was a problem with the HTTP Client, obviously because a wrong queueID was automatically inserted in the URL.

Help SOAP to RFC Scenario using BPM (Synchronous communication)

Hi,
I am doing a scenario from SOAP to RFC scenario(Synchronous communication). Here I am creating a PM Notification in the SAP system through a webservice.
I am using three BAPI'S here,
1. BAPI_ALM_NOTIF_CREATE
2. BAPI_ALM_NOTIF_SAVE
3. BAPI_TRANSACTION_COMMIT
I am successful in calling the first BAPI from the Web Service. For this I have not used BPM. But to commit the transaction(PM notification in this case), I have to execute the other two BAPI's as well. I have to pass the output of first BAPI to the second BAPI and then execute the 2nd BAPI. And finally have to execute the 3rd BAPI. FYI, 3rd BAPI is not dependent on any output. It has to be executed independently after execution of the first two BAPI's.
How can I execute this scenario? Do I have to use BPM? If yes please let me know the steps in detail. I have not done any BPM scenario till now. So please answer me in detail.
Thanks in Advance,
Vijay
p.s. reward points are must

Hi Vijay,
Yes, You will indeed need a BPM in this case...
Based on my understanding of the Scenario u have explained, here are the steps that would be needed.
1. Receive With the Sync-Async Bridge open.
2. Transformation Step (Between the source Request and The BAPI_ALM_NOTIF_CREATE Request)
3. Send Synchronous
4. Fork
5. In one Branch of the fork - Transformation (Between the BAPI_ALM_NOTIF_CREATE Response and API_ALM_NOTIF_SAVE Request)
6. In the other branch of the fork - Transformation (Between a Dummy Source and the BAPI_TRANSACTION_COMMIT Request)
7. Send Synchronous (to make the 2nd BAPI Call)
6. Transformation ( BAPI_ALM_NOTIF_SAVE Response and the source Response)
7. Send Asynchronous (to make the 3rd BAPI call)
8. Send the Source Response and close the Sync-Async Bridge.
There might be alternative ways also of doing it...
Also a better design would be to take care of the 2nd and the 3rd BAPI call within the code of the 1st RFC Function Module.
Regards,
Abhy Thomas

Public URL for Synchronous SOAP to RFC scenario

Hello Everyone,
I have synchronous SOAP to RFC scenario.
i have created the http URL for testing environment through sender agreement.
However, now the user wants a public URL and that too secured one ... means ( https ) in production.
i tried this blog, but Service registry is not configured in our landscape.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23725
is there any other way ..?
Regards,
Ravi

The process of creating the wsdl will remain same. The url in your case will start with HTTPS instead of HTTP. Note that the port at which HTTPS data would be received will be different than HTTP port and thererfore you need to change that as well. You don't have to set any client authentication unless there is a business requirement. You may simply use certificates for SSL.
In some cases, if PI always receives data through web-dipatcher (ask your network team), then the data hostname and port of web-dispatcher should be used.
Regards,
Prateek Raj Srivastava

File to RFC scenario using BPM : a synchronous one

Hi All
I am doing File>RFC>File scenario using BPM with help of the blog
RFC Scenario using BPM --Starter Kit
here everything is explained but i am getting error while the processing of BPM part
Input file is being picked (this part is success) but rest BPM and response i am not getting back in .
interface names
filereq_MI >Filetoabstract_MI>Sync_MI>RFCtoabstract_MI>Fileres_MI
(abstract means its an abstract interface)
i have configuered the Integration process as follows
Start>Recieve>synch_send>send>end
step : Recieve
mode : asynch
message:Filetoabstract_MI
step : synch_send
mode : synch
synch interface : synch_send
req message:Filetoabstract_MI
res message : RFCtoabstract_MI
step : send
mode : asynch
message:RFCtoabstract_MI
and i have given interface mapping during second (synch_send) step but here mapping is giving problem its showing exception error during mapping
error is there
1) Integration process ---> file
2) Integration process-->R/3 system

Hi,
Configure the Integration Engine According to this Blog and Trigger the Process again
Configuration of a Central Integration Server
Regards
Seshagiri

File to RFC scenario with no BPM

I want to create File to RFC scenario with no BPM. I want to invoke RFC synchronously to verify that I'm getting correct response back, but i dont wanna process the response. So, In SXMB_MONI i can check the response back from RFC right? Or do I need to have BPM if want to see the response back from RFC?
What kind of business system i need to create for RFC? can i use same business system for both File and RFC? I'm using one Business System created on Third party technical system, which i'm using for file Input, also for RFC. Is that OK?
Thanks,
Deepesh

Hi,
I need to have BPM if want to see the response back from RFC? ... yes
The BPM will help you find the response very comfortable.
What kind of business system i need to create for RFC? can i use same business system for both File and RFC? I'm using one Business System created on Third party technical system, which i'm using for file Input, also for RFC. Is that OK? ..Yes you can .
Regards
Agasthuri Doss

XI to RFC Scenario: Runtime error during RFC Call

Hi,
I am testing a XI-to-RFC scenario involving BPM. The RFC works perfectly from SE37; but I get 'ICM_HTTP_TIMEOUT, Error code 402' when I invoke it from XI. On digging through the problem, it appeared that the calling program produced a short dump at the ABAP end. The code is as follows:
<b>module %_rfcdia_start output.
    "Do not display screen !
    call 'DY_INVISIBLE_SCREEN'.
    perform remote_function_diastart.
endmodule.
module %_rfcdia_call output.
    "Do not display screen !
    call 'DY_INVISIBLE_SCREEN'.
    perform remote_function_diacall.
endmodule.
module %_cpic_start.
if sy-xprog(4) = '%RFC'.
    perform remote_function_call using rfctype_external_cpic.
else.
    call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
    perform cpic_call using convid.
endif.
endmodule.
form cpic_call using convid type c.
communication send id convid buffer header.
if sy-subrc eq 0.
    perform (sy-xform) in program (sy-xprog).
else.
    message a800.
endif.
endform.
form remote_function_call using value(type).
data rc type i value 0.
do.
********This is the line where error occurs************
    <i>call 'RfcImport' id 'Type' field type.</i>
    if sy-xprog = 'JAVA'.
      system-call plugin
                  id 'JAVA' value 'FORW_JAVA'
                  id 'RC'   value rc.
if there is no rollout on the JAVA side which
rolls both, JAVA and ABAP, we return to the
C-Stack and reach this point
in case there was an rollout, the ABAP-C stack is lost
and we jump direkt to this point
here we trigger the rollout on this Abap side with
the following statement
      system-call plugin
                  id 'JAVA' value 'ROLL_OUT'
                  id 'RC'   value rc.
    else.
      perform (sy-xform) in program (sy-xprog).
      rsyn >scont sysc 00011111 0.
    endif.</b>
Anybody has any idea why it is happening? Is it a network issue? The dump in ST22 says that 'The program "SAPMSYS1" was terminated manually'. How it is possible to manually abort an automatic call?
Awaiting reply.
Regards.

Hi,
Probably because of timeout, it is unable to execute the request ..so it is aborted.
btw, is it a synchronous call ? what is the message size ? the given data to RFC is correct and valid structure ? check the mapping .for this use the data from SXMB_MONI and test it
Check this blog for timeout errors-
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Regards,
moorthy

XI to RFC Scenario

Hi SapAll.
i had created a Remote Function Module in SAP-R/3 with 2 structures under tables(tab)and this rfc is going to collect data from xi for doing some bdc and then when the bdc fails,rfc will return values to xi.
in this real time scenario what xi will do,i know that xi will collect the data from rfc.
as i have got the Netweaver-PI Software i would like to create a sample interface in PI for doing the above mentioned scenario
so what my question is how and in what way we can do this in XI without BPM,after xi collect the export parametes from rfc with failed reasons what xi do,will it update the sender.
will be waiting for a good answer.
regards.
Varma

1. if ur sender adapter is sync like SOAP
you sync RFC scenario...whatever the resposne that u get from RFC can be mapped back to sender using the response mapping..if the sender supports that fore.g if u are using SOAP as sender..
2. if ur sender adapter is not sync like file / JDBC / JMS
just do the RFC lookup in mapping ..map the response to the target structure and use the receiver which is same as the sender and generate file to the sender

RFC TO RFC SCENARIO

Hi,
I want to try RFC to RFC scenario .For this have One client with Solution manager and another client has R/3 on it .I want update a z table in R/3 from the data i have in solution manager (RS001).
I want to know following things :
what is the program ID in RFC sender adapter ?
where should i make the rfc destination .....which my abap program will call ...via xi ....picking data from solution manager.

Hi,
what is the program ID in RFC sender adapter ?
The same ID as u configure in RFC destination at sending SAP system.
where should i make the rfc destination?
1. Transaction SM59 on sending sap system: To XI
2. On XI: To receiving sap system
which my abap program will call ...via xi?
Your abap program at sending sap system calls a function modul at XI:
CALL FUNCTION 'myFunction' DESTINATION 'myDestSM59' ...
....picking data from solution manager.
receiving SAP system
You need a synchronous scenario. R/3 system function modul works as Outbound, sol man function modul as Inbound.
Regards,
Udo

Using multi mappings in a synchronous intergace mappings scenario.

Hi XI Gurus
I have a synchronous soap --> XI --> Sync. RFC scenario (non BPM) which works fine.
My requirement is to add another mapping object using multi mappings in this scenario, but since XI has a limitation which prohibits me to use multimappings as interface mapping used is a synchronous one.
Can this be achieved using a BPM ?
Is it possible to use two asynchronous message mappings instead of one synchronous Interface mappings?
Thanks,
Lovein

Hi Pratheek ,
Thanks for your reply.
To explain the issue in other words..
I would like to use a asynchronous interface mapping instead of synchronous one being used currently to access RFC.
I need to use asynchronous Interface mapping as the multi mappings are not supported by synchronous Interface mappings in XI
as has been described on help.sap.com "If you want to map multiple messages to each other by using a multi-mapping, you can only specify asynchronous interfaces" on link
[http://help.sap.com/saphelp_nw04/Helpdata/EN/4f/ef761a5ecfb1418b79896e10fe4c57/content.htm]
So the burning issue boils down to if I can break a synchronous call (RFC request/response in my case) in to 2 asynchronous ones.
If a BPM is needed to achieve the goal then can you guide how that can be done.
Thanks,
Lovein

NO_RECEIVER_CASE_BE error in a SOAP - XI - RFC scenario

Hi gurus:
I'm configuring a SOAP -> XI -> RFC scenario and I'm getting a "NO_RECEIVER_CASE_BE" error when I send a test message using the SOAP adapter.
I have another interfaces using the SOAP adapter of the same XI server and no problems with it. So I think my problem is not into the SOAP adapter.
Thanks to all in advance,
Alejandro Gomez.
Edited by: Alejandro Gómez on May 27, 2008 10:24 AM

Hi:
The entire XML result from MONI is next:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30"><SOAP:Header><SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7"><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>synchronous</SAP:ProcessingMode><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:TimeSent>2008-05-27T09:10:24Z</SAP:TimeSent><SAP:Sender><SAP:Service>Openlab_Desarrollo</SAP:Service><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Sender><SAP:Interface namespace="http://www.huc.es/xmlns/openlab">ServicioObtencionDatosPaciente</SAP:Interface></SAP:Main><SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>BestEffort</SAP:QualityOfService></SAP:ReliableMessaging><SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="AE">af.xi2.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2008-05-27T09:10:24Z" wasRead="false"><SAP:Engine type="IS">is.00.xidserver</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>BD9B57A1-2BCC-11DD-C738-001B7899027A</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList><SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Date>20080527</SAP:Date><SAP:Time>101024</SAP:Time><SAP:Host>xidserver</SAP:Host><SAP:SystemId>XI2</SAP:SystemId><SAP:SystemNr>00</SAP:SystemNr><SAP:OS>Windows NT</SAP:OS><SAP:DB>ORACLE</SAP:DB><SAP:Language/><SAP:ProcStatus>023</SAP:ProcStatus><SAP:AdapterStatus>000</SAP:AdapterStatus><SAP:User>XIAFUSER</SAP:User><SAP:TraceLevel>3</SAP:TraceLevel><SAP:Logging>1</SAP:Logging><SAP:LogSeqNbr>001</SAP:LogSeqNbr><SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr><SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal><SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal><SAP:PipelineElementId>5BC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId><SAP:PipelineService>PLSRV_RECEIVER_DETERMINATION</SAP:PipelineService><SAP:QIdInternal/><SAP:CommitActor>X</SAP:CommitActor><SAP:SplitNumber>0</SAP:SplitNumber><SAP:NumberOfRetries>0</SAP:NumberOfRetries><SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries><SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine><SAP:PlsrvExceptionCode/><SAP:EOReferenceRuntime type="TID"/><SAP:EOReferenceInbound type="TID"/><SAP:EOReferenceOutbound type="TID"/><SAP:MessageSizePayload>508</SAP:MessageSizePayload><SAP:MessageSizeTotal>2985</SAP:MessageSizeTotal><SAP:PayloadSizeRequest>508</SAP:PayloadSizeRequest><SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap><SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse><SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap><SAP:Reorganization>INI</SAP:Reorganization><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound><SAP:InterfaceAction>INIT</SAP:InterfaceAction><SAP:RandomNumber>00</SAP:RandomNumber><SAP:AckStatus>000</SAP:AckStatus><SAP:SkipReceiverDetermination/></SAP:RunTime><SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="end" host="xidserver">20080527091024.6</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="xidserver">20080527091024.616</SAP:Timestamp></SAP:RunTimeItem></SAP:PerformanceHeader><SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Fatal</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic><SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external = </Trace>
<Trace level="1" type="T">Sender party normalized = </Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = xidserver:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.137.73.104</Trace>
<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace>
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB... </Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
</Trace>
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found </Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK. </Trace>
</Trace>
<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="3" type="T">system-ID = XI2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = S</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z 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>
<Trace level="1" type="T">Message-GUID = BD9B57A12BCC11DDC738001B7899027A</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace>
<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="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline attributes </Trace>
<Trace level="3" type="T">PID        = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE     = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE    = A</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline elements </Trace>
<Trace level="3" type="T">ELEMPOS    = 0001</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0002</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0003</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0004</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0007</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0008</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">ELEMPOS    = 0009</Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">FL_DUMMY   = </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message </Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"></Trace>
<Trace level="1" type="Timestamp">2008-05-27T09:10:24Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
<Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS    = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG     = </Trace>
<Trace level="3" type="T">FL_DUMMY   = 0</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<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 level="2" type="T">Start without given receiver </Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers. </Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace>
<Trace level="3" type="T">Persisting message Status = 023</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:payload-bd9b57a22bcc11dd95bc001b7899027a#sap.com"><SAP:Name>MainDocument</SAP:Name><SAP:Description>Main XML document</SAP:Description><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>
Thanks,
Alejandro Gomez.

Removing ABAP dump when JDBC is down in RFC- JDBC- RFC scenario

Hi All,
I need help to build one scenario.
I am working on RFC->XI->JDBC->XI->RFC scenario. It is working fine.
But problem is that whenever JDBC server is down RFC is giving ABAP dump in SAP. How can i Remove ABAP dump in SAP and give information to RFC that "JDBC is out of order"
Is it possible to implement without BPM, then How?
If not possible then what could be the steps of BPM?
Thanks & Regards

Rohan,
1.Recive Step should open the Synch - Asynch Bridge
2. Block Step --> Send Synchronous inside this step with an Exception Hanler.
3. Now in the exception ahndler step, do the necessary error handling requirement.
4. Send Step --> closes Synch Asynch bridge.
My question is what data do you want to send back to the RFC if the DB is down? This data should be populated inside the exception handling block and then this data should be mapped to the corresponding RFC response and used in the step 4.
Regards,
Bhavesh

Unable to view payload in HTTP to RFC Scenario

Hi,
I have done HTTP to RFC Scenario. It's working fine. I know that for synchronous message the payload will be deleted (for save memory) after execution. But i want to see the payload of request and response messages. I am unable to. Please suggest any way to see payload.
For helpful answer i will rewards points too.
Regards
Bhupal Reddy

Hi,
Refer this blog by michal.
/people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
Regards,
sudheer.

Can anyone plz send HTTP to RFC scenario

Hi everyone,
can u guys send me the HTTP to RFC scenario? plz send the detail scenario for HTTP-XI-RFC.
thank u in advance
xilearner

1.Created data types for mapping with HTTP request and response.
2. Created messsage types and assigned corresponding data types to the message types.
3. Created one Message Interface (Outbound/Synchronous) for HTTP type and no need to create interface for RFC. You ca use the one which you have imported from R/3.
4. Create request and response message mapping and one Inteface mapping (with request tab and response tab) properly assigned.
Defined the following in ID:
1. Created HTTP business system (no communication channel)
2. Created communication channel for receiving system (SAP).
3. Created receiving determination and interface determination, receiver agreement, no sender agreement.
Check this link on how to configure RFC channel.
http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/e80440a832e369e10000000a155106/content.htm
Send XML message from HTTP client and you will see the response in the same.
Regards,
Sudheer.

Reg : JMS-RFC-JMS

Hi Friends,
My Scenario is JMS-RFC--JMS.(I have to get request XML from Sender JMS adpter to R/3 and then Response from R/3 has to sent back to receiver JMS adapter) i.e Both sender and receiver JMS has different queue names
I have created scenario exactly like FileRFC-FIle.So in my sender JMS adapter in Module tab i have used these two module AF_Modules/RequestResponseBean and AF_Modules/ResponseOnewayBean .
Please let me know whether the approach is rite or we can have some other apporirate design..
Thanks,
Dinesh

Hi Dinesh
you are on right track..
this one you can always refer for any message related JMS..
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8060448a-e56e-2910-f588-9af459e7ce21
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8060448a-e56e-2910-f588-9af459e7ce21?quicklink=index&overridelayout=true
Thanks,
Bhupesh

Synchronous JMS RFC scenario

Similar Messages

Maybe you are looking for