Comparing Typical and OEM-Compliant Packaging
OUAF-based service packs available on Oracle Support are typically packaged in the format pBUG_NUMBER_VERSION.zip. The package includes the Framework installer and application installer. A Framework rollup installer may also be packaged with it.
Each installation has two parts: the database installation and the application installation. Separate installers are therefore available for each type of installation.
The following image illustrates the structure of a typical OUAF service pack:
| Filename | Contents | Description |
|---|---|---|
| *Oracle-Database-MultiplatForm.zip | *Oracle-Database-MultiplatForm | Contains framework and application installer for database |
| *FW-PREREQ- MultiplatForm.zip | *FW-PREREQ- MultiplatForm.jar | Contains the Framework application rollup installer |
| <application>-<version>- MultiplatForm.zip | <application>-<version>- MultiplatForm.jar | Contains application installer |
| FW-<version>- MultiplatForm.zip | FW-<version>- MultiplatForm.jar | Contains the Framework application installer |
OEM-Compliant Packaging Structure
A service pack must be packaged in a different way to enable installation by the Enterprise Manager for Oracle Utilities plugin.
Structurally, it must include the following three top-level items:
- App folder. This folder contains application installers, e.g., the edge product installer, the Framework installer, and the Framework rollup installer (if any).
- DB folder. This folder contains database installers for OUAF and the edge product.
- Metadata.xml. This file contains the sequence of execution of the installers. This needs to be created separately and then included in the final Service Pack zip file.
The following image illustrates a compliant service pack structure:
The next topic describes the steps involved in repackaging an existing Service Pack to make it OEM compliant.