<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! RTCEE Performance Testing: Mixed EE Benchmark and Incremental Build for Regression Scenario<img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/todo.png" alt="todo.png" width="50" height="50" align="right"> %DKGRAY% Authors: [[Main.JorgeAlbertoDiaz][Jorge Diaz]] <br> Build basis: RTC 4.x %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> %STARTSECTION{"Intro"}% This scenario is consider one of the "Additional" ones, as it's not part of the standard set of test scenarios executed every time (i.e. in every release), as part of the RTCEE Benchmark Tests. <br/> The specific scenarios in this category will vary because they are specially designed in every release to test the features that have performance related changes. %ENDSECTION{"Intro"}% ---++ Scenario Detailed Description Following the detail of the different steps that are performed for testing this scenario: <table class="gray-table"> <tbody> <tr> <th align="center">Scenario</th> <th align="center">Test Steps</th> <th align="center">Description</th> </tr> <tr> <td>Enterprise Extensions Benchmark Scenario</td> <td>1. Perform an initial Full Enterprise build of all the programs included in the test data set</br>2. Run a Promotion</br>3. Package the application</br>4. Run a Deployment.</td> <td> After a first complete build of all the programs, a component promotion is performed. Once promoted the sources and binaries, the latter are packaged and finally deployed. <br/> The tests are executed with different sets of the Scalability Test Data to get information of the system resources consumption with different levels of load. </td> </tr> <tr> <td>Incremental Build Scenario</td> <td>1. Change a copybook and request build. </br>2. Change a COBOL file and request build</br>3. Change ALL copybooks and request build</td> <td>Once finished the full end-to-end iteration of the "Enterprise Extensions Benchmark Scenario" this follows executing different changes and scope of team builds. <br/> Firstly the copybook "MortgageApplication-Common\zOSsrc\COPYBOOK\JKEMTCOM.cpy" is modified and a build requested. Modifying this copy will impact four COBOL files: "JKEMLIST.cbl", "JKECSMRT.cbl", "JKECMORT.cbl" and "JKECMAIN.cbl". <br/> Then the COBOL file "MortgageApplication-JKECMORT\zOSsrc\COBOL\JKECMORT.cbl" is changed for a new build request. <br/> The test finishes requesting a build after changing all the copybooks. </td> </tr> </tbody> </table> ---++ Test Topologies The following topologies are being used for the execution of this scenario in order to test the performance and gather relevant data. %INCLUDE{"RTCEETestingTopologies" section="SingleTierZ"}% ---++ Test Reports %RED% Fill with a brief introduction and links to relevant data %ENDCOLOR% ---+++++!! Related topics: ---+++++!! External links: * [[https://www.ibm.com][IBM]] ---+++++!! Additional contributors: <sticky></div></sticky>
This topic: Deployment
>
WebHome
>
DeploymentPlanningAndDesign
>
PerformanceDatasheetsAndSizingGuidelines
>
RTCSystemZPerformanceTesting
>
RTCEEBenchmarkIncBuildTests
History: r2 - 2014-09-08 - 15:43:05 -
JorgeAlbertoDiaz
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.