Failover MID server for LDAP Integrations

[nicholasmayo]

Hey there folks,

I couldn't find anything on the documentation so I was wondering if anyone could help me. We're moving over to a MID server integration with our LDAP server to populate our user base, and I was wondering what the best practice is for redundancy?

I don't want to set up two entries that simultaneously run, but I would like to have an automatic failover in case the MID server goes down. Ideally, if the MID server goes down and the integration is severed, another MID -> LDAP integration becomes active in it's place.

Any idea if this is possible OOB? Or would I have to set up some event queuing and scripts to set a different MID -> LDAP entry to active?

Thanks!

[rlatorre · Accepted solution]

We do the same thing for all integrations that utilize a MID server. We have an alternate (BCP) server with mirrored MID servers installed.

We have a business rule on the MID server table that does the switch-over if a "Production" MID server's status changes from "Up" to another value.

It searches these tables for records referencing the downed MID server and switches to the BCP counterpart. These meet our needs.

sys_soap_message_function

sys_data_source

Then it creates an Incident for investigating the issue.

If you want an example of the code let me know and I'll try to provide a generic version for you.

[nicholasmayo]

Alright thanks! I'll use that if there isn't a simpler solution.

[Admin Pro]

This might be too late, but you can use the cluster feature under MID Server. There are two types of cluster, fail-over and load balance. You can read more about it in here: Cluster

[Addie3]

Can you help with an example of this code please? I am in the same boat and need urgent solution.

Thanks.