Hi All,
Finding that everyone should know: Export Sets do not support MID Server Cluster i.e. If your export target is set to MIDServer1 and if that MID server belongs to MID Server Cluster and if it goes down ServiceNow do not change this MID Server to another MID Server under the same Failover MID Server Cluster.
Note: This is expected because ServiceNow only support the cluster to all the records which enters in ServiceNow ecc queue(ecc_queue). As we have one Business Rule which works on "OnBefore" on ecc_queue table and checks the cluster information if the MID Server status is down and routes to another MID Server within the same Failover MID Server Cluster
There is a field called as "ECC Queue" and every time it creates a export set history record it populates the ecc queue as "StreamPipeline" which shows the Agent Name as MID Server name but it insert the record in export history with ecc queue and mid server attachment as empty as the MID Server which is used by your Export set is down and it put the export history with status as "Completed with Error"..
This is my learning for the day which is very helpful to me to understand why the file didnt reach to destination even when the cluster was ON.
Hope this helps.
Please mark this helpful if it really helps you out.
Thanks,
Shamma
Regards,Shamma Negi
