Last updated on MARCH 08, 2017
Applies to:Oracle Access Manager - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
There are 2 machines, i.e., one instance of OAM, one instance of OHS, respectively. There is no load balancer.
Case 1 - OAM configuration includes Access Manager Settings (load balancer) to point to itself (oam host) and 14101 port.
This arrangement works. When a protected application is requested, customer gets directed to oam login with the following url pattern,
Upon submitting credentials, it successfully logs the user into the application. Logout also works.
Case 2 - Customer do not want to expose and use 14101 port to the outside world,
Customer change OAM Access Manager Settings (load balancer) configuration to point to OHS host and 443 (OHS port).
In this arrangement, when they request the same application URL, they get the following error,
"The requested URL /oam/server/obrareq.cgi was not found"
On the URL bar, following appears,
Customer has "Case 2" working in many other internal environments involving OAM and OHS here. Not in Oracle Cloud yet.
In Oracle Cloud environment, there are 2 sets of IP addresses - External and Internal
Machines having to access cloud services from outside need to use use External IP addresses; and services within the cloud accessing each other use Internal IP addresses.
On local windows workstation from where browser is launched (to invoke application), we reference the External IP addresses to these servers, in windows hosts file,
On OAM and OHS machines in cloud, we set Internal IP addresses to reference these servers in etc hosts file,
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