In order to test the automatic TSE replacement, the same criteria (prerequisites) must be met as those that apply to a replacement during live operation. Further information on this can be found in the article "Automatic TSE Replacement".
Unlike the automatic replacement of, for example, a faulty TSE or in the event of a certificate expiry,
- during tests, the switch from one TSE to another is carried out immediately once the prerequisites are met (no open TSE transactions, EndOfDay completed, etc.),
- the TSE replacement does not need to be activated in the configuration (checkbox “Enable automatic TSE replacement” does not need to be selected).
Performing a test
To test the behaviour during a TSE replacement, click the "TSE Replacement" button. This will be displayed as an action item on all terminals that meet the prerequisites (see the article "Automatic TSE Replacement").
If the button is not displayed, not all prerequisites are met. Please check the requirements again (including the Middleware version used and the licence assignment).
Once the TSE replacement has been triggered via the "TSE Replacement" button, the replacement is carried out immediately (!).
If
- there are any open TSE transactions, or
- no EndOfDay document has been stored on the client,
the process is aborted and corresponding error messages are displayed in the log events, via the notification bell (top right) and by email.
Similarly, if the replacement is carried out successfully, corresponding messages are displayed (log events, bell, email).
Attention: the "TSE Replacement" button also works on live systems and can be used there to replace a TSE immediately (!). A confirmation prompt will appear asking whether you really wish to proceed. Please bear in mind that immediately replacing a TSE in live operation should only be done with caution.
Comments
0 comments
Please sign in to leave a comment.