Adobe Flex/AMF

These preferences allow:

Adobe AMF server

The Adobe server-side implementation consists of implementing the LiveCycle or BlazeDS -based servers.

In this case, implementing java.io.Externalizable server-side allows customizing how Java objects are sent over the network. To display these objects correctly in NeoLoad, JAR files containing the Java classes need to be declared (including all dependent Java classes and third party libraries).

  1. Select the Adobe implementation.
  2. Click on the + button, and select the WAR file or the directory of the Web application being tested. NeoLoad automatically retrieves all the required JAR files. You may also manually select the JAR files used by the Adobe Flex applications being tested.
  3. NeoLoad automatically repairs all AMF requests not already successfully converted into XML.
  4. In case of failure, more information is available in the relevant plugins.log.XXX log file (the logs directory can be opened through Help > Open logs folder).

GraniteDS AMF server

GraniteDS is an open-source server-side implementation of the AMF protocol. NeoLoad supports Flex applications based on GraniteDS 1.1.0 RC4 or higher.

GraniteDS allows customizing the way objects are sent over the network. To display these objects correctly in NeoLoad, the following elements need to be declared:

  1. Select the GraniteDS implementation.
  2. Click on the + button, and select the WAR file or the directory of the Web application being tested. NeoLoad automatically retrieves all the required JAR files as well as the granite-config.xml file. You may also manually select the granite-config.xml file and JAR files containing the custom mechanisms and Java Beans used by the Flex applications being tested.
  3. NeoLoad automatically repairs all AMF requests not already successfully converted into XML.
  4. In case of failure, more information is available in the relevant plugins.log.XXX log file (the logs directory can be opened through Help > Open logs folder).