/  32
 
JDE.INI File Settingsfor Clientsand Servers
 
T
heJDE.INIfileisapowerfultoolthathelpscontrolhowyoursystemwillbehave.Thebetteryouunderstandthisfileandhowitaffectsyoursystem,themoreyou will be able to do with OneWorld. Settings in this file can help you debugproblems through advanced logging features, and other settings can help youtune your system for performance to meet your business’s needs.
Overview of the JDE.INI File
The JDE.INI files are located throughout your system. These files are initialization files,and they give the system the location of specific required tables. These tables, such asthe F986101 (Object Configuration Manager), F98611 (Data Source Master), F00941(Environment Detail), F00945 (Release Master), and F00942 (Path Code Master), arereferred to as bootstrap tables. These tables are required for the system to start upcorrectly. This is one reason why the JDE.INI file is important. This file also controlsseveralfeaturesofthesystem,includingreplication,unifiedlogon,andsign-onsecurity.The JDE.INI file resides on workstations, servers, and Windows Terminal Servers.Eachfatclientworkstationwillhaveitsowncopy.Also,eachinstanceofOneWorldonthe enterprise server will have its own copy of the JDE.INI file. You will need to keepthis in mind when you review the values of this file. The only exception to this is on Windows Terminal Server. Each user will have his or her own profile on a WindowsTerminal Server. This profile is a directory that contains a copy of the JDE.INI file foreach user. Remember, on a Windows Terminal Server you are sharing specificationfilesformultipleusers.TheseuserswillneedtheirownJDE.INIfilestocontrolloggingand other functionality.
Values for JDE.INI Files
In the following table, we will cover the valid values for JDE.INI files. Some of thesevalues are “hidden” values, meaning they do not show up in the standard shipped JDE.INI files. In the past, you needed a senior CNC consultant to tell you what thesevalues were. Just in case you don’t have one of these consultants in your back pocket,we have documented all the current JDE.INI file values for you. These values will helpyou maintain, tune, and administer your OneWorld system.You will notice that some of these settings are shown as internal only. This meansthey were designed to be used by J.D. Edwards developers only. You will need to beextremely careful if you plan to use these settings. In fact, you probably should not
2
 J.D. Edwards OneWorld: The Complete Reference
 
modify these settings unless directed to by J.D. Edwards development. If you modifythese settings on your own, you run the risk of having unpredictable results. Thefollowing table contains some settings that are not documented in the current J.D.Edwards manuals.
(Section, “Key, “Default)Comment and Valid ValuesDescription
BSFN BUILDThis section in the JDE.INI file tells thepackage build where the path is to thepackage directory and the link flags tobuild the business function.(“BSFNBUILD”,“DoCompression”,0)“Turns Compression On/Off[Default 0 – Do Not Use Compression][!=0 Use Compression]Used to compress Server Packagesfor re-deployment to other serversof the same platform type, i.e., thepackage would not have to be builton each server.[Default 0 – Do NotUse Compression][!=0 Use Compression](“BSFN BUILD”, BuildArea”, “)“Sets Base Build AreaAny valid pathThepathwherethe“packagename”directorywillgetcreatedandthepackagewillbebuilt.(“BSFN BUILD”, “DebugFlags”, “)“Machine and Compiler Specific”/Gz /Od /Zi /MDd /Yd /W4 /GX /Gy /D “_DEBUG”(“BSFNBUILD”,“OptimizationFlags”,““)“Machine and Compiler Specific/Gz /O2 /MD /W4 /GX /Gy(“BSFN BUILD”, “OSReleaseLevel”, ““)“Machine and Compiler Specific”(“BSFN BUILD”, “DefineFlags”, “)“Machine and Compiler Specific”/D WIN32” /D “_WINDOWS” /D“IAMASERVER” /D “KERNEL”(“BSFN BUILD”, “CompilerFlags”, “)“Machine and Compiler Specific”/nologo /c(BSFN BUILD, LinkFlags, )Machine and Compiler Specific/DLL /DEBUG /SUBSYSTEM:windows /FORCE:MULTIPLE /FORCE:UNRESOLVED /INCREMENTAL:YES /VERBOSE /MAP(“BSFN BUILD”, “LinkLibraries”, ““)“Machine and Compiler SpecificJDEKRNL.LIBJDEL.LIBJDENET.LIBJDEIPC.LIB(“BSFN BUILD”, “SimultaneousBuilds”,DEFAULT_BUILD_COUNT)“Setstheamountofsimultaneousbuilds”[0–SetsallDLLstobebuiltatthesametime]Thenumberofprocessesthatarestartedforthebusinessfunctionbuild.**AS400 (“BSFN BUILD”,“CompileOutput”, ““)“Machine and Compiler Specific”**AS400 (“BSFN BUILD”,“InliningFlags”, ““)“Machine and Compiler Specific”
 JDE.INI File Settings for Clients and Servers
3

Share & Embed

More from this user

Recent Readcasters

Add a Comment

Characters: ...

Deepesh Divakaranleft a comment

Thanks for the File.. It was of great help.