OSI PI UDS/UDC Collective Name failover

[Former Member]

We are running SAP XMII 11.5.3 b66, utilizing UDS 2.5.0.4. There is a collective set up on the PI server but when we failover the PI servers the UDS does not do the same. We expected the collective PI to utilize the secondary, but never does.

PI-SDK is loaded on the xmii server.

Should we be using a more recent version of the UDS, or is there a way to monitor the pi servers and switch the server connector to the live system?

Thanks,

Ed for Shari

[Former Member]

Hi Ed:

The UDS does not support PI Collective, however there are several work arounds you can use. Please se SAP Note 1545962 for more details.

Regards

Chris Carney

[Former Member]

The UDS does not support PI collectives because the connector is based on the PI-API, which is not HA-aware. PI-OLEDB or PCo-based connections are aware of collectives because they are based on the PI-SDK (the SDK's connection manager handles the failover - nothin' to do with MII).

Apparently, UDS-based data writes would function in a collective and recognize a failover, providing the PI-Buffer Server has been enabled (which is SDK-based). Haven't tested that one though.

[agentry_src]

Hi Paul,

I would be curious to see what the result of your testing is, having run into the PI-API failover issue in the past.

Thanks,

Mike

[jcgood25]

Ed - signing up for SDN access is free, then you can have your own identity

Thank you for posting here on the forum - hopefully someone will chime in soon with some practical insight, but I'll simply restate what I put in my response to Doug (your other shared identity of the week):

Unless the PI system bridges some sort of a hot swap or could be u2018connectedu2019 through a shared IP address that dispatched the request to the u2018aliveu2019 instance I donu2019t think there is any way that MII would do this (aside from programming it yourself with a bit of a ping check before the queries would run to data server A or B).

Regards,

Jeremy