E1 Web Client on Citrix

RAMMEDJR

Well Known Member
During our testing of the web client running through Citrix we are
seeing performance issues over running off the desktop. Mostly the
performance issues are opening apps, drilling down a grid row item for
more detail and then returning to original screen. The times for these
are about double sometimes more, such as opening an app on citrrix takes
approx 8 seconds, off the desktop 2 seconds. Drill down about 8 seconds
to 4, etc. Anybody running E1 web on Citrix and if so, any suggestions
on increasing performance. The terminal servers are running other apps
such as MS Office 2003 products.



Thanks.



Dave Rammer

Sheboygan County



Prod: EO810 TR 8.93_N1 HP-UX 11i Oracle 9.2.0.5



Test: EO810 TR 8.95_J1 HP-UX 11i Oracle 9.2.0.5 OAS
10.1.2.0.0



Terminal Servers: Windows 2003 R2 SP1 HP DL 360s
2gb ram



Citrix Presentation Server 4


NOTICE: This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
 
I have tested our JDE 8.11 SP1 system via Citrix and I see generally better performance due to the lack of an insanely aggressive desktop anti-virus solution as well as the fact that the servers have mulitple processors versus my desktops single core Pentium M @ 1.4GHz.

On the Citrix server, P01012 opens in 2 seconds on a Windows 2000 server hosting IE 6.0 SP1 as well as an identically configured HP DL360 running Windows 2003 SP1 and IE 6.0 SP1.
 
We are doing the same thing, the web client in a Citrix seamless app - the user does not even know that the browser is coming from Citrix. We also force the users to use a particular icon (Citrix icon for the browser) to get to the web server, this way we will prevent users from attempting to connect from a remote location using their local browser..so far no problems in our testing (going live in December).

-john
 
Thanks for the information. We actually have McAfee anti-virus running
on our terminal servers. Turned the services off today on one of the
terminal servers and I was able to get performance times comparable to
running the web client off my desktop. We want to keep the anti-virus
running so the trick now is to figure out how to bypass it from checking
anything to do with the web client.



Any thoughts.



Thanks.



Dave Rammer

Sheboygan County



Prod: EO810 TR 8.93_N1 HP-UX 11i Oracle 9.2.0.5

Test: EO810 TR 8.95_J1 HP-UX 11i Oracle 9.2.0.5 OAS
10.1.2.0.0

Terminal Servers: Windows 2003 R2 SP1 HP DL 360s
2gb ram

Citrix Presentation Server 4
 
Re: RE: E1 Web Client on Citrix

Perhaps you could disable scanning of java script or only scan connections to/from the JDE web server once per day.
 
Re: RE: E1 Web Client on Citrix

In addition to disabling 'ScriptScan' in McAfee I can also recommend to exclude files like 'E1*.htm' from scanning.
 
RE: RE: E1 Web Client on Citrix

Thanks a lot that helped a lot by doing both. We still have some
performance issues and will continue to work on those.



Dave Rammer

Sheboygan County IS



EO810 TR 8.95_J1 HP-UX 11i Oracle 9.2.0.5 OAS 10.1.2.0.0

TS: Windows 2003 Citrix Presentation Server 4
 
Re: RE: RE: E1 Web Client on Citrix

I see that you are testing 8.95_J1. There were some changes starting with 8.94_U1 that you might want to look at. First I suggest you look at the AppLaunchNewBrowser setting in the JAS.INI

[OWWEB]
AppLaunchNewBrowser=TRUE

This improves performance of switching between two forms with large grids.
This renders each application in a separate browser, eliminating the re-rendering of the grid in memory each time the window is selected by the user.
The switch from one application to another will then be as instantaneous as clicking on a new browser windows.

Secondly if you want to put in the time you can make some dramatic performance improvements by creating “Custom Grids” across some of the applications that have a large number of columns. Many of the large transaction tables have 200+ columns but user only actually use a small fraction of them. When a program is called up and data is retrieved the web app will format the data in ALL of the columns in the grid. If you significantly reduce the number of columns that the app needs to format, performance will increase.
NOTE: Keep in mind that if the grid columns drop to a value less that 60, the rowset size doubles. You can control this using the SectionSize in the JAS.INI
 
RE: RE: RE: E1 Web Client on Citrix

# Please refer to the JAS Installation Guide for detailed information on
# this file.
#
#

[SECURITY]
DataSource=System - 810
SecurityServer=chisux01
UseLogonCookie=FALSE
CookieLifeTime=7
SSOEnabled=FALSE
SSOUserIDOnly=FALSE
# set password only if SSOUserIDOnly is set to TRUE
Password=
#Version Security level for task explorer - 0 is default, set to 1 for strict version security
StrictVersionSecurity=0
OracleSSO=FALSE

