![]() ![]() The maximum time to wait to establish the connection by the sampler. The truststore file can be specified in same file with =. The keystore file and password can be specified in system.properties file by adding the lines =, =. The SSL protocol to use if it's required by the server. If the server does not supports the chosen one, it will use the default value for the protocol. The terminal type to emulate from the client. If the server is an AS400 or iSeries it typically uses TN5250, on the other hand, if it's a mainframe system it uses TN3270. The protocol to use in the communication. The port number to connect, default value is 23. The RTE Config element sets the parameters to be used by the sampler in order to establish a connection to the server. ![]() When a View Results Tree JMeter test element is included as a child of the RTE recorder, then all interactions between the Terminal Emulator and the mainframe application will be showed on the View Results Tree and allow for proper analysis and validation of all information sent and received from the mainframe application. Once we have ended the flow that we want to record, we can easily close the terminal emulator or press STOP button to stop our recording. Every interaction will be automatically saved in samplers ( check out everything about samplers ). Now we are able to interact with our client through RTE-Emulator. After the connection to the mainframe application is established (supposing configurations are right), the Terminal Emulator will show up.Ĭlick here to see all the information you must know about terminal emulator. Once everything is configured, the user proceeds to start the recording session, pressing START button. Timeout Threshold: This field will set the timeout which later on the waits conditions will use to set the proper time out for the conditions.Restart: This button is the equivalent to pressing stop and start buttons.Once this button is pressed, the recording will be stopped and Disconnect Sampler will be added to the test plan followed by the closure of the terminal emulator. Stop: This button allows the user to stop current recording.Additionally, after button is pressed, an RTE-Config and Connect Sampler will be added to the test plan. Start: This button allows the user to begin with the recording and to connect to the mainframe application through a terminal emulator.Details about Timeout Threshold field and how the wait conditions works can be found here. These configurations are the same ones detailed in RTE-Config. To start recording, the user should specify the Server, Port, Protocol, Terminal Type, SSL Type, Timeout and Timeout Threshold. Go to Files -> Templates -> and select Recording RTE The plugin adds four different elements to JMeter: A Recording Controller (RTE-Recorder)įirst all is necessary to add a template which is going to contain all the elements required to begin with recording. To use it as a maven dependency, just add this in your pom.xml: Besides, the sampler allows to simulate the existing attention keys on the terminal keyboard like ENTER, F1, F2, F3., ATTN, CLEAR, etc. Additionally, the plugin allows for manual test plan creation, providing a config element for setting connection parameters and a sampler to set fields on screen and attention key to send to the mainframe application. The plugin provides a recording controller, which allows the user to interact through a terminal emulator, recording every interaction (samplers) with the mainframe application. People who usually work with these IBM servers interact with them, basically, by sending keystrokes from the terminal keyboard (or emulator) to fill forms or call processes. Nowadays the plugin supports IBM protocol's TN5250, TN3270 and VT420 by using embedded xtn5250, dm3270 and jvt220 emulators, with some modifications on xtn5250 fork, dm3270 fork and jvt220 fork to better accommodate to the plugin usage (exception handling, logging, external dependencies, etc). This project implements a JMeter plugin to support RTE (Remote Terminal Emulation) protocols by providing a recorder for automatic test plan creation, and config and sampler for protocol interactions.
0 Comments
Leave a Reply. |