The sitesconfigsetup URL During Installation Fails Via OHS That Resides in DMZ/Firewall

(Doc ID 2160698.1)

Last updated on JANUARY 10, 2018

Applies to:

Oracle WebCenter Sites - Version and later
Information in this document applies to any platform.


An installation of Sites in an environment with OHS in a DMZ (firewall between OHS and WebCenter Sites) results in errors like the following in the sites.log:

[2016-07-04T12:34:49.159+00:00] [wcsites_1] [ERROR] [] [oracle.wcsites] [tid: 109] [userId: ] [ecid: 005DgtlXnWwDc_7pzGp2iW0006z^0000AX,0:1] [APP: sites] [partition-name: DOMAIN] [tenant-name: GLOBAL] com.fatwire.cs.core.http.HttpAccessException: Connection timed out
[2016-07-04T12:34:49.160+00:00] [wcsites_1] [NOTIFICATION] [] [oracle.wcsites.install] [tid: 109] [userId: ] [ecid: 005DgtlXnWwDc_7pzGp2iW0006z^0000AX,0:1] [APP: sites] [partition-name: DOMAIN] [tenant-name: GLOBAL] CSSetupEngine.postURL: PostURL failed for http://<ohs host>:<ohs port>/sites/Install?test=test [[
:: ERROR = No response was received from the server

The connection from OHS to WCS nodes is one-way through the DMZ to WebCenter Sites, that means only OHS can connect to WebCenter Sites. WebCenter Sites is in the application zone, so it cannot connect to the OHS that is in the DMZ zone.

The /sites/sitesconfigsetup after clicking the "Test" button is stuck running and does not return a response or continue. The error message said that it failed when HelloCS, Ping DB and check DB Permission were tested.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms