Sef
VIP Member
Here some suggestions for additions/changes to the JDE.INI file.
These are merely suggestions and are generally only applicable to address specific issues.
Before applying these changes, please investigate the related threads/documentation and test thoroughly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(collated by Dave Helsley)
To re-activate OW tools
[OMW]
PH9001_WORKFLOW_TRANSFER=U
P9864A_ACTIVERA_TRANSFER=S
P9860_OBJECT_LIBRARIAN=E
P9864_RECORD_COPY=O
P98603_PROMOTION_MANAGER=M
R9830512_UBE_VERSION_COPY=W
(suggested by Dave Rammer)
To prevent Commitment problems in commitment processing
[DB SYSTEM SETTINGS]
OracleServerHandleReuse=0
Also See article ODS-01-0069 (Commit Failed - invalid Cursor Error)
(Suggested by Larry Jones)
To prevent passwords being visible using the grep command
[SECURITY]
ServerPswdFile=TRUE
[NETWORK QUEUE SETTINGS]
QUser=JDE
QPassword=<JDE Password>
QEnv=PD7333
QueueDelay=30
---------------
RunOneWorld.sh:
---------------
change the lines in the script with "runque.sh" in them. Currently they look something like:
$SYSTEM/bin32/runque.sh $OWUSR $OWPWD $OWENV $OWQUE1 UBE 15
Remove the first 3 arguments (JDE User, Password, and Environment) from each of the runque.sh lines.
Note that there are other lines containing User and Password values ($SYSTEM/bin32/cleanup $OWUSR $OWPWD $OWENV $OWQUE2). Don't try to remove this information from the cleanup lines.
---------------
Stop and Start OneWorld and your UID/PWD info will no longer appear on "ps" output.
Don't forget to make sure that only JDE accounts have read access to JDE.INI
(suggested by many users, text taken ex post from Paul (Badda Bing))
To allow the usage of UTB through WTS
You can add OWDEVELOPER=TRUE (Case sensitive) into the [DEBUG] section of the client's JDE.INI file.
There is another way that involves creating a local group on the Term server called OWDEVELOPER and adding the users to this but we could never get that to work.
This will allow users to run all of the dev tools, namely rda.exe, fda.exe, utb.exe etc etc.
If you add this to the deployment servers JDE.INI file it will allow you to run Term Service in admin mode (Win2000) on the deployment server, although that is unsupported. We experience errors when trying to run VNC on the dep server so we had to use it.
Effectively this tells JDE that it is not in fact running a term services session therefore allows access to the design tools as if you where a fat client.
(Note by Jenga61688): As of SP 16, UTB will run on Citrix without any jde.ini changes or anything
else. It was enabled on Citrix with SAR 5038438
(suggested by Scottw)
To display TAM files in UTB
[INTERACTIVE RUNTIME]
TAMMENUS=Show
(Suggested by Larry Jones and Libbi Fletcher)
To speed up UBE performance
In the JDE.INI file (oneworld/b7333/ini/) find the [LOCK MANAGER]section and make sure that the RequestedService parameter is set to NONE, per oti-99-0024. This has the effect of speeding up transaction processing for some UBEs (this should only be changed on the server's JDE.INI file).
You may want to change the jde.INI file in the Lock Manager section to
Requested Service = *none. It took us from 20 hours for a repost to 1 hour.
(Suggested by Sheena Bamsey)
To Turn on Security History
In OneWorld you can set "security history" on, which writes to F9312.
Set Enterprise Server JDE.INI [Security] stanza, History=1. This logs to
F9312, which should be monitored and purged regularly
(Suggested by Paul Clark)
To Promote version between environments
The JDE.INI file has to be modified as its an upgrade report:
[OMW]
R9830512_UBE_VERSION_COPY=W
Create a custom version, this one copies all interactive custom version from one PathCode to another:
Processing Options are:
1: 1
2: Blank
3: 1
4: 1
Data Selection:
Where BC Version History <> ZJDE0000-ZJDE9999
And BC Version History <> XJDE0000-XJDE9999
And BC Version History <> ZJDEAAAA-ZJDEZZZZ
And BC Version History <> XJDEAAAA-ZJDEZZZZ
And BC Version List Mode = 1
Run it locally and enter the Source and Destinations at runtime.
(Suggested by Ian Cooke)
To display the Exit Bar by default at first start up
[INTERACTIVE RUNTIME]
PWndLocation=66,66,666,477,327681
Additional comment by Christian Audet
(From J.D. Edwards OneWorld: A Developer's Guide (Appendix F
)
PWndLocation:
The First four values define the location of OneWorld Explorer on the client's screen. The fifth value controls whether the exit bar and type-ahead is enabled. The valid values for the fifth value are as follows : 1114113, for disabling the exit bar and type-ahead; 65537, for disable the exit bar and enabling the type-ahead features; 1376257, for enabling the exit bar and disabling type-ahead features; and 327681, for enabling the exit bar and type-ahead features.
(Suggested by Ian Cooke)
To force locally run UBE's to use a separate database connection
Because local UBEs are running through OExplore (the same as all
interactive applications), the entire OW system comes to a virtual halt when the UBE performs a large data selection.
To overcome this issue, under the UBE section of your ini include the following line:
UBEThread=0
This will cause a separate application (Ubeprint) to run on your PC.
Both Oexplore & Ubeprint will then have separate connections to your
database
(Suggested by Richard Manning)
To change Check Kernel settings (AS/400)
While the Enterprise Server is running, it passes messages between the network jobs and the kernel jobs. By default, the network job will verify that each of the call object kernels is running, every 10th time it sends or receives a message. J.D. Edwards has released an enhancement in SAR #5128281 with SP16.1, which enables you to customize this verification to occur less frequently. This change reduces the amount of overhead within the Enterprise
Server and improves the overall response time. You can choose to check for a kernel’s health every 1,000 times there is a message or, say, 5,000 times there is a message; the trade-off is performance versus prompt knowledge of a kernel problem. While you do want to continue to monitor your kernels, if you have a heavy load of transactions, you might consider increasing this
number to have it check for kernel health less frequently. In the [JDENET] section, add the new line, checkKrnlHealth with the value that you choose,
as in the example below.
100 user example:
[JDENET]
checkKrnlHealth=1000
(Suggested by Larry Jones)
To prevent the occurance of 'Commit failed' errors in transaction processing
This issue is caused when Oracle forfeits the cursors created in the previous connection when OneWorld middleware creates a new connection.
Add the following to the JDE INI on both the client machine and the server:
[DB SYSTEM SETTINGS]
OracleServerHandleReuse=0
Client machine needs to be on SP11.1 or higher. Server needs to be at SP16 or higher.
NOTE: Both client and server need to be at the same SP level. If logic is processed on the server then both client and server need to be at SP16 or higher.
MORE TO FOLLOW
Sef van den Nieuwelaar
Australia
B732 on NT, XE on NT, B732/A73 on AS400, B733 on NT<P ID="edit"><FONT SIZE=-1>Edited by Sef on 3/7/02 03:58 PM.</FONT></P>
These are merely suggestions and are generally only applicable to address specific issues.
Before applying these changes, please investigate the related threads/documentation and test thoroughly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(collated by Dave Helsley)
To re-activate OW tools
[OMW]
PH9001_WORKFLOW_TRANSFER=U
P9864A_ACTIVERA_TRANSFER=S
P9860_OBJECT_LIBRARIAN=E
P9864_RECORD_COPY=O
P98603_PROMOTION_MANAGER=M
R9830512_UBE_VERSION_COPY=W
(suggested by Dave Rammer)
To prevent Commitment problems in commitment processing
[DB SYSTEM SETTINGS]
OracleServerHandleReuse=0
Also See article ODS-01-0069 (Commit Failed - invalid Cursor Error)
(Suggested by Larry Jones)
To prevent passwords being visible using the grep command
[SECURITY]
ServerPswdFile=TRUE
[NETWORK QUEUE SETTINGS]
QUser=JDE
QPassword=<JDE Password>
QEnv=PD7333
QueueDelay=30
---------------
RunOneWorld.sh:
---------------
change the lines in the script with "runque.sh" in them. Currently they look something like:
$SYSTEM/bin32/runque.sh $OWUSR $OWPWD $OWENV $OWQUE1 UBE 15
Remove the first 3 arguments (JDE User, Password, and Environment) from each of the runque.sh lines.
Note that there are other lines containing User and Password values ($SYSTEM/bin32/cleanup $OWUSR $OWPWD $OWENV $OWQUE2). Don't try to remove this information from the cleanup lines.
---------------
Stop and Start OneWorld and your UID/PWD info will no longer appear on "ps" output.
Don't forget to make sure that only JDE accounts have read access to JDE.INI
(suggested by many users, text taken ex post from Paul (Badda Bing))
To allow the usage of UTB through WTS
You can add OWDEVELOPER=TRUE (Case sensitive) into the [DEBUG] section of the client's JDE.INI file.
There is another way that involves creating a local group on the Term server called OWDEVELOPER and adding the users to this but we could never get that to work.
This will allow users to run all of the dev tools, namely rda.exe, fda.exe, utb.exe etc etc.
If you add this to the deployment servers JDE.INI file it will allow you to run Term Service in admin mode (Win2000) on the deployment server, although that is unsupported. We experience errors when trying to run VNC on the dep server so we had to use it.
Effectively this tells JDE that it is not in fact running a term services session therefore allows access to the design tools as if you where a fat client.
(Note by Jenga61688): As of SP 16, UTB will run on Citrix without any jde.ini changes or anything
else. It was enabled on Citrix with SAR 5038438
(suggested by Scottw)
To display TAM files in UTB
[INTERACTIVE RUNTIME]
TAMMENUS=Show
(Suggested by Larry Jones and Libbi Fletcher)
To speed up UBE performance
In the JDE.INI file (oneworld/b7333/ini/) find the [LOCK MANAGER]section and make sure that the RequestedService parameter is set to NONE, per oti-99-0024. This has the effect of speeding up transaction processing for some UBEs (this should only be changed on the server's JDE.INI file).
You may want to change the jde.INI file in the Lock Manager section to
Requested Service = *none. It took us from 20 hours for a repost to 1 hour.
(Suggested by Sheena Bamsey)
To Turn on Security History
In OneWorld you can set "security history" on, which writes to F9312.
Set Enterprise Server JDE.INI [Security] stanza, History=1. This logs to
F9312, which should be monitored and purged regularly
(Suggested by Paul Clark)
To Promote version between environments
The JDE.INI file has to be modified as its an upgrade report:
[OMW]
R9830512_UBE_VERSION_COPY=W
Create a custom version, this one copies all interactive custom version from one PathCode to another:
Processing Options are:
1: 1
2: Blank
3: 1
4: 1
Data Selection:
Where BC Version History <> ZJDE0000-ZJDE9999
And BC Version History <> XJDE0000-XJDE9999
And BC Version History <> ZJDEAAAA-ZJDEZZZZ
And BC Version History <> XJDEAAAA-ZJDEZZZZ
And BC Version List Mode = 1
Run it locally and enter the Source and Destinations at runtime.
(Suggested by Ian Cooke)
To display the Exit Bar by default at first start up
[INTERACTIVE RUNTIME]
PWndLocation=66,66,666,477,327681
Additional comment by Christian Audet
(From J.D. Edwards OneWorld: A Developer's Guide (Appendix F
)PWndLocation:
The First four values define the location of OneWorld Explorer on the client's screen. The fifth value controls whether the exit bar and type-ahead is enabled. The valid values for the fifth value are as follows : 1114113, for disabling the exit bar and type-ahead; 65537, for disable the exit bar and enabling the type-ahead features; 1376257, for enabling the exit bar and disabling type-ahead features; and 327681, for enabling the exit bar and type-ahead features.
(Suggested by Ian Cooke)
To force locally run UBE's to use a separate database connection
Because local UBEs are running through OExplore (the same as all
interactive applications), the entire OW system comes to a virtual halt when the UBE performs a large data selection.
To overcome this issue, under the UBE section of your ini include the following line:
UBEThread=0
This will cause a separate application (Ubeprint) to run on your PC.
Both Oexplore & Ubeprint will then have separate connections to your
database
(Suggested by Richard Manning)
To change Check Kernel settings (AS/400)
While the Enterprise Server is running, it passes messages between the network jobs and the kernel jobs. By default, the network job will verify that each of the call object kernels is running, every 10th time it sends or receives a message. J.D. Edwards has released an enhancement in SAR #5128281 with SP16.1, which enables you to customize this verification to occur less frequently. This change reduces the amount of overhead within the Enterprise
Server and improves the overall response time. You can choose to check for a kernel’s health every 1,000 times there is a message or, say, 5,000 times there is a message; the trade-off is performance versus prompt knowledge of a kernel problem. While you do want to continue to monitor your kernels, if you have a heavy load of transactions, you might consider increasing this
number to have it check for kernel health less frequently. In the [JDENET] section, add the new line, checkKrnlHealth with the value that you choose,
as in the example below.
100 user example:
[JDENET]
checkKrnlHealth=1000
(Suggested by Larry Jones)
To prevent the occurance of 'Commit failed' errors in transaction processing
This issue is caused when Oracle forfeits the cursors created in the previous connection when OneWorld middleware creates a new connection.
Add the following to the JDE INI on both the client machine and the server:
[DB SYSTEM SETTINGS]
OracleServerHandleReuse=0
Client machine needs to be on SP11.1 or higher. Server needs to be at SP16 or higher.
NOTE: Both client and server need to be at the same SP level. If logic is processed on the server then both client and server need to be at SP16 or higher.
MORE TO FOLLOW
Sef van den Nieuwelaar
Australia
B732 on NT, XE on NT, B732/A73 on AS400, B733 on NT<P ID="edit"><FONT SIZE=-1>Edited by Sef on 3/7/02 03:58 PM.</FONT></P>
