cancel
Showing results for 
Search instead for 
Did you mean: 

Facing Problems while Installing SAP Material Availablity App

Former Member
0 Kudos

Hi Experts,

I am currently installing SAP Material Availability app.

When i run the application It's coming online in SCC but after that am getting an exception "Network Error While retrieving Data".

I am attaching the detailed log for your reference.

Your help would be appreciated.

Regards,

Abhishek Wajge

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Experts,

Please see the sup server log as well as it will help u to identify the issue.

2013-01-18 09:56:01.563 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In releaseconnection() method of Connection Factory--------

2013-01-18 09:56:01.563 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response Body is written into OutputStream

2013-01-18 09:56:01.563 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]------In writing response method-----

2013-01-18 09:56:01.563 ERROR PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]No connection returned from the Connectionpool.Endpoint is not whitelisted with SUP. Hence terminating the request

2013-01-18 09:56:01.563 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]ConnectionPool did not grant connection as the Backend URL specified is not white listed

2013-01-18 09:56:01.563 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Flag value is (2)false

2013-01-18 09:56:01.563 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Address to which connection object has to be assigned is:http://Host:8010/sap/opu/sdata/mive/salesmaterial/?sap-client=400&sap-language=EN

2013-01-18 09:56:01.562 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Inside getConnection() of GWCConnectionPoolManager

2013-01-18 09:56:01.562 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]Pm is not null

2013-01-18 09:56:01.562 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In getconnection() method of Connection Factory--------

2013-01-18 09:56:01.562 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]----Application Id sent from client is--------com.sap.meps.erpmaterialsearch

2013-01-18 09:56:01.562 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy handle()----------

2013-01-18 09:56:01.561 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------Leaving GWCRequestAdapter constructor()----------

Regards,

Abhishek Wajge

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Abhishek,

The logs says "ConnectionPool did not grant connection as the Backend URL specified is not white listed"

I guess you are using latest SUP2.2 server.

So can solve this issue by creating a new connection with your proxy URL.

Go to  Domains>>Domain Name>> Connections

Create new connection of type proxy and name same as your applicationID.

Add your Service doc URL (proxy URL) and save.

Try the application again. This should solve your issue.

Regards

Rohith

Former Member
0 Kudos

Hi Rohith,

Thanks for your reply.

I am using sup 2.1.3

To solve white-listing problem,I tried same what you mentioned above.

I put proxy URL in new connection of type proxy but when i test connection it gives me error saying "Unauthorized".

Regards,

Abhishek Wajge

Former Member
0 Kudos

Hi Rohith,

One more thing,When i validate the services am getting "HTTP code 400

An exception has occurred sy530".

Is thr any problem with rfc connections or trust system?

I also put breakpoint in that RFC and when i test service from rest client,It's going in backend.

Regards,

Abhishek Wajge

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Abhishek,

1. You can ignore "test Connection" "Unauthorized" issue. Just create the connection.

2.  Are you getting this error when you run the URL "

:http://Host:8010/sap/opu/sdata/mive/salesmaterial/?sap-client=400&sap-language=EN"

in REST client?

If so, its problem in gateway Or backend.  You can post this issue in gateway forum to get help from gateway experts.

Regards

Rohith

Former Member
0 Kudos

Hi Rohith,

As u said,I've created connection pool in domain as type proxy.

Still am getting the same exception.

I put breakpoint also in backend to check whether its going in backend or not.but when i run the app its not even going in backend.

That means from gateway to backend nothing is happening.

After creating the connection in domain,I am getting following sup server log.

Here See the url properly it has been changed now.

2013-01-18 17:44:15.365 INFO PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP:Returning Response from Gateway Back to Message Channel

2013-01-18 17:44:15.364 DEBUG PROXY Thread-1051 [com.sybase.suplite.gwc.req.util.domainReqRespLogHandler]Inside Domain Logger for ReqResp

2013-01-18 17:44:15.364 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Connection released

2013-01-18 17:44:15.363 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----Inside releaseConnection() of GWCConnectionPoolManager------

2013-01-18 17:44:15.363 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In releaseconnection() method of Connection Factory--------

2013-01-18 17:44:15.363 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response Body is written into OutputStream

