Datasource Name Generation

The Development Client installation creates entries in the registry based on values in the Development Client installer oraparam.ini file located at:

\\<deployment server>\<release>\OneWorld Client Install\install\oraparam.ini

Assuming you have edited the oraparam.ini file as described in the section of this guide entitled: Update the oraparam.ini File, these entries are in the oraparam.ini file:

[Attributes]
DataByPathCode=0|1
LocalDS=Local (this can be any string; the default value is "Local")

The registry entries on the Development Client machine after the Development Client is installed are located under:

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Jdedwards\OneWorld\install.ini\<releasenumber>

In the above location, assuming the oraparam.ini file contains the requisite entries, these registry key values are assigned:

DataByPathCode=0|1LocalDS=some_string 

Using these values, the WLSH4A and WASH4A installers create these datasource entries that point to the EnterpriseOne specs stored in a local database:

1. Entry in the jdbj.ini used by the web client:

   [JDBj - SPEC DATA SOURCE]
   name=
   

2. Entry in the jde.ini used by the Development Client:

   [LOCALWEB]

   Spec Datasource=
   

For WLSH4A, the jdbj.ini file is located in this directory on the Development Client machine:

<installpath>\system\JAS\EA_JAS_80.ear\webclient\WEB-INF\classes\jdbj.ini

For WASH4A, the jdbj.ini is located in this directory on the client machine:

<installpath>\JAS\EA_JAS_80.ear\webclient.war\WEB-INF\jdbj.ini

The rules for generating the spec datasource name in the jdbj.ini and jde.ini are based on the values of the DataByPathCode and LocalDS in the [Attributes] section of oraparam.ini, which is located in this directory of the Development Client installer:

OneWorld Client Install\install

In hierarchical order, the rules are:

1. DataByPathCode is 0 or missing

   This condition indicates a shared local database. The datasource name will be "OneWorld Local" regardless of the value of LocalDS.

   The following table shows the parameters used to create a datasource name that points to a local database:

   ini File	Settings
   oraparam.ini	[Attributes] DataByPathcode=0 or missing LocalDS is missing
   jdbj.ini	[JDBj - SPEC DATA SOURCE] name=OneWorld Local
   jde.ini (Development Client machine)	[LOCALWEB] Spec Datasource=OneWorld Local

2. DataByPathCode is 1 and LocalDS is Missing

   This condition indicates separate databases and LocalDS is missing. The datasource name will be "Local" followed by a hyphen and then the pathcode.

   ini File	Settings
   oraparam.ini	[Attributes] DataByPathcode=1 LocalDS is missing
   jdbj.ini	[JDBj - SPEC DATA SOURCE] name=Local - <pathcode>
   jde.ini (Development Client machine)	[LOCALWEB] Spec Datasource=Local - <pathcode>

3. DataByPathCode is 1 and LocalDS is Set

   This condition indicates separate databases and LocalDS is set. The datasource name will be the value of LocalDS followed by a hyphen and then the pathcode.

   ini File	Settings
   oraparam.ini	[Attributes] DataByPathcode=1 LocalDS=Local
   jdbj.ini	[JDBj - SPEC DATA SOURCE] name=Local - <pathcode>
   jde.ini (Development Client machine)	[LOCALWEB] Spec Datasource=Local - <pathcode>

Caution: The WLSH4A and WASH4A installers will update these strings in the ini files on the Development Client.