Difference: APPXODBCInstallationInstructions (1 vs. 53)

Revision 532016-01-20 - JeanNeron

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="APPX500"
>
>
META TOPICPARENT name="APPX500InstallationInstructions"
 

APPX ODBC Installations Instructions

This page provides instructions for installing APPX ODBC 5.

Revision 522012-06-21 - GaryRogers

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 15 to 15
 
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 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 "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.
 
Changed:
<
<

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.
>
>
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.
 
Changed:
<
<

This is the same as the other driver installer except that it does include ASQL. This must be installed on at least one desktop so that ASQL.exe can be used to import the APPX data dictionary of the desired APPX files.
>
>
This is the same as the other driver installer except that it does include ASQL. This must be installed on at least one desktop so that ASQL.exe can be used to import the APPX data dictionary of the desired APPX files.
 

Disclaimer

Line: 223 to 220
 AppxODBC is a 32 bit product. The Windows ODBC System DSN it creates is 32 bit not 64 bit. To view and manage 32 bit DSNs on a 64 bit version of Windows, you must specify the 32 bit version of odbcad32.exe. For 64 bit Windows, to manage 32 bit DSNs like AppxODBC, use \Windows\SysWOW64\odbcad32.exe and not the 64 bit version with the same name found at \Windows\system32\odbcad32.exe.

If you are working on a 32 bit version, this does not apply to you, just run the odbcad32.exe found in your Administrative tools (which is mapped to \Windows\system32\odbcad32.exe.)

Added:
>
>

Manuals

The Dharma Interface Manual explains how our ODBC interface works and details supported SQL statements and syntax.

 

Linux and Unix

Known Issues

  • APPX Server version and AppxODBC version should match. Mismatched version can cause failure to connect, or extreme loss of performance in AppxODBC data connection.

Revision 512011-06-14 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 132 to 132
  020.jpg
Changed:
<
<
Running ASQL, you are first prompted for a Data Source Name (aka DSN), and a user name and password to log into APPX with. Optionally you can enter a Database ID and Applicaiton ID.
>
>
Running ASQL, you are first prompted for a Data Source Name (aka DSN), and a user name and password to log into APPX with. Optionally you can enter a Database ID and Application ID. Bug: Entering a database may cause connection errors. If this happens, leave the database blank.
  021.jpg
Line: 205 to 205
 037.jpg038.jpg

The images above can occur when 0SA\Struct\SYSDIR.dat file is missing. This error will occur at the beginning of the connection attempt from ASQL to APPX.

Added:
>
>
This error can also occur if you specify a Database on the ASQL login screen. This is a bug, until it is fixed, just leave the database blank. You can specify an Application.
 
Appx ODBC Gateway Service stopped or blocked by firewall.

039.jpg

Line: 224 to 226
 

Linux and Unix

Known Issues

  • APPX Server version and AppxODBC version should match. Mismatched version can cause failure to connect, or extreme loss of performance in AppxODBC data connection.
Added:
>
>
  • Entering a Database on the connection screen will cause connection problems. Leave the database blank.
 

Revision 502010-07-14 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

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.
Added:
>
>
AppxODBC_5.0_chart_-_color.jpg
 
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...

Revision 492010-07-14 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 274 to 274
 
META FILEATTACHMENT attachment="038.jpg" attr="h" comment="" date="1277836691" name="038.jpg" path="038.jpg" size="6898" stream="038.jpg" tmpFilename="/tmp/Nwzy5riBLc" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="039.jpg" attr="h" comment="" date="1278529255" name="039.jpg" path="039.jpg" size="13655" stream="039.jpg" tmpFilename="/tmp/e65p4MAfiV" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="040.jpg" attr="h" comment="" date="1278529755" name="040.jpg" path="040.jpg" size="17973" stream="040.jpg" tmpFilename="/tmp/br9w2PBu92" user="JoeOrtagus" version="1"
Added:
>
>
META FILEATTACHMENT attachment="AppxODBC_5.0_chart_-_color.jpg" attr="h" comment="" date="1279125412" name="AppxODBC_5.0_chart_-_color.jpg" path="AppxODBC 5.0 chart - color.jpg" size="48255" stream="AppxODBC 5.0 chart - color.jpg" tmpFilename="/tmp/QZN3RyY1ay" user="JoeOrtagus" version="1"

Revision 482010-07-14 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

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.

Revision 472010-07-14 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

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. 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 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...
 


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.

Revision 462010-07-14 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

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. 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...

AppxODBCserver_5_0_2_windows.exe

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This must be installed on at least one desktop so that ASQL.exe can be used to import the APPX data dictionary of the desired APPX files.
>
>

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. 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...


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 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.


This is the same as the other driver installer except that it does include ASQL. This must be installed on at least one desktop so that ASQL.exe can be used to import the APPX data dictionary of the desired APPX files.

 

Disclaimer

Revision 452010-07-14 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 9 to 9
  APPX ODBC is used by APPX customers to gain access to APPX data from external products, such as Crystal Reports or Excel. Installation of APPX ODBC 5 is accomplished by simply following the steps outlined below. APPX ODBC 5 is a Windows only product for now.
Changed:
<
<
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.
>
>
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.
 
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. 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...

AppxODBCserver_5_0_2_windows.exe

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This must be installed on at least one desktop so that ASQL.exe can be used to import the APPX data dictionary of the desired APPX files.