2013-01-18 17:44:15.363 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]------In writing response method-----

2013-01-18 17:44:15.363 ERROR PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]No connection returned from the Connectionpool.Endpoint is not whitelisted with SUP. Hence terminating the request

2013-01-18 17:44:15.363 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]ConnectionPool did not grant connection as the Backend URL specified is not white listed

2013-01-18 17:44:15.362 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Flag value is (2)false

2013-01-18 17:44:15.362 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Address to which connection object has to be assigned is:http://<host>:8010/sap/opu/sdata/mive/salesmaterial/$metadata

2013-01-18 17:44:15.362 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Inside getConnection() of GWCConnectionPoolManager

2013-01-18 17:44:15.361 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]Pm is not null

2013-01-18 17:44:15.361 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In getconnection() method of Connection Factory--------

2013-01-18 17:44:15.361 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]----Application Id sent from client is--------com.sap.meps.erpmaterialsearch

2013-01-18 17:44:15.360 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy handle()----------

2013-01-18 17:44:15.360 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------Leaving GWCRequestAdapter constructor()----------

2013-01-18 17:44:15.359 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]AppId got is POCDevelopment_com.sap.meps.erpmaterialsearch

2013-01-18 17:44:15.359 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Json Request header : [{"X-SAP-applicationId":"com.sap.meps.erpmaterialsearch"},{"request":"GET"},{"url":"http://<host>:8010/sap/opu/sdata/mive/salesmaterial/$metadata"},{"Accept-Encoding":"gzip"},{"X-SAP-applicationId":"com.sap.meps.erpmaterialsearch"},{"Accept-Language":"en"},{"X-SAP-deviceType":"iphone"},{"X-SAP-deviceId":"d20291c81eb09b77f355553beb86639024cb0299"}]

2013-01-18 17:44:15.358 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]context.getDeviceUserName() is sapm

2013-01-18 17:44:15.358 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request header : [{"X-SAP-applicationId":"com.sap.meps.erpmaterialsearch"},{"request":"GET"},{"url":"http://<host>:8010/sap/opu/sdata/mive/salesmaterial/$metadata"},{"Accept-Encoding":"gzip"},{"X-SAP-applicationId":"com.sap.meps.erpmaterialsearch"},{"Accept-Language":"en"},{"X-SAP-deviceType":"iphone"},{"X-SAP-deviceId":"d20291c81eb09b77f355553beb86639024cb0299"}]

2013-01-18 17:44:15.358 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request body Read :

2013-01-18 17:44:15.358 INFO PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]ODP: Read the Request information

2013-01-18 17:44:15.358 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]UsrName/Pwd is extracted from context:

2013-01-18 17:44:15.358 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------In GWCRequestAdapter constructor()----------

2013-01-18 17:44:15.355 INFO PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP :Recieved a request to fire to Gateway

2013-01-18 17:44:14.871 INFO PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP:Returning Response from Gateway Back to Message Channel

2013-01-18 17:44:14.869 DEBUG PROXY Thread-1050 [com.sybase.suplite.gwc.req.util.domainReqRespLogHandler]Inside Domain Logger for ReqResp

2013-01-18 17:44:14.869 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Connection released

2013-01-18 17:44:14.868 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----Inside releaseConnection() of GWCConnectionPoolManager------

2013-01-18 17:44:14.868 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In releaseconnection() method of Connection Factory--------

2013-01-18 17:44:14.868 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response Body is written into OutputStream

2013-01-18 17:44:14.868 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]------In writing response method-----

2013-01-18 17:44:14.868 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response body is obtained from BackEnd

