The following check steps have been changed:
| Check Step | Phase | Type | Description |
|---|---|---|---|
| Check RFC generation | Playback | Check Step | The check on whether the RFC wrappers have been generated or not is only relevant to outbound RFC service virtualization. This is currently not generally supported in v2.20 so this check step has been removed configuration is put in place in the gateway (transaction SMGW). |
| Shared Memory Check | Recording | Check Step | This check step ensures that there is sufficiently enough shared memory upon each application server of the recording system prior to allowing the recording to be turned on. The two key parameters are the amount of shared memory allocated and the maximum number of objects that are allowed in shared memory. The comparison is currently made against a fixed value. The shared memory estimation should be used in conjunction with this check to make sure that there is enough shared memory to capture the relevant transactions. |
| Screen sizing program check | Playback | Check Step | This check step ensures that the screen-sizing program has been executed on the execution queue prior to the playback. The program name is /BTI/AUT_BOT_SCRN_SIZE_ANLYSIS and it should be run on the central system after the execution queue has been built. The output of this program is to inform you of the screen-sizes contained within the recording (number of rows) and prompt you to ensure that the bots have the right screen-resolution to support the playback. |
Post your comment on this topic.