R12.2 Highlights
- This release is largely focused on providing new technology stack components, new configuration options, and new system management tools.
- Supports for Online Patching.
- Use of Oracle WebLogic Server instead of AutoConfig for many (but not all) of AutoConfig's previous functions.
- Use of Oracle WebLogic Server instead of Oracle Containers for Java (OC4J).
- Integration between Oracle Enterprise Manager 11g Fusion Middleware Control and Oracle Applications Manager to monitor EBS environments with Oracle WebLogic Server technology.
- Enhanced Workflow Worklist notification and management features.
Configuration Management Tools
- Fusion Middleware Control
- This tool provides a high-level view of Oracle WebLogic Server (WLS)
- It is used to configure Oracle HTTP Server
- Fusion Middleware Control also includes links to Oracle Application Manager and Oracle WebLogic Server Admin Console.
- WebLogic Server Administration Console
- Manage Oracle WebLogic Server settings and managed servers.
- Oracle Application Manager and AutoConfig
- Handles Oracle E-Business Suite settings and Database Settings
What happened to OC4J ? What is Weblogic doing ?
In Oracle E-Business Suite Release 12.2, OC4J has been replaced with Oracle WebLogic Server.
This has resulted in a reduced role for AutoConfig in the configuration of the Oracle HTTP Server and the oacore, oafm, forms and forms-c4ws services.
Configuration Management Changes in Release 12.2
Configuration Activity - Oracle E-Business Suite Database, Concurrent Processing, Oracle Developer 10g, profile options, and other Oracle E-Business Suite components.
Prior to Release 12.2
- Oracle Applications Manager.
In Release 12.2
- Oracle Applications Manager.
Configuration Activity - Changes to HTTP Configuration.
Prior to Release 12.2
- All HTTP configuration was managed via AutoConfig templates.
- Configuration changes were done by editing the respective context variables and subsequently running AutoConfig.
In Release 12.2
- Most HTTP configuration is managed via native Oracle WebLogic Server tools, Fusion Middleware Control, or manually editing of the configuration files.
- Only a limited set of HTTP configuration files are maintained via AutoConfig.
Configuration Activity - Changes to configuration of oacore, oafm, forms and forms-c4ws services.
Prior to Release 12.2
- All configuration settings for the oacore, oafm, forms and forms-c4ws services were managed via AutoConfig templates.
- Configuration changes were accomplished by editing context variables and running AutoConfig.
In Release 12.2
- Properties for the oacore, oafm, forms and forms-c4ws services, including the classpath and JVM arguments, need to be updated through native WebLogic tools such as WebLogic Administration Console.
- The context variable values are used only to set the initial values during managed server creation.
Configuration Activity - Managing JVM instances of the oacore, oafm, forms and forms-c4ws services.
Prior to Release 12.2
- The number of instances of a service was controlled via Oracle Process Manager (OPMN).
- This number could be modified by editing the nprocs context variable, running AutoConfig, then stopping and restarting the services.
In Release 12.2
- Each JVM instance of a service corresponds to a managed server of that service type.
- The number of instances needs to be controlled by explicitly creating or deleting managed servers for the service.
