Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps

Thursday, July 19, 2007

During an R12 Multi-node Install Why Do All Middle Tiers Run All Services?

Metalink note 415385.1 explains the reason for something queer which I observed during an R12 multi node install. All middle tiers run all services irrespective of what you have defined for them. Here's a copy paste from the relevant section in the note, which explains why this is happening:

In R12, the concept for Applications Nodes has changed. When installing R12 with multiple nodes. all the nodes are now set as 'Y' in FND_NODES.

This occurs because in R12, concept of unified APPL_TOP is introduced which means everything is laid down on all servers.


From the APPL_TOP perspective, all the servers on a Multi-node environment will have the same files and can now potentially start any service if needed. In some cases, additional configuration will be required before this can be done since there can be profiles, etc associated with each server.

For R12, the only difference between the servers, are the Services that have been activated on each node.

The services are identified by the variables on the /service_group/ section in the Apps Context File:

Root Service Group : s_root_status
Web Entry Point Services : s_web_entry_status
Web Application Services : s_web_applications_status
Batch Processing Services : s_batch_status
Other Service Group : s_other_service_group_status
Depending on the value of these variables (enabled or disabled), adstrtal.sh / adstpall.sh will only start/stop the services associated with them, ignoring the rest.

For example, if a node has only /s_batch_status/ "enabled" and the rest of the services are disabled, when you run adstrtall.sh on that server it will only start the Concurrent Managers and the TNS Listener for Apps.

NOTE: If you experience the problem where all of the service_group variables are enabled on all application tiers make sure you are using the latest version of the Rapid Install StartCD (12.0.0.21) shipped with Patch 5766801.

3 comments:

Manoj said...

I spent few hours trying to understand my R12 multi-node install was having Y in all those "Support_(ComponentName)" columns, until I hit upon this blog.

However, just as a small add-on, the following query may be helpful to identify what all components are hosted on which all servers. This may be helpful for releases prior to R12

SQL> col webhost format a25
SQL> select node_name, status, webhost, support_db d, support_web w, support_admin a, support_cp c, support_forms f from fnd_nodes;

NODE_NAME S WEBHOST D W A C F
------------------------------ - ------------------------- - - - - -
DB01 Y Y N N N N
APP2 Y app2.xyz.com N Y Y Y Y
AUTHENTICATION N N N N N
CONCMGR Y concmgr.xyz.com N N N Y N
EXTRANET N extranet.xyz.com N Y N N N

杨佳 said...

I am wondering if setting s_root_status to 'Y' means ADMIN_SERVER is 'Y' in fnd_nodes tables.
Does these 2 have such relationship?

杨佳 said...

I am wondering if setting s_root_status to 'Y' means ADMIN_SERVER is 'Y' in fnd_nodes tables.
Does these 2 have such relationship?