JDE on CPS 4.0 Scalability Analysis

8/2/2019 JDE on CPS 4.0 Scalability Analysis

1/33

OOrraaccllee -- JJDD EEddwwaarrddss EEnntteerrpprriisseeOOnnee SSccaallaabbiilliittyy AAnnaallyyssiiss

oonn CCiittrriixx PPrreesseennttaattiioonn SSeerrvveerr44..00

Citrix Systems, Inc.


2/33

Oracle - JD Edwards EnterpriseOne Scalability Analysis on Citrix Presentation Server 4.0 i

Notice

The information in this publication is subject to change without notice.

THIS PUBLICATION IS PROVIDED AS IS WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED,INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. CITRIX SYSTEMS, INC. (CITRIX), SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIALERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR DIRECT, INCIDENTAL, CONSEQUENTIAL OR ANYOTHER DAMAGES RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS PUBLICATION, EVENIF CITRIX HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES IN ADVANCE.

This publication contains information protected by copyright. Except for internal distribution, no part of this publication maybe photocopied or reproduced in any form without prior written consent from Citrix.

The exclusive warranty for Citrix products, if any, is stated in the product documentation accompanying such products.Citrix does not warrant products other than its own.

Product names mentioned herein may be trademarks and/or registered trademarks of their respective companies.

Copyright 2005 Citrix Systems, Inc., 851 West Cypress Creek Road, Ft. Lauderdale, Florida 33309-2009 U.S.A. Allrights reserved.

Version History

Citrix Consulting Solutions Version 1.0 Final Deliverable 13 September 2005


3/33

Oracle - JD Edwards EnterpriseOne Scalability Analysis on Citrix Presentation Server 4.0 ii

Table of Contents

EXECUTIVE SUMMARY.............................................................................................................................................................1TEST METHODS.........................................................................................................................................................................2

SCRIPTED TEST.......................................................................................................................................................................... 2REAL USER TEST .......................................................................................................................................................................2REAL USERS WITH TASK LIST ......................................................................................................................................................2COMBINATION ............................................................................................................................................................................3SCALABILITY TEST METHODS SUMMARY .......................................................................................................................................3ENTERPRISEONE SCALABILITY TESTING METHOD..........................................................................................................................3

TEST PLAN.................................................................................................................................................................................4SCALABILITY TESTING PROCESS ..................................................................................................................................................4

TEST ENVIRONMENT................................................................................................................................................................5HARDWARE SPECIFICATIONS .......................................................................................................................................................6SOFTWARE SPECIFICATIONS........................................................................................................................................................6

Windows 2003 Environment ................................................................................................................................................6Citrix Presentation Server Configuration..............................................................................................................................6JD Edwards EnterpriseOne Configuration...........................................................................................................................6Mercury LoadRunner Configuration.....................................................................................................................................6

WORKFLOW CONFIGURATION ......................................................................................................................................................7

SCALABILITY RESULTS AND ANALYSIS ............................................................................................................................... 9MEASUREMENTS ........................................................................................................................................................................9PROCESSOR SCALABILITY RESULTS ...........................................................................................................................................10MEMORY SCALABILITY RESULTS ................................................................................................................................................10RESULTS CONCLUSION .............................................................................................................................................................11

APPENDIX: MERCURY INTERACTIVE LOADRUNNER......................................................................................................... 12


4/33

Oracle - JD Edwards EnterpriseOne Scalability Analysis on Citrix Presentation Server 4.0 1

Executive SummaryOracles business is informationhow to manage it, use it, share it, protect it. Citrix provides a way to accessinformation enabling companies to react more quickly to competition and market change. In 2005, the merger of

Oracle and PeopleSoft marked a major turning point in the evolution of the software industry. Citrix Systems, Inc, amember of the Oracle Partner Network (OPN), has been working jointly with Oracle to bring our customers theservices and software necessary to operate efficiently in a challenging IT environment. Now more than ever, CitrixSystems continues to provide value to Oracles suite of web-based applications with the Citrix Access Suite. TheCitrix Access Suite increases a companys ROI by minimizing management of the application and provides secureaccess to sensitive company information while providing quicker time to value.

