= Making Connections to Informix on Avaya CMS Servers = %TOC% == Our General Recommendation == Options have changed over time. The version (R#.#) of your CMS is key to everything else. * **For CMS R16.2 or later** -- The optimal solution will be specific to your environment and deployment. We can [[http://support.openlinksw.com/support/online-support.vsp| assist in narrowing the field of options, and recommend the optimal solution]]. * **For CMS R16.1 or earlier** -- As discussed in some detail below, the optimal and recommended solution is to install the currently shipping Multi-Tier server components on the CMS host, and the version-matched Multi-Tier client components on ALL client hosts. We can assist with installation and/or upgrade, either as [[http://ps.openlinksw.com/consultancy/|Professional Services]] or through a [[http://support.openlinksw.com/support/online-support.vsp| Support Case]]. == The Details == Options have changed over time. The version (R#.#) of your CMS is key to everything else. * **For CMS R16.2 or later** -- Any of our Single-Tier drivers may be used in the usual way, and our Multi-Tier solutions may be deployed in "three-tier" style. None of our components may be installed on the CMS R16.2 host itself, but such installation is not required for successful connections. * **For CMS R16.1, R16.0, and R15.x** -- Any of our Single-Tier drivers may be used (subject to limitations described below), and the server-side components of our Multi-Tier solutions may be upgraded (or installed) on the CMS host itself. This is fully permitted by all Avaya maintenance agreements. * **For CMS R14.x, and all previous** -- The server-side components of our Multi-Tier solutions may be upgraded (or installed) on the CMS host itself, permitting access from any Multi-Tier-supported client environment. This is fully permitted by all Avaya maintenance agreements. === Some Explanation === Through CMS R14, the Informix configuration shipped by Avaya was set to accept client connections //**only**// from processes running on the same physical host -- so no network client connections were possible except through our Multi-Tier Universal Data Access components, the server-side components of which Avaya OEM licensed and shipped pre-installed on the CMS server host. This additional level of database security was part of the original reason that Avaya chose our solution. This configuration prevents use of any "Wire Protocol" driver, any of our Single-Tier ("Lite" or "Express") solutions, and indeed, any solution from any vendor which does not include either (a) installing some components on the CMS host, or (b) reconfiguring the Informix instance to accept such remote client connections.
//**VERY IMPORTANT** %BR%%BR% The pre-installedYou may continue to use any existing server-side components under the existing license, if your client-side requirements permit (most significantly, if you do not require 64-bit Windows client support, for which Multi-Tier Release 6.x is required). If you do not have the appropriate version-matched client-side installers, you may need to enroll in a Maintenance & Support Agreement to gain access to such deprecated installers. Our currently shipping Release 6.x ODBC Generic Clients are available in both 32-bit and 64-bit form, for all current versions of AIX, Linux, Windows, Mac OS X, Solaris, HP-UX, and others. 32-bit and 64-bit Generic Clients are also available for use with JDBC or ADO.NET client applications, running on most versions (old and new) of AIX, Linux, Windows, Mac OS X, Solaris, HP-UX, and others. Most users are best off upgrading any and all existingOpenLink components on the CMS host are typically from our Release 3.x or 4.x, and occasionally from our Release 5.x, all of which have been deprecated for some time. %BR%%BR% The version of the Multi-Tier Generic Client on the data consumer side **must** be matched to the version of the Multi-Tier Request Broker running on the target host(s) (i.e., the CMS appliance). Mixing Multi-Tier Client components from one Release with Multi-Tier Server components from another Release is untested and unsupported, and is not recommended.//