Connection Manager and I4GL
All Following 'recent' issues (this week and 15 months ago !!) management have decided we need some fail-over mechanism in place for when the database 'locks up'. IDS HDR is the obvious candidate but I need to get my head around how an application can seamlessly fail-over from primary to secondary. I'm investigating Connection Manager for our ancillary applications that use ODBC/JDBC/PHP etc., but the application that runs our busines is written in I4GL running on 'green screens'. My understanding is that Connection Manager cannot be used with I4GL, is this correct? If so does any one know of an application that provides similar functionality to enable auto-switching between databases, how do other people get around this issue? Thanks. Keith
Keith Simmons wrote: > All > > Following 'recent' issues (this week and 15 months ago !!) management > have decided we need some fail-over mechanism in place for when the > database 'locks up'. > IDS HDR is the obvious candidate but I need to get my head around how > an application can seamlessly fail-over from primary to secondary. I'm > investigating Connection Manager for our ancillary applications that > use ODBC/JDBC/PHP etc., but the application that runs our busines is > written in I4GL running on 'green screens'. My understanding is that > Connection Manager cannot be used with I4GL, is this correct? If so > does any one know of an application that provides similar > functionality to enable auto-switching between databases, how do other > people get around this issue? > Thanks. > > Keith Connection Manager does not require the concept of the 'group' connectivity as in older version of IDS. What you will do: 1. Install the Connection Manager component and CSDK 3.50 2. Configure sqlhost file (on your client side) so that your client connects to the CM instead of the IDS server (i.e. redirect your client to connect to CM as if CM is your ultimate IDS server). 3. Configure the sqlhost file on the machine where CM is installed to add in an entry (or entries) for the CM (as if CM is another IDS server). 4. Configure the CM configuration file (yes, another config file to fiddle with, unfortunately) to define one or two things: - how you want CM to manage the failover (e.g. Pri to HDR, to SDS, to RSS...) - how you want CM to manage the client redirection (and possibly load balancing even when there is no failover). 5. Start CM (oncmsm) as you would start IDS. Please consult the IDS Admin manual for detailed commands. Infocenter:http://publib.boulder.ibm.com/infocenter/idshelp/v115/index.jsp Note: It is not necessary to define 'group' entries in sqlhost. Note: Once your client is redirected by CM, your client will be connecting to the IDS server directly from then on - so there is no constant 'pipelining' overhead. CM does not 'bridge' the connection for you - it just handover the connection handle to you once and for all. This is a big improvement of IDS handling client redirection as compared with 'old technology', where a client has to connect to the failed server, wait for a time-out/retry, EVERY time a connection is attempted. Hope this helps. Ray.
On Aug 13, 6:16 am, Keith Simmons <smile...@googlemail.com> wrote: > All > > Following 'recent' issues (this week and 15 months ago !!) management > have decided we need some fail-over mechanism in place for when the > database 'locks up'. > IDS HDR is the obvious candidate but I need to get my head around how > an application can seamlessly fail-over from primary to secondary. I'm > investigating Connection Manager for our ancillary applications that > use ODBC/JDBC/PHP etc., but the application that runs our busines is > written in I4GL running on 'green screens'. My understanding is that > Connection Manager cannot be used with I4GL, is this correct? If so > does any one know of an application that provides similar > functionality to enable auto-switching between databases, how do other > people get around this issue? I4GL 7.50 is built using CSDK 3.50 and should be able to use Connection Manager without problem. Older versions of I4GL use older versions of ESQL/C (or CSDK) and will not work with Connection Manager. -=JL=-
2009/8/14 Jonathan Leffler <jonathan.leffler@gmail.com>: > On Aug 13, 6:16 am, Keith Simmons <smile...@googlemail.com> wrote: >> All >> >> Following 'recent' issues (this week and 15 months ago !!) management >> have decided we need some fail-over mechanism in place for when the >> database 'locks up'. >> IDS HDR is the obvious candidate but I need to get my head around how >> an application can seamlessly fail-over from primary to secondary. I'm >> investigating Connection Manager for our ancillary applications that >> use ODBC/JDBC/PHP etc., but the application that runs our busines is >> written in I4GL running on 'green screens'. My understanding is that >> Connection Manager cannot be used with I4GL, is this correct? If so >> does any one know of an application that provides similar >> functionality to enable auto-switching between databases, how do other >> people get around this issue? > > > I4GL 7.50 is built using CSDK 3.50 and should be able to use > Connection Manager without problem. > > Older versions of I4GL use older versions of ESQL/C (or CSDK) and will > not work with Connection Manager. > > -=JL=- > > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list > Many thanks to all my correspondants. I feel a test setup of two or three (virtual) servers coming up to investigate all this before risking my live environment. A couple of flies in the ointment is that the application is a third party supplied package and that all the GL is currently run as interpreted rather than compiled. We may need to change this !! Thanks once again. Keith