For this step, the UTM application can be run on any UTM platform. (BS2000, Unix, Linux, or Windows system).
The UPIC clients can run on any UPIC platform. Even UPIC clients based on the product openUTM-JConnect are supported.
During this phase, the communication between the UTM application and the UPIC clients must be recorded in full and the trace length must be greater than the maximum message length. This is achieved using the UTM function BCAM trace.
In addition, UpicReplay ignores the UPIC client call for setting a new password.
On BS2000 systems, both UPIC clients and UTM applications support encryption.
On Unix, Linux and Windows systems, UPIC clients and UTM applications only support encryption if a suitable openSSL library has been provided.
Please note that it must also be possible to repeat the required UTM services as often as necessary.
To do this, proceed as follows:
Start the BCAM trace by setting the start parameter BTRACE=ON,length, see "Start parameters for openUTM". You are recommended to specify the maximum value for length to prevent messages from being truncated. You can also enable the BCAM trace by means of the administration functions (KDCDIAG command or via WinAdmin/WebAdmin). In this case, however, the default value (256 bytes) is assumed for length, if you have not specified any other length with the BTRACE start parameter.
Perform the UPIC conversations between the UPIC client and the UTM application that are required for the load simulation. This also includes all aspects of establishing the connection to the UPIC clients. The associated UTM services must be fully completed at least once.
End the BCAM trace by means of the KDCDIAG command or via
WinAdmin/WebAdmin.
This step results in binary TRACE files for all UTM processes. For details on the BTRACE files, see openUTM manual ”Messages, Debugging and Diagnostics”.