Implementing JD Edwards EnterpriseOne using the Citrix Access Suite 4.0 and Citrix best practices, enablesorganizations to better serve its employees and customers by providing the flexibility to access the latest applicationsand information securely from any device, while administrators gain financial flexibility from lower IT operating costsand enhanced data security. This scalability study for JD Edwards EnterpriseOne provides Citrix Presentation Server

Architects, System Integrators, and Project Managers with the necessary data to help design and plan a CitrixPresentation Server environment. This study also provides a description of the testing environment as well as theworkflows executed to gather the scalability figures. Leveraging the methodology and workflows used in this analysis,similar testing scenarios can be performed to benchmark future or alternative hardware configurations.

Citrix Consulting leveraged a proven methodology, to assess the server scalability of Citrix Presentation Server 4.0hosting JD Edwards EnterpriseOne. After a baseline was established on the server, users were incrementally addedto the server as system resources were monitored for potential bottlenecks. Throughout the duration of the test anactual user logged on to the systems and validated the performance of the environment as new users were added.

During the scalability analysis, automated user sessions were launched on a Citrix Presentation Server that executeda combination of workflows based on the JD Edwards HTML Benchmark Kit. During the testing cycle, the serverexhibited 0.17% total processor utilization increase and 12.7 MB memory consumption per user. The memoryconsumption discussed in this paper is an average used by virtual users executing predefined workflows; however, itis likely that this average consumption will increase depending on usage patterns of actual users.

As a best practice, Citrix recommends that Citrix administrators cap user load on a server when the average resourceutilization reaches 70% to 80%. The threshold accounts for the periodic spikes experienced during normal systemusage as well as proving a buffer for unexpected or scheduled server operations, such as virus scanning or backups.In some instances, organizations may choose to increase or decrease the acceptable threshold based on applicationcharacteristics and redundancy requirements. In addition, these organizations may choose to leverage the MemoryOptimization and CPU Utilization features in Citrix Presentation Servers which may affect the results. This scalabilityanalysis did not leverage the new features and configured the test environment with default settings.

Based on the characteristics of JD Edwards EnterpriseOne application, it is recommended to reduce the memorythreshold to 70% to account for the potential spikes of memory that can be consumed by a single user or group ofusers.

The limiting factor that determined the maximum number of users per server based on the workflows and hardwareplatforms outlined in this document was memory consumption. The recommend memory threshold of 70%correlates to 127 active ICA sessions for a Citrix Presentation Server. Throughout the test, a manual user sessionwas performed to ensure the usability and performance of the system. As the thresholds were reached, acceptableperformance levels were maintained. The results will vary based on the type of workflows and the hardwareconfiguration used for testing. The results documented in this whitepaper should be leveraged as guidelines for sizinga Citrix Presentation Server environment.


5/33


Test MethodsThere are four primary types of scalability testing methods appropriate for the Citrix Presentation Server 4.0environment. Therefore, a decision must be made in selecting a test method in order to standardize a valid scalability

test of the environment. Below are the appropriate testing methods:

Scripted Test.Automated execution of scripts that mimic a users actions without any user intervention

Real Users Test.Actual users enter the system and run through their daily tasks without any specifiedorder

Real Users with Tasks List.Actual users enter the system and run through a set of pre-defined tasks

Combination.A combination of two or more of the aforementioned testing methods

This section discusses each method in more detail and compares the advantages and disadvantages of using eachmethod.

Scripted TestFor this method, a standard set of scripts are leveraged to control the actions of test users that are similar to typicalJD Edward EnterpriseOne users. These scripts are developed to simulate a desired set of predefined actions(workflows), which are based on the users role and applications used during a typical user session. Each workflowmay contain sub-workflows that dictate the multiple paths users take to complete these daily tasks. These sub-workflows will be the basis for scripts that are generated. Initiation of script execution would be at set intervals toensure that steps taken while working in an application are not repeated simultaneously for all virtual users during thetest. These intervals ensure more accurate results since the application is able to respond in a more realistic manner.

