{"id":1125,"date":"2009-03-10T15:41:29","date_gmt":"2009-03-10T19:41:29","guid":{"rendered":"http:\/\/onlineappsdba.com\/index.php\/2009\/03\/10\/application-tier-services-in-oracle-apps-r12\/"},"modified":"2009-03-10T15:41:29","modified_gmt":"2009-03-10T19:41:29","slug":"application-tier-services-in-oracle-apps-r12","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2009\/03\/10\/application-tier-services-in-oracle-apps-r12\/","title":{"rendered":"Application Tier Services in Oracle Apps R12"},"content":{"rendered":"

\"Oarcle<\/a><\/p>\n

Services<\/strong> (new concept introduced in R12) define the set of processes<\/strong> that will be started on each application node. These services can be activated or deactivated on a specific application tier\/node.<\/p>\n

.<\/p>\n

Type of Application Services<\/u><\/strong>
\nApplication tier processes are broadly\u00a0classified in to five type of Services<\/p>\n

i) Root Service<\/strong>\u00a0 – Oracle Process Manager and Notification (OPMN) is part of Oracle Application Server 10G R2\/R3. OPMN is used for inter process communication (between OC4J, HTTP Server), death detection and start\/stop of Services for 10g R3.<\/p>\n

ii) Web Entry Point Services<\/strong> – HTTP Server is part of Oracle Application Server 10G R3 and built on Apache<\/strong> (aka Oracle Apache. All web request to R12 first hit HTTP Server.<\/p>\n

iii) Web Application Services<\/strong> – OACORE OC4J, Forms OC4J, OAFM OC4J – These are set of 3 OC4J<\/strong> (Oracle Container for J2EE) to run application.<\/p>\n

iv) Batch Processing Services<\/strong> – This set of service consist of Apps Listener<\/strong> (FNDFS & FNDSM), Concurrent Manager<\/strong>, Fulfillment<\/strong> Server and Interaction<\/strong> Server\u00a0<\/p>\n

v) Other Services<\/strong> – Oracle Forms<\/strong> Service, Forms Metric Client\/Server<\/strong> and Mobile Web Application<\/strong> (MWA)\u00a0Service<\/p>\n

\u00a0.<\/p>\n

Process\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0—>\u00a0\u00a0 Services –> Startup\u00a0Script –>\u00a0Context parameter <\/u><\/strong><\/p>\n

a)<\/strong> Oracle Process Manager –\u00a0 Root Service\u00a0 – adopmnctl.sh<\/strong>– s_root_status, s_opmnstatus
\nb)<\/strong> Oracle HTTP Server\u00a0 – Web Entry Point Service – adapcctl.sh<\/strong>– s_web_entry_status, s_oacorestatus
\nc)<\/strong> OACORE OC4J – Web Application Services – adoacorectl.sh<\/strong>– s_web_applications_status s_oacorectrl
\nd)<\/strong> FORMS OC4J – Web Application Services – adformsctl.sh<\/strong>– s_web_applications_status, s_formsstatus
\ne)<\/strong> OAFM OC4J – Web Application Services – adoafmctl.sh<\/strong>– s_web_applications_status, s_oafmstatus
\nf)<\/strong> Concurrent Manager –\u00a0\u00a0 Batch Processing Service – adcmctl.sh<\/strong>– s_batch_status, s_concstatus
\ng)<\/strong> Apps Listener –\u00a0 Batch Processing Service – adalnctl.sh<\/strong>– s_batch_status, s_tnsstatus
\nh)<\/strong> Interaction Center (ICSM) –\u00a0 Batch Processing Service – ieoicsm.sh<\/strong>– s_batch_status, s_icsmctrl
\ni)<\/strong> Fulfillment Server –\u00a0 Batch Processing Service – jtffmctl.sh<\/strong>– s_batch_status, s_jtffsstatus
\nj)<\/strong> Forms Server –\u00a0\u00a0 Other Service – adformsrvctl.sh<\/strong>– s_other_service_group_status , s_formsserver_status
\nk)<\/strong> Metric Client –\u00a0\u00a0 Other Service – adfmcctl.sh<\/strong>– s_other_service_group_status , s_metcstatus
\nl)<\/strong> Metric Server –\u00a0\u00a0 Other Service – adfmsctl.sh<\/strong>– s_other_service_group_status , s_metsstatus
\nm)<\/strong> Mobile Web Application (MWA) –\u00a0\u00a0 Other Service – mwactlwrpr.sh<\/strong>– s_other_service_group_status , s_mwastatus<\/p>\n

.<\/p>\n

Key points to note<\/u><\/strong><\/p>\n

1)<\/strong> When you select Root services, Web Services are automatically selected i.e. First three Services Root, Web Entry Point<\/strong> and Web Application Services<\/strong> can only be enabled or disabled together.
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 If you want Web Entry Point Services, Web Application Services, and Root Services to be installed on different nodes then use autoconfig after installation.<\/p>\n

2.<\/strong> In R12 with introduction of Services there is NO<\/strong> concept of Forms node<\/strong> or Web Node<\/strong>.<\/p>\n

3. <\/strong>With default installation all services Root, Web Entry Point, Web Application Services, Batch Processing and Other\u00a0services are enabled.<\/p>\n

.\u00a0<\/p>\n

References<\/u><\/strong>\u00a0<\/p>\n