JDE.INI Basic Setting for XML Workload

JDE.INI Basic Setting for XML Workload

DSI Whitepaper – JDE.INI Basic Setting for XML Workload

Contents

Introduction 3

INI Sections and Basic Settings 4

Call Object Kernel 4

XML Dispatch Kernel 4

XTS Service 5

JDE Kernel Recycling 5

XML Dispatch Stanza 5

Conclusion 6

Introduction

This purpose of this document is to outline basic settings that should be configured on the EnterpriseOne Enterprise/Application server that will host the XML workload when integrating dcLINK into an E1 Environment. These setting are the basis for being able to successfully process dcLINK transactions via the XML Interoperability client. These settings are not meant as tuning settings as those can only be determined through a performance audit and stress test. Instead these setting are designed to configure the enterprise/application server to accept and process the XML workload in a stable and reliable manner.

This document assumes that the clients EnterpriseOne system has the most recent E1 tools release and is fix current on application code patches and fixes. DSI does not guarantee a stable system reliable platform for XML operation if the EnterpriseOne system if not current on tools and/or application code fixes.

INI Sections and Basic Settings

Call Object Kernel

The Call Object Kernel is used to process business function requests on the enterprise/application server. In E1 tools release 8.97 and higher and application release 8.11 and higher, the Call Object Kernel is generally configured to be a multi-threaded. This means that each COK can host multiple user sessions. Therefore the total number of kernel process can be fewer. If this is configured then thread pool sizing is used. DSI has determined the optimal initial settings for the Call Object Kernel are as follows.

Kernel Settings / Notes
[JDENET_KERNEL_DEF6]
krnlName=CALL OBJECT KERNEL
dispatchDLLName=XMLCallObj.dll
dispatchDLLFunction=_XMLCallObjectDispatch@28
maxNumberOfProcesses=5
numberOfAutoStartProcesses=5
ThreadPoolSize=10
ThreadPoolSizeIncrement=5
singleThreadedMode=N / This value may be set differently and can remain as set.

XML Dispatch Kernel

The XML Dispatch kernel is used as the dispatcher of XML request to the Call Object Kernel Pool. Each dispatcher can handle roughly 5 requests simultaneously before queuing occurs. However because dcLINK is a multi-threaded system and the number of simultaneous request can be quite large DSI has determined the optimal initial settings for the XML Dispatch Kernel are as follows.

Kernel Settings / Notes
[JDENET_KERNEL_DEF22]
krnlName=XML DISPATCH KERNEL
dispatchDLLName=xmldispatch.dll
dispatchDLLFunction=_XMLDispatch@28
maxNumberOfProcesses=5
numberOfAutoStartProcesses=5 / This value must be changed.

XTS Service

The XML Translation Service is used to interpret XML requests and is the intermediary between the JDENET process and the XML Dispatcher. It is also used to check the state of the XML Dispatcher, by default the Response Timeout is set far too high generally 600 seconds. Because the dcLINK Function Caller or Connector Timeout is typically set to 120 seconds DSI has determined the optimal initial settings for the XML Dispatch Kernel are as follows.

Kernel Settings / Notes
[XTS]
ResponseTimeout=110 / This value must be changed.

JDE Kernel Recycling

Kernel recycling is a recently added feature to the E1 tools code that forces kernel processes to close and reopen, releasing memory and cleaning up system memory. In general this is a very nice feature added to the tools, however because dcLINK threads open and reuse user sessions and thereby kernel processes kernel recycling can cause dcLINK to experience communication timeout during overnight periods. Therefore DSI has determined kernel recycling should be disabled on all servers that will host dcLINK XML workload, this is done as follows.

Kernel Settings / Notes
;[RECYCLING]
;krnlRecycleTimeOfDay=Sun:03:30
;krnlRecycleElapsedTime=
;inactiveUserTimeout=6:00
;timeToForcedExit=12:00 / All lines must be commented out by using a semicolon.

XML Dispatch Stanza

In most JDE.INI files the XML Dispatch stanza does not exist, for dcLINK this stanza and the associated parameter shown below provide a polling interval for the Dispatch Kernel to check that status of submitted XML requests to the Call Object Kernel. DSI has determined the optimal initial settings for the Poll Interval Millisecond parameter as follows.

Kernel Settings / Notes
[XML DISPATCH]
PollIntervalMillis=3000 / This value must be added.

Conclusion

The editing or changing of these values in the JDE.INI will not eliminate all possible errors that can occur within EnterpriseOne Related to XML workload but they do provide an established best practice configuration for servers running XML workload.

Again it should be noted that these values are not considered tuning values but only a baseline for which an enterprise or application server should be set when adding XML workload to the system.

Proper tuning of the system can only be accomplished by execution of a full Performance Audit and Stress Test to determine the proper tuning values for a client’s specific environment.

Data Systems International, Inc. 7/10/2013 Page 1