Revision 442010-07-07 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 200 to 200
  ASQL.exe failure to connect to the APPX ODBC gateway server (aka appxODBC Server) on TCP port 1990.
Added:
>
>
040.jpg

WinSQL failure to connect to the APPX ODBC gateway server (aka appxODBC Server) on TCP port 1990.

 If you receive the either of the two above errors, verify that the appxODBC Server's service named "Appx ODBC Data Gateway Service 05.02.0000" is started. Also make sure the TCP port 1990 is not blocked between the Appx ODBC client and Appx ODBC server.
Installing on Windows 64 bit

Revision 432010-07-07 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 194 to 194
 037.jpg038.jpg

The images above can occur when 0SA\Struct\SYSDIR.dat file is missing. This error will occur at the beginning of the connection attempt from ASQL to APPX.

Added:
>
>
Appx ODBC Gateway Service stopped or blocked by firewall.

039.jpg

ASQL.exe failure to connect to the APPX ODBC gateway server (aka appxODBC Server) on TCP port 1990.

If you receive the either of the two above errors, verify that the appxODBC Server's service named "Appx ODBC Data Gateway Service 05.02.0000" is started. Also make sure the TCP port 1990 is not blocked between the Appx ODBC client and Appx ODBC server.

 
Installing on Windows 64 bit

AppxODBC is a 32 bit product. The Windows ODBC System DSN it creates is 32 bit not 64 bit. To view and manage 32 bit DSNs on a 64 bit version of Windows, you must specify the 32 bit version of odbcad32.exe. For 64 bit Windows, to manage 32 bit DSNs like AppxODBC, use \Windows\SysWOW64\odbcad32.exe and not the 64 bit version with the same name found at \Windows\system32\odbcad32.exe.

Line: 253 to 260
 
META FILEATTACHMENT attachment="037.jpg" attr="h" comment="" date="1277836680" name="037.jpg" path="037.jpg" size="6706" stream="037.jpg" tmpFilename="/tmp/NNk3vFKQpH" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="038.jpg" attr="h" comment="" date="1277836691" name="038.jpg" path="038.jpg" size="6898" stream="038.jpg" tmpFilename="/tmp/Nwzy5riBLc" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="039.jpg" attr="h" comment="" date="1278529255" name="039.jpg" path="039.jpg" size="13655" stream="039.jpg" tmpFilename="/tmp/e65p4MAfiV" user="JoeOrtagus" version="1"
Added:
>
>
META FILEATTACHMENT attachment="040.jpg" attr="h" comment="" date="1278529755" name="040.jpg" path="040.jpg" size="17973" stream="040.jpg" tmpFilename="/tmp/br9w2PBu92" user="JoeOrtagus" version="1"

Revision 422010-07-07 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 252 to 252
 
META FILEATTACHMENT attachment="036.jpg" attr="h" comment="" date="1277304455" name="036.jpg" path="036.jpg" size="32571" stream="036.jpg" tmpFilename="/tmp/pPa12K2ehd" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="037.jpg" attr="h" comment="" date="1277836680" name="037.jpg" path="037.jpg" size="6706" stream="037.jpg" tmpFilename="/tmp/NNk3vFKQpH" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="038.jpg" attr="h" comment="" date="1277836691" name="038.jpg" path="038.jpg" size="6898" stream="038.jpg" tmpFilename="/tmp/Nwzy5riBLc" user="JoeOrtagus" version="1"
Added:
>
>
META FILEATTACHMENT attachment="039.jpg" attr="h" comment="" date="1278529255" name="039.jpg" path="039.jpg" size="13655" stream="039.jpg" tmpFilename="/tmp/e65p4MAfiV" user="JoeOrtagus" version="1"

Revision 412010-07-07 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

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. 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...

AppxODBCserver_5_0_2_windows.exe

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This is what administrators will install when they will be manipulating the Data Gateway schemas and importing Appx dictionaries.
>
>

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. 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...

AppxODBCserver_5_0_2_windows.exe

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This must be installed on at least one desktop so that ASQL.exe can be used to import the APPX data dictionary of the desired APPX files.
 

Disclaimer

Revision 402010-07-07 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

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. 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...

AppxODBCserver_5_0_2_windows.exe

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.

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This is what administrators will install when they will be manipulating the Data Gateway schemas and importing Appx dictionaries.
>
>

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. 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...

AppxODBCserver_5_0_2_windows.exe

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This is what administrators will install when they will be manipulating the Data Gateway schemas and importing Appx dictionaries.
 

Disclaimer

Revision 392010-07-07 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 179 to 179
  035.jpg
Changed:
<
<
The value you use in the first field in the image above, Data Source Name, will be referenced by the ASQL data importer when you are prompted for the Data Source Name. The second field, Description, is just for reference. The third field, Host, should be a DNS name that is resolvable, or an IP address to the appxODBC Server. The last field we will fill in is the Database field. This field is the name of the database on the appxODBC server that we wish to connect to. Each database will have a databasename.dbs directory in the C:\Program Files\AppxODBC Server\ directory.
>
>
The value you use in the first field in the image above, Data Source Name, will be referenced by the ASQL data importer when you are prompted for the Data Source Name. The second field, Description, is just for reference. The third field, Host, should be a DNS name that is resolvable, or an IP address to the appxODBC server, that may or may not be the same as the Appx server.. The last field we will fill in is the Database field. This field is the name of the database on the appxODBC server that we wish to connect to. Each database will have a databasename.dbs directory in the C:\Program Files\AppxODBC Server\ directory.
  036.jpg

