Reproducing error situations

Often, error situations are difficult to reproduce, especially, when running GUI applications. In order to be able to reproduce application errors, ODABA supports an activity log, which allows recording and replaying a sequence of activities for one or more asynchronous applications.

In order to replay GUI applications, the ACTIVITY_LOG.PATH option has to be set to a file location for the activity log file. In case of recording asynchronous applications, all applications may refer to the same activity log file. This ensures the proper recording of activity sequence, although when time settings of applications differ. In order to record activities for several users (applications), a user name may be set in ACTIVITY_LOG.USER . When no user is defined, the system login name is used, for recording activities.

In order to replay an activity log, the ACTIVITY_LOG.REPLAY option has to be set to true (or YES ). One may replay an activity log in real time ( ACTIVITY_LOG.SPEED = 1 ) or with higher speed depending on the speed factor defined. When speed is set to 0, time relations are ignored and activities are performed immediately.

In order to synchronize sessions for several applications, one may set a start time ( ACTIVITY_LOG.START ) for replaying several applications simultaneously.

An activity log may contain activities of several sessions. In order to replay a specific session within an activity log, a session number may be set (( ACTIVITY_LOG.SESSION = 5 ).