Technical and Functional Changes in Oracle E-Business Suite 12.2
Upgrading to EBS 12.2 brings changes to your system architecture and the way you deploy and patch the system. Here are some of the major technical changes you should start taking into account now before you begin your EBS 12.2 upgrade.
Changes in E-Business Suite 12.2’s Architecture
1. 12.2 Dual File Systems: There are two complete file systems in the EBS 12.2 environment: The “run” file system is the current system in use running the application, and the “patch” file system is responsible for either patching or awaiting the start of the next online patching cycle. This is a new feature in EBS 12.2’s architecture.
2. EBS 12.2’s Application Tier: Unlike database and desktop tiers, the architecture of the application tier has changed significantly in EBS 12.2. This tier is made up of three servers: Web services, forms services, and concurrent processing server.
The application tier essentially has two roles: It’s responsible for hosting the various servers and service groups that process the business logic, and it manages communication between the desktop tier and the database tier.
3. Web Services: A big change in EBS 12.2 is the employment of the Oracle WebLogic Server for many system management and configuration tasks. Configuration using the Oracle WebLogic Server Console in EBS 12.2 supplements, but does not replace, the traditional use of the autoconfiguration tool. Together, these tools provide comprehensive management capabilities for the new EBS 12.2
Introducing Your New Best Friend: Online Patching
EBS 12.2 introduces online patching, which is designed to drastically reduce downtime—especially when compared to the downtime associated with previous releases for things like critical patch updates and other bug fixes.Key features of E-Business Suite 12.2’s online patching:
Key features in EBS 12.2's online patching include:
- All patching operations are not carried out while applications are still in use and users are actively online.
- Patching is performed using the new AD Online Patching utility.
- A short period of downtime is required, but this is usually no longer than the standard restart period. This means downtime is now a matter of minutes, not hours, and you can choose when you want the downtime to occur.
- Patching now occurs in a cycle, which consists of several smaller phases: prepare, apply, finalize, cutover, and cleanup.
Understanding and Planning for the Functional Impact of 12.2.
Upgrading to EBS 12.2 also affects the way your existing products work after the upgrade, as well as the look and feel of the user interface. These functional, business-related changes can have a big impact on the way you use the products day-to-day.
To prepare for the functional impact of EBS 12.2, make sure you:
- Provide reasons for the change, and how certain areas of your business will benefit from new functionality.
- Evaluate any changes that may occur to your user interfaces or menu options, and how your team can navigate them.
- Address any downtime complications, and how you can potentially reduce its impact.
- Assess any functionality that may be temporarily disabled and made obsolete from the upgrade. Here’s a full list of obsolete products in the EBS 12.2 release.
Preparing for Customizations
If you have customized environments, they’ll need special attention during your upgrade to EBS 12.2.
Here are a couple things you can do now to preserve your customizations and minimize the impact of the upgrade:
- Maintain complete documentation for customizations.
- Back up your customizations before the upgrade.
Looking for More Resources?
No two EBS systems are alike. There’s a good chance the version you’re running, the data your business houses, and the customizations you’ve built, is different from the business next door.
Check out our full guide on how to choose the best path to EBS 12.2, and how to prepare for and execute the upgrade.