Revision 382010-07-07 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 107 to 107
  017.jpg
Changed:
<
<
In the image above, I'm specifying localhost because my AppxODBC server is the same machine as the AppxODBC driver/ASQL machine. Click Next.
>
>
In the image above, I'm specifying localhost because my AppxODBC server is the same machine as the AppxODBC driver/ASQL machine. You should enter the DNS resolvable name or IP address of the server you install appxODBC server and then click Next.
  018.jpg

Revision 372010-07-06 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 182 to 182
 The value you use in the first field in the image above, Data Source Name, will be referenced by the ASQL data importer when you are prompted for the Data Source Name. The second field, Description, is just for reference. The third field, Host, should be a DNS name that is resolvable, or an IP address to the appxODBC Server. The last field we will fill in is the Database field. This field is the name of the database on the appxODBC server that we wish to connect to. Each database will have a databasename.dbs directory in the C:\Program Files\AppxODBC Server\ directory.

036.jpg

Added:
>
>
Your newly created appxODBC System DSN is now ready for the schema importer ASQL.exe.
 

Troubleshooting

Troubleshooting AppxODBC Server
Troubleshooting AppxODBC Driver/ASQL

Revision 362010-07-06 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 179 to 179
  035.jpg
Added:
>
>
The value you use in the first field in the image above, Data Source Name, will be referenced by the ASQL data importer when you are prompted for the Data Source Name. The second field, Description, is just for reference. The third field, Host, should be a DNS name that is resolvable, or an IP address to the appxODBC Server. The last field we will fill in is the Database field. This field is the name of the database on the appxODBC server that we wish to connect to. Each database will have a databasename.dbs directory in the C:\Program Files\AppxODBC Server\ directory.
 036.jpg

Troubleshooting

Troubleshooting AppxODBC Server

Revision 352010-07-06 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 175 to 175
  034.jpg
Added:
>
>
The blank fields above are presented after you select the driver. You'll want to fill in the first four fields: Data Source Name, Description, Host and Database.
 035.jpg

036.jpg

Revision 342010-07-06 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 171 to 171
  033.jpg
Added:
>
>
In the image above, after clicking the Add button on the System DSN tab, we are presented with the choice of data source driver. Choose AppxODBC Driver.
 034.jpg

035.jpg

Revision 332010-07-06 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 167 to 167
  032.jpg
Added:
>
>
In the photo above as a point of reference, you can see the values that are assigned to the default created AppxODBC System DSN. Notice the database is named appx. This corresponds to the appx.dbs directory on the appxODBC server in the \Program Files (x86)\AppxODBC Server\ directory. In the next steps below we will create a System DSN using a database named localhost to match what we created on the appxODBC server.
 033.jpg

034.jpg

Revision 322010-07-06 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 159 to 159
  030.jpg
Added:
>
>
As you can see above, there are actually two odbcad32.exe files on my APPX ODBC client (the desktop that I install ASQL.exe). My 64 bit OS places the 32 bit odbcad32.exe inside \Windows\SysWOW64\odbcad32.exe. Use the 32bit version to create the new DSN for the newly created ODBC datasource on the appxODBC server.
 031.jpg
Added:
>
>
\Windows\SysWOW64\odbcad32.exe (for 64 bit windows) or \Windows\System32\odbcad32.exe (for 32 bit Windows), System DSN tab shows the default created AppxODBC System DSN. We want to create a new DSN to match the manually created data source that we created on the appxODBC server.
 032.jpg

033.jpg

Revision 312010-07-06 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 155 to 155
  029.jpg
Added:
>
>
In the screen shot above, you can see the newly created directory on the appxODBC server. I named my new appxODBC gateway localhost, and the mdcreate tool created a directory on the appxODBC server named localhost.dbs. Inside the directory localhost.dbs you can see a configuration file named appx.env. This appx.env file contains a string "APPX_DATA_SERVER=localhost:8060". This string tells the appxODBC server that listens on TCP port 1990 to connect to the APPX Server on localhost at TCP port 8060.
 030.jpg

031.jpg

Revision 302010-07-06 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 151 to 151
  028.jpg
Added:
>
>
On the appxODBC server, open a command window in the appxODBC\bin\ directory, and execute "mdcreate development" where development is the name of the name you wish to give the odbc gateway. It doesn't have to match anything on the APPX server side, but it would be a good idea to name it meaningfully.
 029.jpg

030.jpg

Revision 292010-06-29 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 169 to 169
 

Troubleshooting

Troubleshooting AppxODBC Server
Troubleshooting AppxODBC Driver/ASQL
Added:
>
>
Missing $APPXPATH\0SA\Struct\SYSDIR.dat

If you receive an error like below when you connect to a local instance of APPX via ASQL, you may be missing the 0SA\Struct\SYSDIR.dat file. You can create this file by selecting System Administration > System Setup > System Administration File Management > Create Files. Then restart ASQL and attempt to connect to APPX again.

037.jpg038.jpg

