Difference: APPXODBCInstallationInstructions (47 vs. 48)
Revision 482010-07-14 - JoeOrtagus
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
APPX ODBC Installations Instructions | ||||||||
| Line: 11 to 11 | ||||||||
| APPX ODBC 5 is a new product compared to earlier versions of APPX ODBC. There is no upgrade, just uninstall the older version prior to installing the new version. | ||||||||
| Changed: | ||||||||
| < < | AppxODBC requires 3 components to work now. The Appx FMS Server, The Appx ODBC Data Gateway (aka AppxODBC Server), and the Appx ODBC Driver with ASQL tool. The Appx FMS server should already be installed and running. The APPX FMS Server is an APPX server configured to accept APPX client connections via TCP, by default TCP 8060. Step 2 is to install the Appx ODBC Data Gateway, then the Appx ODBC Driver + ASQL. Run ASQL to import Apppx dictionaries. Then on non-admin PCs install the Appx ODBC Driver (minus ASQL). Here's what each installer does do... | |||||||
| > > | AppxODBC requires 3 components to work. The Appx FMS Server (APPX server configured to listen on TCP 8060 by default), The Appx ODBC Data Gateway (aka AppxODBC Server, configured to listen on TCP 1990), and the Appx ODBC Driver with ASQL tool. These components can all be installed on one computer or each component could be installed on separate computers. The Appx FMS server should already be installed and running. The APPX FMS Server is an APPX server configured to accept APPX client connections via TCP, by default TCP 8060. Install the Appx ODBC Data Gateway, then the Appx ODBC Driver + ASQL. Run ASQL to import Apppx dictionaries. On non-admin PCs you could choose to install the Appx ODBC Driver (minus ASQL). Here's what each installer does do... | |||||||
| ||||||||
| Changed: | ||||||||
| < < | This will install the "Appx ODBC Data Gateway Service" and supporting files. This service runs listening on TCP port 1990 for connections from the Appx ODBC Driver installed on someone's desktop. The Data Gateway contains one or more database directories each with it's own schemas imported via ASQL and each having its own appx.env file that tells it the host and port of the Appx FMS Server for that database. By default the installer creates a default database called "appx". This creates a directory tree in the server install directory called "appx.dbs". That directory contains all the schema files for database "appx" as well as its appx.env file. The bin subdirectory of the AppxODBC Server directory contains two important executables the gateway service tool AppxODBC.exe. This is the program that will listen for connection attempts on TCP port 1990 from desktop computers running the Appx ODBC driver. You'll also find in the bin sub directory the mdcreate.exe. I'll explain this in an example further in this documentation, but mdcreate is a command line tool used to optionally create connections to secondary APPX servers. When a connection request is received from a desktop driver it takes the database from the request, "appx" by default, reads the appx.env file, and attempts to start up an FMS connection to that Appx host using the login and password received from the desktop driver. If authentication is successful then it starts brokering SQL requests from the driver to the FMS server. You have a new Data Gateway task for each driver connection. Each Data Gateway task creates its own FMS connection to the Appx server. The installer should create everything needed in the way of the "appx" database, the appx.env file, and configure and start the service task. Upon completion of the installer the Appx ODBC Data Gateway should be ready for connections. This installer does not install an Appx ODBC driver or ASQL application. Nothing on this server is visibly runnable other than you can see that the service is running and you can look at the appx.env file to see that it looks right. | |||||||
| > > | This will install the "Appx ODBC Data Gateway" service and supporting files. This service listens on TCP port 1990 for connections from the Appx ODBC Driver installed on the ODBC client desktops. The Data Gateway contains one or more database directories each with it's own schemas imported via ASQL and each having its own appx.env file that tells it the host and port of the Appx FMS Server for that database. By default the installer creates a default database called "appx". This creates a directory tree in the server install directory called "appx.dbs". That directory contains all the schema files for database "appx" as well as its appx.env file. The bin subdirectory of the AppxODBC Server directory contains two important executables the gateway service tool AppxODBC.exe. This is the program that will listen for connection attempts on TCP port 1990 from desktop computers running the Appx ODBC driver. You'll also find in the bin sub directory the mdcreate.exe. I'll explain mdcreate in an example further in this documentation, mdcreate is a command line tool optionally used to create connections to secondary APPX servers. When a connection request is received from a desktop driver it takes the database from the request, "appx" by default, reads the appx.env file, and attempts to start up an FMS connection to that Appx host using the login and password received from the desktop driver. If authentication is successful then the APPX ODBC server starts brokering requests from the ODBC client desktop's ODBC driver to the APPX FMS server. Your server's process list on the APPX ODBC server will have a new Data Gateway task for each ODBC client driver connection. Each Data Gateway task creates its own APPX FMS connection to the Appx server. The installer should create everything needed in the way of the "appx" database, the appx.env file, and configure and start the service task. Upon completion of the installer the Appx ODBC Data Gateway should be ready for connections. This installer does not install an Appx ODBC driver or ASQL application. Nothing on this server is visibly runnable other than you can see that the service is running using Microsoft Windows Services applet. You might look at the appx.env file to see that it looks right. | |||||||
This will install the desktop Appx ODBC Driver. This is what WinSQL and other desktop application will use to connect to the Appx ODBC Data Gateway, which in turn connect to APPX. During the install it will create a default System DSN using the driver and setting up the DSN to properly connect to the Appx ODBC Data Gateway. Once this installer is done the driver should be installed and there should be a functioning System DSN you can use to request data. That can't happen until ASQL has been run to import Appx data dictionaries into the Data Gateway database schemas. ASQL is not included in this installer for security reasons. When you use the driver to get data the user and password you use is your Appx user and password for the Appx server on the back end of the FMS connection between the Appx ODBC Data Gateway and the Appx FMS server. | ||||||||
View topic | History: r53 < r52 < r51 < r50 | More topic actions...
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback