Record RTMP requests

To record RTMP requests, see Record a test scenario and check RTMP in the recorded protocols.

• Warning: There are certain limitations regarding the recording of RTMP applications in NeoLoad. See Limitations.

For the record, the RTMP protocol enables the carrying of data including customized objects (encoded using AMF protocol), audio and/or video. If the Java object classes are missing, the request binary data cannot be decoded for conversion to XML. The following procedure explains how to solve the problem of missing Java classes.

In Java, an object is termed externalizable when it implements the java.io.Externalizable interface. These objects are particular, in that they manage the saving and restoring of their attribute values themselves. Declaring these Java classes using Adobe RTMP libraries manager is mandatory.

• To record RTMP requests

1. When you close the browser, the Post-Recording Wizard is displayed.
2. Select the JAR files to declare.
3. Repeat the operation as required.
4. Once all the necessary JAR files have been loaded successfully, a confirmation screen is displayed.

During recording, NeoLoad detects that RTMP channels have been created and offers to create a copy of the Virtual User that will allow the scenario to be run. The RTMP channels are blocking actions pending reception of the server messages. To be able to simulate a user using RTMP, you need to create this simplified Virtual User. See RTMP channel.

When copying the Virtual User, NeoLoad inserts the RTMP channels in Fork actions and creates the various types of Push message received during the recording.

For more information about the next steps in the wizard, see Post-recording wizard.

Home