Web Dispatcher access - Page cannot be displayed

[Former Member]

We have a Web Dispatcher in a DMZ (DMZ2) that is used for external (Internet) access to our E-Sourcing application. The E-Sourcing application is in another DMZ (DMZ1).

When external (sell-side) users enter the url in their browser to connect through the Web Dispatcher over the Internet, the initial E-Sourcing screen is displayed very briefly in the browser and then the message 'Page cannot be displayed' comes up on the screen. If the browser screen is refreshed, the login screen is then displayed and the user is able to log in with no issues.

This occurs only when trying to access the E-Sourcing application through the Web Dispatcher. It does not make any difference if the Web Dispatcher hostname is used in the url (internal access through Web Dispatcher) or if the url created specifically for the Web Dispatcher is used (external (Internet) access through the Web Dispatcher). The result is the same.

If either http://WebDisp_Hostname (internal) or http://www.myESOapp.here.com (external Internet) is entered in the browser, both display the front-end ESO screen briefly and then display the 'Page cannot be displayed' message. Refreshing the browser screen then displays the login screen and users can log in OK.

Can anyone point me in the right direction to solve this? I have reviewed the Web Dispatcher trace file and the E-Sourcing log file and can find no errors or anything that would indicate what might be going on. It appears to be a Web Dispatcher issue. Any help would be appreciated.

WL

[Former Member]

When the Internet url http://www.myESOapp.here.com is entered in the browser, it redirects to https://www.myESOapp.here.com:443/sourcing/fsvendor/vendordesktop/login?cookie-test=true&referUrl=nu.... At this point the E-Sourcing login screen appears briefly.

However, another redirect is then done to https://WAS.JAVA.fqhn.com:443/sourcing/fsvendor/vendordesktop/login?cookie-test=true&referUrl=null&c.... For clarification, WAS.JAVA.fqhn.com is the fully qualified host name for the E-Sourcing back-end app server. The 'company.cluster.id' in the url is the external id of the E-Sourcing 'company' cluster definition in E-Sourcing. At this point, the 'Page cannot be displayed' message is displayed.

When the screen is refreshed, it reverts back to the correct url, the login screen is displayed and the user can log in. From here everything works OK.

Can anyone tell me why it is going back to E-Sourcing and getting the cluster external id (company.cluster.id) and building a url with this in it? It also gets the WAS.JAVA.fqhn.com from the cluster definition and uses it in the url as well.

The E-Sourcing 'company' cluster is defined with WAS.JAVA.fqhn.com as the Host Name and www.myESOapp.here.com as a Hostname Alias URL. This allows in-house users access via the FQHN url and external (Internet) users access via the www.myESOapp.here.com url.

WL

[Former Member]

A separate cluster was created for sellside users and the sellside directory was changed to point to the new cluster. After adding it to an enterprise context, the 'Page cannot be displayed' message no longer is displayed and sellside users can log in without having to refresh the screen. The buyside configuration was not changed. We are testing this solution now.

WL

[Former Member]

Hi Ankush,

Thanks for the reply. Are you talking about memory on the Web Dispatcher Windows server or on the E-Sourcing Unix server?

WL

[Former Member]

Hi Wayne,

I am not sure because our web dispatcher and ESO on same machine.

but logically it should be dispatcher, try increasing you dispatcher memory

~Ankush

[Former Member]

Hi,

I guess this is memory issue...we to face this issue on small hardware server.

Try increasing your memory...

~Ankush