Friday

Forget to configure your application server as an Administration Instance?

I’ve installed Oracle Application Server quite a few times and today I had to perform another one.   After I installed the application server I tried to login to the console but was greeted by a lovely message:

Oops! This link appears to be broken.

The apache error logs showed:

File does not exist: /u01/app/oracle/product/apps1013/Apache/Apache/htdocs/em/console


The access log:

"GET /em/console HTTP/1.1" 404 342


It turns out, while installing the application server I forgot to select a check box which designated the server as an administrator instance. 

image

In a single instance environment, such as the one I am setting up, you need to select this option to be able to manage the instance.   If this was a node in a cluster, you should only designate one instance as the administration instance.

So what do you do if you forgot to select it like I did?  Nothing to worry about, you just need to edit two files:

1. Open $ORACLE_HOME/j2ee/home/config/server.xml

Change start=”true” for the ascontrol line.  It should look like this:

<application name="ascontrol" path="../../home/applications/ascontrol.ear" parent="system" start="true" />


2. Edit $ORACLE_HOME/j2ee/home/config/default-web-site.xml

Add ohs-routing=”true” to the ascontrol line.  It should ook like this:

<web-app application="ascontrol" name="ascontrol" load-on-startup="true" root="/em" ohs-routing="true" />

Now you just need to restart the application server:

$ORACLE_HOME/opmn/bin/opmnctl stopall;
$ORACLE_HOME/opmn/bin/opmnctl startall;

and if you goto http://servername:/em/console the application server control should now work.

2 comments:

yemi said...

my friend thank you, i couldnt figured out why 1 of my app servers em console wouldnt work where as the other 4 did.

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