For the test process detailed in this document, the functional flows for these scripts have been developed by CitrixConsulting and are based on test flows created by Oracle for application verification testing.

Real User Test

The second method for scalability testing is to have users log into the system and perform tasks similar to those of atypical workday. The results obtained from this method are geared toward real-life scenarios. The caveat to using thismethod is that more variables exist in the test, such as the number of users, activities, and interruptions. This makesit more difficult to run the same exact test while increasing user load, making system configuration changes, orrepeating the test.

When running this type of test, most client environments would benefit from monitoring their systems and capturingthe performance counters and data in a database format over an extended period of time. Resource Manager forCitrix Presentation Server is designed to accomplish this, and these figures can provide significant value andaccuracy, provided that a large enough population sample of data is captured.

Real Users with Task List

The next method for scalability testing is a combination of Scripted Tests and Real User Testing. Real User Testingwith task lists includes having real users access the system, while executing a written set of tasks in a random order.These tasks are analogous to the workflows defined in this document. Developing customer specific tasks forscalability testing will represent the different types of users that will access the system on a daily basis. Each user willbe accessing the system at different speeds, reflecting a realistic production environment. However, these users willbe following a common set of tasks that will help with standardizing the scalability tests when they need to be re-runwith additional users.


6/33


This type of test is resource intensive and can be difficult to coordinate. Most corporate environments cannot providemultiple resources for this type of application testing and evaluation.

Combination

The final method for scalability testing is a combination of a custom script and real users accessing the testenvironment. For example, five client computers emulating six users each could be used in conjunction with severalreal users performing searches and more complex customer transactions. This would allow the administrators to loadthe system to specific level, and then evaluate the subjective and objective results of the users interaction with theCitrix Presentation Servers.

Scalability Test Methods Summary

The Scalability Test Methods Summary table summarizes the advantages and disadvantages of each scalability testmethod described above.

Table 1. Scalability Test Methods Summary

Testing Method Advantages Disadvantages

Scripted test Completely controlled with no variables

Identical tests can be repeated as many t imes asneeded

User time is not required to do test

Tests can be re-run as environment grows

Takes significant time/tools to create test scripts

User skill levels not incorporated in test

Real Users Test Real life test

Allows for different user types and skill levels

Impossible to have two identical tests

User's time is needed to perform test

Need Users from ISV's customer base

Real Users withTask List Test

Can be as controlled as necessary

Tests can be repeated with high degree of similaritybetween previous tests

Allows for different user types and skill levels

User's time is needed to perform test

The project team will have to create task list forusers customized to their role. (very complexand time consuming)

Combination Can emulate most user activities with custom scriptswhile real users can test actions that are not scripted

Multiple users' time is needed to perform tests

EnterpriseOne Scalability Testing Method

Based on the project requirements, the Scripted Test Method has been leveraged. This ensured identical, controlledtests that could be repeated for multiple tests. The scripts developed for testing were carefully formulated by CitrixConsulting while following the workflows created by Oracle to accurately simulate normal user load on the CitrixPresentation Servers. Mercury Interactive LoadRunner and the Citrix ICA client integration were the primary testingtools that were used to develop the scripts.


7/33


Test PlanThis section will provide details of the test plan for the scalability testing on the JD Edwards EnterpriseOneenvironment. As with all testing strategies, a clearly defined testing process helps to ensure accurate and repeatable

results.

Scalability Testing Process

The purpose of the scalability testing was to determine the maximum number of users that could access JD EdwardsEnterpriseOne applications via a published Internet Explorer on a Citrix Presentation Server while not overwhelmingthe server. By using Internet Explorer, a user could access the JD Edwards EnterpriseOne application via the Webclient and leverage the benefits of using Citrix Presentation Server 4.0.

LoadRunner Virtual User Generator 7.6 was utilized to run the scripts. The LoadRunner Controller managed thenumber of virtual users (vUsers) while Windows Performance Monitor was used to log the performance of the CitrixPresentation Server. The data was leveraged to determine the limiting resource of the server and the maximumnumber of active concurrent users a Citrix Presentation server can support.

