Very Computer

> I am working on a system where we have a server-type application that
> uses Sun Directory Server 5.2 as a data store (for user information,
> etc.), and we have two instances of DS 5.2 configured with replication
> between them.  

> The  application does both reads and writes to DS 5.2, but it itself
> doesn't have any failover capabilities built-in (e.g., where it would
> detect if one instance of DS is down and switch to the other instance).
> The server application is a COTS product, so we don't have any way to
> get into the source code.

> So, I was wondering if there is any capability in Solaris 9 that would
> allow us to configure things so that when the primary (master/supplier)
> DS 5.2 instance is down, Solaris itself would somehow automatically
> switch things around (sorry for the non-technical terminology) so that
> the server application would access (again, read/write) the backup
> (replica/consumer) DS 5.2 instance?

> Thanks in advance,
> Jim

> P.S.  My understanding is that, assuming that we configured things
> correctly on the DS 5.2 end, that when the master/supplier DS 5.2 comes
> back up, that any changes made to the replica/consumer would be
> replicated back (synchronized) to the master/supplier DS 5.2.

> > Hi,

> > I am working on a system where we have a server-type application that
> > uses Sun Directory Server 5.2 as a data store (for user information,
> > etc.), and we have two instances of DS 5.2 configured with replication
> > between them.

> > The  application does both reads and writes to DS 5.2, but it itself
> > doesn't have any failover capabilities built-in (e.g., where it would
> > detect if one instance of DS is down and switch to the other instance).
> > The server application is a COTS product, so we don't have any way to
> > get into the source code.

> > So, I was wondering if there is any capability in Solaris 9 that would
> > allow us to configure things so that when the primary (master/supplier)
> > DS 5.2 instance is down, Solaris itself would somehow automatically
> > switch things around (sorry for the non-technical terminology) so that
> > the server application would access (again, read/write) the backup
> > (replica/consumer) DS 5.2 instance?

> > Thanks in advance,
> > Jim

> > P.S.  My understanding is that, assuming that we configured things
> > correctly on the DS 5.2 end, that when the master/supplier DS 5.2 comes
> > back up, that any changes made to the replica/consumer would be
> > replicated back (synchronized) to the master/supplier DS 5.2.

> You could setup a hardware virtual IP solution but the easiest and
> cheapest is to use the SUN Directory Proxy. It needs to be installed on
> a seperate machine to the directories to give it the indepence you want
> but it has to install into a directory for its configuration store. One
> option is to install a stand-alone directory on the machine with the
> application but use a non standard ldap port. Install the directory
> proxy on this machine too into this directory so that it listens on the
> ldap port. Configure the directory proxy with the other directories and
> point the application to the directory proxy. The documentation is
> available from docs.sun.com

> I am working on a system where we have a server-type application that
> uses Sun Directory Server 5.2 as a data store (for user information,
> etc.), and we have two instances of DS 5.2 configured with replication
> between them.  

> The  application does both reads and writes to DS 5.2, but it itself
> doesn't have any failover capabilities built-in (e.g., where it would
> detect if one instance of DS is down and switch to the other instance).
> The server application is a COTS product, so we don't have any way to
> get into the source code.

> So, I was wondering if there is any capability in Solaris 9 that would
> allow us to configure things so that when the primary (master/supplier)
> DS 5.2 instance is down, Solaris itself would somehow automatically
> switch things around (sorry for the non-technical terminology) so that
> the server application would access (again, read/write) the backup
> (replica/consumer) DS 5.2 instance?