The images above can occur when 0SA\Struct\SYSDIR.dat file is missing. This error will occur at the beginning of the connection attempt from ASQL to APPX.

 
Installing on Windows 64 bit

AppxODBC is a 32 bit product. The Windows ODBC System DSN it creates is 32 bit not 64 bit. To view and manage 32 bit DSNs on a 64 bit version of Windows, you must specify the 32 bit version of odbcad32.exe. For 64 bit Windows, to manage 32 bit DSNs like AppxODBC, use \Windows\SysWOW64\odbcad32.exe and not the 64 bit version with the same name found at \Windows\system32\odbcad32.exe.

Revision 282010-06-29 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 169 to 169
 

Troubleshooting

Troubleshooting AppxODBC Server
Troubleshooting AppxODBC Driver/ASQL
Added:
>
>
Installing on Windows 64 bit

AppxODBC is a 32 bit product. The Windows ODBC System DSN it creates is 32 bit not 64 bit. To view and manage 32 bit DSNs on a 64 bit version of Windows, you must specify the 32 bit version of odbcad32.exe. For 64 bit Windows, to manage 32 bit DSNs like AppxODBC, use \Windows\SysWOW64\odbcad32.exe and not the 64 bit version with the same name found at \Windows\system32\odbcad32.exe.

If you are working on a 32 bit version, this does not apply to you, just run the odbcad32.exe found in your Administrative tools (which is mapped to \Windows\system32\odbcad32.exe.)

 

Linux and Unix

Known Issues

  • APPX Server version and AppxODBC version should match. Mismatched version can cause failure to connect, or extreme loss of performance in AppxODBC data connection.
Line: 220 to 225
 
META FILEATTACHMENT attachment="034.jpg" attr="h" comment="" date="1277304439" name="034.jpg" path="034.jpg" size="19771" stream="034.jpg" tmpFilename="/tmp/VRliPdcrqm" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="035.jpg" attr="h" comment="" date="1277304447" name="035.jpg" path="035.jpg" size="22592" stream="035.jpg" tmpFilename="/tmp/OBpEaJB6MU" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="036.jpg" attr="h" comment="" date="1277304455" name="036.jpg" path="036.jpg" size="32571" stream="036.jpg" tmpFilename="/tmp/pPa12K2ehd" user="JoeOrtagus" version="1"
Added:
>
>
META FILEATTACHMENT attachment="037.jpg" attr="h" comment="" date="1277836680" name="037.jpg" path="037.jpg" size="6706" stream="037.jpg" tmpFilename="/tmp/NNk3vFKQpH" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="038.jpg" attr="h" comment="" date="1277836691" name="038.jpg" path="038.jpg" size="6898" stream="038.jpg" tmpFilename="/tmp/Nwzy5riBLc" user="JoeOrtagus" version="1"

Revision 272010-06-29 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

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, and the Appx ODBC Driver. The Appx FMS server should already be installed and running. 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...

AppxODBCserver_5_0_2_windows.exe

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.

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This is what administrators will install when they will be manipulating the Data Gateway schemas and importing Appx dictionaries.
>
>

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. 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...

AppxODBCserver_5_0_2_windows.exe

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.

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This is what administrators will install when they will be manipulating the Data Gateway schemas and importing Appx dictionaries.
 

Disclaimer

Revision 262010-06-29 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 170 to 170
 
Troubleshooting AppxODBC Server
Troubleshooting AppxODBC Driver/ASQL

Linux and Unix

Added:
>
>

Known Issues

  • APPX Server version and AppxODBC version should match. Mismatched version can cause failure to connect, or extreme loss of performance in AppxODBC data connection.
 

Revision 252010-06-29 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 169 to 169
 

Troubleshooting

Troubleshooting AppxODBC Server
Troubleshooting AppxODBC Driver/ASQL
Added:
>
>

Linux and Unix

 

Revision 242010-06-29 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 167 to 167
  036.jpg

Troubleshooting

Added:
>
>
Troubleshooting AppxODBC Server
Troubleshooting AppxODBC Driver/ASQL
 

Revision 232010-06-29 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 166 to 166
 035.jpg

036.jpg

Added:
>
>

Troubleshooting

 

Revision 222010-06-28 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 147 to 147
  Prospect in the DMO database is selected, and IMPORT is run. The APPX DMO PROSPECT data is then made available to external sources such as WinSQL or Excel using thier ODBC connection / data import and referencing the AppxODBC System DSN.
Added:
>
>

Manually creating a new AppxODBC data source on the AppxODBC Server

 028.jpg

029.jpg

Revision 212010-06-28 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 145 to 145
  027.jpg
Added:
>
>
Prospect in the DMO database is selected, and IMPORT is run. The APPX DMO PROSPECT data is then made available to external sources such as WinSQL or Excel using thier ODBC connection / data import and referencing the AppxODBC System DSN.
 028.jpg

029.jpg

Revision 202010-06-28 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 137 to 137
  025.jpg
Added:
>
>
The ASQL program is performing some initial setup of the data structure.
 026.jpg
Added:
>
>
At this point, we are presented with the databases available to our appx user that we logged into APPX with since we did not identify the initial database in the ASQL login screen. Out account can see the 1EX and DMO databases.
 027.jpg

028.jpg

Revision 192010-06-28 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 133 to 133
  023.jpg
Added:
>
>
The ASQL program is performing some initial setup of the data structure.
 025.jpg

