How to configure EM console after Oracle Application Server 10g (10.1.3) Application Server
Steps to enable ascontrol. This can also be used to enable and disable the custom deployed applications.
1: Check the opmn status
opmnctl status -app
Following example, “ascontrol” row showing it is “stopped” and routable is set to “false”:
application type: OC4J
——+——————-+———+———+—————-+———-+—– —
pid | name | state | rtid | classification | routable | pare nt
——+——————-+———+———+—————-+———-+—– —
14963 | datatags | started | g_rt_id | internal | true | default
14963 | default | started | g_rt_id | external | true | system
14963 | ascontrol | Stopped | g_rt_id | external | false | system
Note this can be set to false and stopped because this instance was not chosen for ascontrol at installation time, or becomes disabled when creating a new instance.
If the status for the routable value is “false”, the Oracle HTTP Server will not recognize the /em location.
2. Change the following ORACLE_HOME/j2ee/home/config/server.xml line –
From:
<application name=”ascontrol” path=”../../home/applications/ascontrol.ear” parent=”system” start=”false” />
To:
<application name=”ascontrol” path=”../../home/applications/ascontrol.ear” parent=”system” start=”true” />
3. Change the following ORACLE_HOME/j2ee/home/config/default-web-site.xml line –
From:
<web-app application=”ascontrol” name=”ascontrol” load-on-startup=”true” root=”/em” ohs-routing=”false” />
To:
<web-app application=”ascontrol” name=”ascontrol” load-on-startup=”true” root=”/em” ohs-routing=”true” />
4. Restart HTTP_Server and OC4J to ensure ascontrol is automatically started and routed:
opmnctl stopall
opmnctl startall
5. Validate ASControl page:
http://hostname.domainname:port/em
6. The ascontrol application should be starting automatically and can also be checked from backend.
opmnctl start -app
opmnctl startproc application=ascontrol
opmnctl start -app
Post a Comment
Post a Comment