How to properly install and configure the 11g Webgate 126.96.36.199.0 for Apache 2.2 Webserver when Apache is installed/owned by ROOT user ?
(Doc ID 1958128.1)
Last updated on DECEMBER 19, 2017
Applies to:Oracle Access Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
From the documentation at "Oracle® Fusion Middleware Installing WebGates for Oracle Access Manager 11g Release 2 (184.108.40.206.0) Part Number E49451-04"
See the Chapter #5 "Installing and Configuring Apache 11g WebGate for OAM"
In this installation scenario where we have the Apache webserver as installed and owned by "root" user, but pointing out to a separate OS user/group in its directives.
So, Apache is installed and owned by root, but we have these parameters/directives being set in its httpd.conf , for example. :
So, we use this different Operating System's user/group as directives set in httpd.conf, and with which the Apache processes are actually spawned as with this OS user (e.g. "oracle1").
Also, please note that the Webgate 11g software bits have been installed by this different OS user/group on the system, and NOT by the root user.
It looks like there are issues faced as on the "Post-Installation Steps for Apache 11g WebGate" which prevent us to complete the webgate configuration properly (for instance, issue when running with EditHttpConf tool ).
So, How do we properly install and configure this new 11g Webgate 220.127.116.11.0 for Apache Webserver 2.2 as in this specific use-case ?
Is the root user supposed to be used for executing the EditHttpConf tool ? Or is it with the OS specific user/group who installed the Webgate bits ?
Is this use-case supported at all? And which exact documentation steps to follow for configuring with this use case ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document