We are working to adjust the notification settings in Archer Control Panel. We need run some tests to replicate the failed email attempts to gather the test evidence. How can we replicate this?
My assumption is to shut down RSA Archer Job Engine service in app server where we can replicate the issue?
not only firewall configuration, it could take days for FW to implement then changes in non-Production environment. we are looking the easiest way to replicate the issue.
We have detected the issue when there was patch updates that require reboot, where it cause the notification failed email attempt.
We are looking for fail-success scenario. We tried to mockup SMTP address or port number with the Retries is 5 and the retry timeout is 120 seconds in Archer Control Panel.
My expectation is failed notification with 5 or 6 times should be ultimately failed for notification to trigger after 10 minutes. If failed notification attempts runs less than 10 minutes, this same notification should trigger.
the failed notification attempts log seems not accurate. Is there something we need raise the case to RSA Archer Support?
Hm, I am not sure. If you defined the retries as 5 times with timeout of 120 sec, it means that there will be 5 trials in 120 sec each, and nothing after that. Did it behave differently?
that's correct. if i understanding correctly with ACP Notification option settings with retire 5 times with 120 seconds timeout:
1. Notification should triggered after failed attempts few times less than 4 times or less than 10 minutes.
2. Notification could abandoned after 5 times or after 10 minutes.
The first one above which we tried to revert the changes in mockup SMTP or Port in ACP notification settings during 5 minutes, notification has not triggered.
Per our policy in our company, we are required to provide the proof / evidence of fail/success scenario.
I would say it is not like failed notification should be resent less than 4 times OR less than 10 minutes. It is AND, it will be resent 4 times with 120 sec interval.
That should be logged in the Archer logs, I would say. If it is not doing so or not logged anywhere, you can ask clarification for support.
Here is how we tried to gather the test evidence with replicate the fail/success scenario:
- Update mockup with bad info in [Server Address] or [Port] and save changes in ACP
- Create new record with instant notification
- Wait for 5 minutes
- Revert the changes to correct info in ACP and save
- Check the activity log reports for ‘Failed Attempts’ and ‘Notification Sent’
RSA Archer Support mentioned that retry logic is job specific. If I am updating the ACP correct information (step #5 above) , the issue is same notification will not sent due to the job was created when then bad information was in the ACP.
Updating the bad information in ACP during middle of testing will not help at all, is there alternative way to change and test with failed attempts and then sent same notification WITHOUT touching the ACP? All I can think of to test the 'Fail/Success' scenario:
1. Disconnect mail sever?
2. Disable RSA Archer job engine service?
3. Disconnect network pointing from Archer app server?