2013-01-18 17:44:14.868 INFO PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP:Read response body from Gateway

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]------------content encoding is ZIP ----------gzip

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]------------content type|encoding|length--------application/atomsvc+xml----gzip----548----

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyset-cookie          Response header valuesap-usercontext=sap-language=EN&sap-client=400; path=/

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyset-cookie          Response header valueMYSAPSSO2=AjQxMDMBABhBAFcAQQBKAEcARQAgACAAIAAgACAAIAACAAY0ADAAMAADABBHADEAMAAgACAAIAAgACAABAAYMgAwADEAMwAwADEAMQA4ADEAMgAxADQABQAEAAAACAYAAlgACQACRQD%2fAPswgfgGCSqGSIb3DQEHAqCB6jCB5wIBATELMAkGBSsOAwIaBQAwCwYJKoZIhvcNAQcBMYHHMIHEAgEBMBkwDjEMMAoGA1UEAxMDRzEwAgcgEgcJFgI3MAkGBSsOAwIaBQCgXTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzAxMTgxMjE0MTRaMCMGCSqGSIb3DQEJBDEWBBS2X7LyhU8o17rNttSNrkr%2fOZIt9jAJBgcqhkjOOAQDBC8wLQIVAKDvCtcuejU8iuO9LrOZUzy0fiakAhRmsfS4ubNjrQSNd2h%2f%211%21IBrNrxw%3d%3d; path=/; domain=.corp.capgemini.com

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-type          Response header valueapplication/atomsvc+xml

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-encoding          Response header valuegzip

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keycontent-length          Response header value548

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyx-sap-odata-extension-version          Response header value0.9

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keydataserviceversion          Response header value2.0

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response header keyserver          Response header valueSAP NetWeaver Application Server / ABAP 702

2013-01-18 17:44:14.867 INFO PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]Response code is HTTP/1.1 200 OK

2013-01-18 17:44:14.867 INFO PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP:Recieved the response from the gateway

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Finished firing the request to GW-----------

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Leaving FireRequest Method-----------

2013-01-18 17:44:14.867 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Finished Execute-----------

2013-01-18 17:44:14.370 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------Before Execute-----------

2013-01-18 17:44:14.370 INFO PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]ODP: Firing the request to the Gateway

2013-01-18 17:44:14.370 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]----Host request header set is ----<host>

2013-01-18 17:44:14.370 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept-Encoding    value=gzip

2013-01-18 17:44:14.370 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=X-SAP-deviceType    value=iphone

2013-01-18 17:44:14.370 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=X-SAP-deviceId    value=d20291c81eb09b77f355553beb86639024cb0299

2013-01-18 17:44:14.370 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Authorization    value= Not printed for security reasons

2013-01-18 17:44:14.370 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]header: key=Accept-Language    value=en

2013-01-18 17:44:14.370 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy fireRequest()----------

2013-01-18 17:44:14.370 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]--------------About to fire the request to the GW-----------

2013-01-18 17:44:14.324 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]-----Leaving getConnection() of GWCConnectionPoolManager-- Found in cache first time----

2013-01-18 17:44:14.324 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Flag value is (1)true

2013-01-18 17:44:14.324 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Address to which connection object has to be assigned is:http://<host>:8010/sap/opu/sdata/mive/salesmaterial/?sap-client=400&sap-language=EN

2013-01-18 17:44:14.324 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCConnectionPoolManager]Inside getConnection() of GWCConnectionPoolManager

2013-01-18 17:44:14.324 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]Pm is not null

2013-01-18 17:44:14.324 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.ConnectionFactory]---------In getconnection() method of Connection Factory--------

2013-01-18 17:44:14.323 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]----Application Id sent from client is--------com.sap.meps.erpmaterialsearch

2013-01-18 17:44:14.323 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWProxy]----------In GWProxy handle()----------

2013-01-18 17:44:14.323 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------Leaving GWCRequestAdapter constructor()----------

2013-01-18 17:44:14.320 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]AppId got is POCDevelopment_com.sap.meps.erpmaterialsearch

2013-01-18 17:44:14.320 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Json Request header : [{"X-SAP-applicationId":"com.sap.meps.erpmaterialsearch"},{"request":"GET"},{"url":"http://<host>:8010/sap/opu/sdata/mive/salesmaterial/?sap-client=400&sap-language=EN"},{"Accept-Encoding":"gzip"},{"X-SAP-applicationId":"com.sap.meps.erpmaterialsearch"},{"Accept-Language":"en"},{"X-SAP-deviceType":"iphone"},{"X-SAP-deviceId":"d20291c81eb09b77f355553beb86639024cb0299"}]

2013-01-18 17:44:14.319 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]context.getDeviceUserName() is sapm

