[omniORB] switching from production to backup

[Milet, Eric]

Hi,

How does a client application achieve switching from using a remote
object on a production server to a remote backup server? Is it done via
the 'clientTransportRule' parameter in the omni.cfg file, or using the
naming service and register 2 objects (1 for production and 1 for
backup). Or perhaps there is an easy way to do it.

Any help and comments would really be appreciated.

Eric Milet



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20080227/c524e327/attachment.htm

[Duncan Grisby]

Post by Milet, Eric
How does a client application achieve switching from using a remote
object on a production server to a remote backup server? Is it done via
the 'clientTransportRule' parameter in the omni.cfg file, or using the
naming service and register 2 objects (1 for production and 1 for
backup). Or perhaps there is an easy way to do it.

It depends entirely on what the requirements of your application are. If
you have a small number of persistent objects where all the state is
visible from the production and backup servers, you could configure
additional endpoints in the object references so clients automatically
fail-over to use the backup if they can't contact the production server.
If your objects are stateful, you have to do whatever is necessary to
continue processing with a different server.

If you post some more details about what your application does, people
might be able to offer some more specific suggestions.

Cheers,

Duncan.