Oracle E-Business Suite Release 12.2 introduces significant changes in its patching procedures and the technology stack. As a result, additional preparation steps must be completed for customizations. This section describes the technical preparation required for customizations in implementing Online Patching as well as Oracle WebLogic Server as the new J2EE Server in the Oracle E-Business Suite Release 12.2 technology stack.
Database Object Development Standards for Online Patching
Developer Guidelines for Customizations with Online Patching
Java Code Changes for Release 12.2
Preparation Steps before Upgrade
Create a Customizations Catalog.
Creating a catalog of your customizations allows you to manage your upgrade project in a more organized way.
Identify customized database components that need updates in preparation for Release 12.2.
Use the utilities described in the section Utilities for Online Patching Enablement.
Prepare the database components according to the Release 12.2 guidelines.
In this step you will implement the recommended changes to your customizations. The majority of the modifications your database objects require will be performed automatically by the Oracle E-Business Suite Online Patching preparation process. However, before you begin preparation process you need to make sure the following steps are completed:
Make sure your customizations are associated with an application registered in Oracle E-Business Suite. Refer to Setting Up Your Application Framework.
Implement the recommended updates in the Online Patching Enablement-Readiness Report - This report, mentioned above, checks all the database objects in the schemas that have been registered in your Oracle E-Business Suite instance. Database objects that do not comply with the Release 12.2 development standards are listed in the report output.
The majority of the database objects will be modified and fixed automatically by the Release 12.2 Preparation Process, executed after the Release 12.2 Upgrade Process. The items that will not be automatically fixable are listed by this Online Patching Enablement-Readiness Report. The report provides recommendations on how to fix them. These modifications need to be implemented manually.
Make sure to test your customization after implementing such recommendations in order to validate the expected functionality of the customization.
Identify customized components on the application tier that need updates to comply with the Release 12.2 guidelines.
See also:Extending Seeded Java Rule Function, Oracle E-Business Suite Integrated SOA Gateway Developer's Guide
Back up your instance after implementing all the recommended updates.
Oracle recommends you back up your instance after implementing the recommended updates. This backup would be your milestone environment for Release 12.2 that is ready for the upgrade.
Upgrade Steps
Execute the upgrade process.
Follow the instructions in the Oracle E-Business Suite Upgrade Guide for your release to perform the upgrade process.
Prepare the application tier components according to the Release 12.2 guidelines.
Customizations in the application tier can be implemented in:
Oracle Developer technologies: Forms and Reports
Java technologies: Oracle Application Framework pages, JavaServer Pages (JSPs), Web Services, and other supporting libraries.
In Release 12.2 the following guidelines need to be followed for these components, make sure you review that all your customizations comply with these guidelines:
Any component that references Oracle E-Business Suite tables must go through a synonym present in the APPS schema. This guideline applies to all programmatic references.
Some Java-based libraries have been deprecated, replaced or updated. Please review Java Code Changes for Release 12.2 and Extending Seeded Java Rule Function, Oracle E-Business Suite Integrated SOA Gateway Developer's Guide for additional information.
Your customizations must be compliant with the J2EE specifications version (Servlet APIs, EJB, and so on). See the WebLogic Server documentation (https://www.oracle.com/middleware/technologies/weblogic.html) for more information.
Recompile your code with Java Version 1.6.
Ensure that your custom files are in the appropriate locations in the file system. See: Working with Editions and the Oracle E-Business Suite Concepts Guide.
Test the customizations after the upgrade.
After testing the base Oracle E-Business Suite product functionality for Release 12.2, test your customizations.