Monday, April 07, 2014

HTTP-404 on /oamconsole

WeblogicHost versus WeblogicCluster

Despite the fact, the oamconsole can not be clustered, it has to be "clustered". If you ever find yourself in a scenario, where your configure a webgate in front of your OAM Console, make sure you configure it like
############################################## ## Entries Required by Oracle Access Manager ############################################## # OAM Console <Location /oamconsole> SetHandler weblogic-handler WebLogicCluster oamhost1.home.local:7001, oamhost2.home.local:7001 </Location>
This looks wrong, as -when you actually are running the OAM console on oamhost1- you simply cannot navigate to oamhost2.home.local:7001/oamconsole. You *can* navigate to oamhost1.home.local:7001/oamconsole.
As you manually have to reconfigure the adminserver in case of disaster, you may consider putting this in your configuration:
############################################## ## Entries Required by Oracle Access Manager ############################################## # OAM Console <Location /oamconsole> SetHandler weblogic-handler WebLogicCluster oamhost1.home.local:7001 </Location>

This does NOT work

BTDT:
############################################## ## Entries Required by Oracle Access Manager ############################################## # OAM Console <Location /oamconsole> SetHandler weblogic-handler WebLogicHost oamhost1.home.local WebLogicPort 7001 </Location>
This is what the Enterprise Deployment Guide suggests.
My config uses WLS 10.3.6.0.7, OAM 11.1.2.2.0, RedHat Enterprise Linux Server release 6.5 (Santiago), Kernel version 2.6.32-431.el6.x86_64

Symptoms

Your call to /oamconsole is initially redirected, and produces a login screen. You seem to authenticate OKAY, as other screens can be accessed without being re-authenticated.
However, /oamconsole is not displayed, and results in a 404 (Not Found).
Hope this helps!

14 comments:

Pandora said...

Hi I been having the same issue with the oamconsole. I tried your solution and haven't produced any results. Right now we have our oam servers in a cluster with a webgate and a load balancer on top of it. I still get the 404 error.

Frank said...

You have the same symptoms? You *can* access the admin server on 7001 and activate oamconsole?

Pandora said...
This comment has been removed by the author.
Pandora said...

Yeah, I have the same symptoms. I can access the admin server on 7001 and activate oamconsole when is down that which doesn't contain the admin server on it. When everything is on I get a 50/50 chance of hitting the oamconsole. I should be hitting the oamconsole 100% of the time shouldn't I?

Pandora said...
This comment has been removed by the author.
Pandora said...
This comment has been removed by the author.
Pandora said...

< Location /oamconsole>
SetHandler weblogic-handler
WebLogicCluster oamhost1.home.local:7001,oamhost2.home.local:7001
< / Location>

Frank said...

Ah - that helps. Technical details. I would say, you should have just oamhost1.home.local:7001 as your cluster (assuming that is where your admin server runs).
As the console typically is deployed on the admin server, and the admin server only runs on one member of the cluster.
Nevertheless, you *should* use the keyword WeblogicCluster here (as I tried to make clear in the blog), even though there's only one member!

bdobson said...

I have a new Oracle OAM setup and everything except for the /oamconsole redirect is working.

If I put in http://domainname.com:7001/oamconsole I get tossed to http://null:14100/oam/server. If I change that to http://domainname:14100/oam/server it comes up and appears to be working just fine. It is purely the redirect that is broken and throughout lengthily searches I've not been able to find out why.

Frank said...

Brian, have to look into that. Meanwhile, are we taking this scenario (Load Balancer, Virtual hostname, this is the webgate, protecting your oamconsole)?
domainname.com is *not* the name of the actual server, running oam, but the virtual host?
Can you access servername:7001/oamconsole correctly?

bdobson said...

In this case it is the servername that is giving me the problem. No virtual hosts have been setup as of yet as I wanted to test that working first. I have done this before and it worked fine so this time I have missed something.

http://servername:7001/oamconsole redirects me to http://null:14100/oam/server.

If I manually change that to http://servername:14100/oam/server it comes up and works.

Now, http://servername:7001/console for the Weblogics works just fine. It's only oamconsole that will not redirect.

So I fear I've missed something that I want to solve before proceeding.

Frank said...

Brian,
the URL is the one of the webgate, protecting your oamconsole, so I'd look there.
Hostnames on your Host Identifiers screen for this webgate; the challenge URL or challenge Redirect URL on your AuthN Scheme (though Challenge URL is non-optional, so that would be odd).
And you did transfer the Artefacts to the webgate machine, didn't you?

bdobson said...

Everything should be copied over, which worked in the first version but now this never seems to go right. The final few commands that are run for the WebGate before testing are:

./deployWebGateInstance.sh -w /opt/app/oracle/Middleware/Oracle_WT1/instances/instance1/config/OHS/ohs1 -oh /opt/app/oracle/Middleware/Oracle_OAMWebGate1

./EditHttpConf -w /opt/app/oracle/Middleware/Oracle_WT1/instances/instance1/config/OHS/ohs1 -oh /opt/app/oracle/Middleware/Oracle_OAMWebGate1 -o Edithttpconf.log

Sandesh Jain said...

i am facing the same issue as bdobson is facing , have you find any solutions ti this yet, please do share with me.