E1: PKG: JDE.INI and JDBJ.INI Values Changed After Package Deployment (Doc ID 971333.1)

Last updated on JULY 17, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Symptoms

In this example scenario, customer in EnterpriseOne 8.12 application release level. They have custom environments, named QA812 and DATAUPG.

1. After deploying a full package, the jde.ini deployed does NOT have all the settings. The problem is that on the jde.ini the parameter:
DefaultEnvironment=
should be QA812, as previously defined; but after the deployment of the package this setting is changed to DATAUPG.

2. After a package deployment, the jdbj.ini does not have the desired values.
Values in the jdbj.ini file should be:

name=Local - DV812
databaseType=X
server=localhost
serverPort=3372
database=JDELocal_DV812
physicalDatabase=JDELocal_DV812
owner=dbo
lob=false
unicode=true
databaseInstance=JDESSELocal
user=sa
password=

And after the package is deployed, this jdbj.ini is found as :

name=[Variable "dsName" is not defined]
databaseType=[Variable "dbType" is not defined]
server=localhost
serverPort=3372
database=JDELocal_DV812
physicalDatabase=JDELocal_DV812
owner=dbo
lob=false
unicode=true
databaseInstance=[Variable "dbInstance" is not defined]
user=sa
password=

 

NOTE: Although the example above is for E1 8.12 apps release level, this solution is valid for latest E1 apps release level as 9.1.x).

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms