Click Connection Events Test on the Debug menu to confirm that the life cycle event handlers and model event handlers you have added to your model are performing as you expect. Use this dialog box to test sequences of events that require a reset of the terminal session: connecting to the host and establishing a client connection. You can perform tests in both dedicated model and pooled session environments. In order to use the Connection Events Test, the model must be connected to the host, but login is not required.
Review the details on the startup and shutdown behavior for each of these test options.
Click New Client to simulate the sequence of one client application disconnecting and another client connecting to this model using the ConnectToModel API.
If the event handler requires a user name and password, specify the client user credentials here. An Authenticate User event will be sent to the event handler based on the credentials shown here. The initial values are based on those provided on the Environment tab in the Event Handler Settings dialog box, but you can change them. You can also update the Environment tab settings if you make changes here. The credentials you use for this test remain current until another test or a reset.
You can also specify or review host credentials. Click the Model Variables button to view or change other model variable values.
The Connection Events Test dialog box checks the event handlers currently associated with life cycle or model event handlers displayed here.
After you have specified your test parameters, the Edit, Rebuild, and Reload options are available as you debug the event handlers.
Click the Edit button to open the selected event handler in your default editor.
After editing an event handler, click this button to recompile event handlers and to update them for the default JAR file.
Click this button to reload all event handler libraries to match the latest copies stored with the model.