The test scripts simulated, as best as possible, how most users would use the EnterpriseOne application. The vUserslaunched an ICA session to the Citrix Presentation Server and opened the published Internet Explorer application likea real user would. After launching Internet Explorer, the vUsers logged into the EnterpriseOne application andfollowed the steps provided by selected workflows. Refer to the Test Environment section for more details on theworkflows.


8/33


Test EnvironmentThis section describes the elements of the testing environment used throughout the scalability analysis test cycle.

Figure 1. Test Environment

As the figure above illustrates, the test environment between Citrix Presentation Server 4.0 and JD EdwardsEnterpriseOne Release 8.10 consists of the following components:

Mercury LoadRunner Generator. This server was configured to generate multiple vUsers to access the JDEdwards EnterpriseOne application using Citrix Presentation Server 4.0

Mercury LoadRunner Controller. This server was configured to act as an administrative mechanism forcontrolling the vUsers running on each LoadRunner Generator server

Citrix Presentation Server. This server runs Citrix Presentation Server 4.0 application allowing multi-useraccess published resources; for the purpose of this test Internet Explorer was published pointing directly tothe JD Edwards EnterpriseOne Web Client

Zone Data Collector Server. This server is responsible for maintaining dynamic data for all CitrixPresentation Servers in the zone

Citrix Data Store. This server stores the static information for all Citrix Presentation Servers in the farm

Citrix License Server. This server is rte4sponsible for marinating and providing concurrent user licenses toICA sessions

EnterpriseOne Web Server. This web server handles the frontend aspect of accessing the EnterpriseOneapplication using a web browser; it generates the web-based interface of the JD Edwards EnterpriseOneWeb Client

EnterpriseOne Enterprise Server. This application server handles all the processes and provides the logicfor all the EnterpriseOne application programs; it is the middle tier between the browser-based frontendsand the backend databases

Database Server. This server stores EnterpriseOne application data within a predefined database schemaon a third-party relational database management system


9/33


EnterpriseOne Deployment Server. This server provides the main focus of the Release 8.10 installationprocess by deploying the Release 8.10 software to the workstations and enterprise servers; the deploymentserver is used to create and maintain installation plans for the EnterpriseOne environment

Hardware SpecificationsThe following chart provides detailed information for the hardware involved in this test environment.

Table 2. Hardware Specifications

Server Role Hardware

Citrix Presentation Server 4.0 HP ProLiant DL 360 G2; Dual 3.06 GHz Processor (Hyperthreaded); 3 GB RAM

EnterpriseOne Web Server HP ProLiant DL 360 G2; Dual 1.4 GHz Processor; 1.25 GB RAM

EnterpriseOne Enterprise Server HP ProLiant DL 360 G2; Dual 1.4 GHz Processor; 2 GB RAM

EnterpriseOne Database Server HP ProLiant DL 360 G2; Dual 1.4 GHz Processor; 2 GB RAM

EnterpriseOne Deployment Server HP ProLiant DL 360 G2; Dual 1.4 GHz Processor; 2 GB RAM

Software Specifications

The following section provides all the software necessary for the test environment.

Windows 2003 Environment

The servers in this test environment were built with Windows Server 2003, Enterprise Edition. All Windows Server2003 systems were updated using Microsoft Windows Update with all Critical Updates and Service Packsinstalled that were suggested by Microsoft Windows Update. Also, anti-virus software was not installed on theservers in the testing environment. In addition, all Windows Server 2003 settings were configured with defaultoptions.

Citrix Presentation Server Configuration

The two Citrix servers were installed with Citrix Presentation Server 4.0 with one designated as the Zone DataCollector. The other server was designated to host the published applications, i.e. Internet Explorer 6.0. CitrixPresentation Server 4.0 was installed with default options for the JD Edwards EnterpriseOne scalability testing.This includes leaving the Memory Optimization and CPU Utilization features disabled. Two other servers wereused to be the designated License Server and the data store. The data store was configured on a SQL 2000Server with direct connections from the Citrix Presentation Servers to the data store.

JD Edwards EnterpriseOne Configuration

