This section provides initial recommended configuration parameters stored in the JDE.INI file for the JD Edwards EnterpriseOne Enterprise (logic) Server. These settings represent values to consider for configuring EnterpriseOne In-Memory Applications running on the Oracle engineered systems. These settings are based on a load of 2,000 concurrent interactive users. You should use the basic configuration rules provided in the comments for scaling above the 2,000 user limit and you should refrain from configuring any of the settings below the default values.
|
Note: You should always use Server Manager to set the values in the JDE.INI file for the JD Edwards Enterprise logic server. The settings provided in this guide are a good starting point for properly configuring EnterpriseOne running on the Oracle Exalogic platform. |
The following general rules may not always apply to all industry verticals and EnterpriseOne implementations. They have found to be provide good performance characteristics during lab testing of EnterpriseOne on the Oracle Exalogic engineered systems. The In-memory applications require a slight deviation from the default best tuning practices.
|
Note: For simplicity, changes to specific sections of the JDE.INI for performance are provided below. |
JDENET network processes
The best practice to determine the number of network process remains the same, 100 users per netprocess + 1.
DEF4 Security Kernels
Similarly, the best practice for the number of security kernels, 100 users per security_kernel + 1.
DEF6 Call Object Kernel
The DEF6 process for Call Object Kernels (COK) is an area in the EnterpriseOne logic server that requires a deviation from the standard tuning recommendations. The JD Edwards EnterpriseOne tools code has been optimized for the JD Edwards EnterpriseOne In-memory applications. Starting with Tools code X9.1.3.1 for Oracle engineered systems, a change in the number of database connections the COK process can establish has been increased. For JD Edwards EnterpriseOne In-memory applications, child threads can establish their own independent database connections. Prior to this change, only the master business function was allowed to establish database connections. This change increases the consumption of resources that COKs require. A ratio of five users per COK is recommended.
A second tuning value is the number of threads per session. Testing indicates that the default value of 10 is the proper setting for both In-memory applications. If Project Portfolio Management is the predominate application used, then a setting of five may provide a slight boost to performance.
Following is a snapshot of a JDE.INI file with the above recommended setting changes.
[JDENET]
## The maxNetProcesses is derived by assuming 100 users per netProcess + 1
## (main jdenet process)
## For example 2000 users would be 20 + 1 or 21 total processes
maxNetProcesses=21
maxNetProcesses=6
maxNetConnections=2000
maxNumSocketMsgQueue=800
maxIPCQueueMsgs=400
maxLenInlineData=4096
maxLenFixedData=16384
maxFixedDataPackets=2000
The following are configuration settings for the Security kernels:
[JDENET_KERNEL_DEF4]
## The maxNumberOfProcesses is derived assuming 100 users per security
## kernel +1.
## For example 21 security servers will handle 2000 users
krnlName=SECURITY KERNEL
dispatchDLLName=libjdeknet.so
dispatchDLLFunction=JDEK_DispatchSecurity
maxNumberOfProcesses=21
numberOfAutoStartProcesses=0
The following are configuration settings for the Call Object kernels:
[JDENET_KERNEL_DEF6]
krnlName=CALL OBJECT KERNEL
dispatchDLLName=libxmlcallobj.so
dispatchDLLFunction=XMLCallObjectDispatch
## Processes setting for this kernel assumes 2000 users where the ratio is 10:1
## for NON-In-memory applications
## For In-memory applications, set this to a 5:1 ratio
maxNumberOfProcesses=400
numberOfAutoStartProcesses=0
singleThreadedMode=N
ThreadPoolSize=30
ThreadPoolSizeIncrement=5
## In-memory tuning value, default is 10. Change to 5 if Project Portfolio
## Management is the predominate application.
The combined configuration of the JDENET section of the JDE.INI for the network processes, the EnterpriseOne kernel settings defining the Security Server and the Call Object kernels, provided good scaling to 2,000 concurrent users with the in-memory applications with slightly adjusted changes to the JD Edwards EnterpriseOne configuration