During the recording, NeoLoad compares the HTTP headers in the request and response with those configured. When there is a match, the request is identified as an Oracle Forms request and the encapsulated binary data is decoded.
By default, HTTP headers are configured to recognize Oracle Forms 9i and 10g messages.
To change the module general settings, see Oracle Forms.
During the recording, NeoLoad simultaneously uses two mechanisms to prepare the requests for execution :
DataMessages that reference invalid components (non-existing or previously destroyed). These
DataMessages are removed from the requests.
handlerId's to be handled dynamically. The component naming option must be configured on the Oracle Forms server for this mechanism to function.
During a test run, NeoLoad plays back the recorded requests.
For each played-back request, NeoLoad searches the previous responses to find the component having the same name and replaces the Id assigned by the server (its
handlerId). This mechanism only functions if the component has a server-assigned name.
If the component does not have a name, NeoLoad compares the played-back response with the recorded response and updates the component
handlerId. This mechanism only functions if the response received during the test playback contains exactly the same number of
DataMessages as during the recording.
NeoLoad also checks to make sure the
handlerId's used in the requests
DataMessages reference valid Oracle Forms components. If one or more invalid components are found, an error is returned and the Virtual User is stopped.
To change the module project settings, see Oracle Forms.