Two servers were installed with Visual Studio SP5 and EnterpriseOne Release 8.10. One server was designatedas the Deployment Server while the other one was designated as the Enterprise Server. A third server wasinstalled with EnterpriseOne Web Server and WebSphere 5.0. In addition, a fourth server, the database server,

was installed with SQL Server 2000 with SP3A. The database was populated with a benchmark database.

Mercury LoadRunner Configuration

One server was installed with Mercury LoadRunner version 7.6 which was designated as the LoadRunnerController. The other server was installed with the Load Generator option. While the LoadRunner controllerramped up virtual users, the LoadRunner Generator logged on the users, who stepped through the LoadRunner


10/33


Virtual User Script. The ICA client was installed on the Load Generator to properly connect to the CitrixPresentation Server and run the LoadRunner script.

Workflow Configuration

The workflows used during testing are based on the HTML Benchmark Kit: Scripting Process Version 2.0 provided byOracle. The following provides an outline for each of the four workflows that were used.

Distribution Script 6 (Sales Order Processing Clerk) Simulates how a Sales Order Clerk would use theprogram.

At the main JD Edwards EnterpriseOne login screen, the vUser enters the username and password in thelogin field. On the next screen, the vUser selects the environment

At the main directory, the vUser enters the Fast path, 2/G42112, to initiate the specific function

The vUser performs a customer service inquiry by entering the Order Number, 4341, Order Type, SO,Branch/Plant, M30A, and clicking the Find button

The vUser selects the first row from the list of results, clicks the Select button, and then clicks the Ok button

The vUser ends the customer service inquiry by clicking the Close button

Distribution Script 4 (Purchase Order Processing Clerk) Simulates how a Purchase Order Clerk would use theprogram.


At the main directory, the vUser enters the Fast path, 3/G43B112, to initiate the specific function

The vUser performs a purchase receipt inquiry by entering the Order Number, 1138, Order Type, OP, andclicking the Find button

The vUser selects the first row from the list of results, clicks the Select button, and then clicks the Cancelbutton

The vUser ends the purchase receipt inquiry by clicking the Close button

Financial Script 5 (General Ledger Clerk) Simulates how a G/L Clerk would use this program.


At the main directory, the vUser enters the Fast path, 22/G0912, to initiate the specific application

The vUser enters 1 in the Skip to Account field, unchecks the Select/Skip To Account box and enters theThru Dates, 02/28/99 and 12/31/99. Afterwards, the vUser clicks the Find button

The vUser performs another transaction by entering the LOD, 5, and clicking the Find button

The vUser performs another transaction by entering 1, again, in the Skip to Account field and clicking the

Find button

The vUser ends this function by clicking the Close button

Financial Script 2 (Accounts Payable Clerk) Simulates how a typical accounts payable clerk would use theprogram.



11/33


At the main directory, the vUser enters the Fast path, 16/G0411, to initiate the specific application

The vUser focuses on the Supplier Number field and types CTRL-S. The vUser enters the Name searched,BAABRP, the Search Type, V, and clicks the Find button

The vUser selects the first row from the list of results and clicks the Select button

The vUser clicks the Open radio button and the Find button

The vUser initiates another transaction by entering a Supplier Number, 3334, and clicking the Open radiobutton and the Find button

The vUser ends the inquiry by clicking the Close button

LoadRunner will repeat the assigned workflow N amount of times for each vUser allowing the Citrix PresentationServer to maintain a constant load. This is continued until the maximum number of vUsers are running the workflowsimultaneously. The figure below provides the basic concept that each script followed during the testing cycle. For fulldetails of each script, please reference theAppendix section.

Figure 2. Workflow Overview


12/33


Scalability Results and AnalysisThis section details the scalability results of the JD Edwards EnterpriseOne on Citrix Presentation Server during thetesting cycle. In addition, this section provides graphs and data that explicitly show the impact that each user had on

the processor and memory while running the JD Edwards EnterpriseOne application.

Measurements

Throughout the testing cycle, server performance activity was monitored and recorded using the MicrosoftPerformance Monitoring Utility. The following list contains the performance counters that were recorded during testexecution.

LogicalDisk(_Total): % Disk Time

