xServer2 - SAP SOAMANAGER issue, RC=404

[ClaasB]

Hi there,

We are trying to change from xserver to xserver2 in the SAP SOAMANGER / WebServices.

- We downloaded the wsdl file for xroute --> https://xserver2.cloud.ptvgroup.com/ser ... /2.19?wsdl
- Then we created a new Consumer Proxy using this wsdl file.
- When we try to ping this we get an error with "Web service ping failed (RC=404). Service Ping ERROR

In SRT_UTIL -> erorr messages we see the following:

XML-File -->

srt_xml.XML

(1.13 KiB) Downloaded 27 times

Can someone help us here?

Best regards,
Claas

[MISTERX]

High Claas

Seems that you have spoiled several things:

Using WSDL and SRT points out that you like to communicate with xServer via SOAP/HTML. But why do you create a port in SOAMANAGER for REST?

PTV xServer2 Internet is always latest version (aka 2.19 actually). For what reason do you assume, that 2.18-end point is still available?

I'm quite sure, with proper settings HTTP-Statuscode 404 ("not found") will not come up anymore.

[YNIK]

Hi All and Mr.X ,

I am the second person working on the PTV xServer2 integration scenario through the SOAP protocol. Sorry, the first input was too fast and with the mistakes. The right target server coming from the wsdl is ofcourse:
https://xserver2.cloud.ptvgroup.com:443 ... Route/2.19

And the main problem is the rc=403 (Forbidden Service Ping ERROR: Forbidden).

Will be very thankfull for any further help

BR
YNIK.

[MISTERX]

Hi Ynik

First of all: why do you point to https://xserver2.cloud.ptvgroup.com/ser ... Route/2.19? This is the production xServer Internet (EU) and not intended to be abused for integration tests. This instance will serve "paying" PTV customers. Please use test instance of xServer Internet (https://xserver2-test.cloud.ptvgroup.co ... Route/2.19) for your actual objective.

HTTP 403 didn't point to communication problems (according to RFC 7231 https://tools.ietf.org/html/rfc7231):

The 403 (Forbidden) status code indicates that the server understood the request but refuses to authorize it.

Assuming that PTV has not redefined HTTP-RCs, the response does not point to any problems. My experience with SAP SOAMANAGER / SRT shows, that implementation of test functionalities for web services does not fit to particular requirements. I will try to reproduce your scenario tomorrow with one of my SAP systems. For that purpose I need to know what SAP system you are using (solution name, like ECC 6 EhP 4, TM 8.1, . . . kernel/base-version, like 720, 730, . . . or HANA version, like 1709, 1808, . . .).

Did you ran already any test request by using the proxy? Perhaps you get a valid response without any problems.

I've just tried to ping PTV xServer Internet and it timed out. Seems that PTV xServer Internet does not answer to PING by its settings . . .

[Bernd Welter]

cheers,

if you try to access the PROD URL with the test token this will hopefully explain the 403. Test tokens aren't granted access to PROD.

For access to PROD you need a specific token != test token. Get in touch with sales or order management if you wish to get a PROD token.

Does this info close the gap?

Best regards from France,
Bernd

[MISTERX]

Hi Bernd

Thx. I think your remark is really helpful.

@Ynik: Please retry with the Test xServer Internet and report - before I waste time by trying to reproduce your situation.

[YNIK]

Hi All ,
I reallly appreciate your help.
Regarding the server. I just consumed the WSDL File , so this server was defined as automatically.
And I still get the rc=404.

.

SAP BASIS - 754
S4CORE - 104
S4HANA - 1909

I will try also today to consume the proxy despite the mistake.
Anyway, thanks for the help.

Best regards
YNik.

[YNIK]

Hi All

Trying to implement RFC Connection for REST consume I still have the problem of RC=404

And also I have the same mistake if I do the consumption in my test program. I suppose it's not the case when it still works despite the connection mistake.

Best Regards,
YNik

[YNIK]

Hi All,

Finally I got the 200 response. The topic can be closed.

BR YNik

[Bernd Welter]

Please let us know what caused the issue