404 Resource not found Server proxy [PI to SAP]

[Former Member]

Hello,

We developed a inbound Server proxy [JDBC to SAP] . When it comes to Call adapter in PI it fails with the error below. The target SAP server IP address is correct and logon is PIUSER . Though we use the different logon id and password it keeps coming back saying that it is trying to logon to SAP with PIAFUSER.

The port is open between PI and SAP.

Path = /sap/xi/engine?type=entry

The connection between PI and SAP is good. The outbound client proxy is working fine

Please advice.

Thanks,

Teresa

404 Resource not found Partner not reached

Error: -20 Version: 7011 Component: ICM Date/Time: Thu Mar 29 15:45:50 2012  Module: icxxconn_mt.c Line: 2271 Server: Amexhop_PI_00 Error Tag: {0006497b} Detail: Connection request from (52/2298/0) to host: 63.20.137.34, service: 00 failed (NIECONN_REFUSED) AP-T52, U2298, 010 PIAFUSER, , 15:45:50, M0, W5, , 1/0

[Former Member · Accepted solution]

hi Teresa,

Goto SM59, open the type H connection to corresponding SAP system and click on Connection Test.

Check what HTTP response it is returning, It should return 500 for healthy connection. If it does not return 500. Get the basis to correct it.

Hope this helps,

Ankit

[Former Member · Accepted solution]

Hi ,

In my PI system in SM59 I do not see any HTTP connection created to external server . There is one HTTP Connection created that points to PI server itself.It is of type H with service no 50000.

In my SAP system I have a HTTP connection of type H that points to PI server. As i mentioned earlier client proxy works fine.

I want to clarify is that do we need any HTTP connection to be created in PI with the connection pointing to SAP Server ?

Thanks,

Teresa

[Former Member · Accepted solution]

Hi Teresa,

Yes, HTTP connection of type H is required pointing to target SAP system. Please get it created with path prefix "/sap/xi/engine?type=entry".

[former_member184681 · Accepted solution]

Dear Teresa,

The answer is: not necessarily. You can put the connection details directly in receiver Communication Channel config. But this approach has two major weaknesses:

• testing not available (while you can perform a connection test from sm59), and
• same data is stored in multiple places (in case of multiple receiver channels for same receiver systems).

So it might be considered a best practice, to put the connection details in an RFC destination of type H, and only use reference to this RFC destination in the Communication Channel.

Hope this helps,
Greg

[Former Member · Accepted solution]

Hi,

Create an RFC connection (for example - SAPTEST)in SM59 under "HTTP Connections to ABAP System" of type H which connects to your SAP server. Make sure that RFC destination connection is tested successfully.

In the next step, same RFC connection name created should be provided in the HTTPDestination in the Receiver XI adapter.

[Former Member]

Dear Teresa

Is SLD check working in ECC?

RFC Destination type H working between ECC and PI?

Regards

Monika

[Former Member]

The SLD check and RFC destination type H from SAP to PI  are working fine. Do I need a RFC destination of type H from PI to SAP created in PI ?

[baskar_gopalakrishnan2]

I would recommend Yes. Plus if you deal with multiple interfaces to the SAP System you use the same http destination in the proxy receiver adapter as addressing type http destination.

[former_member214364]

Hi Teresa,

From your Error Description its looking like its an issue with Service:

Detail: Connection request from (52/2298/0) to host: 63.20.137.34, service: 00 failed (NIECONN_REFUSED) AP-T52, U2298, 010 PIAFUSER, , 15:45:50, M0, W5, , 1/0

In RFC destination of Type H, give service number as HTTP port in Target system(SAP), usually its 8000.

How to check HTTP Port in SAP: Execute Tcode SMICM -> click on Services icon in Application tool bar.

Cheers,

Jag

[baskar_gopalakrishnan2]

Please Check your login credentials used in the receiver proxy adapter. If the credentials are right and still problem exists there might be cache issue. Refresh Cache.

>The connection between PI and SAP is good

How do  you confirm this?  You might want to check this link

[Former Member]

Hi Baskar,

The connections are good. As the client proxy is working perfectly fine. When we send data from SAP[Proxy] to SQL[JDBC]  it does inserts and do not see any issues.

I did refresh Cache too. Is there anything that needs to be done on PI side for Communication to SAP ?

I believe that if client proxy is working than server proxy should also work.

Thanks,

Teresa

[baskar_gopalakrishnan2]

Are you using URL or http destination?  Your path prefix seems correct. Your error shows PI could not reach SAP. Are you configuring any http proxy in the proxy adapter? 

You might try one simple test

IN PI: Do you see RFC connection of type H for connecting PI to abap system? This should be there.

If not create one. Create RFC Destination of type H in PI   and input target host, path prefix, service number, logon details etc. Similar to whatever you did in the server proxy adaper over there and do RFC connection test. If it fails, then you can take help from BASIS to resolve this RFC connection problem.

Message was edited by: Baskar Gopalakrishnan

[former_member184681]

Hi Teresa,

>>> I believe that if client proxy is working than server proxy should also work.
Most likely you are right about that, but there is one thing you can do to be hundred percent sure. In your receiver Proxy communication channel (XI adapter), use Addressing Type = HTTP Destination and specify a name of HTTP destination maintained in sm59 transaction of the ABAP stack. And there in sm59, create an RFC destination pointing to your receiver system. Thanks to that, you will be able to perform a connection test from PI to the receiver.

Moreover, there was a similar thread here, that you might find useful: http://scn.sap.com/thread/1882528.

Hope this helps,
Greg