[OWWEB]
PathCodes=('DV810','PY810')
MO QUEUE=webclient/moqueue
MAXUser=100
UseMOWinNTShare=FALSE
SystemDateFormat=MDE
SystemDateSeparator=/
ShowSubmitJobs=FALSE
AutoPopulate=ON
AutoPopulateBufferSize=50
# Added following line 10/31/2006 - DR
AppLaunchNewBrowser=TRUE

# Added following three lines 5/10/2006 - DR
DefaultEnvironment=JDV810
DefaultRole=*ALL
workcenter=WorkCenter

# The HelpPath key determines where JAS looks for help files.
# Syntax: "http://[machine]/[path]/".
# Note, if you specify "/jde/owhelp/", this machine is assumed.
HelpPath=/jde/owhelp/
PPCSetDefaultFocus=FALSE
# auto resume interval for fetch update dialogs, in milliseconds
# TimeWaitBeforeAutoResume=10000 ** Commented out 3/22/2006 - DR
TimeWaitBeforeAutoResume=0
# Global Page size for grids.
# This setting overrides the application level page size when
# the application level page size is smaller than this setting.
# Valid values are from 0 to 100. When this value is greater than
# 100, the Global Page size will be set to 100.
# The default value is 0, which will never override application level page size.
GlobalPageSize=25
# the default section size for "go to end" functionalilty
# if there are more than 60 visible columns on the grid,
# the system will reduce this section size by half.
# SectionSize=200 ** Commented out 3/22/2006 - DR
SectionSize=70
# added following 3/22/2006 - DR
FetchAllPageSize=500

[CACHE]
# These intervals are in milliseconds. For example, 60000ms = 1 minute
UserSession=24000000
ResultSet=600000
CacheCheck=600000




[SERVER COMPONENTS]
#
# Do not modify this section
#
com.jdedwards.runtime.virtual.MAFComponentLoader
com.jdedwards.jas.UserManager
com.jdedwards.jas.JDBCProxy
com.jdedwards.jas.JDEORB
com.jdedwards.jas.DDValidation
com.jdedwards.jas.security.SecurityBroker
com.jdedwards.jas.UDCJDBC
com.jdedwards.jas.JDEUDCText
com.jdedwards.jas.JDEUpdates
com.jdedwards.jas.JDEQueries
com.jdedwards.jas.JDEOWDirect
com.jdedwards.jas.ServerQuery
com.jdedwards.jas.JDESignon
com.jdedwards.jas.PerfMonInit


[JDENET]
# Enterprise Server JDENET port
serviceNameConnect=6212

# JAS Server JDENET Listening port
serviceNameListen=6212

# Maximum number of dedicated kernel types
maxKernelRanges=1

# Time out value for requests sent to the Enterprise Server
enterpriseServerTimeout=900000

# Directory for JDENET temporary file
tempFileDir=webclient/temp

# Clustered logical datasource retry interval
ClusterRetryInterval=60000

# Dedicated Kernel Definitions
[JDENET_KERNEL_DEF1]
krnlName=XAPI Kernel
processClassName=com.jdedwards.runtime.virtual.xapi.PublishedMessageProcessor
startMessageRange=15001
endMessageRange=15250
maxNumberOfThread=3


[SERVER]
# Enterprise Server and port providing Glossary Text information
glossaryTextServer=chisux01:6212

# Encoding scheme
# 1252- English and Western European
# 932- Japanese
# 950- Traditional Chinese
# 936- Simplified Chinese
# 949- Korean
codePage=1252
#per application team, set the default setting to
 
Re: RE: RE: RE: E1 Web Client on Citrix

I know you’re not going to like this but according to Oracles Lab tests upgrading your PIII’s on your DL360 to a PIV processor will make a big difference. In their words:
“Pentium IV hyper threaded processors seem to make a significant impact on performance.”
Example:
750 rows/ 45,000 cells:

863 Mhz: 140 seconds
1993 Mhz: 83 seconds
2524 Mhz: 60 seconds

As always increasing the amount of memory on you Citrix server will also improve performance but not to the extent that faster processors will.
Example:

200 row fetch

Processor CPU, Memory, Response Time in Seconds
P3, 1.1, 261, 22
P4, 1.5, 261, 12
P4, 1.7, 261, 8
P4, 2.0, 1 GB, 7

So much for "Thin" client!
 
Back
Top