LogicalDisk(_Total): % Free Space

Memory:Available Bytes

Memory: Pages/sec

Network Interface: Bytes Total/sec

Paging File: % Usage

PhysicalDisk(_Total): Current Disk Queue Length

Processor(_Total): % Interrupt Time

Processor(_Total): % Processor Time

System: Context Switches/sec

System: Processor Queue Length

Terminal Services:Active Sessions

During test execution, an administrator remained logged into the Citrix Presentation Server. After every five users

logged onto the Citrix Presentation Server, the session was used to obtain qualitative measurements of the server,including application responsiveness of JD Edwards EnterpriseOne and screen refresh speed.

It is important to note that utilizing Mercury LoadRunner to perform this test did not add any additional overhead tothe Citrix Presentation Server. Therefore, the scalability results directly correlate to users logging into a CitrixPresentation Server while simultaneously following the workflows.


13/33


Processor Scalability Results

The percentage of Processor Time was logged throughout the JD Edwards HTML Benchmark Kit testing cycle, withthe results charted below. The amount of the total processor consumed increased steadily as user sessions

increased on the Citrix Presentation Server. The trendline indicates an increase of approximately 0.17% processorutilization per active ICA session; and the baseline processor utilization during the testing cycle was 1.7%. Thebaseline processor utilization level is the amount of CPU consumed by the server without user load. The followingfigure illustrates the processor utilization as a function of user load.

% CPU per User

0

10

20

30

40

50

60

0 10 20 30 40 50 60 70 80

Number of Users

%Processo

Figure 3. Processor Utilization

Citrix Consulting recommends that Citrix Presentation Server administrators cap user load on a server when theaverage processor resource utilization reaches between 70% and 80%. Based on processor utilization alone, thiscorresponds to between 392 and 449 users.

Memory Scalability Results

The amount of memory consumed on the Citrix Presentation Server was tracked throughout the testing cycle and ispresented in the chart below. The following graph shows the amount of consumed memory, in megabytes, as activeICA sessions were added to the server by LoadRunner. As the number of ICA sessions was increased, the amountof memory consumed also increased; this was expected behavior. The trendline shows an increase of 12.7 MB peruser with a baseline memory consumption of 523 MB. The baseline memory consumption level is the amount ofmemory consumed by the server without a user load.


14/33


RAM Memory per User

0

200

400

600

800

1000

1200

14001600

0 10 20 30 40 50 60 70 80

Number of Users

ConsumedRAM(

MB)

Figure 4. Memory Scalability Results

Citrix Consulting typically recommends that Citrix administrators cap user load on a server when the averageresource utilization reaches 80%. However, base on the characteristics of the JD Edwards EnterpriseOneapplication, it is recommended to reduce the memory threshold to 70% to account for the potential spikes of memorythat can be consumed by a single user or group of users. Users have the ability to query large amounts of data whichwill impact the available memory for the remaining users. Based on memory utilization alone, this corresponds to 127users.

Results ConclusionData analysis for the JD Edwards HTML Benchmark Kit testing cycle show each user consumed 0.17% of theprocessor and 12.7 MB of the available memory. The limiting factor that determined the maximum number of usersper server based on the workflows and hardware platforms outlined in this document was memory consumption.The recommend memory threshold of 70% correlates to 127 active ICA sessions for a Citrix Presentation Server.Throughout the test, a manual user session was performed to ensure the usability and performance of the system.

As the thresholds were reached, acceptable performance levels were maintained. The results will vary based on thetype of workflows and the hardware configuration used for testing. The results documented in this whitepaper shouldbe leveraged as guidelines for sizing a Citrix Presentation Server environment.

Processor and memory utilization have the greatest overall affect on the performance of a Citrix Presentation Server.Sometimes there is a bottleneck in another server resource which can cause an artificial increase in processor andmemory utilization. The other performance counters were monitored as they are the resources that are most likely tocause a bottleneck. The results of the performance counters measured during the testing cycle did not show signs of

approaching a bottleneck and therefore will not be subject to further data analysis.


15/33


