To maintain user session the Oracle Forms Application Server will usually issue session information to the Oracle Forms client via a ticket number (ICX_TICKET). To correctly establish a connection to the server this session or ticket number may need to be parsed from the Oracle Forms server response and then set in the connection string of the function "OraFormsConnect". In the example below you can clearly see that the ICX_Ticket number is not being sent to the server for the function "OraFormsConnect". Although the application has indicated that the script has successfully logged on it does not mean that the virtual user can correctly communicate with the server. If the dynamic ticket number is not parsed and set in the OraFormsConnect function then it can result in errors for any of the subsequent OraForms functions. Recommendations: Ensure that if the Oracle Forms Server issues a dynamic ticket number that this number is correctly parsed and set in the BDF script. Use verification to ensure that the correct data / window has been returned, e.g. OraFormsVerifyRadioValue function to verify the values of the radio buttons. See also Load Testing Oracle Forms in the Silk Performer"s Advanced Concepts book. Start | Programs | Silk Performer x.x | Documentation | Advanced Concepts NOTE: if recording Oracle Forms 12i, it may be necessary to clear the hardcoded ICX_Ticket number before the parse to get the new session infromation is parsed. Please see Customizing Oracle Applications 12i Scripts for Replaying in the Silk Performer User Guide Start | Programs | Silk Performer x.x | Documentation | UserGuide Old KB# 17981
↧