ViaSQL Integrator

Request a demo

If you'd like to get some real-time, hands-on experience with ViaSQL Direct, we're ready to help you. Send us an email to request a demo and our Sales and Pre-Sales team will be glad to work with you to get you familiar with the product.

Get Started

Download white paper

Take a moment to tell us a little bit about yourself and download our whitepaper on "Data Connectivitiy Solutions" today!

Customer Spotlight

Marin County uses ViaSQL for its Criminal Justice and Tax Assessor systems. Visual Basic, PowerBuilder, and Cold Fusion applications all use ViaSQL to directly access mainframe data. ViaSQL is also used to transfer data, in both directions, between the mainframe and MS SQL Server.

Horizontal Tabs

Overview

ViaSQL™ Integrator lets z/OS, and VSE systems participate in all the new and exciting computing technologies. From the desktop, to the LAN, to the Internet, ViaSQL enables it all. ViaSQL has four fundamental capabilities:

1	ViaSQL gives client-based and web-based applications ODBC, JDBC, and SOAP access to these mainframe data sources:

ViaSQL provides client-based and web-based applications with the ability to execute CICS and batch programs. These customer-written applications can return result sets, perform special processing, or execute important business logic. Access all the data sources listed above, plus Adabas, Datacom, IDMS, and others.

3	ViaSQL lets your CICS and batch applications use SQL to access any LAN-based, ODBC compliant, DBMS. Use ViaSQL to pull data to the mainframe, or use it to push data to the LAN.

4	The built-in TRANSFER feature allows PC-clients or mainframe applications to seamlessly move data between z/OS or VSE and any ODBC data source. Use ViaSQL for bi-directional data transfer to Oracle, Microsoft SQL Server, Sybase ASE, DB2/UDB and others.

From Excel spreadsheets that give the accounting department access to the latest sales information, to dynamic web pages that support e-business applications — ViaSQL makes it happen.

The capabilities listed above, along with a myriad of other important features, combine to make ViaSQL extremely flexible and easy-to-use. ViaSQL supports the following activities:

Web Integration
Desktop Access
Data Movement
Multi-tiered OLTP

Note

ODBC applications can use either ViaSQL Direct, or ViaSQL Integrator to access mainframe data. For a brief discussion of the differences between the two, click here.

ViaSQL consists of separate components brought together into one package; some reside on the mainframe, some on the LAN. The specific mix of components deployed depends on the the specific mainframe data sources that are to be accessed.

And because both the ViaSQL Direct ODBC Driver and the ViaSQL Direct JDBC Driver are shipped with ViaSQL Integrator, all of the streamlined architectural possibilities of ViaSQL Direct are also available.

ViaSQL is rich with features that make it the most versatile middleware solution available for z/OS and VSE mainframes

Use desktop and web tools and applications like . . .

Websphere
Microsft IIS
Microsoft Access
Excel
PowerBuilder
Visual Basic
Cognos Impromptu
Crystal Reports
and others . . .

ViaSQL Feature Highlights

	ViaSQL supports standard SQL SELECT constructs like multi-table joins, unions, search conditions, ordering of result sets, and more. INSERT, UPDATE, and DELETE are also supported.
	A sophisticated mapping tool allows non-relational data sources to be quickly and easily defined to ViaSQL. Or if you like, ViaSQL will use your existing COBOL copybooks to automatically perform the relational mapping.
	Complex VSAM, DL/I and IMS data structures, VSAM indexes, variable-length records, and all S/390 datatypes are supported.
	Choose either TCP/IP or LU6.2 for your LAN-to-mainframe connectivity.

The ViaSQL transfer feature provides bi-directional movement of data between the mainframe and RDBMS systems . . .

SQL Server
Oracle
Sybase
SQL AnyWhere
Microsoft Access
Informix
DB2/UDB
and others . . .

Transfer Highlights

	Two flavors of transfer, Bulk and Template, give you flexible methods for populating and updating relational data sources throughout the enterprise.
	ViaSQL lets your CICS and batch applications initiate TRANSFER operations. Move data to LAN-based DBMS systems after the nightly batch run is complete, or as often as you like.
	For special purpose transfers, or for transfers from mainframe data sources for which ViaSQL provides no direct SQL support, CICS or batch programs can used as either the source or destination for transfer operations.
	ViaTransit™ adds the ability to schedule and monitor transfer operations.

Architecture

ViaSQL Integrator Architecture

