1. Deployment Server Reference Guide for Microsoft Windows
  2. Updating the oraparam.ini File

Updating the oraparam.ini File

The Development Client installer for Tools Releases prior to 9.1 used an installer framework called Exemplar. Installation parameters for Exemplar-based installers were stored in a file called install.inf. When the installer was migrated to OUI with Tools Release 9.1, the installation parameters are now stored in the oraparam.ini file.

When updating a Deployment Server to Tools Release 9.2, the oraparam.ini file is not updated from the existing install.inf file (for Exemplar-based installers) or oraparam.ini file (for OUI-based installers). Therefore, you must manually update some settings in the Tools Release 9.2 oraparam.ini file as described in this section.

This oraparam.ini file resides with the OUI executable called setup.exe in this directory:

\\<deployment server name>\<release>\OneWorld Client Install\install

The oraparam.ini file follows the standard format of ini files for Microsoft Windows: it contains sections with names inside square brackets ( [ ] ) and key/value pairs. The keys and their values are separated by equals signs ( = ).

If the section or keys in the following table do not exist in your oraparam.ini, you must add them along with the values indicated. Be sure that any paths on the Deployment Server can be reached from the Development Client machine; that is, do not use local paths -- use Uniform Naming Convention (UNC) format for paths such as:

\\<deployment server name>\<release>\xxx

Section

Key

Value Description

Value Example

[Oracle]

DEFAULT_HOME_LOCATION

Default Oracle Home path into which Development Client will be installed. Users can change this path at installation time.

E920

[Oracle]

DEFAULT_HOME_NAME

Default Oracle Home name of path into which Development Client will be installed. Users can change this name at installation time.

JDE_E920_Client

[FileLocations]

PackageInfs

Path to package.inf files.

\\depsvr2\E920\package_inf

[FileLocations]

currentReleaseMasterPath

Path including deployment server and share.

\\depsvr2\E920

[FileLocations]

JdbcPath

Optional - Used when installing WLSH4A or WASH4A

- Path to JDBC files

- If not specified, installer looks for a directory called JDBC; this directory is expected up one level from the directory containing the setup.exe file for WLSH4AorWASH4A.

\\depsvr2\E920\My_JDBC

[Attributes]

DataByPathCode

Optional - Used when installing WLSH4A or WASH4A to create the datasource name that points to local data

=1 means that local data is specific to individual pathcodes.

=0 means that local data is shared among all installed pathcodes.

For details, see the appendix of this guide entitled Data by Pathcode.

1

[Attributes]

LocalDS

Optional - Used when installing WLSH4A or WASH4A to create the datasource name that points to local data

For details, see the appendix of this guide entitled  Data by Pathcode.

OneWorldLocal