026.jpg

Revision 182010-06-26 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 129 to 129
  022.jpg
Added:
>
>
The connecton to the Appx server is being made via the AppxODBC server.
 023.jpg

025.jpg

Revision 172010-06-26 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 125 to 125
  021.jpg
Added:
>
>
In the image above, I'm using the default created DSN named AppxODBC, and I've specified an APPX user name and password. I am going to leave Database ID and Application ID empty and will browse via the data selector after I log in.
 022.jpg

023.jpg

Revision 162010-06-26 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 121 to 121
  020.jpg
Changed:
<
<
Running ASQL
>
>
Running ASQL, you are first prompted for a Data Source Name (aka DSN), and a user name and password to log into APPX with. Optionally you can enter a Database ID and Applicaiton ID.
  021.jpg

Revision 152010-06-25 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 117 to 117
  You have completed the installation of AppxODBC driver and ASQL components. You should now run ASQL to begin the data structure import.
Added:
>
>
Importing APPX data structure via the AppxODBC ASQL tool.
 020.jpg
Added:
>
>
Running ASQL
 021.jpg

022.jpg

Revision 142010-06-25 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 95 to 95
  014.jpg
Added:
>
>
ASQL data is created by the user at runtime. You should install AppxODBC in a directory that the user has write access to. A good choice is C:\Appx\AppxODBC Driver\. This will prevent write access problems for OS configurations that prevent users writting to C:\Program Files\ or C:\Program Files (x86)\ directories.
 015.jpg
Added:
>
>
Accept the default name for the Windows Start Menu program group for AppxODBC driver.
 016.jpg
Added:
>
>
AppxODBC driver needs to know the location of the AppxODBC server.
 017.jpg
Added:
>
>
In the image above, I'm specifying localhost because my AppxODBC server is the same machine as the AppxODBC driver/ASQL machine. Click Next.
 018.jpg
Added:
>
>
The installer should report that the AppxODBC data source has been created. Click OK.
 019.jpg
Added:
>
>
You have completed the installation of AppxODBC driver and ASQL components. You should now run ASQL to begin the data structure import.
 020.jpg

021.jpg

Revision 132010-06-25 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 91 to 91
  013.jpg
Added:
>
>
Click Next when the AppxODBC driver/ASQL installation welcome screen is presented to you.
 014.jpg

015.jpg

Revision 122010-06-25 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 115 to 115
  026.jpg
Added:
>
>
027.jpg

028.jpg

029.jpg

030.jpg

031.jpg

032.jpg

033.jpg

034.jpg

035.jpg

036.jpg

 

Comments:

Revision 112010-06-25 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 81 to 81
  C:\Program Files (x86)\AppxODBC Server>more appx.dbs\appx.env

APPX_DATA_SERVER=hankwilliams.internal.appx.com:8060

C:\Program Files (x86)\AppxODBC Server>
Changed:
<
<
See above the contents of the appx.env file.
>
>
The contents of the appx.env file is displayed above.
 
Download and run the AppxODBC driver and ASQL data importer.

Revision 102010-06-25 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 113 to 113
  025.jpg
Added:
>
>
026.jpg
 

Comments:

Revision 92010-06-25 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 107 to 107
  021.jpg
Added:
>
>
022.jpg

023.jpg

025.jpg

 

Comments:

Revision 82010-06-25 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 35 to 35
  Let's download the APPX ODBC Server and start the installation.
Changed:
<
<
001.jpg
>
>
001.jpg
  Execute the AppxODBCserver _5_0_2_windows.exe installation file shown in the image above.
Line: 49 to 49
  004.jpg
Added:
>
>
You can accept the default Start Menu Folder name of AppxODBC Server.
 005.jpg
Added:
>
>
In the image above, you can see the ODBC Server prompting for the TCP port that your APPX Server's appxLoginMgr is configured to listen on. This can be APPX on any platform (Windows, Linux, HPUX, IBM AIX, Sun Sparc based Solaris) with the same version of APPX as the AppxODBC that you are installing now.
 006.jpg
Added:
>
>
The image above shows that I'm instructing AppxODBC to point to the APPX server named hankwilliams.internal.appx.com on TCP port 8060.
 007.jpg
Added:
>
>
AppxODBC server installation is complete.

008.jpg

The image above demonstrates the use of OS commands tasklist, findstr and netstat to verify that the AppxODBC server process is indeed running and listening on TCP port number 1990.

009.jpg

In the image above, you can see the service "Appx ODBC Data Gateway Service" in the OS Services panel. Notice that the Startup Type is set to Automatic, and the Status is Started.

010.jpg

As you can see in the image above, the tool placed an uninstall option in the just created AppxODBC menu group.

011.jpg

The directory listing above shows some of the files that are created in the AppxODBC Server directory structure. Notice the executable in the bin subdirectory, the appx.dbs subdirectory and the appx.env file inside appx.dbs. appx.dbs is the directory created for the default DSN database named appx. The configuration information for TCP port number of APPX and the APPX Server name is contained in the appx.env file.

C:\Program Files (x86)\AppxODBC Server>more appx.dbs\appx.env

APPX_DATA_SERVER=hankwilliams.internal.appx.com:8060

C:\Program Files (x86)\AppxODBC Server>

See above the contents of the appx.env file.