The specific mix of components deployed depends on the specific types of functionality desired, and the mainframe data sources that are to be accessed. The components included with ViaSQL Integrator are as follows:

	ViaSQL Gateway is deployed on an NT, 2000, or 2003 system. It provides the connectivity to the mainframe from both client-based and web-based tools and applications. Shipped with the ViaSQL Gateway are the network drivers that support client connections across the LAN from ODBC and Open Client applications.
	ViaSQL Direct ODBC Driver resides on Windows 95, 98, ME, XP, NT, 2000,or 2003. It provides direct connectivity (the ViaSQL Gateway is not required) to the mainframe from both client-based, and web-based, tools and applications
	ViaSQL Direct JDBC Driver resides on the same platform as the Java application or servlet. Like the ViaSQL Direct ODBC Driver, it provides direct connectivity (no gateway) to the mainframe from both client-based and web-based tools and applications. This driver requires TCP/IP connectivity to the mainframe
	Access Server resides in CICS or in a batch address space/partition. For desktop or server access, it receives connections from the LAN-based ViaSQL components, and manages access to DB2, Datacom, the Legacy Data Server, RSPs and XSPs. For mainframe access to LAN-based databases, this component mediates the activities of Client Services Applications, the ViaSQL Redirector, and the ViaSQL Preprocessor runtime components, and communicates with either the Windows or Java CSA Server to provide SQL access to LAN-based databases. For access to web-based resources, this component communicates directly with web and application servers.
	Legacy Data Server runs in a separate z/OS address space or VSE partition, and provides SQL access to legacy data sources like VSAM, IMS. DL/I, and sequential. From the ViaSQL Access Server perspective, the Legacy Data Server appears to be a relational DBMS, just like DB2.
	Legacy Data Manager is a Windows-based GUI application used to map non-relational data formats into relational formats, and to configure and administer the Legacy Data Server environment
	Windows CSA Server is deployed on Windows NT, and provides mainframe applications with SQL access to LAN-based databases.
	Java CSA Server is deployed on on any Java platform, and provides mainframe applications with SQL access to LAN-based databases.
	ViaTransit™ is an easy-to-use, Windows-based tool that allows the creation, initiation, scheduling, and monitoring of enterprise-wide transfer operations.

How It Works

How It Works for Desktop and Web Access

Step 1	The Data Is Mapped
	In order to use SQL to access a non-relational data source, for example VSAM, the data must first be mapped into a relational format. DB2 data, already in relational format, requires no mapping. The mapping is typically done by the database administrator, and must be done once for each file that is to be accessed. The mapping is performed using the Legacy Data Manager, a Windows-based GUI application that uses your existing COBOL copybooks to automatically do the mapping. The Legacy Data Manager stores the mapping information in a mainframe-resident catalog.
Step 2	The Client Accesses the Data
	Using the standard ODBC, Open Client, or DB-Library API, front-end tools, client applications, web-based applications, and web servers request access to data. The requests may take the form of either an SQL statement or a Remote Stored Procedure (RSP) call. Based on local ODBC and/or network configuration, the requests are sent to the ViaSQL Gateway. The ViaSQL Gateway prepares the request for transmission to the mainframe (ASCII-to-EBCDIC conversion for example), establishes a TCP/IP or LU6.2 connection to the mainframe, then transmits the request the ViaSQL Access Server.
Step 3	The ViaSQL Access Server Executes the Request
	Having received the request from the ViaSQL Gateway, the ViaSQL Access Server executes the request against the appropriate data source. Depending on the request, the ViaSQL Access Server calls either DB2, the Legacy Data Server, or a Remote Stored Procedure. If the request is targeted to DB2, the standard DB2 call interface is used. If the request is targeted to the Legacy Data Server, the LDS call interface is used. If the request is a Remote Stored Procedure or eXternal Stored Procedure call, the specified RSP or XSP is executed. In any case, result sets, SQL codes, or messages produced by the request are packaged up in a relational format, and returned to the ViaSQL Gateway.
Step 4	Results Are Returned to the Gateway
	As the results are returned from the ViaSQL Access Server to the ViaSQL Gateway, the appropriate transformations are performed (ASCII to EBCDIC conversion, datatype conversions, etc.). The data ends up in a format that is appropriate for the client application.
Step 5	The Client Gets the Data
	The data, SQL codes, and any messages are returned, back through the network, to the requesting application. From the client's point of view, the mainframe data appears as though it came from a LAN-based relational DBMS.

How It Works for Transfer Operations

Step 1	The Data Is Mapped
	As with client and web access described above, in order to use SQL statements to transfer data to or from a non-relational data source, the data must first be mapped.
Step 2	The Transfer is Initiated
	Using the standard ODBC, Open Client, or DB-Library API, the client application (PC-based or web-based) sends a TRANSFER statement to the ViaSQL Gateway. Typically, the TRANSFER statement includes a SQL statement that specifies the tablenames, the columns to be transferred, and the selection criteria. Alternatively, the TRANSFER statement can specify the name of a Remote Stored Procedure that is to participate in the transfer operation. Additionally, a Client Services Application, or an add-on product called ViaTransit, can initiate transfer operations.
Step 3	The Gateway Receives the Transfer Request
	Based on specifications in the TRANSFER statement, the ViaSQL Gateway establishes two connections: one connection to the data source that will supply the records for the transfer operation, and one to the data source that will receive the records. If the TRANSFER statement specifies an SQL statement, the statement is sent to the source data source for execution. If the TRANSFER statement specifies a Remote Stored Procedure or eXternal Stored Procedure, the specified RSP or XSP is invoked. In either case, the transfer operation begins.
Step 4	The Transfer Proceeds
	For Bulk Transfers, the ViaSQL Gateway will attempt to use the bulk load mechanism of the destination DBMS. For Destination Template Transfers, the Gateway will perform an INSERT, UPDATE, or DELETE for each row in the source result set. In any event, the selected data is moved directly into the target DBMS.
Step 5	The Transfer Completes
	When the transfer is complete, the ViaSQL Gateway notifies the initiating process of the success or failure of the transfer operation.

Request a demo

Download white paper

Customer Spotlight

Horizontal Tabs

Note

How It Works for Desktop and Web Access

How It Works for Transfer Operations

Corporate Offices

Development & Support

Billing

Phone

E-Mail

Search form

ViaSQL Integrator

Request a demo

Download white paper

Customer Spotlight

Horizontal Tabs

Note

How It Works for Desktop and Web Access

How It Works for Transfer Operations

Corporate Offices

Development & Support

Billing

Phone

E-Mail