Appendix: Mercury Interactive LoadRunnerCitrix vUser scripts emulate the Citrix ICA Protocol communication between a Citrix client and server. LoadRunnerenables easy creation of automated testing scripts by recording all activity during manual interactions with a

published application and creating a corresponding vUser script. The functions within the vUser script emulate theanalog movements of the mouse and keyboard in an ICA session.

/* -------------------------------------------------------------------------------

Script Title : Distribution Script 4

Script Description : From Oracle (PeopleSoft) HTML Benchmark Kit

Recorder Version : 792

------------------------------------------------------------------------------- */

vuser_init(){

ctrx_set_connect_opt(APPLICATION, "#PeopleSoft Test");

ctrx_set_connect_opt(NETWORK_PROTOCOL, "TCP/IP");

ctrx_connect_server("172.16.10.215", "{UserID}", "citrixccs", "CCSLAB");

lr_think_time(3);

ctrx_wait_for_event("LOGON");lr_think_time(3);

ctrx_set_window_ex("*Microsoft Internet Explorer", 120);

return 0;

}

web_login_4(){

ctrx_key("o", MODIF_CONTROL);

ctrx_type("http://www.google.com");

ctrx_key("ENTER_KEY", 0);

lr_think_time(3);


ctrx_type("http://ccslabs27.ccslab.com:82/jde/servlet/com.jdedwards.runtime.virtual.LoginServlet");

ctrx_key("ENTER_KEY", 0);lr_think_time(3);

ctrx_type("psft");

ctrx_key("TAB_KEY", 0);

lr_think_time(1);

ctrx_type("psft");


lr_think_time(1);

return 0;

}

env_select_4(){

lr_think_time(1);


ctrx_key("TAB_KEY", 0);ctrx_key("TAB_KEY", 0);

ctrx_type(" ");

lr_think_time(1);



ctrx_type(" ");

lr_think_time(1);


16/33


return 0;

}

order_processing_4(){

lr_think_time(3);

while (!ctrx_win_exist("PeopleSoft*- Microsoft Internet Explorer",8)==0){web_login_4();

env_select_4();

}








lr_think_time(8);

ctrx_type("3/G43B112");

lr_think_time(3);



lr_think_time(3);

return 0;

}

order_entry_4(){

lr_think_time(5);

ctrx_key("BACKSPACE_KEY", 0);

ctrx_type("1138");

lr_think_time(5);


ctrx_type("OP");

lr_think_time(3);

ctrx_key("i", MODIF_ALT);

lr_think_time(5);






















17/33














ctrx_type(" ");


lr_think_time(5);

ctrx_key("s", MODIF_ALT);

lr_think_time(5);

ctrx_key("c", MODIF_ALT);

return 0;

}

close_account_4(){

lr_think_time(5);


lr_think_time(5);

return 0;

}

vuser_end(){

ctrx_disconnect_server("172.16.10.215");

return 0;

}

Figure 5. Distribution Script 4


18/33


/* -------------------------------------------------------------------------------

Script Title : Distribution Script 6

Script Description : From PeopleSoft HTML Benchmark Kit


------------------------------------------------------------------------------- */

vuser_init(){




lr_think_time(3);

ctrx_wait_for_event("LOGON");

lr_think_time(3);


return 0;

}

web_login_6(){




lr_think_time(3);




lr_think_time(3);

ctrx_type("psft");


lr_think_time(1);

ctrx_type("psft");


lr_think_time(1);

return 0;

}

env_select_6(){

lr_think_time(1);




ctrx_type(" ");

lr_think_time(1);



ctrx_type(" ");

lr_think_time(1);

return 0;

}


lr_think_time(3);

while (!ctrx_win_exist("PeopleSoft*- Microsoft Internet Explorer",8)==0){

web_login_6();


19/33


env_select_6();

}







lr_think_time(8);

ctrx_type("2/G42112");

lr_think_time(3);



lr_think_time(3);

return 0;

}

