Connected systems like databases or others have maintenance times during the night or weekend, when they are shut down. Installed connectors (for DB2 for instance) then throw 'can't connect to database' errors. These type of errors then appear in reports and alarms, having no real meaning or importance. They are bastardising the (report) results, statistics and messages.
by: Ted E. | over a year ago | Integrations
Comments
This is probably more about being able to schedule when event sources run/don't run than the connector itself. (The code would still be part of the connector)