cancel
Showing results for 
Search instead for 
Did you mean: 

Need sample standard WebDynpro Java Application

bhavya_sri3
Participant
0 Kudos

Dear All,

We are facing a strange behavior with UWL Application.

We are running on Portal 7.4 version. When we are accessing the portal, everything elase seems to work fine except UWL.

We have the below network Architecture.

Client System --> Firewall1 --> Hardware Load balancer --> Apache Proxy --> SAP Web Dispatcher --> Firewall 2 --> SAP Portal/ECC Servers.

We are using SiteMinder(third party) for authentication. So they replaced the Portal logon page.

When we access the UWL through load balancer url, we are getting 403 Forbidden error in place of UWL. But when we access the UWL with proxy URL, it is working fine.

Network team is pointing that when accessing the UWL through load balancer, it is failing in creating connection with backend hence resulting in the error.

We want to isolate the issue, if the issue is with accessing WebDynpro Java application or when it is trying to access backend. We have only one WebDynpro Java application that is UWL in our entire portal. All the others are in WebDynpro ABAP. So can anyone suggest any standard webdynpro Java application which does not need to connect to backend. So that we create an iview for the same and analyze the behavior.

Any suggestion is truly appreciated as we have been with this issue for such a along time..

Thanks,

Bhavya

Accepted Solutions (1)

Accepted Solutions (1)

bhavya_sri3
Participant
0 Kudos

At last we were able to resolve the issue. We have integrated with SiteMinder for login authentication. While doing so, we have to maintain the login modules under nwa --> Configuration --> Authentication and sso --> tickets.

There we have to maintain the sequence and priorities for the login modules. After doing that the issue got resolved.

Thanks,

Bhavya

Answers (2)

Answers (2)

bhavya_sri3
Participant
0 Kudos

Hi Lutz, Thanks for your inputs. But with a further close analysis, we performed the below steps.

1. Switched off the Web Dispatcher

2. Accessed the Portal with Proxy URL.

so our systems is Apache Proxy -> SAP Portal.

So we observed that even when we are accessing with the Proxy, we are getting the error and in this case, the Load Balancer is not involved.

We also observed that the error is showing as SiteMinder Login module authentication failure and exactly at that point we are getting 403 Access Denied error.

We were able to access all the other applications except UWL.

So we are suspecting that there is an issue with SiteMinder Login Module.

Has anyone faced this kind of an issue with SiteMinder before? Can anyone throw some light on this issue..

Thanks,

Bhavya

LutzR
Active Contributor
0 Kudos

Hi bhavya sri, for me this looks like a configuration issue on the hardware load balancer. It is probably configured to forward all requests to URIs starting with /irj. But it is probably not configured to forward URIs starting with /webdynpro. So let the load balancer experts check their configuration and trace files.

Do not let them forward /webdynpro/* because that would include NWA and other admin tools. Provide them with the exact URL that you expect your application to use.

Good luck, Lutz