Regarding ABAP Proxy : on a different client on XI Box

Experts,
I was referring to this thread
Has anyone generated server proxy on XI box??
where Michal has answered saying it is possible to have ABAP Proxies in XI box if its a separate client.
Does anyone have experience of doing this, what are the setup steps ?

Hey
yeah its possible if you have two clients of XI server,one client can act as ABAP proxy client and the other one can be the XI server .
please have a look at the following blog
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Thanx
Aamir

Similar Messages

  • How to connect ABAP proxy to two different XIs

    Hi, everyone. 
    I want to know there is a way to connect ECC to two different XIs using ABAP proxy.
    As I know, it is much easier to make scenario with RFC or IDoc sender
    but in our case we have to use ABAP proxy and must send to two XIs
    So, according to the plant type in the record, data should be splitted to each XIs.  
    And I wonder I should use logical port for each XI.
    Does anyone have a experience to implement this kind of scenario?
    Then Pls show me the guide how to implement.
    Very Urgent.
    Thanks.

    Hi,
    You cannot connect one ABAP proxy to two different XI systems at the same time.
    The configuration held in transaction SLDAPICUST holds the XI system that is connected (as well as the SM59 details held will only point to one XI system at any one time)
    Why would you want to send a message dependant on content to different XI systems ? Surely you would use conditional receiver determination in XI to route the message correctly.
    Cheers
    Colin.

  • PI 7.0 ABAP Proxy Wrong Namespace after Client copy

    Hello,
    i am looking for an PI expert because we have some problems with a standard ABAP proxy interface.
    We use the FSCM Module and we send Credit Commitment Notification from a SAP ECC 6.0 to PI 7.0.
    We use the Interface CreditCommitmentNotification_Out and it works fine on the Development System (D46). But on the integration system (Q46) it doesn't work. The Q46 is build up from our production system (P46) by a system/client copy.
    We get the error:
    The payload include a wrong namespace for the proxy interface.
    wrong: xmlns:prx="urn:sap.com:proxy:P46:/1SAI/TAS7DF374ECCA722B654BFE:700:2007/10/04"
    correct: xmlns:prx="urn:sap.com:proxy:Q46:/1SAI/TAS7DF374ECCA722B654BFE:700:2007/10/04"
    I dont know why we get the wrong namespace. I check the transaction SICF, SPROXY and SXMB_ADM  and compare it with the customizing on our development system. I didnt find any gap.
    Please help me if you have some ideas what is wrong on our system.
    Regards
    Jürgen 8-))

    Hi,
    We experience the same problem after an upgrade from ECC 5.0 to 6.0
    How did you solve this?
    Ron

  • Regarding abap proxy

    can i do the scenario by using abap proxy like this?
    Flow: XI (Client 800) -
    > XI (Client 001) ---> XI (Client 800)
    Regards,
    Madhav

    hai sumit,
    thanks for u r answer,
    i have done the same that u have mentioned,
    that issue is resolved and now it is showing Black & white flag in the sxmb_moni in 001 client
    now it is giving this error.
    <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>
      <SAP:P1>ifmmessif</SAP:P1>
      <SAP:P2>mi_flietdata_OA</SAP:P2>
      <SAP:P3>urn:proxytoproxy</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No implementing class registered for the interface (ABAP interface, request message mi_flietdata_OA, request message, namespace urn:proxytoproxy)</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    please do the need ful
    thanks & regards,
    Madhav Poosarla.

  • Help regarding ABAP proxy

    Hi ,
       please provide documentation or links  regarding generation and Configuration of ABAP Proxies.
    Ravi Raika

    Hi,
    Check the following links:
    <a href="/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies Approach for coding ABAP Proxies</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0ae9874-109c-2910-f48a-e91f0cdd1c81">EDM EMM Scenario Part I: Service Enabling - How to Implement eSOA-Compliant Services</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/41e08c90-0201-0010-9197-d8774336ea78">ABAP Proxy Generation</a>
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm">SAP Help - ABAP Proxy Generation</a>
    Thanks,
    Dipankar

  • Error while invoking the ABAP Proxy via SOAP Adapter

    Hi,
    My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
    SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
    Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
    SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
    With this approach, i am encountering the below error message
    2009-05-29 12:17:55 Error Adapter Framework caught exception: null
    2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
    Any ideas on the above errror message? Any pointers or inputs will be appreciated.
    Thanks,
    Vinayak Kamath

    > 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
    > 2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
    This is a generic error message which does not have any information about the error which has occurred.
    Do you see any error messages in the SOAP client?
    Regards
    Stefan

  • Http to abap proxy

    Hi ;
    Can somebody help me by sending screenshots for a http to abp proxy scenario.
    I am new to sap xi .
    i need a http cleint also,
    Thnx

    Hi
    Here in this case it is a http client to abap proxy. For http client (sender CC) u wud not req sender agreement. Follow the below link for http client config:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
    And u shud have the DT,MT, MI, Mapping in place. U wud do the req confir in ID and recv agreement will be for proxy. For that follow this link.
    /people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy
    Combine these two and u will get ur thread anwsered for sure. In this post the file will be replaced by http client. remeber no need to sender agreement.

  • ABAP PROXY CLEINT - PACKAGE

    Hi,
    I am trying to create an Abap Proxy of the type client and synch. 
    In the moment of the creation, it is necessary to select a package. 
    What package should I select? 
    Should I create a package and to add the elements "SAI_PROXY_GENTIME_PIF, SAI_PROXY_GENTIME_PIF_RESTRICT, SAI_PROXY_PUBLIC_PIF, SAI_PROXY_RUNTIME_PIF, SAI_TOOLS?"
    Thanks

    Hi,
    After all the information passed, I got to create the abap proxy. But when I will execute the program abap, the following message appears in the transaction sxi_monitor in R/3.
    xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Mensagem de entrada
      -->
    - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <SAP:Context />
      <SAP:Code p1="XML message not well-formed in node (7 ,49 )unexpected symbol: 'target'" p2="" p3="" p4="">PARSING.GENERAL</SAP:Code>
      <SAP:Text language="EN">Parsing error: XML message not well-formed in node (7 ,49 )unexpected symbol: 'target'</SAP:Text>
      </SAP:ErrorHeader>

  • What is package structure for Client ABAP Proxy?

    1.     What is the package structure need to be  followed for creating abap client proxy.
    2.     I read some where in the form, it need to be 4 levels. Why is it?
    Thank you
    Ganges Leaves

    Hi
    U hav to create a 4 level package structure for client ABAP proxy.
    U can create ur on packages
    1st level-structure package.
    2nd level-main package.
    3rd and 4th level-sub packages.
    To the 4th level only u hav to create proxy.
    The classes and code wil be automatically generated at the time of proxy creation.
    I think the 4 level structure bcz while in r/3 everythin in integration builder like software component version and all wil be takin as different levels.
    Also u can go through the weblogs in the above replies u got.
    Regards
    Victoria.

  • Missing asyn abap proxy client message in ECC

    Hi,
    I have a asyn scenario which an abap program will send data from ECC to PI using abap proxy client. My problem is i notice some of the message was no send to PI. Checked in PI SXMB_MONI no message was found. Any idea where the message was stuck? I check on smq1 in ECC also found nothing in the queue.
    Thanks.

    Hi ,
    KIndly check with the abap program if its thrwing any dump . If every thing is fine with ABAP program then might be its issue of RFC destination . check with transaction SPROXY are u able to connect and your sender interface is reflecting there if yes then double click on your interface open the proxy andthen click on GOto and click on connection test if nay issue is in connection then it will display the error here .might be some rfc DESTINATION is missing or authnetication error .
    Regards,
    Saurabh

  • Access/set dynamic configuration in client/server abap proxy

    Hi,
    I have 2 question regarding reading/setting dynamic configuration in ABAP proxies:
    1) Is it possible to set dynamic configuration objects in a server abap proxy (SAP --> XI)?
    When looking at the class CL_PROXY_FRAMEWORK is looks as if it is possible. This class has en attribute IF_XMS_MAIN~DY which is a reference to the class CL_XMS_MSGHDR30_DYNAMIC.
    I'm not sure if I'm supposed to try and access the dynamic configuration objects via this class or if I'm supposed to use the GET_PROTOCOL method in some manner as suggested by:
    http://help.sap.com/saphelp_nw04s/helpdata/en/51/d5cd16235e4643ae8ec92395c4ad97/frameset.htm
    Above link is for client proxies not server, and I've been unable to find any documentation on this for server proxies.
    2) The same question goes for server proxies (XI --> SAP), though now I would like to set some dynamic configuration data.
    This I believe should be done using get_protocol( if_wsprotocol=>ws_header ) as indicated by before mentioned link.
    However in both cases I'm not sure of if it is indeed possible and which road to choose for sure. So a hint or 2 would be really nice.
    Best Regards,
    Daniel
    ps. maybe I should just mention that I am pretty new to the ABAP world, so bear with me.

    The link that you gave does give you an example for both server and client proxies:
    Accessing Protocol Classes for Client Proxies
    In client proxies, you access the protocol class by using the GET_PROTOCOL method. Below is an example for the IF_WSPROTOCOL_PAYLOAD protocol:
    DATA:
    lo_clientProxy      TYPE REF TO co_clientProxy,
    lo_payload_protocol TYPE REF TO if_wsprotocol_payload
    lo_payload          TYPE REF TO if_ws_payload.
    CREATE OBJECT lo_clientProxy.
    Get Protocol Class Using Method GET_PROTOCOL
    lo_payload_protocol ?=
           lo_clientProxy->get_protocol( if_wsprotocol=>payload ).
    CALL METHOD lo_clientProxy->execute_synchronous
                EXPORTING output  = ls_request
                IMPORTING input   = ls_response.
    Use Protocol Methods
    lo_payload = lo_payload->get_sent_request_payload( ).
    Accessing Protocol Classes for Server Proxies (XI Only)
    Within the implementation of a server proxy, you get the protocol class by using the CL_PROXY_ACCESS=>GET_SERVER_CONTEXT( ) method:
    DATA:  lo_server_context   TYPE REF TO if_ws_server_context,
           lo_payload_protocol TYPE REF TO if_wsprotocol_payload.
    lo_server_context   = cl_proxy_access=>get_server_context( ).
    lo_payload_protocol =
         lo_server_context->get_protocol( if_wsprotocol=>payload ).

  • "SOAP:Fault" in scenario with ABAP proxy client

    Hello,
    I realized the scenario CRM40_Basis620(ABAP proxy client)->XI->File.
    XI:
    The sender communication channel is a XI adapter (Parameters: HTTP 1.0, XI 3.0, Integration Server, Security profile unchecked, Security level - HTTP).
    CRM:
    The proxy generation is ok.
    SLDCHECK is ok.
    All RFC destinations are ok.
    APPINT_200_620 for CRM was installed and configured well (I think so, but...).
    When I ran the ABAP proxy client on CRM, sxmb_moni(CRM) returned the text for the XML Message (Display-CallIntegrationServer-Payloads-TraceDocument):
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <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="1" type="T">system-ID = EST</Trace>
      <Trace level="1" type="T">client = 300</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = BABKIN_RA</Trace>
      <Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</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 level="1" type="T">Message-GUID = DC4424A659314CF18F500002A541D0E7</Trace>
      <Trace level="1" type="T">PLNAME = SENDER</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTS0004</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
      <Trace level="1" type="T">system-ID = EST</Trace>
      <Trace level="1" type="T">client = 300</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = BABKIN_RA</Trace>
      <Trace level="1" type="Timestamp">2007-08-06T13:55:12Z</Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
      <Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
    - <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV">
      <Trace level="1" type="T">URL for integration server read from global configuration</Trace>
      <Trace level="1" type="T">URL= http://SRMDEV.oao.sng:8011/sap/xi/engine?type=entry</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY" />
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="1" type="System_Error">HTTP-client: error response= <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Error during conversion of XI message</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIServer</SAP:Category><SAP:Code area="SECURITY">INBOUND_SECURE_LEVEL</SAP:Code><SAP:P1>DC4424A659314CF18F500002A541D0E7</SAP:P1><SAP:P2/><SAP:P3>HTTP</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Message DC4424A659314CF18F500002A541D0E7 was sent with ''. Channel configuration, however, requires 'HTTP' </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></Trace>
      </Trace>
      <Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>
      <Trace level="1" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>
      <Trace level="1" type="System_Error">HTTP status code 500 : Error during conversion of XI message</Trace>
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      </SAP:TraceHeader>
    I think the main problem is the parameter "HTTP Security level" for the channel, but not sure.
    Does anybody know where to find a solution?
    Regards,
    Roman

    Hi Roman
    There is no need for an XI adapter for client proxy.... we only use that for server proxies.
    Vaibhav

  • Client ABAP Proxy : how to know which program is calling that service interface proxy

    Hi All,
    I have prepared some client proxy in ECC to communicate with PI.
    But, if I am not wrong, unlike server proxy which is written directly in the class Provider class in SPROXT transaction, in client proxy we write abap code to trigger proxy in SE38 .
    My question is : If I am in SPROXY and looking at any outbound SI, of which proxy is already generated, then how can in SE38  can I find which program is triggering that interface or proxy?

    Hi,
    check below thread for calling client proxy
    ECC outbound abap proxy (client) - Get ECC messageID from Protocol
    Regards,

  • Sample Client ABAP Proxy Program - PI 7.1

    I created Proxy. I need to call in a Report Program. I am using PI 7.1
    Can anyone send me a sample Client ABAP Proxy program to use with PI 7.1

    Hi,
    >>>Can anyone send me a sample Client ABAP Proxy program to use with PI 7.1
    it's exactly the same as for 7.0 and there are blogs that show such sample reports on SDN
    just do a little search and I'm sure you can find it
    Regards,
    Michal Krawczyk

  • Abap proxy client  and https webservice

    Hi, I have a problem with an abap proxy client.
    This proxy works perfectyl when I call the test webservice (via HTTP protocol) but it does not work if I try to call the productive webservice (via HTTPS protocol).  Of course I have configured LPCONFIG in order to let the proxy point to the correct web site.
    I'm pretty sure that problkem is caused by different protocols HTTP vs HTTPS.
    I thought the problem could be the web site certificate, so I added it into the PSE (transaction STRUST) but nothing happnes.
    Your help is really appreciated.
    Edited by: robcom69 on Feb 22, 2010 3:34 PM
    Edited by: robcom69 on Feb 22, 2010 3:35 PM
    Edited by: robcom69 on Feb 22, 2010 3:49 PM

    I have loaded the certificate in the TRUST transaction.
    Anyway, in our system we do not have the SAPCRIPTOLIB libraries and I do not underastand if they are necessary or not.
    I mean, I need these libraries only if I expose an HTTPS server from SAP or even if SAP is the client and it need to access an external https webservice ?
    Please help.

Maybe you are looking for