Download and run the AppxODBC driver and ASQL data importer.

012.jpg

With AppxODBC 5.0.2 we've seperated the ODBC driver from the data importer. You may wish to put the APPX Server, AppxODBC server and AppxODBC driver and ASQL all on one machine. Then put just the AppxODBCdriver on each client's desktop that needs to access APPX from an application such as Microsoft Excel. If the AppxODBC user is an APPX developer, it might be desirable to have the AppxODBC driver and ASQL importer on the same desktop as the ODBC client client application (Excel, Crystal Reports, etc...). For this example I am keeping all AppxODBC components on a single machine, with the APPX Server on a separate machine. Your configuration could demand each component be installed on a separate machine.
I'm going to execute the AppxODBCdriver+ASQL_5_0_2_windows.exe to begin the installation of the driver and ASQL importer.

013.jpg

014.jpg

015.jpg

016.jpg

017.jpg

018.jpg

019.jpg

020.jpg

021.jpg

 

Comments:

Revision 72010-06-25 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 30 to 30
  000.jpg
Changed:
<
<
The port is available as you can see in the image above.
>
>
The image above demonstrates using the Windows OS commands netstat and findstr to search for TCP port 1990. As you can see nothing was returned, so we can be sure that the port is available.
 
Download and run the APPX ODBC Server installation file.

Let's download the APPX ODBC Server and start the installation.

001.jpg

Added:
>
>
Execute the AppxODBCserver _5_0_2_windows.exe installation file shown in the image above.

002.jpg

Click Next on the APPX ODBC installation welcome screen.

003.jpg

The APPX ODBC server is a 32bit application. It will install by default to either C:\Program Files\AppxODBC Server\ if you are installing it on a 32 bit version of Windows, or C:|Program Files (x86)\AppxODBC Server\ if you are installing onto a 64 bit version of Windows.

004.jpg

005.jpg

006.jpg

007.jpg

 

Comments:

Revision 62010-06-23 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 24 to 24
 

Windows Server/XP/Vista/Win 7

New Installation

Changed:
<
<



>
>
We're going to install APPX ODBC Server on a Windows Server 2008 64 bit. APPX 5.0.2 is already installed on a Windows Server 2003 32 bit server and configured to listen on TCP port 8063. You should keep the versions the same between APPX ODBC and APPX Server, otherwise you could end up with performance issues or failure to connect errors. APPX ODBC Server listens on TCP port 1990. Let's make sure that that TCP port is available with the OS netstat command line tool.
Verify TCP Port 1990 is open via Netstat Command

000.jpg

The port is available as you can see in the image above.

Download and run the APPX ODBC Server installation file.

Let's download the APPX ODBC Server and start the installation.

001.jpg

 

Comments:

Revision 52010-06-23 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 33 to 33
 
<--/commentPlugin-->

-- JoeOrtagus - 2010-04-05

