Editing the Initial oraparam.ini for the Development Client Installer
When a Deployment Server is first installed, a few settings in the oraparam.ini for the Development Client must be configured manually. Follow these steps:
- Navigate to the directory:
<E1_dep_svr_install_directory>\OneWorld Client Install\install
- Make a backup copy of
oraparam.ini
. - Edit the
oraparam.ini
and set the values from the below table:
If the section or keys in the 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. Do not use local paths; rather use the Uniform Naming Convention (UNC) format for paths such as:
\\<deployment server name>\<release>\xxx
Section | Key | Value Description | Value Example |
|
|
Default Oracle Home path into which Development Client will be installed. Users can change this path at installation time. |
|
|
|
Default Oracle Home name of path into which Development Client will be installed. Users can change this name at installation time. |
|
|
|
UNC path to package inf files. |
|
|
|
UNC path including deployment server and share. |
|
|
|
Optional - Used when installing WLSH4A or WASH4A (Tools Releases prior to 9.2.9) or the Development Client (Tools Release 9.2.9) - UNC path to JDBC files - If not specified, installer looks for a directory called JDBC.
|
|
|
|
(Tools Releases prior to 9.2.9) 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. |
|
[Attributes] |
LocalDS |
(Tools Releases prior to 9.2.9) 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 |