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".

Similar Messages

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...

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?

Message Not coming to XI system

Hello,
Am Facing an issue in Production XI system. The issue is in File to RFC Interface,which is running on Daily basis,there is a daily job to Place the File on FTP server. The Problem is File is Picking by XI and File also archived in Archive directory,but Message not coming to XI system.I have checked in MONI and Sender communication channel,but not able to see any messages.The File Format is CSV,used FCC in sender channel.
Kindly help me to solve this problem,
Thanks,
Madhu

Hi Madhu
Please check the communication channel in RWB and see the channel is in error or not.
The channel should show some logs including message id.
Next check the RWB-->message monitoring-->adapter engine
The message could have failed there and hence does not present in MONI.
Finally make sure that none of other communication channels are polling in that same server.
In non-prod environment we some times use the same server credential for DEV and QA.
So if that is the case , then please deactivate the other channel so that you get the message in desired environment.

Proxy messages not processed in PI 7.1 pipeline coming from local client

Dear experts,
We have recently installed a PI7.1 system with two clients:
200 - Integration Server
250 - Local Integration Engine
Now, when we send proxy messages from the 250 client to the 200 client,
the messages are not processed in the integration server. The message
does arrive as we can see in SXMB_MONI, but there is no receiver determination
or what-so-ever executed. In SXMB_MONI we can see that only the SENDER
pipeline is executed.
Proxy messages from 6.20 and 7.0 systems to IS are properly processed.
Ofcourse the 250 client is defined as an application system in the integation engine
configuration (SXMB_ADM).
regards,
Jeroen

In SXMB_MONI we can see that only the SENDER pipeline is executed.
Yes. Even if no receivers are configured the data from sender to XI should be visible in sxmb_moni.
Check smq1 at XI. There could be some problem with the technical system for client 250.
Regards,
Prateek

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

Client proxy message strucked in ECC queues

Hi All,
I am working on Proxy interface. My interface is like below
ECC 6----
>PI (7.1) -
>File
I had done the entire configuration in ECC and PI for proxy activation. While testing the interface in ECC system messages processed successfully, but the message strucked in queues (SMQ2) in ECC system. If run the queue manually the message processed successfully to the PI.
Can you please tell any more configurations required?
Regards,
Ramesh

Hi,
The queue used for Proxy call is not registerd in ECC system. You need to register the queue to process successfully.
you will get the name of Queue from SMQ2 t-code and register it with t-code SMQR.
Thanks
Swarup
Edited by: Swarup Sawant on Aug 24, 2009 8:03 AM

Client Proxy - Message waiting in queue

Hi all,
I have a client proxy in R3 that sends information to XI. I see in XSMB_MONI a green flag, but in the field "status queue" appears a yellow triangle with the message "Message waiting in queue".
In Runtime Workbench I don't see any message.
Any help? I have to activate the queue?
Regards,

Hi,
Have u registered the queue in R3? If not....
1.Go to SXMB_ADM(R/3)
2. Go to Manage Queues and then
3. Register All Queues.
<a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically Failed Messages</a>
Regards
San

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.

FTP Sender - Message not reaching XI

Hi,
I am using FTP sender adapter to send an XML file to XI.
The file is being picked up by XI properly from the Source directory on the FTP server which is running on my local machine but it is not reaching the integration server. SXMB_MONI shows no message.
I have checked all the parameters in the communication channel and am sure that the fule is picked up. Alternatively, I am able to put a file on the FTP server. So the FTP server seems to be working fine.
If any of you have any idea of where the error could lie, could you please respond.
Kind Regards,
Dhananjay

Hi Dhananjay,
try setting the file adapter to Delete mode
this way you'll know if your file got picked from the FTP
if you're sure that is was picked then:
http://xiserver:port/MessagingSystem/monitor/monitor.jsp
here you'll find your message if it reached Adapter Framework (file/ftp adapter)
also remember to always check this address:
http://xiserver:port/mdt/amtServlet
Regards,
michal

Sent messages not reaching destination

Mail sent through .mac account does not reach destination, but everything looks completely normal. Messages sent using mail but from another mail account reach their destinations just fine. I still have tons of space on my .mac mail account and absolutely no error messages are appearing. Most grateful if anyone has a clue about what's going on.
Thanks, SP

hi jim, thanks for the reply.
yes, i tried sending mail to myself, also at a yahoo acct... it seems to be sent (doesn't bounce) but never reaches destination. The only way i can make it work is not to use mac.com as my outgoing server (i have to use the server of my local provider) and not to activate ssl sockets in mail preferences... naturally no pw check etc.
the annoying thing is that Mail doesn't tell me when it's not working, it saves the messages as sent but doesn't deliver them.
any ideas?
thanks again, sp

Message not reaching to XI

Hello ,
I have configured a scenario Http ->XI->Idoc.
when I test this scenario using runtime workbench test tool,it gives me message sent , but message is not available in SXMB_moni.
message is not struck in SMQ2.
Pl can you suggest on this.
thanks,
Sharada

Hello Matias,Udo,Prateek,
Letter case are correct.
This is the url of Intergration Engine used for testing.
http://WCSPIDEV1:8051/sap/xi/engine?type=entry
There cannot be entry at SM58 as message is not reaching to IE from http request.
Pl can you suugest.
thanks,
Sharada

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.

HTTP receiver adapter : message not reaching partner

Hi,
Scenario: IDOC -> PI7.0 -> HTTP
Idoc has to be routed after mapping to XML message to partner via HTTP post.
Partner says, he has not received any message from PI.I can see successful status in SXMB_MONI. As HTTP adapter is not part of adapter framework, so I can not see message under Adapter engine in RWB, Right?
Outbound message has DTD reference, is this should cause any problems?
One more thing, under sxmb_moni, under trace I can see message
"HTTP code:200, Ok".
How can I ensure that PI has sent successfully message to partner.
Please note that for HTTP adapter configuration: I have created HTTP destination on XI system with URL, service number and path prefix. It is successful.
Best Regards,
Divyesh

For the already executed scenario, there is nothing much you can do now. sxmb_moni is the last point for monitoring the http related call. For the traces you may check transaction sicf
http://help.sap.com/saphelp_nw04/Helpdata/EN/80/b2dd3a6dac703be10000000a11405a/content.htm
You may use TCPGateway to trace further calls.
/people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway
Regards,
Prateek

Message not coming to Receiver system - File to RFC

I have a small problem in File to RFC connection. We are trying to create a PO using a BAPI. In the XI system , it shows the XML is processed successfully but PO is not generated in the R/3 system.
Is there any way to check whether the message has come to the receiver system. In fact we tried with a dummy insert command in a Z table . Even thats not happening. I thing the message is not at all coming to the receiver system, but the SXMB_MONI in Xi shows the message got processed successfully.
Do we need to make any settings in the Receiver system?

hi,
did you commit this bapi:
a) in the rfc adapter (in your communication channel) if you have sp14
b) in the bapi wrapper if you have < sp14 ?
https://websmp206.sap-ag.de/~sapdownload/011000358700000328352005E/HowtouseBAPandccBPM.pdf
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Client proxy message not reaching to XI system

Similar Messages

Maybe you are looking for