Added:
>
>
META FILEATTACHMENT attachment="000.jpg" attr="h" comment="" date="1277304149" name="000.jpg" path="000.jpg" size="18326" stream="000.jpg" tmpFilename="/tmp/0dC8iqp03a" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="001.jpg" attr="h" comment="" date="1277304204" name="001.jpg" path="001.jpg" size="41845" stream="001.jpg" tmpFilename="/tmp/43xTx6P64c" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="002.jpg" attr="h" comment="" date="1277304215" name="002.jpg" path="002.jpg" size="24963" stream="002.jpg" tmpFilename="/tmp/nuVEZwqYWz" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="003.jpg" attr="h" comment="" date="1277304223" name="003.jpg" path="003.jpg" size="28149" stream="003.jpg" tmpFilename="/tmp/V0IJyOBQNN" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="004.jpg" attr="h" comment="" date="1277304232" name="004.jpg" path="004.jpg" size="29765" stream="004.jpg" tmpFilename="/tmp/k70x4gt4uX" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="005.jpg" attr="h" comment="" date="1277304238" name="005.jpg" path="005.jpg" size="22924" stream="005.jpg" tmpFilename="/tmp/yDfEo8Jhyb" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="006.jpg" attr="h" comment="" date="1277304244" name="006.jpg" path="006.jpg" size="23785" stream="006.jpg" tmpFilename="/tmp/sdumVHumLG" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="007.jpg" attr="h" comment="" date="1277304250" name="007.jpg" path="007.jpg" size="22728" stream="007.jpg" tmpFilename="/tmp/5YdisbD8i8" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="008.jpg" attr="h" comment="" date="1277304255" name="008.jpg" path="008.jpg" size="27816" stream="008.jpg" tmpFilename="/tmp/PldCEh2rCO" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="009.jpg" attr="h" comment="" date="1277304261" name="009.jpg" path="009.jpg" size="49935" stream="009.jpg" tmpFilename="/tmp/TQxgcCISQF" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="010.jpg" attr="h" comment="" date="1277304269" name="010.jpg" path="010.jpg" size="43957" stream="010.jpg" tmpFilename="/tmp/DU1qDvpQtd" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="011.jpg" attr="h" comment="" date="1277304276" name="011.jpg" path="011.jpg" size="104160" stream="011.jpg" tmpFilename="/tmp/B1DQHdWJA2" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="012.jpg" attr="h" comment="" date="1277304283" name="012.jpg" path="012.jpg" size="39164" stream="012.jpg" tmpFilename="/tmp/tomMxUZiNw" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="013.jpg" attr="h" comment="" date="1277304292" name="013.jpg" path="013.jpg" size="25691" stream="013.jpg" tmpFilename="/tmp/WxKo6a8Cdt" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="014.jpg" attr="h" comment="" date="1277304299" name="014.jpg" path="014.jpg" size="28268" stream="014.jpg" tmpFilename="/tmp/k6jYk60iN3" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="015.jpg" attr="h" comment="" date="1277304309" name="015.jpg" path="015.jpg" size="30909" stream="015.jpg" tmpFilename="/tmp/uWbhqJivYF" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="016.jpg" attr="h" comment="" date="1277304324" name="016.jpg" path="016.jpg" size="38554" stream="016.jpg" tmpFilename="/tmp/ViqGPhGIeW" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="017.jpg" attr="h" comment="" date="1277304330" name="017.jpg" path="017.jpg" size="38854" stream="017.jpg" tmpFilename="/tmp/BjutKKk30o" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="018.jpg" attr="h" comment="" date="1277304336" name="018.jpg" path="018.jpg" size="5214" stream="018.jpg" tmpFilename="/tmp/EpASDIsHRW" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="019.jpg" attr="h" comment="" date="1277304341" name="019.jpg" path="019.jpg" size="35022" stream="019.jpg" tmpFilename="/tmp/jSlOoyedwy" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="020.jpg" attr="h" comment="" date="1277304349" name="020.jpg" path="020.jpg" size="27192" stream="020.jpg" tmpFilename="/tmp/9NGDHrYgSd" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="021.jpg" attr="h" comment="" date="1277304354" name="021.jpg" path="021.jpg" size="27935" stream="021.jpg" tmpFilename="/tmp/alkPr6if65" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="022.jpg" attr="h" comment="" date="1277304359" name="022.jpg" path="022.jpg" size="7035" stream="022.jpg" tmpFilename="/tmp/u6m5Ggt5xy" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="023.jpg" attr="h" comment="" date="1277304365" name="023.jpg" path="023.jpg" size="7453" stream="023.jpg" tmpFilename="/tmp/PnxR2hITHn" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="024.jpg" attr="h" comment="" date="1277304372" name="024.jpg" path="024.jpg" size="7453" stream="024.jpg" tmpFilename="/tmp/D1SlkEXgcG" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="025.jpg" attr="h" comment="" date="1277304378" name="025.jpg" path="025.jpg" size="7197" stream="025.jpg" tmpFilename="/tmp/yUK7FxuaTg" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="026.jpg" attr="h" comment="" date="1277304383" name="026.jpg" path="026.jpg" size="28459" stream="026.jpg" tmpFilename="/tmp/1kiFUDgWi9" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="027.jpg" attr="h" comment="" date="1277304389" name="027.jpg" path="027.jpg" size="70914" stream="027.jpg" tmpFilename="/tmp/ScXzPsRi1o" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="028.jpg" attr="h" comment="" date="1277304397" name="028.jpg" path="028.jpg" size="82613" stream="028.jpg" tmpFilename="/tmp/r88zqqW7rC" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="029.jpg" attr="h" comment="" date="1277304403" name="029.jpg" path="029.jpg" size="89056" stream="029.jpg" tmpFilename="/tmp/f5tDAJQFTe" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="030.jpg" attr="h" comment="" date="1277304411" name="030.jpg" path="030.jpg" size="26236" stream="030.jpg" tmpFilename="/tmp/haZohC55lw" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="031.jpg" attr="h" comment="" date="1277304419" name="031.jpg" path="031.jpg" size="30736" stream="031.jpg" tmpFilename="/tmp/3DWeCYNTDa" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="032.jpg" attr="h" comment="" date="1277304426" name="032.jpg" path="032.jpg" size="21442" stream="032.jpg" tmpFilename="/tmp/sXyb80eAg3" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="033.jpg" attr="h" comment="" date="1277304432" name="033.jpg" path="033.jpg" size="29462" stream="033.jpg" tmpFilename="/tmp/SBOa9NqvaJ" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="034.jpg" attr="h" comment="" date="1277304439" name="034.jpg" path="034.jpg" size="19771" stream="034.jpg" tmpFilename="/tmp/VRliPdcrqm" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="035.jpg" attr="h" comment="" date="1277304447" name="035.jpg" path="035.jpg" size="22592" stream="035.jpg" tmpFilename="/tmp/OBpEaJB6MU" user="JoeOrtagus" version="1"
META FILEATTACHMENT attachment="036.jpg" attr="h" comment="" date="1277304455" name="036.jpg" path="036.jpg" size="32571" stream="036.jpg" tmpFilename="/tmp/pPa12K2ehd" user="JoeOrtagus" version="1"

Revision 42010-06-23 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 33 to 33
 
<--/commentPlugin-->

-- JoeOrtagus - 2010-04-05

Deleted:
<
<
META FILEATTACHMENT attachment="001.jpg" attr="h" comment="APPX ODBC Server Install 001" date="1276635530" name="001.jpg" path="001.jpg" size="93630" stream="001.jpg" tmpFilename="/tmp/YQZUaUwVBB" user="JoeOrtagus" version="1"

