Login Register Actian.com  

Actian Community Blogs

Rate this Entry

Introducing the Actian Client Runtime for Windows

Submit "Introducing the Actian Client Runtime for Windows" to Digg Submit "Introducing the Actian Client Runtime for Windows" to del.icio.us Submit "Introducing the Actian Client Runtime for Windows" to StumbleUpon Submit "Introducing the Actian Client Runtime for Windows" to Google
Posted 2012-09-20 at 01:25 PM by teresa
Updated 2012-09-26 at 02:04 PM by teresa

The Client Runtime provides a means for 32-bit applications to connect to remote Ingres, Vectorwise, Enterprise Access, or EDBC databases, simplifying deployment of client-only installations. This is especially beneficial for running ODBC and JDBC applications across an enterprise where there are typically a large number of clients and few DBMS servers.

Features and capabilities include:
  • Support for common database access interfaces: ODBC and JDBC
  • Base client terminal monitor support to handle ad-hoc queries
  • Support for common network communication protocols: TCP/IP, Named Pipe
  • Remote connections configurable during the installation process
  • Support for installing multiple copies of a client on the same computer. These copies can be the same or different versions.
    • The default instance ID is VT and is not configurable.
    • If additional copies of the client runtime are installed, the instance ID is automatically incremented, for example: VT, VU, VV, etc.
  • Smaller deployment footprint compared to the full Client Runtime in terms of installation image size and disk space required
  • Simpler to install, as only relevant client-side configuration options are exposed

The Data Access Server (GCD) is also provided as a configurable option, although it is not started by default. Typically the Data Access Server runs on the same machine as the DBMS Server (Ingres, Vectorwise, or Enterprise Access), but in some situations the Data Access Server needs to run on the Client machine, for example, when accessing EDBC Servers or older Ingres Servers where the Data Access Server does not exist.

Other utilities provided:
  • Ingres Network Utility (ingnet) and Network Management Utility (netutil) to manage remote connections
  • Ingres Service Manager (winstart) to start or stop Client Runtime services

Two separate downloads are provided at ESD - Electronic Software Distribution that simplify the configuration even further. Each is defaulted for a particular server type, although a single installation is sufficient to access all the server types: Ingres, Vectorwise, Enterprise Access, and EDBC Servers.
  • Vectorwise Servers - defaults to ANSI Dates and UTF8 character set
  • Ingres, Enterprise Access, and EDBC Servers - defaults to Ingres dates and WIN1252 character set, but both can be overridden during the installation process

Because we have traditionally had a separate simple installer for the .NET Data Provider, we decided to not include it in the Client Runtime package. The .NET Data Provider requires no components of the Client Runtime package unless accessing an installation that does not contain a Data Access Server.

Futures
  • The initial version of the Client Runtime does not provide a silent installation option, but this will be provided in a future iteration.
  • A new and improved configuration wizard for defining ODBC DSN and Remote Connections will be included to improve the overall user experience.
Views 1872 Comments 0 Edit Tags

« Prev     Main     Next »

Total Comments 0

Comments

 
© 2011 Actian Corporation. All Rights Reserved