DDP / OCP Add-ons
When installing an add-on, you must be logged on as the same user who initially installed the application, and must have administrative rights on the Windows machine. For step-by-step instructions, see DDP / OCP Installation Procedure.
Command lines below assume you previously ran the command oware (Windows) or . /etc/.dsienv (Solaris) in the command shell to set the environment correctly. Ensure an existing application is installed, and the local system is down.
You must install to all “nodes” (clients and servers) where you are using the Java client.
All compatible products, including optional addons, are packaged and installed the same way unless there is an update to the web portion of the package (see How to: Perform Patch Upgrades for instructions about updating the web client). A product consists of one or more functional components. All product installations are essentially an installation of the application’s foundation classes (Oware), plus some combination of application and device driver components.
If you upgrade an existing ocp, it can remove all database entries for that product. You must manually check to ensure those removals and any dependencies based on those removals do not impair your application. See also Addons and Oracle.
Also: If you are preserving old files when upgrading components, do not store these old files in the installation source directory, even if they are renamed.