2013-01-18 17:44:14.319 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request header : [{"X-SAP-applicationId":"com.sap.meps.erpmaterialsearch"},{"request":"GET"},{"url":"http://<host>:8010/sap/opu/sdata/mive/salesmaterial/?sap-client=400&sap-language=EN"},{"Accept-Encoding":"gzip"},{"X-SAP-applicationId":"com.sap.meps.erpmaterialsearch"},{"Accept-Language":"en"},{"X-SAP-deviceType":"iphone"},{"X-SAP-deviceId":"d20291c81eb09b77f355553beb86639024cb0299"}]

2013-01-18 17:44:14.319 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]Request body Read :

2013-01-18 17:44:14.319 INFO PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]ODP: Read the Request information

2013-01-18 17:44:14.319 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]UsrName/Pwd is extracted from context:

2013-01-18 17:44:14.319 DEBUG PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GWCRequestAdapter]----------In GWCRequestAdapter constructor()----------

2013-01-18 17:44:14.316 INFO PROXY MessageChannel Thread-451 [com.sybase.suplite.gwc.req.handler.GatewayConnectorHandler]ODP :Recieved a request to fire to Gateway

Regards,

Abhishek Wajge

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Abhishek,

The Error still says "ConnectionPool did not grant connection as the Backend URL specified is not white listed"

So still the problem is with connection pool. Please recheck the connection pool which you have created. The connection pool should have the gateway (proxy) URL.Without connection pool request will not reach gateway.

Ideally connection pool gets created automatically when you create applicationID with proxy URL. I guess in your case, you created applicationID first and later edited the ApplicationConnectionTemplate to enter proxy URL. That could be the reason for connection pool not being created in you case.

Regards

Rohith

Former Member
0 Kudos

Hi Rohith,

Thanks for your reply.

I recreated the application templates and connections in SCC.

As u said,connection pool got created automatically but still i am facing the same problem :

"No connection returned from the Connectionpool.Endpoint is not whitelisted with SUP. Hence terminating the request"

Here am attaching all the screenshots of SCC Config.

Please check the same.

Am i missing anything in scc settings?

Your help would be appreciated.

Regards,

Abhishek Wajge

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Abhishek,

I checked the screenshots and I do not find any problem..

I observed something in the Logs.

When you connect the application for the first time to fetch data, there will be 3 consecutive requests made.

1. Request for Service doc

URL in your case is

http://<host>:8010/sap/opu/sdata/mive/salesmaterial/?sap-client=400&sap-language=EN.

I see in the logs that this is successful(response code 200).

2. Request for metadata doc

URL in your case is

http://<host>:8010/sap/opu/sdata/mive/salesmaterial/$metadata  which is failing with whitelisting issue.

3. Search request.

It is strange that firt request to the same server is working fine and second request is failing.

Do you see any change in the "host" address for request 1 and 2?

Can you please run the second URL (metadata) in REST client and check?

Regards

Rohith

Former Member
0 Kudos

Hi Rohith,

I cant see any change in the "host" address for request 1 and 2.

In fact,When i run the URL(Metadata) in Rest Client Its giving me http 200 ok status code.

Regards,

Abhishek Wajge

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Abhishek,

This is really strange behaviour and appears to be an issue on server.  May be you can create an OSS ticket to SAP.

Regards

Rohith

Former Member
0 Kudos

Hi Rohith,

Thanks for your reply.

I did some work around and observed on thing which i would like to share with you.

In SM59, I have created a RFC connection from gateway system to backend system which is working fine and it also accepts backend system as trusted one.

But i can see there is one more connection and it got created automatically(TRUSTING@backendsystemname) and when i try to do remote logon it says "No Authorization to logon as trusted system RC = 0".

Also when i run the tcode sso2 for this rfc connection it gives error saying "No connection to TRUSTING@backendsystemname".

Can we target this issue or its something irrelevant?

Need your suggestions.

Regards,

Abhishek Wajge

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Abhishek,

I dont think the above observation is related to the error you are getting. Request is failed to reach gateway  itself from SUP server.  

This is how it works:

SUP server creates a connection pool to the gateway server (host:port) based on the proxy URL mentioned in application connection template.

