Using AutoConfig to Manage Oracle E-Business Suite Services
- In previous Oracle E-Business Suite releases, the Applications services were categorized into service groups according to the type of service provided.
- In Oracle E-Business Suite Release 12.2, this concept has been extended by the introduction of additional services and service groups.
- Web Administration Service Group has been introduced in Release 12.2 and it contains WebLogic Administration server. It is not supported to enable WebLogic Administration server on any other Application tier node except the node on which it was enabled during Rapid Install.
- Root Service Group now comprises Node Manager and not Oracle Process Manager (OPMN)
- In R12.2 OPMN only manages Oracle HTTP Server and it is now part of the Web Entry Point Services Group
|Service Group||Service(s)||Service Control Script|
|Root Service||Node Manager||adnodemgrctl.sh|
|Web Administration||WebLogic Admin Server||adadminsrvctl.sh|
|Web Entry Point Services||Oracle HTTP Server||adapcctl.sh|
|Oracle Process Manager||adopmnctl.sh|
|Web Application Services||oacore||admanagedsrvctl.sh|
|Batch Processing Services||Oracle TNS Listener||adalnctl.sh|
|Other Services||Forms Server||adformsrvctl.sh|
|Oracle MWA Service||mwactlwrpr.sh|
Modifying AutoConfig-Managed Services and Service Groups
- Depending on the requirement of a particular Applications instance, it is possible to modify the set of Applications services and service groups that will be started and stopped via the adstrtal and adstpall scripts respectively.
- Check the value of the 'status' context variable corresponding to the service group and make it enabled/disabled as required.
- In case of the oacore, oafm, forms and forms-c4ws services, there may be more than one instance of the service. To cater for this, check that the context variable corresponding to the name of the service contains the name of the managed server to be enabled. If not, add it to the list, using a comma as a separator.