mlreplay [options] [name=value  [name2=value2...]] [[dll_name] filename]

Each recorded file is called a recorded protocol file. Everything received from the start of a connection until the end of that connection is recorded in a separate recorded protocol file. Each recorded protocol file is named recorded_protocol_x.mlr where x is the job ID. The MobiLink server -rp option is used to specify that the MobiLink server should record all MobiLink protocol it receives from its clients. See -rp mlsrv12 option.

In addition to the data sent to and from the MobiLink server, the recorded protocol file also contains timing information so that mlreplay can replay the recorded protocol information exactly as it was originally performed. The timing information is also used to try to make the simulated client take the same amount of time as the original client.

By default, mlreplay plays back the recorded protocol file without any changes. However, you can customize the replay session using different options. The simulated client information consists of the username, password, remote ID, and last download time. This information can be customized using the -u, -p, -r (or -rg), and -ldt options respectively.

The mlreplay utility can replay a recorded protocol file concurrently using the -sci simulated client information file option, where the simulated client information file is a .CSV file that lists the username, password, remote ID, and last download time for each simulated client. The mlreplay utility launches a simulated client for each simulated client information line in the simulated client information file.

The mlreplay utility can run multiple simulated clients to replay a protocol at the command line. The number of simulated clients to run can be specified by the -n option. Use the asterisk character to denote the simulated client number when specifying usernames, passwords and remote IDs with the -u, -p and -r options, respectively. The username, password and remote ID for each simulated client are determined by the following rules:

The amount of time the original synchronization took is part of what is recorded, so mlreplay can attempt to replay the synchronization in the same amount of time.

The mlreplay utility can replay a recorded protocol file multiple times concurrently.

Use the following MobiLink server options with the mlreplay utility:

Further customizations can be made to the replay session using the MobiLink Generated Replay API utility.

• MobiLink Generated Replay API utility (mlgenreplayapi)
• -rrp mlsrv12 option
• -rp mlsrv12 option
• -lsc mlsrv12 option

Assume that you have a simulated client information file, mlreplay.csv, that specifies 100 simulated clients. The following example illustrates how to use the -sci and -n mlreplay options together to replay up to five of those simulated clients:

mlreplay -ap -x tcpip -sci mlreplay.csv -n 5 recorded_protocol_mlreplay_svr.mlr

In the following example, you run multiple simulated clients at the command line:

mlreplay -ap -x tcpip -u user_$ -p password_$ -r remoteid_$ -n 5 -rp $ recorded_protocol_mlreplay_svr.mlr

In this example, mlreplay runs two simulated clients. The first client is run with the user_1 username, password_1 password, and remoteid_1 remote ID. The second client is run with the user_2 username, password_2 password, and remoteid_2 remote ID. By default, the asterisk character is used to indicate the simulated client number in the -u, -p, and -r parameters. The -rp option overrides this pattern and instructs mlreplay to substitute the dollar sign character for the simulated client number.