Installation Procedure

Copy the Device Driver package files (files ending with .ocp or .ddp) to the target installation’s owareapps directory. To rebuild databases during installation, component packages must be available for importing required seed data. This is why adding a component from CD requires copying the file onto the target system.

Installation is a three-step process:

1. Extract

2. Update / verify the database schema (on database servers only).

3. Seed the database (on database servers only).

Installation scripts do not create the correct environment. You must use the command line oware (on Windows) or . /etc/.dsienv (on Solaris).

The ocpinstall script installs all components, including device drivers, that comprise the application. Use ocpinstall script for all package installations (files that end with ddp or ocp). The installer automates this step-by-step procedure. Here is the syntax for either script (produced with a -? or -h action):

ocpinstall -action [filename] [filename_2] ... [filename_n]

Supported actions are as follows:

-? Display this usage text.

-v Show component package version information. Please note this is
not necessarily the installed version. Use 'showversions' for
installed version information.

-x Extract component files.

-s Import component seed data.
SERVER ONLY

-u Update component database schema. This is a safe schema
evolution process that preserves data.
SERVER ONLY

-l Load database schema. WARNING - this may destroy existing data.
Requires explicit filename(s) provided on command line.
SERVER ONLY

Server only actions will only have effect on database or application servers.

A filename is optional except for the load database schema option (-l).

The filename may be a component file (.ocp or .ddp) or a list file (.ocl) which is essentially a batch operation. If no filename is provided, then the scope varies based on the action. Extraction (-x) or version (-v) will process all component files in the owareapps directory. Seeding (-s) and schema update (-u) will be applied to all extracted (installed) components.

You can do the following with a package file (ocp/ddp):

Full installation -- unpack files and import seed data if running on a database server. For example:

ocpinstall -x packagefile.ocp

ocpinstall -l packagefile.ocp

ocpinstall -s packagefile.ddp

[spacer]

When installing to Oracle, use loaddb -p instead of ocpinstall -l.See Oracle Database Management for more Oracle information.

Import seed data only -- import seed data if running on the server with a database (not a client). For example:

ocpinstall -l packagefile.ocp

ocpinstall -s packagefile.ocp

[spacer]

Append the greater than (>) character and a file name (for example: ocpinstall -s packagefile.ocp > installlog.txt) to the command line if you want to capture installation messages output to a file (here, installlog.txt).

[spacer]

Also: Since rcinit is deprecated in this release, you can clean out a database with the following sequence of command lines:

loaddb

ocpinstall -s [example].ocp