Revision 32010-06-15 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 10 to 10
 APPX ODBC is used by APPX customers to gain access to APPX data from external products, such as Crystal Reports or Excel. Installation of APPX ODBC 5 is accomplished by simply following the steps outlined below. APPX ODBC 5 is a Windows only product for now.

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.

Added:
>
>

AppxODBC requires 3 components to work now. The Appx FMS Server, The Appx ODBC Data Gateway, and the Appx ODBC Driver. The Appx FMS server should already be installed and running. 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...

AppxODBCserver_5_0_2_windows.exe

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.

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This is what administrators will install when they will be manipulating the Data Gateway schemas and importing Appx dictionaries.
 

Disclaimer

APPX ODBC 5 includes many new features and bug fixes. As always, before upgrading your APPX production system, you are strongly encouraged to install APPX ODBC 5 into a test environment where you can verify the compatibility of your applications. APPX ODBC 5 has been thoroughly tested but, because of the complexity of computer software, there will certainly be bugs and some ODBC clients that will not be able to connect to the ODBC server. Consequently, there is no guarantee that your applications will be completely compatible with this significant new release. It is your responsibility to test your applications to ensure that they are compatible with this new release of APPX ODBC and to make any changes that may be necessary to maintain compatibility. Finally, before upgrading your production system, make a backup of your applications and your data. Your computer software and your data are important assets of your organization. Please be prudent and take the steps needed to protect this important investment.

Line: 20 to 24
 

Windows Server/XP/Vista/Win 7

New Installation

Changed:
<
<
Documentation

Overview:

AppxODBC requires 3 components to work now. The Appx FMS Server, The Appx ODBC Data Gateway, and the Appx ODBC Driver. The Appx FMS server should already be installed and running. 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...

AppxODBCserver_5_0_2_windows.exe

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.

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This is what administrators will install when they will be manipulating the Data Gateway schemas and importing Appx dictionaries.

>
>



 

Comments:

Line: 31 to 33
 
<--/commentPlugin-->

-- JoeOrtagus - 2010-04-05 \ No newline at end of file

Added:
>
>
META FILEATTACHMENT attachment="001.jpg" attr="h" comment="APPX ODBC Server Install 001" date="1276635530" name="001.jpg" path="001.jpg" size="93630" stream="001.jpg" tmpFilename="/tmp/YQZUaUwVBB" user="JoeOrtagus" version="1"

Revision 22010-05-24 - GaryRogers

Line: 1 to 1
 
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

Line: 20 to 20
 

Windows Server/XP/Vista/Win 7

New Installation

Changed:
<
<
Documentation

Overview:

AppxODBC requires 3 components to work now. The Appx FMS Server, The Appx ODBC Data Gateway, and the Appx ODBC Driver. The Appx FMS server should already be installed and running. 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...

AppxODBCserver_5_0_2_windows.exe

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.

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 form 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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This is what administrators will install when they will be manipulating the Data Gateway schemas and importing Appx dictionaries.
>
>
Documentation

Overview:

AppxODBC requires 3 components to work now. The Appx FMS Server, The Appx ODBC Data Gateway, and the Appx ODBC Driver. The Appx FMS server should already be installed and running. 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...

AppxODBCserver_5_0_2_windows.exe

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.

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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This is what administrators will install when they will be manipulating the Data Gateway schemas and importing Appx dictionaries.
 

Revision 12010-04-05 - JoeOrtagus

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="APPX500"

APPX ODBC Installations Instructions

This page provides instructions for installing APPX ODBC 5.


Overview

APPX ODBC is used by APPX customers to gain access to APPX data from external products, such as Crystal Reports or Excel. Installation of APPX ODBC 5 is accomplished by simply following the steps outlined below. APPX ODBC 5 is a Windows only product for now.

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.

Disclaimer

APPX ODBC 5 includes many new features and bug fixes. As always, before upgrading your APPX production system, you are strongly encouraged to install APPX ODBC 5 into a test environment where you can verify the compatibility of your applications. APPX ODBC 5 has been thoroughly tested but, because of the complexity of computer software, there will certainly be bugs and some ODBC clients that will not be able to connect to the ODBC server. Consequently, there is no guarantee that your applications will be completely compatible with this significant new release. It is your responsibility to test your applications to ensure that they are compatible with this new release of APPX ODBC and to make any changes that may be necessary to maintain compatibility. Finally, before upgrading your production system, make a backup of your applications and your data. Your computer software and your data are important assets of your organization. Please be prudent and take the steps needed to protect this important investment.

Known Issues:

  • ?

APPX ODBC Server and Driver Installation Instructions

Windows Server/XP/Vista/Win 7

New Installation

Documentation

Overview:

AppxODBC requires 3 components to work now. The Appx FMS Server, The Appx ODBC Data Gateway, and the Appx ODBC Driver. The Appx FMS server should already be installed and running. 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...

AppxODBCserver_5_0_2_windows.exe

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.

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 form 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.

AppxODBCdriver_5_0_2_windows.exe

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. 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.

AppxODBCdriver+ASQL_5_0_2_windows.exe

This is the same as the other driver installer except that it does include ASQL. This is what administrators will install when they will be manipulating the Data Gateway schemas and importing Appx dictionaries.

Comments:

Read what other users have said about this page or add your own comments.


<--/commentPlugin-->

-- JoeOrtagus - 2010-04-05

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback