Thursday, April 16, 2009

Application Server HTTP 404 problem

Hi SOA lovers

Writing blog after a long gap, this time with new flavors.

Sometimes when you navigate to the Enterprise Manager’s Application Server Control you will hit a 404 "Page not found exception".

The most probable reason is that Application Server Control has no routing relationship defined with the Oracle HTTP Server by default.

To establish this relationship you have to set the ohs-routing attribute to true (default value in the file will be false) in the default-web-site.xml file at SOA server location: <SOA home>/j2ee/home/config. Make sure to make the changes always in the home container.

Make the changes as follws in the file:
<web-app application="ascontrol" name="ascontrol" load-on-startup="true" root="/em" ohs-routing="true" />

Now restart the SOA Server and try it. It should work.

If this solution doesn't work, follow my latest finding, posted on 22nd December 2009.


Anonymous said...

I was hoping this would solve my problem. Unfortunately, I still can't bring up the OC4J Admin console running from JDeveloper.

Anonymous said...