Generated SOAP wsdl url is not accessible on PRD server

[xiswanto]

Hello,

So I've generated the SOAP wsdl url for DEV and QA server, and they are both accessible when I opened the url on chrome / internet explorer browser,
but somehow not for my PRD server. The url does get generated, but it is not accessible no matter where I opened it (chrome, IE, or when I tried to create a new SOAP project in SOAPUI apps).

the DEV / QA url:

http://gwdev.company.local:port/sap/bc/srt/wsdl/flv_10002A111AD1/bndg_url/sap/bc/srt/rfc/sap/zws_ast...

,but somehow the PRD url does not begin with gwdev, but gwdb instead:

http://gwdb.company.local:port/sap/bc/srt/wsdl/flv_10002A111AD1/bndg_url/sap/bc/srt/rfc/sap/zws_ast_...

the error when I opened the PRD url in Chrome:

the error when I tried to create SOAP project based on the PRD url:

rror loading [http://gwdb.company.local:port/sap/bc/srt/wsdl/flv_10002A111AD1/srvc_url/sap/bc/srt/rfc/sap/zws_ast_intgr/888/zws_ast_intgr/zws_ast_intgr?sap-client=888]: java.lang.Exception: Failed to load url; http://gwdb.company.local:port/sap/bc/srt/wsdl/flv_10002A111AD1/srvc_url/sap/bc/srt/rfc/sap/zws_ast_..., 0

I assume the problem is that the port is not accessible because of security settings, but I want to make sure of it first whether the problem is solvable from ABAP or BASIS side since I am not able to discuss it currently with my basis colleague.

Any clue to why the url is not accessible and how to solve it?
*the service definition works fine when I tried it.

[thkolz]

I guess you need to check with your basis team…

It seems to be a configuration issue on your PROD gateway.

Did you run SOAMANAGER there to retrieve the WSDL url?

[xiswanto]

Hello c12b61ded10b4e18beae75c3b6218d2c ,

-> I guess you need to check with your basis team…

Noted, will do as soon as they're back.

-> Did you run SOAMANAGER there to retrieve the WSDL url?

yes, I run SOAMANAGER to retrieve the WSDL binding url after creating the service using the 'Create Service' button there.

Although there is one more thing I found out, so I checked my SAP logon connection to PRD, and the address ended in .com instead of .local, so I tried to modify the PRD SOAP url a bit and it show this error

modified url:

http://gwdb.company.com:port/sap/bc/srt/wsdl/flv_10002A111AD1/bndg_url/sap/bc/srt/rfc/sap/zws_ast_intgr/888/zws_ast_intgr/zws_ast_intgr?sap-client=888

*EDIT 10.08.2023 15:27

apparently I try again to check my SAP logon PRD connection, and I found out that that it is using connection type 'Group/Server Selection' and found out that there are 2 group/server, one of them is so called the gwdb which I have been trying, and the other is gwapp, so I tried to modify the WSDL url into gwapp.company.local, and somehow the url could be opened, so perhaps this issue is settled.

But still, I'm curious why there are server which is actually divided into two, but somehow the url is generated based on the wrong server name, Is there is actually problem with the SOAP config, or is it my SAP logon connection which is incorrect?

[thkolz]

So this is definitely something to be handled by your basis team...

I guess you're running your system in a private cloud, right (because of the .local)?

Maybe it's also a firewall issue.
Is the URL that is launched by running SOAMANAGER also starting with http://gwdb.company.com?

[xiswanto]

-> I guess you're running your system in a private cloud, right (because of the .local)?

I'm not sure about this one, it could be in private cloud, since my SAP logon connection is connected to gwdb.company.com instead of gwdb.company.local for the PRD server

-> Is the URL that is launched by running SOAMANAGER also starting with http://gwd.company.com?

nope, it originally start like this: http://gwdb.company.local ,
which I do experiment changing it into this: http://gwdb.company.com , and then finally change it this one ( which Is tested working in SOAPUI too 😞 http://gwapp.company.local .

this issue is actually solved since I guessed the correct url name, but I'm curious if there are cases like this for other company system and whether this issue could be solved by the basis team to redirect the correct server name ( hopefully they could solve it ).