if you're connecting to an IP address - this should be transparent.

when a failover happens, the backup takes ownership of the VIP address as part of the process of it becoming a primary, you can find out more details in the documentation - here

I've posted the 'Clustering options for high availability and scalability' slides on SlideShare  (here)

@Sven,

Caché does not support outgoing NTLM authentication, EWS will have to be configured to allow basic authentication which in turn allows Caché to provide a username/password from that domain.

The connection can be made more secure by requiring TLS prior to transmission or requiring client certificate authorization.

Oren

Sven,

which direction are you talking about?

incoming - clients coming into Caché providing credentials that need to be authenticated against Active Directory

outgoing - Caché/Ensemble needs to authenticate against a third party service and needs to provide credentials that can be authenticated against Active Directory

Oren

Just to clarify regarding option 1, the idea is to add the extent index to the USA.President class like this

Class USA.President extends USA.Person

{

Property PresNumber as %Integer;

Index PresNumberIDX on PresNumber;

Index Extent [Type=Bitmap, Extent];

}

Kevin,

FWIW i've setup a mirror on windows 10 & 7 and doing so through the management portal was fairly easy and straight forward (assuming you remember to turn off windows firewall or open the right ports before you start)

I'd also repeat an earlier comment - remember that if you're setting failover mirror with those two machines, operations can failover from one to the other, i suspect that's not what you're looking for so you might want to make the second member an async member.