This was the only documentation that I could find with ADSM regarding
the ODBC interface. I did find this useful though, and was able to
drill into the ADSM database with Microsoft Access.
> In ADSM Version 3, to compliment the ability to use SQL to query the
> contents of the ADSM database, an Open Database Connectivity (ODBC)
> interface has
> also been implemented. This allows the output from the ADSM server
> database to be tailored for presentation to meet particular business
> Graphical SQL Interface
> ODBC is a standard interface between database engines and front-ends.
> allows products such as Lotus Approach or Microsoft Access to be used
> graphically construct SQL select statements, which are then dispatched
> to the database. The information produced by these select statements
> then returned in
> an tabular form, enabling further processing to be undertaken. This
> further processing is normally in the form of producing graphs or
> ODBC Driver
> The ODBC driver supplied with Version 3 is part of the client package.
> The ODBC client application, Lotus Approach for example, interfaces to
> the ADSM
> client which in turn interacts with the ADSM server. This
> is only available for the following Win32 clients: Windows 95, Windows
> NT 3.51, and
> Windows 4.0.
> ODBC Version 2.5
> The ODBC driver in Version 3 supports the ODBC 2.5 application program
> interface (API). The ADSM SQL interface supports read-only SQL SELECT
> statements and does not allow any alteration of the information in the
> database. This means that the interface does not completely conform to
> any of ODBC API
> or SQL grammar conformance levels. Applications that require
> conformance levels may have problems connecting to ADSM.
> ODBC Implementation
> The chart above illustrates the flow of information, both to and from
> the server, during the processing of an SQL SELECT operation from an
> ODBC application.
> The ODBC interface through which the client application accesses the
> server is built into the ADSM admin client. Using the ODBC API which
> interfaces into the
> ADSM ODBC driver, the client application submits requests to the
> code of the ADSM client. At this point a login prompt is displayed
> within the client
> application and a valid admin id and password must be provided. An
> session is then started with the ADSM server using normal client
> The server, on receiving the ODBC request, starts an admin session
> may be tracked with the QUERY SESSION command. The admin session then
> submits the SQL SELECT statement to the server which in turn queries
> database for the information. Once the results of the query have been
> generated, they
> are passed back through the common client code to the ODBC API in the
> application and the session is closed.
> ODBC Configuration
> To ensure that the ODBC implementation with ADSM is as flexible as
> possible, the ODBC connectivity is implemented as an ODBC driver
> the operating
> system. This enables the operating system to offer ODBC connectivity
> a standardized way to all ODBC-compliant applications.
> Setup Utility
> The Version 3 client package includes the ODBC driver and a copy of
> ODBC Database Source Administrator. At client installation the ODBC
> driver is an
> optional component. If selected this creates an icon in the control
> panel named ODBC. This icon starts the ODBC Data Source Administrator
> which can be
> used to configure the ADSM driver as a User, System or File data
> User data sources are only available to the defining user. System data
> sources may be
> accessed by any user of the system. To configure the ADSM ODBC driver
> a data source the server name, TCP/IP address, and TCP port number
> ODBC Applications
> An application running in an environment with the ADSM ODBC driver
> installed and configured as a data source, can import or link to ADSM
> database tables.
> This is normally done through an "Open ODBC Data Source" or "Get
> External Data" menu item. It is important to note that an import will
> import all the data
> associated with the tables as well as the tables themselves. Standard
> ODBC supports database modification as well as query. However, the
> database is
> only available as read only and an ODBC application cannot update it.
> Having linked local application tables to their equivalent server
> SQL queries may then be constructed by the application. The results
> either be
> manipulated in the application or saved and used with a third
> application such as a graphing package or report generator.
> Server authentication for ODBC applications is performed in the same
> as for other administrative interfaces. When the application accesses
> the server a
> prompt will be issued for an administrator user ID and password. These
> must be entered before the application can access the server.
> [ Top of Page : Previous Page : Next Page : Table of Contents ]