When you fire a request, SUP checks if the connection pool exists for the host:port  in the URL and grants a conection. If no connection pool exists, then it throws "URL whitelisting" error.

In your case, connection pool exists and still SUP is failing to grant connection to the second request. You can understand this when you read through the logs bottom up.

Regards

Rohith

Former Member
0 Kudos

Hi Rohith,

Finally app is working.

Solved that problem by my own.

Thanks for ur valuable suggestions.

Regards,

Abhishek Wajge

rohith_deraje
Advisor
Advisor
0 Kudos

Hi Abhishek,

Glad that your issue is resolved. Can you please share the details on how did you solved the issue?

This would be a useful information if someone else face the same issue.

Regards

Rohith

Former Member
0 Kudos

Hi Abhishek,

Would you like to share how did you solve the problem. I am facing exactly the same problem with my EmployeeLookup application. Would really appreciate it.

Former Member
0 Kudos

Hi Rohith,

You mentioned in one of your replies that URL for the first and 2nd request should be same. For my case,

First URL is http://hostName:8000/sap/opu/sdata/MIVE/EMPLOYEELOOKUP, it returns

Response Code = 200 (which is correct response)

Second URL is

http://hostName.companyName.Province.ca:8000/sap/opu/sdata/MIVE/EMPLOYEELOOKUP/$metadata, (example, http://hostName.telus.on.ca:8000/sap/opu/sdata/MIVE/EMPLOYEELOOKUP/$metadata)

it returns Response Code=403

i am not sure why

Former Member
0 Kudos

Hi Arfan,

Check your Two URL's Properly.

Can u find any difference in host name?

Because sup internally converts host name either in uppercase or lowercase.

If First URL which is working and giving http code 200 and host name is in uppercase

Then for second url which is giving http 403, host name will be in lowercase or vice versa.

Now take the url as it is which is giving 403 error and put that url in your application endpoint(It's case sensitive so take as it is).

Make sure you change application endpoint at all the places.

If you are using httploginmodule security profile then make sure u use new url there as well.

Restart the server once or if first time ur app dint work then run it again.

Let me know if u are able to solve the problem.

Regards,

Abhishek Wajge

Former Member
0 Kudos

Do you mean to take URL that is giving response code 200? (because you mentioned to take the URL which is giving code 403). my URLs seems to different:

First URL is http://hostName:8000/sap/opu/sdata/MIVE/EMPLOYEELOOKUP, it returns

Response Code = 200 (which is correct response)

Second URL is

http://hostName.companyName.Province.ca:8000/sap/opu/sdata/MIVE/EMPLOYEELOOKUP/$metadata, (example, http://hostName.telus.on.ca:8000/sap/opu/sdata/MIVE/EMPLOYEELOOKUP/$metadata), it returns Response Code = 403

Former Member
0 Kudos

Hi Arfan,

Just tell me one thing when you run the URL(which is giving code 403) in Rest client does it returns http success 200 code?.

You are getting two different url's so its expected that Backend URL will not be white listed.

Regards,

Abhishek Wajge

Former Member
0 Kudos

Yes Abhishek, it gives 200 code if i test the 2nd URL in REST client.

Former Member
0 Kudos

Hi Arfan,

Use that URL in your application endpoint proxy(one which is giving code 403 and not 200) also change app endpoint URL at domain level and security profile level.

Restart sup server and run the app if first time ur app dint work then run it again.

Let me know asap.

Regards,

Abhishek Wajge

Former Member
0 Kudos

Hi Abhishek, it seems we have WiFi network problem. I am talking to our network team. I have your email address, i will keep you posted.

Former Member
0 Kudos

Hi Arfan,

Sure.Let me know if u still facing the same problem.

Regards,

Abhishek Wajge

0 Kudos

hi abhishek,

  can you please help me im facing the same prb except that using the url with or without *metadata it gives me status  '200 ok' on the browser but i m getting the endpointTest : unauthorized .

waiting for response

Former Member
0 Kudos

Hi Madiha,

Can you please tell me in detail what problems are you facing.

If possible attach the screenshots.

Regards,

Abhishek Wajge