Libraries manager
< Prev Project Preferences Next >

Libraries manager

The libraries manager allows you to select for AMF and GWT the libraries needed to decode requests and responses of those modules.

Adobe Flex/AMF

Those preferences allows you to:

  • Select the server-side AMF implementation; "Adobe" is the value selected by default. Implementations provided by Adobe and GraniteDS are officially supported.

  • AMF libraries must be declared according to selected implementation.

    • Adobe Flex/AMF project preferences allow you to declare/delete AMF libraries on-the-fly, without the need to restart NeoLoad.

    • When a JAR file has been successfully loaded, the JAR file is copied into the currently open project's folder (in folder <NeoLoad Project>/lib/plugins/amf/).

    • Each time an AMF library is declared, every AMF request within the project is inspected; NeoLoad will try to repair the requests whose content has not been fully converted into XML format.

    • When load testing an Adobe Flex/AMF application, the declared AMF libraries are copied automatically to each Load Generator selected in the scenario.

Adobe AMF Server

Select "Adobe" server-side implementation for LiveCycle or BlazeDS -based servers.

In this case, implementing java.io.Externalizable server-side allows you to customize 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).

To declare one or more AMF libraries:

  1. Select "Adobe" implementation.

  2. Click on the "+" button and select the JAR files used by the Flex application being tested.

  3. NeoLoad automatically repairs all AMF requests not already successfully converted into XML.

  4. In the event of failure, more information is available in the appropriate log file plugins.log.XXX (the logs folder can be opened from the NeoLoad menu by clicking "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 you to customize the way objects are sent over the network. To display these objects correctly in NeoLoad, the following elements need to be declared:

  • granite-config.xml: describes the GraniteDS custom flex application mechanisms.

  • JAR files containing Instanciator, Externalizer, Descriptor...: all custom mechanisms declared in granite-config.xml.

  • JAR files containing Java Beans: the Java objects exchanged between the client and the server using custom mechanisms and all their Java dependents.

To declare one or more AMF libraries (Jar and/or XML files):

  1. Select "GraniteDS" implementation.

  2. Click on the "+" button and select the granite-config.xml file on your hard disk drive.

  3. Click on the "+" button again and then select the JAR files containing the custom GraniteDS mechanisms and the Java Beans used by the Flex application being tested.

  4. NeoLoad automatically repairs all AMF requests not already successfully converted as XML.

  5. In the event of failure, more information is available in the appropriate log file plugins.log.XXX (the logs folder can be opened from NeoLoad menu by clicking "Help / Open logs folder...").

[Note]Note

AMF libraries can be drag and dropped from the file explorer into the declared libraries table.

Google Web Toolkit

For NeoLoad to decode the GWT requests and responses into XML, the required libraries must be declared. The libraries that are required are:

  • Java objects that are transmitted over the network between client and server using GWT-RPC.

  • The interfaces of the services called by the client application using GWT-RPC.

  • The serialization policies files.

Declare these items using the following procedure:

  1. Click the "+" button, then select the files used by the GWT applications to be tested.

  2. NeoLoad automatically repairs any GWT requests flagged as incorrectly converted to XML.

  3. If the repair fails, you will find further information on the error in the log file: plugins.log.XXX (the logs directory can be accessed via the "Help / Open logs folder..." NeoLoad menu item).

< Prev Up Next >
Oracle Forms Home dynaTrace