Apps Services start & shut procedures R11 & R12
In R11 Apps , how to start, verify and stop the apps service.
from application tier,
First verify from the database , where and which components are registered in the which node.
select * from apps.fnd_nodes;
login to the particular host and check the serivce.
cd $COMMON_TOP/admin/scripts
Apache Process:
===============
$./adapcctl.sh start (to start the service)
$ps -eaf|grep http (to verify the service from os level)
$./adapcctl.sh stop (to stop the serivce)
Apps Listener:
=============
$./adalnctl.sh start (to start the service)
$ ps -eaf|grep tns (to verify the service from OS level)
$./adalnctl.sh stop (to stop the service)
Forms Service:
==============
$./adfrmctl.sh start (to start the service)
$ ps -eaf|grep -i f60 (to verify the service from os level)
$./adfrmctl.sh stop (to stop the service)
Reports Service:
================
$ ./adrepctl.sh start (to start the service)
$ ps -eaf|grep -i rep60 (to verify the service from OS level)
$ ./adrepctl.sh stop (to stop the service)
Discover Service:
=================
$ ./addisctl.sh start (to start the service)
$ ps -eaf|grep -i dis (to verify the service from os level)
$ ./addisctl.sh stop (to stop the service)
Concurrent Manager :
===================
$ ./adcmctl.sh start apps/<appspassword> (to start the service)
$ ps -eaf|grep -i fndlibr (or ps -eaf|grep -i cpmgr) [to verify from os level]
$ ./adcmctl.sh stop apps/<appspassword> (to stop the service)
You can verify for all the above process by executing the below procedure, we should see the service is runnning and also when started or stopped we need ensure the status code is always "0" other than "0" stands for some error)
Managing application services in Apps R12 system:
In R12 the scripts are available under $INST_TOP/admin/scripts (or) $ADMIN_SCRIPTS_HOME
or all the scripts the LOG files are located in $INST_TOP/logs/appl/admin/log.
Apps listener :
--------------
$ ./adalnctl.sh {start|status|stop}
Web Server (Apache):
---------------------
$ ./adapcctl.h {start|status|stop}
Note : in R11 , the apache script is customized in such way that it takes care of Jserv, modplsql and TCF socket automatically when it is started up. But in R12 , it starts only the Apache process not the other components, which are taken care by OC4J.
And in R12 we have one more feature, starting up the Apache with Restricted mode which can be done with the below script.
$./adaprstctl.sh {start|stop|status}
Forms Service:
---------------
$./adformsctl.sh {start|stop|status} ==> when you use this script, by default it starts the forms in socket mode.
$./adformsrvctl.sh {start|stop|status} ==> It will start in the servlet mode.
NOte: Feature only in R11 Forms Metric Client it is used for the forms load balancing. if we see the forms are done with load balancing we can start and verify the process using,
$./adfmcctl.sh {start|stop|status}
$ps -eaf|grep -i d21c60 (process from os level)
Reports were decomissioned in R12.
Concurrent Manager Service:
----------------------------
$./adcmctl.sh {start|stop|status} apps/<appspwd>
We can also start using the startmgr.sh script in R12. in R11 we need to execute the command manually.
OC4J Container (additional feature in R12)
------------------------------------------
In R12 Jserv has been replaced with OC4J, for managing the OACORE OC4J the script is
$./adoacorectl.sh {start|stop|status}
OAFM (Oracle Applications Fusion Middleware), the OC4J script is
$./adoafmctl.sh {start|stop|status}
OPMN
$./adopmnctl.sh {start|stop|status}
To start and stop alll the application Services in R11 / R12 the scripts are same.
$./adstrtal.sh apps/<appspwd>
$./adstpall.sh apps/<appspwd>
|
No comments:
Post a Comment