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

Similar Messages

  • 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 Web service

    Hi,
    I have a SOAP to RFC scenario.
    For this I need to provide a public url to the third party to access web service. Generally I provide the url generated by PI from Display WSDL of ID.
    Here vendor is asking for some public url through which he can access the web service.
    Please help .. how to generate this.
    Thanks in advance.

    Hi Kanda,
    I have configured the UDDI server and service registry as it was mentioned in the link provided by you . Now from sender agreement when I am click Publish on SR its not showing the previous error. But clicking on the publish its showing me below error -
                       Error when connecting to services registry; for more information, see the logs
    com.sap.aii.ib.core.uddi.RegistryClientException: Error when connecting to services registry; for more information, see the logs at com.sap.aii.ib.server.uddi.RegistryClientDelegateProvider$EjbRegistryClient.publishPhysicalSystems(RegistryClientDelegateProvider.java:441) at com.sap.aii.ibdir.server.wsquery.WSQUDDIPSPublishTB.execute(WSQUDDIPSPublishTB.java:91) at com.sap.aii.ibdir.core.simulation.DefaultTaskBroker.execute(DefaultTaskBroker.java:173) at com.sap.aii.ibdir.server.simulation.TaskQueryService.specialQuery(TaskQueryService.java:33) at com.sap.aii.ib.server.query.SpecialQueryServiceProvider$SpecialQueryServiceImpl.specialQuery(SpecialQueryServiceProvider.java:63) at com.sap.aii.ib.server.query.QueryServiceImpl.specialQuery(QueryServiceImpl.java:443) at com.sap.aii.ib.server.query.QueryServiceBean.specialQuery(QueryServiceBean.java:112) at sun.reflect.GeneratedMethodAccessor459.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:47) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy1530.specialQuery(Unknown Source) at sun.reflect.GeneratedMethodAccessor458.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:240) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:459) at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72) at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43) at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:983) at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59) at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

  • SOAP to RFC scenario prolem

    Hello Guru's
       Im trying the basic  SOAP TO RFC scenario, in which RFC is SXIDEMO_AIRL_FLIGHT_CHECKAVAIL
    and the out bound interface consists of only basic feilds i.e.
    REQUEST MESSAGE TYPE : AirlineID
                                                 ConnID
                                                 Fldate
    RESPONSE MESSAGE TYPE : Ecnofree
                                                    Bussfree
                                                    Firstfree
    and no fault message type.
    i created the scenario with out any errors, and i defined webservies in ID with the following URL
    http://starxi:50000/XISOAPAdapter/MessageServlet?Channel=:SXI_BS_SOAPRFC_SENDER:SOAP_RFCSENDER
    it is according to the following syntax
    htt://<xi server>:<J2EE Port>/XISOAPAdapter/MessageServlet?channel=:<sender business system>:communication channel.
    But im not able to post SOAP request to the xi server. it is saying following error
    "SOAP Request cannot be posted <with url > 403"
    403 is the error code.
    please can anyone help me in overcoming the above problem. and where iam wrong.
    Thanks in advance
    arjun

    Hi!
    Please check once again reg SOAP URL while generating the WSDL.
    [http://<HOST name:5<Port>00/XISOAPAdapter/MessageServlet?channel=:<Channel Name>:<Adapter Name>]
    [Re: Using SOAP Sender adapter in PI 7.1]
    1. Check whether your SOAP URL s correct or not which you are giving in the receiver SOAP adapter
    2. Also check you are giving the SOAP action in the receiver SOAP adatper correctly or not.
    3. Finally check the SOAP service is activei or not in SAP>BC>XI-->SOAP in ABAP stack
    4. Since FIle is only for ASYN comm and while using FILE for sync interface you need to pass module paramters in the Sender File CC
    ERROR 403 means::
    This error will be comming mostly in the synch scenarios like SOAP to RFC - SOAP and FIle to RFC--FILE
    when the target system is down or service is inactive.
    Error: HTTP 403 Forbidden
    Description: The server understood the request, but is refusing to fulfill it
    Possible Tips:
    Path sap/xi/engine not active
    u2022 HTTP 403 during cache refresh of the adapter framework - Refer SAP Note -751856
    u2022 Because of Inactive Services in ICF u2013Go to SICF transaction and activate the services. Refer SAP Note -517484
    u2022 Error in RWB/Message Monitoring- because of J2EE roles u2013 Refer SAP Note -796726
    u2022 Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. u2013Because of the URL is incorrect or the adapter is not correctly deployed.
    Regards::
    Amar Srinivas Eli

  • Synchronous SOAP to RFC

    Hi All,
    I have a doubt that in a Synchronous SOAP to RFC/PROXY interface that is it we need to configure the entire Interface and then have to test the Webservice for the response from Altova??
    I have configured SOAP at the sender and RFC at the receiver but my Customize BAPI is not yet ready but I want to test the Webservice from Altova,Is it so that i need to configure the whole scenario and test it.
    Isnt it enough if I do basic Configuartion??
    Thanks & Regards,
    R.K

    hi,
    if u want to test u r WEBSERVICE using altova spy...  u need not configure whole scenario.. configure simple soap to file scenario and check u r webservice..
    if u want to check syncronous scenario... for the testing use a BAPI which is already existing..
    Thanks,
    Madhav
    Note:Points if useful

  • 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" ?><!-- Inbound Message --> <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.

  • Alias URL for sender SOAP

    Hi Friends,
    We are working on SOAP to RFC Scenario. We would like to expose different URL instead of   * http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel * where it specifies the business service and communication channel as I dont want to share Interface level details Information with customer. Need your inputs.
    Regards
    Amar

    Hi Amar,
    we have a Reverse Proxy server before our PI - or you can use the SAP dispatcher which is quite easy to setup.
    With both you can define rewrite rules and this is the common solution for this problem.
    e.g.
    www.server.com/customer1/service1 =>  [your url with confidential data]
    Hope this was helpful.
    Best regards,
    Markus

  • Soap to rfc scenario error

    Hi PI Experts,
          For the first time i was doing soap to rfc scenario. I have created all the objects in the ID and in the IR and also created a web service from ID an then i have saved the wsdl in my system. I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
    so kindly please help me to solve this scenario.
    Thanks & Regards,
    B.Srinivas Prasad.

    I have uploaded the wsdl in altova xml spy and tested it but i got an error like 'no channel specified'. and also got an error 'unable to post the file'.
    Make sure that its in the below format :
    From SAP help :
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
    Under party:service:channel enter the party name, the service name, and the name of the communication channel. If no party has been created, enter the following: channel=:service:channel
    and check Sender Soap Channel Status is it activated/not and check Cache Status

  • SOAP to RFC Scenario - Error at Sender Communication channel !!

    Hi Experts ,
    I am trying to execute a SOAP to RFC scenario . At SOAP sender channel level I am getting the error in RWB .
    My findings :-
    1. Error at RWB  9/24/09 4:24:10 PM   error occured
                             9/24/09 4:24:06 PM   request received
    2. At SOAP UI client tool :
       <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
       <SOAP:Body>
          <SOAP:Fault>
             <faultcode>SOAP:Server</faultcode>
             <faultstring>Server Error</faultstring>
             <detail>
                <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                   <context>XIAdapter</context>
                   <code>ADAPTER.JAVA_EXCEPTION</code>
                   <text>com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:UPDATE:HTTP status code401 Unauthorized
         at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:455)
         at com.sap.aii.af.ra.ms.impl.core.queue.consumer.CallConsumer.onMessage(CallConsumer.java:134)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:917)
         at com.sap.aii.af.ra.ms.runtime.MSWorkWrapper.run(MSWorkWrapper.java:56)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:207)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)</text>
                </s:SystemError>
             </detail>
          </SOAP:Fault>
       </SOAP:Body>
    </SOAP:Envelope>
    3.  At SOAP UI level - "requires authentication with the realm 'XISOAPApps'"
    1. I don't see any issue in authorization as i am having SAP_ALL .
    2. URL string seems to be O.K :
        http://ABC:50000//XISOAPAdapter/MessageServlet?channel=:BSer_SOAP:CC_SOAP_Sender&version=3.0&Sender.Service=BSer_SOAP&Interface=urn:ABC.com:%5EMI_CustomerInfo
    Kindly advice !!!
    Regards ,

    1. Check PI id and password is working fine.
    Check if the user you are using has SAP_XI_APPL_SERV_USER role.
    Another way is to pass id and pwd in URL
    Try to pass the User ID and Password in the URL( the URL which is given to the webservice).
    Example: http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel &sap-user=xxxx&sap-password=xxxx
    2.Provide SOAP URL like -
    http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel

  • Reg:soap-xi-rfc scenario

    In soap-xi-rfc scenario if the RFC function modules processed in R/3 system with some errors then , how to handle the errors , do we need to create the error structure in xi by using the fault message type or there is any other way to handle the application errors?
    pls help with suitable answers
    regards
    chandrakanth.k

    Hi,
    The best way to go with ur senario is make it as SOAP XI Proxy.....in proxy u can catch the errors using the fault mesage typw and if u want to validate the data that can be done......if u want to send the error report that can be done in proxy....were u can collect all the errors and send they to the enduser or display them in Application server...
    Think this option if possible....
    check somelinks on fault mesage.
    ExchangeFalultData & ExchangeLogData
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    http://help.sap.com/saphelp_nw2004s/helpdata/en/5d/a45c3cff8ca92be10000000a114084/content.htm
    Asynchronus RFC  exception handling
    XI Alerts are not getting triggered from proxy servers
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ee5bc490-0201-0010-e9b5-
    a258cf083bca
    /people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
    Fault Message
    Regards,
    Phani
    Edited by: phani kumar on Mar 12, 2008 1:05 PM

  • SOAP TO RFC scenario (where the R/3 is not in same network)

    Dear Friends,
    I am trying to configure a SOAP to RFC (syn).where my SAP R/3 system is in our network .And we dont have all the details for creating a BUSINESS SYSTEM. I tried with BS.but every time I am getting "FAILED TO CALL ADAPTER ENGINE Error ,,,witha no_receiver_aggrement clause".
    but i have done the same scenario where the R/3 system is in the same network.
    I would like know ,what are the pre-requites for confeguring such a scenarion.And please give a detailed idea...
    where what is required and why........
    thanks,
    jeevan.

    Hai Raj,
    Thanks for your reply.
    My admin says.....the particular IP has full permissions...
    One more thing when i am trying to import the BAPI request.I am able to get the data from the remote SAP.
    So i believe everything is fine  from NETWORK side.
    And in the receiver RFC communication side I have seen just by changing the sap IP address to the public IP (Earlier the scenario was working fine with the local SAP system).
    I doubt do I have to do in the SLD business system level.
    thanks,
    jeevan.

  • MAPPING JCO_COMMUNICATION_FAILURE (SOAP to RFC scenario)

    Hi,
    Our system is PI 7.1 EHP1 and the scenario is to SOAP to RFC (Synchronous). I have imported the RFC into ESR and used it as data type for Outbound interface for SOAP.
    Initially i havent created any mapping because all Interface fields are same (name and type) with RFC because i have used RFC as data type. When we have tested the integration via SOAPUI we have seen that the request message wasn't transferred to RFC but the response was transferred from RFC to SOAP response. Could it be a bug? or is it normal behaviour?
    Later, i have created a graphical mapping without any data conversion etc.. It is just mapping. This time it transferred the request and response as well.
    When we have started stress test on a PI system (6000 SAPS), the PI JAVA stack started to use %100 of CPU. We have processed 100 message per minute. After 20 minutes, Java stack of PI has crashed and restarted.
    Our plan is to process message more then this test numbers. Possibly it is approx 400 message per minute.
    I have found below errors on RWB (approx 250 message have below errors).
    How this high CPU consumption can be resolved?
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
      <SAP:P1>Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>&quot;COMMUNICATION FAILURE&quot; during JCo call. Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:Stack>
      </SAP:Error>
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
      <SAP:P1>connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>&quot;SYSTEM FAILURE&quot; during JCo call. connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:Stack>
      </SAP:Error>
    Kind regards,
    Altuğ Bayram

    Hi,
    Connection between ABAP and JAVA has been broken...thats the reason for the JCO_COMMUNICATION Error
    you need to either restart the java or have a look at the RFC Connection JCO_AI_CONNECTION...
    re you making use of AAE for this scenario..which can improve the performance than using classic scenario.
    performance depends on the hardware of the server also...
    Check the sizing Guide of the PI 7.1 on SDN.
    Check the below link it may help you..
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782
    HTH
    Rajesh

  • Soap- XI- RFC scenario problem

    Dear all,
    i am configuring a scenario like SOAP->XI->RFC.the third party software send the PM notification  message to R3 via XI and the notification is created in R3.now i am facing the problem that the scenario works fine but i can't monitor the message in the Integration server and the message is also not monitored in the adapter engine.
    appreciate  if anybody can give me some advice.
    P.S.
    some message can be monitored,but the status is system error.the error message lis like below:
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get a client from JCO.Pool: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: 00024No connect to database, session terminated??????????????????????????</SAP
    thanks for your attentions.
    best regards
    xiao feng
    SAP china

    Xiao
    For you to see synchronous messages in Xi, you've got to go
    >sxmb_adm
    >integration engine configuration
    >specific configuration
    >add a new entry
    category : Runtime
    param : logging_sync
    value : 1
    set this settings and you should be able to see messages in sxmb_moni
    How have you configured the RFC adapter?  Have you set the client and login/password?

  • SOAP to RFC Scenario (automatic updation)

    Hi All,
    I have a requirement, i.e we have a web system. In that gold rates will update in every one hour.
    When ever the update will happen that should be update in SAP system via RFC call  automatically.
    Here sender side I am using SOAP adapter.
    I know the process to do the soap--rfc scenario.
    But how the gold rates will updates automatically in SAP system, with out triggering some one?
    can any one guide me to do this scenario.......
    Thanks in advance......

    Hi Maridu,
    yes with availibility time planning you can choose daily: monday, tuesday, not wednesday (for instance), thursday, etc.., plus for these day, a run which begins at 17:00 during 4 hours (for instance)... so to define a range, but that, it's mainly usefull with a FILE adapter as we have a polling (e.g every 60S or 3600S = 1h).
    but as you, you use a sender SOAP, and if I'm not wrong (I have not a PI under eyes just now) you have not a polling. So a solution should be to define several availibility-time plannings (one per hour) on your same sender CC. Low work effort and easy to do.
    Another solution is to not use availlibility-time planning, but to define your sender CC as "external" in "RWB -> CC monitoring", and to use an external tools (*) to trigger externally this sender CC, in fact to call an HTTP address by passing the "party | businessComponent | Sender CC" plus an action (STOP or START, this CC). There are several blogs on SDN to know how to trigger externally a CC (sender or receiver).
    (*) external tool can be a unix command (wget), or a scheduler tool (to buy) like $universe (for instance) or eventually a sap job which run an abap program which call this HTTP address.
    regards
    mickael

  • SOAP to RFC Scenario

    Hi,
    I have a scenario, SOAP to RFC with R/3 as receiver and MDM as sender. From PI side the scenario is working fine, but when the actual data is passed from MDM the data is not getting posted to R/3. Please guide how to test this scenario end to end. Also please tellme how to check if the data si posted to R/3 where RFC adapter used.
    Eg - we have T-code we02 to check whether an Idoc is posted to R/3... In a similar way please tell me how to check for this scenario.
    Thanks

    hi,
    first go to Runtime Workbench>Component Monitoring>Adapter Engine>Communication Channel Monitoring>check the SOAP sender channel
    If no problem,go to SXI_MONITOR and check if exist any record of your escenario. if no, go again to Channel Monitoring and check the RFC Channel.
    Now if you send the data from MDM and you cannot trace it in the first Step you have a problem in the MDM when it send data, so you must trace whats happening there.
    Let usknow

Maybe you are looking for

  • Dashboard will not run

    When I try to run dashboard it does nothing, I can't install widgets, it won't do anything. When I try to install a widget I get a dialog box that pops up and go's away very fast and the dock restarts(also something called crashdump running while the

  • How to copy video event to thumbdrive

    How can I copy a video event to a thumbdrive or burn to a CD?

  • SAP KM custom properties

    Hi all, I have created a new custom boolean  property in my repository I need to change the label icon for this property, in the property parameters I can indicate the imagen name but  where do I have to upload the image.gif? Thanks in advance Regard

  • Can't see my own sampler instruments or presets in 64 bit version.

    If I load up 9.0.0, I can see all my own presets and sampler instruments. But they are not showing up in 9.1. I have searched and seem to be the only one with this? anyone else? Keefy

  • Parametric reports and report server

    hi, how can I invoke parametric reports on report server. parameter form is not visible while invoking the report, hence giving errors. if any one can help Sreekant