Greetings!

Seems like I saw somewhere, a way for OengineServer to redirect a request in the event Oengine(s) is not available. IF so, I am hoping that a redirect could occure if the queue of requests grows.

Any help on this?

Have fun!

Paxton

G'day Scott,

Both failover and round robin support has been built into OI V9.1 oecgi2.exe, not the oengineserver service.

You control this by setting the following OECGI2 registry values:-

*Failover mode*

Given the registry entries:

ServerURL: 192.168.100.101,192.168.100.101,192.168.100.102

ServerPort:8088,8089,8088

MultipleServers:0

Any request to the OECGI2.EXE in that directory, reading this registry, will attempt to connect to 192.168.100.101/8088. If for some reason it can't open that port, it'll attempt to connect to 192.168.100.101/8089; if still no success, then 192.168.100.102/8088 will be tried. If we _still_ fail, we return an error (or the SysDownPage). On the next request, we start again at 192.168.100.101/8088, ad infinitum.

* Round Robin Mode *

With the same values for ServerURL and ServerPort, but MultipleServers changed:

MultipleServers:1

Requests to OECGI2.EXE in that directory, reading this registry, will attempt to connect to either 192.168.100.101/8088, 192.168.100.101/8089, or 192.168.100.102/8088 with (roughly) equally chance. And if, for example, OECGI2.EXE decides to try to connect to 192.168.100.101/8089, and it fails, it will then try 192.168.100.102/8088, and then 192.168.100.101/8088, before giving up (notice how it looped back around to the beginning of the list…)

A HUGE thanks to Bryan for making this magic happen!

Dave G

What Dave [i]meant to say is OECGI2 for OI version 9.2 will have these features, which are currently being tested by a few clients.

What Bob meant to say is iOECGI3/i for OI version 9.2 will have these features, which are currently being tested by a few clients.

Guys - this is all nice, neat, swell etc.

Dave makes the comment that OECGI2 is the wonder which manages the startup / shutdown of the oengine farm.

What if I don't want to use OECGI (ala using RoR) and want to use socket server - how can I manage the same outcomes?

Cheers

Hi Martin,

OECGI is client program which makes socket calls to the oengine server. The calls to the socket server are modeled after the JD3 protocol, described at http://sourceforge.net/projects/jd3/ Anyone can write a socket server client in their language of choice. Round robin and failover occur in that client, so implementing failover and round robin would using tool and techniques appropriate for the client language. Some unsupported examples of logging in to the socketserver and running a request can be found at the links below.

Ruby OECGI example

PHP OECGI example

C# OeSocket server example is not OECGI equivalent, but you get the idea.

Basic+ Socket server example

Bob,

Thanks for the code examples.

So I can do some registry settings in 9.2 and point my failures somewhere OR, I can 'roll my own' now in my choice of languages..

sounds good to me.

Have fun,

Paxton

View this thread on the Works forum...