Is it possible to automate session handling during the recording process when testing AMF3 applications?

Is it possible to automate session handling during the recording process when testing AMF3 applications?

Silk Performer 2010 R2 will have built-in functionality that improves the automation of some session handling during the recording process.

In order to avoid duplicate session errors when replaying against BlazeDS environments, Silk Performer 2010 R2 will dynamically parameterize "AppendToGatewayUrl" Flex headers (jsessionid) and automatically parameterize the "DSid" (which is essentially a session id). Both the "AppendToGatewayUrl" and the "DSId" occur in the response to the "CommandMessage" and they then need to be used in subsequent requests.

It is also possible to add this functionality to Silk Performer 2010 by using the attached "FlexAMF3.sep" file.

To enable this functionality for Silk Performer 2010, rename (or take a backup of) the existing "FlexAMF3.sep" in the "\Working\Essentials" directory. Then copy the new unzipped "FlexAMF3.sep" that is attached to this article into that directory.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.