When a Development Client is installed, it may be configured so that each pathcode on the client has its own local database or for all pathcodes to share the same local database. Initially, JD Edwards EnterpriseOne is set up for each pathcode on a Development Client to have its own database. This section describes how to configure these scenarios.
This appendix discusses these topics:
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
The entries in the oraparam.ini
are:
[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\Jdedwards\OneWorld\install.ini\<releasenumber>
In the above location, the registry key values are assigned:
DataByPathCode=0|1LocalDS=some_string
Using these values, the OH4A, H4A7, or H4A85 installer creates these datasource entries that point to the EnterpriseOne specs stored in a local database:
Entry in the jdbj.ini
used by the web client:
[JDBj - SPEC DATA SOURCE] name=
Entry in the jde.ini
used by the Development Client:
[LOCALWEB]
Spec Datasource=
For OH4A, the jdbj.ini
file is located in this directory on the Development Client machine:
<installpath>\system\OC4J\j2ee\home\applications\webclient.ear\webclient\WEB-INF\classes\jdbj.ini
For H4A7 and H4A85, 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:
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 |
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 |
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 |
DataByPathcode=1 LocalDS is missing |
jdbj.ini |
[JDBj - SPEC DATA SOURCE] name=Local - <pathcode> |
jde.ini
(Development Client machine) |
[LOCALWEB] Spec Datasource=Local - <pathcode> |
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 |
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 OH4A, H4A7, and H4A85 installers look for exact strings to replace. Therefore, you should not change these strings manually; you must allow the installer to change them.String in the JDE.ini template:
#Spec Datasource=OneWorld Local
String in the jdbj.ini template:
;name=OneWorld Local
The package build process uses a value in the c:\Windows\jde.ini
on the build machine when building a full package to determine the directory structure that will be created on target workstations when the package is installed. This key and setting are:
[INSTALL] DataByPathCode=0|1
The directory structure that is formed by the package build based on this setting is stored in the inf
file for the package.
The following table shows what the directory structure would look like when the built package is installed on a workstation using these example values:
Installation Directory
c:\E910
Pathcodes
DV910
PY910
Note:
These values are only examples; additional pathcodes could be included.DataByPathCode | Directory Structure | Comment |
---|---|---|
DataByPathCode=0 | c:\E910\JDEData |
Contains database shared among all pathcodes |
c:\E910\DV910 |
||
c:\E910\PY910 |
||
DataByPathCode=1
This is the default value for package build. |
c:\E910\DV910\JDEData |
Contains database for DV910 |
c:\E910\PY910\JDEData |
Contains database for PY910 |
Caution:
The value of theDataByPathCode
key in the [INSTALL]
section of the jde.ini
on the machine(s) on which any packages are built MUST match the value of the DataByPathCode
key in the [Attributes]
section of the oraparam.ini
in \OneWorld client Install\install
directory for the Development Client installer.As noted in the preceding sections of this appendix, the name of the Spec Data Source stored in the jdbj.ini
is determined based on the values of the DataByPathCode and LocalDS keys in the oraparam.ini
file. Additional entries in the jdbj.ini
complete the definition of the datasource. These entries are copied to the jdbj.ini
by the OH4A, H4A7, or H4A85 installer and come from the [DB SYSTEM SETTINGS - SECONDARY]
section of the Development Client jde.ini
.
The following table shows the mapping between Entries in the jde.ini
and jdbj.ini
.
jde.ini | jdbj.ini |
---|---|
DB SYSTEM SETTINGS - SECONDARY | JDBj - SPEC DATA SOURCE |
Type | databaseType |
DatabaseInstance | databaseInstance |
During the installation of the Development Client, the jde.ini
file for all the Development Clients is created according to specific rules. Refer to the JD Edwards EnterpriseOne Development Client Installation Guide for Oracle Application Server (OAS) and WebSphere Application Server (WAS) Express for details.
The following table describes the only changes that the administrator might need to make to affect the definition of the datasource for the local database.
File | Setting | Comment |
---|---|---|
\\<deployment server name>\<release>\OneWorld Client Install\misc\jde.ini |
[DB SYSTEM SETTINGS - SECONDARY] Type DatabaseInstance= |
Type defines the type of the local database.
DatabaseInstance defines the instance name of the local database. |
[INSTALL]DataByPathCode |
0 = share database among pathcodes
1 = separate databases for each pathcode This setting is only used when building a full package. |
|
\\<deployment server name>\<release>\OneWorld Client Install\misc\<pathcode>.ini |
[DB SYSTEM SETTINGS - SECONDARY] Type DatabaseInstance |
Any values in this file override their respective values in this file:
Type defines the type of the local database. DatabaseInstance defines the instance name of the local database. |
\\<deployment server name>\<release>\OneWorld Client Install\install\oraparam.ini |
[Attributes]DataByPathCode LocalDS |
0 = share database among pathcodes
1 = separate databases for each pathcode This o ptional datasource prefix is only used if DataByPathCode=1. |