Client proxy data not reaching XI ?

Hi Guys,
I have a scenario proxy-soap asynchronus. when i execute the report on the R/3 side the report executes successfully and in the sxmb_moni receiver which is IE of xi is not identified and the data is not reaching XI.
But when i execute the report on the same R/3 system for an synchronus proxy-soap scenario the data reaches xi and everyhting is fine. so i think there is no problem with the proxy setings.
Why the EO asynchronus messages are not identifying the receiver which is IE ?
any help would be really appreciated
Thanks,
Raj

did u check moni in r3 side?

Similar Messages

  • Client proxy message not reaching to XI system

    Hi
    I have done one scenario from CRM to FILE. When i am executing the client proxy through my zprogram its executing without any errors. I have checked in SXMB_MONI of CRD system i can see the messages but they are not with successful flag or not with error flag. But in XI system (SXMB_MONI) i didnt find any messages. Could you please tell me what's the problem is?
    Regards
    Sowmya

    Sowmya,
    As you are not getting any message in SXMB_MONI, there can be following possibilities:
    1. There can be some problem in proxy configuration on your CRM system. Please check with your BASIS team that steps give in this blog are properly followed:
    How do you activate ABAP Proxies? 
    2. Make sure that in
    SXMB_ADM     --->integration engine config -
    >change specific attributes....
    The RUNTIME parameter is defined LOGGING and TRACE_LEVEL and the value is 1.
    3. Make sure the queues are registered in Tx: SMQR.
    Further, I do not think that COMMIT statement or anything like that is missing as in that case you should have got a message in SXMB_MONI with a green flag stating that "Commit statement is missing".

  • ABAP Client proxy message not reaching AAE

    Hi Experts,
    I am facing a strange issue in one of my proxy interfaces. ABAP client Proxy is used to post message to AAE in SAP PI 7.3. The messages are being generated and pushed out of ECC successfully. I can see them in the SXMB_MONI t-code with checkered flag. These messages are reaching the Integartion Engine instaed of the Adapter Engine.
    I have configured the following:
    1. Sender / Receiver ID  in SXMSIF:
    2. Configured the corresponding Runtime parameter in SXMB_ADM
    I have few other such ABAp client proxy i/f's which work fine and their message are being sent to the Adapter engine. Howveere, only this one interface is posing a problem. What can be the issue?
    Please advice.
    Thanks in advance.
    Elizabeth.

    Hi Elizabeth,
    It will be great if you could please let me know all the user profile configured in userID of Logon&Security tab of SM59 for connecting ECC system to post the message via AAE.
    I have used
    SAP_XI_APPL_SERV_USER
    SAP_XI_DEVELOPER_J2EE and
    SAP_XI_IS_SERV_USER
    profiles in my UserID for Basic authentication.
    Currently I am doing the same scenario what you have done with integrated configuration.The message is getting failed in ECC with 403 Forbidden error.
    Please help me.
    Thanks
    Ray...

  • How to find the error when client proxy is not successfully triggered?

    Hi all,
    I want to consume a .NET service in SAP.
    But when I want to test the client proxy the following error occur:
    GENERAL_ERROR Error duing proxy processing (PART
    UNKNOWN (NULL) )
    Transaction ST11:
    TRACE SOAP RUNTIME - trace records                                                                               
    E CONTEXT 20090518061404.5255720 : CL_SOAP_CONTEXT ->SET_FAULT   
    SOAP runtime fault handling                                                                               
    E SOAP_RUNTIME 20090518061404.5256990 : CL_SOAP_RUNTIME_CLIENT   
    ->EXEC_PROCESSING Exception handling in SOAP runtime                                                                               
    E CONTEXT 20090518061404.5255620 : CL_SOAP_CONTEXT ->SET_FAULT set
    fault loop detected                                                                               
    E SOAP_RUNTIME 20090518061404.5256920 : CL_SOAP_RUNTIME_CLIENT                                   
    .NullPointerException:                                           
    Transaction SM21:
    SOAP Runtime Protocol: SOAP Fault exception occurred in program CL_SOAP_RUNTIME_ROOT==========CP in include CL_SOAP_RU NTIME_ROOT==========CM004 at position 80
    SOAP Runtime Protocol: Exception message: Severe processing error; SOAP fault handling required
    How can I find what's wrong????
    This error logging is not really helpful to me...
    Any ideas?
    regards

    Hello Mr. Bauer,
    Will you please elaborate on your solution to fix this issue?
    We are facing this issue too.
    Thanks in advance.
    Regards,
    Victor

  • VPN Client: proxy identities not supported

    Phase 1 is complete since I see this message in the debug output:
    *Jan 17 19:41:04.618: ISAKMP:(2029):Input = IKE_MESG_INTERNAL, IKE_PHASE1_COMPLETE
    The checking of the IPSec proposal fails because of "proxy identities not supported":
    =[ BEGIN debug output ]====================================================================
    *Jan 17 19:41:04.634: ISAKMP:(2029):Checking IPSec proposal 4
    *Jan 17 19:41:04.634: ISAKMP: transform 1, ESP_AES
    *Jan 17 19:41:04.634: ISAKMP: attributes in transform:
    *Jan 17 19:41:04.634: ISAKMP: authenticator is HMAC-SHA
    *Jan 17 19:41:04.634: ISAKMP: key length is 128
    *Jan 17 19:41:04.634: ISAKMP: encaps is 1 (Tunnel)
    *Jan 17 19:41:04.634: ISAKMP: SA life type in seconds
    *Jan 17 19:41:04.634: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B
    *Jan 17 19:41:04.634: ISAKMP:(2029):atts are acceptable.
    *Jan 17 19:41:04.634: ISAKMP:(2029):Checking IPSec proposal 4
    *Jan 17 19:41:04.634: ISAKMP:(2029):transform 1, IPPCP LZS
    *Jan 17 19:41:04.634: ISAKMP: attributes in transform:
    *Jan 17 19:41:04.634: ISAKMP: encaps is 1 (Tunnel)
    *Jan 17 19:41:04.634: ISAKMP: SA life type in seconds
    *Jan 17 19:41:04.634: ISAKMP: SA life duration (VPI) of 0x0 0x20 0xC4 0x9B
    *Jan 17 19:41:04.634: ISAKMP:(2029):atts are acceptable.
    *Jan 17 19:41:04.634: IPSEC(validate_proposal_request): proposal part #1
    *Jan 17 19:41:04.634: IPSEC(validate_proposal_request): proposal part #1,
    (key eng. msg.) INBOUND local= 200.40.164.178, remote= 200.40.164.177,
    local_proxy= 0.0.0.0/0.0.0.0/0/0 (type=4),
    remote_proxy= 192.168.101.22/255.255.255.255/0/0 (type=1),
    protocol= ESP, transform= esp-aes esp-sha-hmac (Tunnel),
    lifedur= 0s and 0kb,
    spi= 0x0(0), conn_id= 0, keysize= 128, flags= 0x0
    *Jan 17 19:41:04.634: IPSEC(validate_proposal_request): proposal part #2
    *Jan 17 19:41:04.638: IPSEC(validate_proposal_request): proposal part #2,
    (key eng. msg.) INBOUND local= 200.40.164.178, remote= 200.40.164.177,
    local_proxy= 0.0.0.0/0.0.0.0/0/0 (type=4),
    remote_proxy= 192.168.101.22/255.255.255.255/0/0 (type=1),
    protocol= PCP, transform= comp-lzs (Tunnel),
    lifedur= 0s and 0kb,
    spi= 0x0(0), conn_id= 0, keysize= 0, flags= 0x0
    *Jan 17 19:41:04.638: IPSEC(crypto_ipsec_process_proposal): proxy identities not supported
    *Jan 17 19:41:04.638: ISAKMP:(2029): IPSec policy invalidated proposal with error 32
    =[ END debug output ]======================================================================
    I see that "local_proxy= 0.0.0.0/0.0.0.0/0/0", but it should have the IP address of the router internal interface.

    Well, finally a coleague found the cause of the problem: I had added a "match address" command to the "crypto dynamic-map" for the RemoteAccess VPN.
    The "match address" command must be used only with VPN L2L.

  • Weblogic 8.1 Webservice Client Proxy Authentication not working

    We have a desktop console based Weblogic webservices client application that uses client stubs to establish the connection and communicate with the server where the WSDL was hosted.
    We are facing a problem in authenticating the Proxy user with valid credentials.
    We are using the following code to set the system properties and Authenticator class to authenticate the proxy user.
    //Code Segment #1
    Code:
    System.setProperty("http.proxyHost", proxyHost);System.setProperty("https.proxyHost", proxyHost);
    System.setProperty("weblogic.webservice.transport.http.proxy.host",proxyHost);
    System.setProperty("weblogic.webservice.transport.https.proxy.host",proxyHost);
    System.setProperty("http.proxyPort", proxyPort);
    System.setProperty("https.proxyPort", proxyPort);
    System.setProperty("weblogic.webservice.transport.http.proxy.port",proxyPort);
    System.setProperty("weblogic.webservice.transport.https.proxy.port",proxyPort);
    //System.setProperty("http.proxyType", "basic");
    //System.setProperty("https.proxyType", "basic");
    //System.setProperty("http.proxy.auth.type" ,"ntlm"); //This is not showing any impact
    System.setProperty("http.proxyUser", "bsil\\ashok.kumar");
    System.setProperty("https.proxyUser", "bsil\\ashok.kumar");
    System.setProperty("http.proxyPassword", " xyzddd");
    System.setProperty("https.proxyPassword", "xyzddd");
    Authenticator.setDefault(new MyAuthenticator());
    //Inner class
    public static class MyAuthenticator extends Authenticator {
    protected PasswordAuthentication getPasswordAuthentication() {
    String username = System.getProperty("http.proxyUser");
         String password = System.getProperty("http.proxyPassword");
         return new PasswordAuthentication(username, password.toCharArray());
    We are using following code initialize the stubs (Which internally opens a connection to the given endpoint base URL)
    //Code Segment #2
    Code:
    SessionService_Impl sessionService = new SessionService_Impl(getEndPointURL(SessionServicePort.class));
    port = sessionService.getSessionServicePort();
    return port;
    Using above code it always throws the following exception:
    Code:
    weblogic.webservice.tools.wsdlp.WSDLParseException: Failed to retrieve WSDL from https://apiclienttest.intralinks.com:443/webservices51/SessionService?WSDL. Please check the URL and make sure that it is a valid XML file [java.io.IOException: Proxy authenticator  failed: java.lang.ClassNotFoundException: ]
    if i replace the above code (Code Segment #2) to as bellow with Code Segment #3 then its working as expected. But we have been told that the Code Segment #2 is required as shwon above for the Weblogic ClientTimeout seconds feature so we cant replace the Code Segment #2 with Code Segment #3 since we don?t want to miss the ClientTimeout seconds feature for the application.
    //Code Segment #3
    Code:
    SessionService_Impl sessionService = new SessionService_Impl();
              SessionServicePort sessionServicePort = sessionService.getSessionServicePort();
              ((SessionServicePort_Stub) sessionServicePort)._setProperty("javax.xml.rpc.service.endpoint.address", endPointBaseURL+"SessionService");
    return sessionServicePort ;
    why the Proxy authentication is failing with the Code Segment #2 and why it is passing in case of Code Segment #3
    The endpoint base URL we are hitting is hosted on Weblogic server 9.0 (which is hosted at client side in US so it is behind our firewall).
    Is some thing more do we need to do in Authenticator class???
    Please help me if any one has worked on proxy server authenticator in java.

    We have a desktop console based Weblogic webservices client application that uses client stubs to establish the connection and communicate with the server where the WSDL was hosted.
    We are facing a problem in authenticating the Proxy user with valid credentials.
    We are using the following code to set the system properties and Authenticator class to authenticate the proxy user.
    //Code Segment #1
    Code:
    System.setProperty("http.proxyHost", proxyHost);System.setProperty("https.proxyHost", proxyHost);
    System.setProperty("weblogic.webservice.transport.http.proxy.host",proxyHost);
    System.setProperty("weblogic.webservice.transport.https.proxy.host",proxyHost);
    System.setProperty("http.proxyPort", proxyPort);
    System.setProperty("https.proxyPort", proxyPort);
    System.setProperty("weblogic.webservice.transport.http.proxy.port",proxyPort);
    System.setProperty("weblogic.webservice.transport.https.proxy.port",proxyPort);
    //System.setProperty("http.proxyType", "basic");
    //System.setProperty("https.proxyType", "basic");
    //System.setProperty("http.proxy.auth.type" ,"ntlm"); //This is not showing any impact
    System.setProperty("http.proxyUser", "bsil\\ashok.kumar");
    System.setProperty("https.proxyUser", "bsil\\ashok.kumar");
    System.setProperty("http.proxyPassword", " xyzddd");
    System.setProperty("https.proxyPassword", "xyzddd");
    Authenticator.setDefault(new MyAuthenticator());
    //Inner class
    public static class MyAuthenticator extends Authenticator {
    protected PasswordAuthentication getPasswordAuthentication() {
    String username = System.getProperty("http.proxyUser");
         String password = System.getProperty("http.proxyPassword");
         return new PasswordAuthentication(username, password.toCharArray());
    We are using following code initialize the stubs (Which internally opens a connection to the given endpoint base URL)
    //Code Segment #2
    Code:
    SessionService_Impl sessionService = new SessionService_Impl(getEndPointURL(SessionServicePort.class));
    port = sessionService.getSessionServicePort();
    return port;
    Using above code it always throws the following exception:
    Code:
    weblogic.webservice.tools.wsdlp.WSDLParseException: Failed to retrieve WSDL from https://apiclienttest.intralinks.com:443/webservices51/SessionService?WSDL. Please check the URL and make sure that it is a valid XML file [java.io.IOException: Proxy authenticator  failed: java.lang.ClassNotFoundException: ]
    if i replace the above code (Code Segment #2) to as bellow with Code Segment #3 then its working as expected. But we have been told that the Code Segment #2 is required as shwon above for the Weblogic ClientTimeout seconds feature so we cant replace the Code Segment #2 with Code Segment #3 since we don?t want to miss the ClientTimeout seconds feature for the application.
    //Code Segment #3
    Code:
    SessionService_Impl sessionService = new SessionService_Impl();
              SessionServicePort sessionServicePort = sessionService.getSessionServicePort();
              ((SessionServicePort_Stub) sessionServicePort)._setProperty("javax.xml.rpc.service.endpoint.address", endPointBaseURL+"SessionService");
    return sessionServicePort ;
    why the Proxy authentication is failing with the Code Segment #2 and why it is passing in case of Code Segment #3
    The endpoint base URL we are hitting is hosted on Weblogic server 9.0 (which is hosted at client side in US so it is behind our firewall).
    Is some thing more do we need to do in Authenticator class???
    Please help me if any one has worked on proxy server authenticator in java.

  • Data not reaching SOA from B2B

    Hi All,
    i have configured a generic file listening channel. B2B is picking up the file succesfully and it is also getting processed succesfully without any error
    But data is not getting read by the B2b adapter(configured in default mode) which i have configured in SOA layer neither i can see in the queue(IP_IN_Queue). if i undeploy the soa process then i am able to see the data in IP_IN_Queue.
    Strangely, if instead of generic file channel, if i configure my trading partner to listen the data using MLLP over TCP. then data is getting read by SOA layer.
    Now i have a couple of questions:
    1. In B2b 11g, we have 4 queues, IP_IN_Queue, IP_OUT_Queue , B2B_IN_Queue, B2B_OUT_Queue. Now which of these are used by B2b to pass data to soa in default configuration.
    2. Why in case of generic file listeing channel my SOA composite is not receiving the data from B2B.
    Regards,
    Saurav Singla

    Hi Anuj,
    I have checked the application message. Application message does not have any detail about the composite instance or any location where its dumping the data.
    In diagnostic logs i can find the following error.
    [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@466f92] [userId: <anonymous>] [ecid: 74f716a25b8ba015:-4fb641d9:130ae246230:-8000-00000000000043a5,0] [APP: soa-infra] Error -: B2B-50029: B2B runtime error: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.[[
         at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToFabric(MessageHandler.java:1588)
         at oracle.tip.b2b.msgproc.MessageHandler.doDeliverMessageToDestination(MessageHandler.java:629)
         at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:246)
         at oracle.tip.b2b.msgproc.Request.putMsg(Request.java:690)
         at oracle.tip.b2b.msgproc.Request.continueRequest(Request.java:500)
         at oracle.tip.b2b.msgproc.Request.incomingRequest(Request.java:421)
         at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2819)
         at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1660)
         at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4047)
         at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3687)
         at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3160)
         at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
         at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
         at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
         at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
         at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
         at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1664)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1555)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1487)
         at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1328)
         at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:376)
         at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:322)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
         at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:155)
         at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:130)
         at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:146)
         at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToFabric(MessageHandler.java:1190)
         ... 15 more
    oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
         at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1664)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1555)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1487)
         at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1328)
         at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:376)
         at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:322)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
         at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:155)
         at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:130)
         at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:146)
         at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToFabric(MessageHandler.java:1190)
         at oracle.tip.b2b.msgproc.MessageHandler.doDeliverMessageToDestination(MessageHandler.java:629)
         at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:246)
         at oracle.tip.b2b.msgproc.Request.putMsg(Request.java:690)
         at oracle.tip.b2b.msgproc.Request.continueRequest(Request.java:500)
         at oracle.tip.b2b.msgproc.Request.incomingRequest(Request.java:421)
         at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2819)
         at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1660)
         at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4047)
         at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3687)
         at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3160)
         at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
         at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
         at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
         at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
         at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Error -: B2B-50029: B2B runtime error: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
         at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToFabric(MessageHandler.java:1588)
         at oracle.tip.b2b.msgproc.MessageHandler.doDeliverMessageToDestination(MessageHandler.java:629)
         at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:246)
         at oracle.tip.b2b.msgproc.Request.putMsg(Request.java:690)
         at oracle.tip.b2b.msgproc.Request.continueRequest(Request.java:500)
         at oracle.tip.b2b.msgproc.Request.incomingRequest(Request.java:421)
         at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2819)
         at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1660)
         at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:4047)
         at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3687)
         at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3160)
         at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:619)
         at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:220)
         at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
         at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
         at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute.
         at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1664)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1555)
         at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1487)
         at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1328)
         at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:376)
         at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:322)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
         at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:155)
         at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:130)
         at oracle.tip.b2b.utility.XMLUtil.parseDocument(XMLUtil.java:146)
         at oracle.tip.b2b.msgproc.MessageHandler.deliverMessageToFabric(MessageHandler.java:1190)
         ... 15 more
    It looks like dat errro is coming while delivering message to fabric.
    But i have no idea why this error is coming because with the same configuration and ecs files, when i am sending the data through MLLP, its working perfectly fine.

  • Async Client proxy -PI - File scenario- Pipeline steps missing in SXMB_MONI

    Hi
    I made a scenario where an ABAP client proxy(in a BW system) pulls data from a BW table and push it to PI.
    In PI a Mapping is done to write an XML file and sump it to a desired location.
    It is working fine in the development environment(request send to PI and mapped into an xml file)..so i migrated it to the quality/test environment where it started failing(It is only visible till SXMB_MONI of Client system and not reaching PI in case of quality/test environment).
    I checked SLDCHECK in the Client environments (say DWC for development and DWA for quality) and it looks fine.
    All I could see is:
    In SXMB_MONI of development system DWC--> Steps that are followed are
    Inbound Message
    Call Integration Server
    Response
    In SXMB_MONI of quality/test system DWA-->The only step is
    Inbound Message
    Could this be an Integration Server issue ??
    Please advise !!
    Regards,
    Naina

    check and compare the the parameter are set in SXMB_ADM of Dev system with Quality system.
    u can refer this blog for steps.
    /people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
    chirag

  • Unknown Namespace when creating Client Proxy

    Hi,
    I'm trying to generate a client proxy using Local File.
    It gives error
    Incorrect value: Unknown Namespace urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2
    The wsdl file does not give any error.
    This error seems to be coming from XSD file  named UBL-CommonAggregateComponents-2.0.xsd
    Below is part of this XSD file.
    Can you tell me what is the problem here.
    <!-- ===== xsd:schema Element With Namespaces Declarations ===== --><xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
                xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
                xmlns:udt="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2"
                xmlns:ccts="urn:un:unece:uncefact:documentation:2"
                xmlns:qdt="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2"
                targetNamespace="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
                elementFormDefault="qualified"
                attributeFormDefault="unqualified"
                version="2.0"><!-- ===== Imports ===== --><xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
                   schemaLocation="UBL-CommonBasicComponents-2.0.xsd"/>
       <xsd:import namespace="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2"
                   schemaLocation="UnqualifiedDataTypeSchemaModule-2.0.xsd"/>
       <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2"
                   schemaLocation="UBL-QualifiedDatatypes-2.0.xsd"/>
    Thanks
    Girishkumar

    Hi ,
    Make sure no restriction from firewall on proxy settings.
    Namespace you are using for client proxy may not be available for consumption/not published.
    Also , Try to check connection.
    OSS note 944029 will give you SAP restrictions on name space.
    Regards
    Nagaraju

  • Error setting up new client proxy, unknown namespace

    Hi all.
    I am trying to setup a new client proxy, with SE80.
    I am using an WSDL file.
    Somehow I get the following error.
    Proxy-Generierung: Fehler aufgetreten
    Exception occurred in library handler
    Incorrect value: Unknown Namespace http://www.mynamespace.com/param
    Anyone have any ideas why? Does namespace need to contain specific values?
    Thanks!

    Hi,
    The namespace you are using for creating client proxy might not be available for consumption(i.e. it might not be published) or there is no connectivity to the source system so namespace is not available.
    Try checking connection.
    Hoping it helps..
    Regards,
    Komal
    Edited by: Komal Lakhwani on Feb 8, 2010 4:31 PM

  • Data passed from ABAP proxy not reaching PI...

    Hi,
    My scenario is
    ECC ABAP Proxy --> PI --> legacy
    In dev box, it is working fine, when data is sent from ECC dev, it reaches PI dev.
    But when data is sent from ECC quality, data is not reaching PI quality.
    This set up has already been in production and working fine.
    I have done some minor mapping changes only in ESR and moved to PI quality. Nothing changed in the Integration builder side.
    But a client copy was done from ECC prod to ECC quality (not PI systems). Will this have any impact on proxy ?
    What can I check to make sure everything is in place ?
    Pl advise.
    thnks

    Hi,
    In SLDAPICUST the SLD server host and port will be maintained. The ECC will use this to connec to SLD at runtime and get the business sytem details. This can be checked via transaction SLDCHECK.
    Also what the transaction SPROXY says in the ECC system. Is it connecting your PI system and loading the ESR information?
    There are a few more configuration that needs to be checked in ECC system for proxy communication, I think this blog can help you.
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    regards,
    francis

  • ABAP Client Proxy to File (File is not getting generated)

    Hi All,
    I'm trying out a scenario ABAP proxy --> XI  --> FILE.
    I have followed the given blog to create ABAP client proxy.
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    While executing the ABAP client proxy, the values are properly sent to XI and in the SXMB_MONI the message shows as successful. But the correspoding file is not created.
    It seems everything is fine in the receiver adpater(Monitoring) and in the SXMB_MONI also the msg shows successful(receiver side).
    The directory path and the corresping file creation parameters also looks fine.
    Couldn't figure out what went wrong. Please help me on this.
    Thanks,
    Ajay.

    Hi Smitha,
        Please find below the Call Adapter trace
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <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 =</Trace>
      <Trace level="1" type="T">Sender agency external =</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 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.0</Trace>
      <Trace level="2" type="T">Host = iscsapapp4w:8010</Trace>
      <Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
      <Trace level="2" type="T">Remote address = 10.191.117.166</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <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 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 = NW2</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z 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 level="1" type="T">Message-GUID = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">QOS = EO</Trace>
      <Trace level="3" type="T">Message-GUID = B2DD6D78BBF141458DDC0DDE39782DE3</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">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">Generate prefixed queue name</Trace>
      <Trace level="1" type="T">Queue name : XBTI0000</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0000</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="3" type="T">Setup qRFC Scheduler</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="3" type="T">Call qRFC .... MsgGuid = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
      <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
      <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
      <Trace level="3" type="T">OK.</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</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="3" type="T">Version number = 000</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 001</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <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="3" type="T">message version successfully read from persist version= 000</Trace>
      <Trace level="2" type="T">Increment log sequence to 001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = NW2</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</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 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 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 level="3" type="T" />
      <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 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 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 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 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 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 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 level="3" type="T" />
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z 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 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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <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="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - ACN_LEGACY2_04_BS</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 001</Trace>
      <Trace level="3" type="T">Message version 001</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_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_ID_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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - 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">Check conditions for (Inb: Party Srvc If) ACN_LEGACY2_04_BS MI_Client_Proxy_Inbound</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: MI_Client_Proxy_Inbound</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="2" type="T">got property produced by receiver determination</Trace>
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTOM2__0001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <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">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="3" type="T">Persisting message Status = 012</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <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="3" type="T">message version successfully read from persist version= 004</Trace>
      <Trace level="2" type="T">Increment log sequence to 005</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = NW2</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</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 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 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 level="3" type="T" />
      <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 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 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 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 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 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 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 level="3" type="T" />
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
      <Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="2" type="T">......attachment XI_Context not found</Trace>
      <Trace level="3" type="T">Mapping is already determined in the interface determination</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping 791955998E03380CA938A0130A348AFB</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping 3475AE80930811DAA18DC14C0ABF75A6</Trace>
      <Trace level="1" type="T">Interface Mapping http://accenture.com/xi101/ABAPclientProxy IM_Valuemapping</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_Valuemapping_</Trace>
      <Trace level="3" type="T">Dynamic configuration is empty</Trace>
      <Trace level="2" type="T">Mode 0</Trace>
      <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_Valuemapping_.</Trace>
      <Trace level="3" type="T">Load 3475ae80-9308-11da-a18d-c14c0abf75a6, http://accenture.com/xi101/ABAPclientProxy, -1, com/sap/xi/tf/_MM_Valuemapping_.class.</Trace>
      <Trace level="3" type="T">Search com/sap/xi/tf/_MM_Valuemapping_.class (http://accenture.com/xi101/ABAPclientProxy, -1) in swcv 3475ae80-9308-11da-a18d-c14c0abf75a6.</Trace>
      <Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_Valuemapping_</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_Valuemapping_</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_Valuemapping_ completed. (executeStep() of com.sap.xi.tf._MM_Valuemapping_</Trace>
      <Trace level="3" type="T">Dynamic configuration is empty</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 005</Trace>
      <Trace level="3" type="T">Message version 005</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
      <Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
      <Trace level="2" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
      <Trace level="2" type="T">-ACN_Sender_BS_XI</Trace>
      <Trace level="2" type="T">-ACN_LEGACY2_04_BS</Trace>
      <Trace level="2" type="T">http://accenture.com/xi101/ABAPclientProxy.MI_Client_Proxy_Inbound</Trace>
      <Trace level="2" type="T">Channel found: - ACN_LEGACY2_04_BS - ValueMap_Repl_Receiver1</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 006</Trace>
      <Trace level="3" type="T">Message version 006</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
      <Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS =</Trace>
      <Trace level="3" type="T">P_IFNAME =</Trace>
      <Trace level="3" type="T">P_METHOD =</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Unknown channel type: File</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
      <Trace level="3" type="T">Channel for adapter engine: File</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="2" type="T">return fresh values from cache</Trace>
      <Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET): af.nw2.iscsapapp4w</Trace>
      <Trace level="3" type="T">URL = http://iscsapapp4w.idcsap.com:51000/MessagingSystem/receive/AFW/XI</Trace>
      <Trace level="3" type="T">User = XIISUSER</Trace>
      <Trace level="3" type="T">Cached = X</Trace>
      <Trace level="3" type="T">Creating HTTP-client</Trace>
      <Trace level="3" type="T">HTTP-client: creation finished</Trace>
      <Trace level="3" type="T">Security: Basic authentication</Trace>
      <Trace level="3" type="T">Serializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
      <Trace level="3" type="T">HTTP-client: request sent</Trace>
      <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
      <Trace level="3" type="T">HTTP-client: response received</Trace>
      <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
      <Trace level="3" type="T">HTTP-client: status code = 200</Trace>
      <Trace level="3" type="T">Deserializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: closing...</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2006-04-03T10:24:19Z CET End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 007</Trace>
      <Trace level="3" type="T">Message version 007</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>
    Thanks,
    Jothivel.

  • Data stuck in QRFC in client proxy scenario

    In client proxy scenario (proxy to file async). I triggered the report porgram from ECC and I the green flag moni in ECC but the mesage is did nto reach PI as it got stuck in qrfc. It reaches PI upon clearing the message from SMQ2. Please help solve this.

    this problem persists when queues are not registered or any abapstack workitem gets into error.
    select the workitem in smq2. execute it manually. after completing the execution, goto sxmb_adm tcode, there select manage queues. then register queues.

  • Some dhcp clients not reaching internet

    This afternoon, I noticed that my iPhone was no longer reaching the internet. Later, we noticed my husband's (new!) iPad and my son's MacBook were not reaching the internet either. At least my MacBook was still reaching the internet. In all cases, the connectivity with the airport was fine; 4-5 bars, most of the time. All were connected yesterday, I believe. We made no real changes. I had my iPhone right next to my MacBook and both had good connections to the wifi, but only the MacBook was reaching the Internet.
    I went into Airport Utility and looked at the Time Capsule and found a long list under DHCP clients (maybe 9), but only 4 on the wireless clients list. I researched the issue, finding very little except generic suggestions (update software and reset the Time Capsule). The software was up to date; resetting it did fix the problem, at least for now. I am concerned it will happen again.
    Our airport devices:
    - Time Capsule running 7.5.2
    - 2 Airport Expresses, also running 7.5.2.
    Most, if not all, our wifi devices are up to date, including my MacBook running 10.6.5 and my iPhone running 4.2.1.

    I'm not sure this is quite the same since simply restarting our Time Capsule fixed things for us. It is annoying since I don't want to have to restart the Time Capsule every week or so when it fails this way, but restarted did fix this, at least temporarily.
    Another possibility I came across is that an ISP might limit the number of devices you can connect to the Time Capsule, but that wasn't the case for us. I'm thinking the Apple person you talked to probably checked on this, though.
    Hope you can figure it out!
    - Liz, aka liz4cps

  • Abap client proxy to xi - no data found

    Hi experts
    I m working on abap client  proxy to file scenario where in I m sending data from R/3 system to legacy system via xi , but after doing all the configurations and running the abap program for triggering client proxy , i dont find any data on the receiver side ,
    I have activated client proxy as per Vijay Kumaris Blog
    I checked sxmb_moni on the R/3 system but shows no data selected , so no question of data being found on xi server ,
    i m really sutcked up ....dont know hwat to do , pl help
    rgds
    mojib

    Hi,
    Have u used commit work at the end of the code.
    Can you please tell me what all configuration u have done.
    U have referred the ABAP Proxy configuration:
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    Refer the below log for Client Proxy -
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    Chirag

Maybe you are looking for

  • Mass role risk analysis issue

    Hello GRC Community, I have a following issue: When I use mass risk analysis the deactivated authorization objects in the role are displayed as result. At the same time, when I use Role Level Risk Analysis the role with deactivated critical authoriza

  • I am trying to delete a file that will not let me

    Ok , so I use to a Seagate Backup Plus Portable Driver 1T to hold and run certain games on mac. I am trying to remove something from my TRASH can , in which in wont budge. - I try to EMPTY trash , makes the trash empired noise, but is still there and

  • BT INFINITY BEING MISSOLD

    BT PROBLEMS COMPLAINT NO VOL012-*********** I am in the throes of a number of problems concerning my ‘contracts’ with BT I shall try to be brief and to the point but there are numerous problems, all of BTs making. On Saturday August 19 at approx. 9am

  • Problem in Database EXPDP and IMPDP

    Dear Friends I am using Oracle 11G R2 (11.2.0.1.0) on Windows 7 Ultimate. I have some 50 tables (along with its data) and corresponding 40 VIEWS (based on those 50 tablees) in User "SYSTEM" schema. I want to take Export DUMP file of these 50 tables a

  • Is it possible to set my computer to chime whenever I visit a specific URL?

    I was wondering if it were possible for a browser to alert the user when a tab visited to a specific URL, through a sound or chime. Press the home button, sent to google. When google loads, *chime*