order_entry_6(){

lr_think_time(5);

ctrx_type("4341");


ctrx_type("SO");



ctrx_type("M30A");


lr_think_time(10);




























20/33























































ctrx_type(" ");


21/33


lr_think_time(5);


lr_think_time(10);

ctrx_key("o", MODIF_ALT);

lr_think_time(5);











































lr_think_time(3);


lr_think_time(5);

return 0;

}

close_account_6(){


22/33


lr_think_time(5);


lr_think_time(5);

return 0;

}

vuser_end(){


return 0;

}

Figure 6. Distribution Script 6


23/33


/* -------------------------------------------------------------------------------

Script Title : Financial Script 2



------------------------------------------------------------------------------- */

vuser_init(){




lr_think_time(3);


lr_think_time(3);


return 0;

}

web_login_2(){




lr_think_time(3);




lr_think_time(3);

ctrx_type("psft");


lr_think_time(1);

ctrx_type("psft");


lr_think_time(1);

return 0;

}

env_select_2(){

lr_think_time(1);




ctrx_type(" ");

lr_think_time(1);



ctrx_type(" ");

lr_think_time(1);

return 0;

}


lr_think_time(3);


web_login_2();

env_select_2();


24/33


}







lr_think_time(8);


lr_think_time(3);



lr_think_time(3);

return 0;

}

search_name_2(){

lr_think_time(3);

ctrx_key("s", MODIF_CONTROL);

lr_think_time(6);

ctrx_type("BAABRP");


ctrx_type("V");

lr_think_time(3);


lr_think_time(7);










lr_think_time(3);

ctrx_type(" ");

lr_think_time(5);


lr_think_time(5);









ctrx_key("LEFT_ARROW_KEY", 0);

ctrx_key("LEFT_ARROW_KEY", 0);

lr_think_time(5);


lr_think_time(5);

return 0;


25/33


}

supplier_entry_2(){





















































26/33


























lr_think_time(7);

ctrx_type("3334");

lr_think_time(8);









lr_think_time(8);


lr_think_time(3);

return 0;

}

close_account_2(){

lr_think_time(2);


lr_think_time(8);

return 0;

}

vuser_end(){


return 0;

}

Figure 7. Financial Script 2


27/33


/* -------------------------------------------------------------------------------

Script Title : Financial Script 5



------------------------------------------------------------------------------- */

vuser_init(){




lr_think_time(3);


lr_think_time(3);


return 0;

}

web_login_5(){




lr_think_time(3);




lr_think_time(3);

ctrx_type("psft");


lr_think_time(1);

ctrx_type("psft");


lr_think_time(1);

return 0;

}

env_select_5(){

lr_think_time(1);




ctrx_type(" ");

lr_think_time(1);



ctrx_type(" ");

lr_think_time(1);

return 0;

}


lr_think_time(3);


web_login_5();

env_select_5();


28/33


}







lr_think_time(8);


lr_think_time(3);



lr_think_time(3);

return 0;

}

change_date_5(){







































29/33

















lr_think_time(3);

ctrx_type("1");








ctrx_type("02/28/99");


lr_think_time(5);

ctrx_type("12/31/99");


ctrx_type(" ");

lr_think_time(4);


lr_think_time(3);

return 0;

}

level_detail_5(){


lr_think_time(5);

















30/33













































lr_think_time(3);

ctrx_key("DELETE_KEY", 0);

ctrx_type("5");

lr_think_time(5);


lr_think_time(3);







31/33



















































ctrx_type("1");

lr_think_time(5);


lr_think_time(3);

return 0;


32/33


}

close_account_5(){

lr_think_time(5);


lr_think_time(5);return 0;

}

vuser_end(){


return 0;

}

Figure 8. Financial Script 5


33/33

851 West Cypress Creek Road Fort Lauderdale, FL 33309 954-267-3000 http://www.citrix.com

Copyright 2005 Citrix Systems, Inc. All rights reserved. Citrix, the Citrix logo, Citrix ICA, Citrix MetaFrame, and other Citrix product names aretrademarks of Citrix Systems, Inc. All other product names, company names, marks, logos, and symbols are trademarks of their respective owners.

JDE on CPS 4.0 Scalability Analysis

Documents

Transcript of JDE on CPS 4.0 Scalability Analysis