1 / 42

Adabas SQL Gateway

swann
Télécharger la présentation

Adabas SQL Gateway

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Adabas SQL Gateway Becky Albin Chief IT Architect Becky.Albin@softwareagusa.com

    2. Natural Boston Conference 2005 | Page 2 Adabas Architecture

    3. Natural Boston Conference 2005 | Page 3 Get to Adabas from .NET and JAVA Imagine If access to Adabas from JAVA and .NET was as easy as it is from Natural If Adabas could drive your Java and .NET applications If the native power of Adabas was fully accessibly via open interfaces If your application programmers could access Adabas with no knowledge of Adabas it is possible

    4. Natural Boston Conference 2005 | Page 4 Open Connectivity and Real-time Data Sharing Challenges Federated/Heterogeneous application and database landscape Cross-platform application development: Mainframe, Java or Microsoft .NET Adabas Adabas SQL Gateway (ACE) Adabas SOA Gateway (ASG) Real-time data sharing with Event Replicator for Adabas

    5. Natural Boston Conference 2005 | Page 5 Connecting Adabas to .NET, JAVA and Web Services

    6. Natural Boston Conference 2005 | Page 6 Adabas SQL Gateway (ACE) Architecture ODBC Driver Mgr ODBC Driver JDBC classes from sun - JDBC server service and ODBC Here is an explanation of OLE DB. It is a more generic access method, and better suited to ADABAS. OLE DB is a strategic system-level programming interface to move data across an organization. It is an open specification designed to build on the success of ODBC by providing an open standard for accessing all kinds of data. While ODBC was created to access relational databases, OLE DB is designed for relational and non-relational information sources alike. OLE DB components consist of data providers (which contain and expose data), data consumers (which use data), and service components such as query processors and cursor engines (which gather and sort data). OLE DB interfaces are designed to help diverse components integrate smoothly, so that OLE DB component vendors can quickly bring high-quality products to market. OLE DB data providers implement a set of core OLE DB interfaces that offer basic functionality, enabling other OLE DB data providers, service components, and consumer applications to interoperate in a standard, predictable manner. Data consumers can be any software program requiring access to a broad range of data, including development tools, personal productivity applications, database services products, or OLE DB service components. OLE DB service components implement functionality not natively supported by some simple OLE DB data providers. ODBC Driver Mgr ODBC Driver JDBC classes from sun - JDBC server service and ODBC Here is an explanation of OLE DB. It is a more generic access method, and better suited to ADABAS. OLE DB is a strategic system-level programming interface to move data across an organization. It is an open specification designed to build on the success of ODBC by providing an open standard for accessing all kinds of data. While ODBC was created to access relational databases, OLE DB is designed for relational and non-relational information sources alike. OLE DB components consist of data providers (which contain and expose data), data consumers (which use data), and service components such as query processors and cursor engines (which gather and sort data). OLE DB interfaces are designed to help diverse components integrate smoothly, so that OLE DB component vendors can quickly bring high-quality products to market. OLE DB data providers implement a set of core OLE DB interfaces that offer basic functionality, enabling other OLE DB data providers, service components, and consumer applications to interoperate in a standard, predictable manner. Data consumers can be any software program requiring access to a broad range of data, including development tools, personal productivity applications, database services products, or OLE DB service components. OLE DB service components implement functionality not natively supported by some simple OLE DB data providers.

    7. Natural Boston Conference 2005 | Page 7 Key Features Adabas SQL Gateway Provides cost-effective mainframe data reusability by extending access to Adabas via standard SQL applications Eliminates the need to duplicate or move data to a data warehouse with direct access to Adabas information from the desktop Increases productivity for both IT programmers and business users by reducing the number of IT requests for Adabas information/reports Lowers operational costs with an easy to install, high performance SQL engine that provides quick and easy access to enterprise data Extensible by other SQL Adapter to do heterogeneous joins across disparate DBMS sources

    8. Natural Boston Conference 2005 | Page 8

    9. Natural Boston Conference 2005 | Page 9

    11. Natural Boston Conference 2005 | Page 11 Bloor Research Report Analysts attention on what we are doing here..appreciate XML and SQL access to ADABASAnalysts attention on what we are doing here..appreciate XML and SQL access to ADABAS

    12. Natural Boston Conference 2005 | Page 12 Architecture - Adabas SOA Gateway What platforms it runs on.What platforms it runs on.

    13. Natural Boston Conference 2005 | Page 13 SQL and SOA Gateway Whats the difference?

    14. Natural Boston Conference 2005 | Page 14 Which Adabas Gateway Should be Used ?

    15. Natural Boston Conference 2005 | Page 15 What the Gateways have in common? No additional programming required Support for Adabas security No knowledge of Adabas required by programmers Open Standards OLTP levels of performance Traditional mainframe class stability and service Simple installation and configuration Support for all Adabas platforms Close integration with Adabas

    16. Natural Boston Conference 2005 | Page 16

    17. Natural Boston Conference 2005 | Page 17 ACE - Functionality Overview ODBC SQL Level 2 Security Meta Data Management Enhanced SQL Capability Views Heterogeneous Joins Bi-directional Data Conversion Read/Write Access to Data

    18. Natural Boston Conference 2005 | Page 18 ACE - Components Data Dictionary ODBC Driver OLE DB RPC Driver Database Server JDBC Driver (Thin client) JDBC Server JDBC Router

    19. Natural Boston Conference 2005 | Page 19 ACE - Data Dictionary Administrator Component CDD contains information describing the data tables and fields in the accessed databases including security contains the metadata about the source information provides easy maintenance of the metadata, views, and integrated security

    20. Natural Boston Conference 2005 | Page 20 ACE - Data Dictionary Administrator Component CDD parent/child topology One central CDD A logical CDD with one or more child CDD Group CDD with its own rights

    21. Natural Boston Conference 2005 | Page 21 ACE - ODBC Driver Is tightly coupled with the CONNX Data Dictionary. Uses Structured Query Language (SQL) as the standard for accessing information. ODBC SQL Level 2 compatibility. Enables the use of off-the-shelf ODBC-compliant reporting and development tools.

    22. Natural Boston Conference 2005 | Page 22 ACE - OLE RPC Server The OLE RPC Server allows the user to make remote procedure calls (RPC) from any programming language that supports OLE 2.0. Supported tools include: Microsoft Access Microsoft Excel Microsoft Visual Basic Microsoft Visual C++

    23. Natural Boston Conference 2005 | Page 23 ACE - Database Server Translates SQL requests into native database requests. The ODBC/JDBC driver makes the translation service transparent to the end user. The primary features of the driver include the following: SQL access to target sources Complete user-level and group-level security Low memory and disk resource utilization Complete file and/or table security

    24. Natural Boston Conference 2005 | Page 24 ACE - Database Server Communication between client and server.

    25. Natural Boston Conference 2005 | Page 25 ACE - JDBC Driver Used with Data Dictionary (CDD), the JDBC driver provides a means of using many popular querying tools and application development tools. Works with JDBC-compliant software. Enables applications to access data using the JavaSoft JDBC API. The JDBC Driver / Router: Runs as a Windows service Is the connection between client and server The router is used on Unix as a connector Type 3 - Net Protocol, Pure Java

    26. An inside tour of the Adabas SQL Gateway

    27. Natural Boston Conference 2005 | Page 27 ACE - Meta Data Meta Data Import Natural DDMs Unload Natural DDMs via the Natural Object Handler Select the appropriate parameter Transfer Format Enter location for the unload file Select Default Options Select DDMs

    28. Natural Boston Conference 2005 | Page 28 ACE - Meta Data Meta Data Import Natural DDMs Make the unload Natural DDMs available FTP or network drive Start the CDD Manager Select Import, Import Type Adabas Systrans Enter the appropriate parameters DBID, Systrans file, ADASCR password, Host, etc. Start Import

    29. Natural Boston Conference 2005 | Page 29 ACE - Meta Data Meta Data Import Adabas LF Start the CDD Manager Select Import, Import Type Adabas LF Enter the appropriate parameters DBID, Systrans file, ADASCR password, Host, etc. Select file(s) to be imported Adjust definitions if necessary Save data either in a new CDD or in a existing one

    30. Natural Boston Conference 2005 | Page 30 ACE - Meta Data Meta Data Import Adabas Dynamic DDL Start the CDD Manager Select Import, Import Type DDL import Enter the appropriate parameters DBID, Systrans file, ADASCR password, Host, etc. Select file(s) to be imported Adjust definitions if necessary Save data either in a new CDD or in a existing one Support of Natural Date / Time fields

    31. Natural Boston Conference 2005 | Page 31 ACE - Adabas Security Support External Security ACE server-based Client user ID and password are used to access RACF at host-side APF authorized library needed Should not be used together with SAF Gateway Performance double-checking AAF-based Client user ID and password are passed through to Adabas No APF authorization needed for ACE server

    32. Natural Boston Conference 2005 | Page 32 ACE - Adabas Security Support Database Security Adabas Security Support allows the usage of external security tools on mainframe Makes use of ADASCR Define a global password in CDD Specify a password in the SQL statement SELECT * FROM adabas_windows.dbo.CUSTOMERS_ADABAS {fn setadapassword CUSTOMERS_ADABAS, PASSWORD}

    33. Natural Boston Conference 2005 | Page 33 ACE - Security Capability Security model with the following features: Established Security Measures Remain Intact CONNX does not bypass security measures established by a database or operating system. For example read-only access to a table remains. Secure Management View, table, and column security levels can be assigned to an individual user, or to a group of users. Record security levels can be established through CONNX views. Seven Access Levels CONNX supports seven access levels: Select Read-only access Update Update queries Insert Insert new data Delete Delete data Drop Drop tables Execute Execute stored procedures RFI Enable Referential Integrity

    34. Natural Boston Conference 2005 | Page 34 ACD - Security Capability Security model with the following features: Integrated Security/Database Account Management enables users to specify a single CONNX user name and password to access multiple databases that may each require a distinct user name and password. Secure Data Dictionary The Data Dictionary is encrypted to only allow access to authorized users. Maximum Security Option allows only users defined in the CONNX Data Dictionary to access data, regardless of database permissions.

    35. Natural Boston Conference 2005 | Page 35 ACE - Security Capability Security model with the following features: Read Only Default Access Option This option restricts all access to all tables in the CONNX Data Dictionary to Read Only. Can be overridden by specifying User or Column level security.

    36. Natural Boston Conference 2005 | Page 36 ACE - MU / PE Fields Presentation MU fields are presented as Sub-tables PE fields are presented as Sub-tables MU within PE fields are presented as Sub-tables

    37. Natural Boston Conference 2005 | Page 37 ACD - MU / PE Fields Example

    38. Natural Boston Conference 2005 | Page 38 ACE - MU / PE Fields Create a Table Creates a SQL table to represent every top-level MU and PE field. Employees Sample Adabas file

    39. Natural Boston Conference 2005 | Page 39 ACE - MU / PE Fields The ISN is used to link the ROOT table to the rotated array tables.

    40. Natural Boston Conference 2005 | Page 40 ACE - MU / PE Fields Parameters CNXARRAYCOLUMN A pseudo column field that represents the # of the occurrence for this SQL record. This numeric field is zero based AutoNumber CONNX reports the ISN field or the CNXARRAYCOLUMN field as an autonumber field. This suggests to applications that the database automatically determines the next value for newly inserted records

    41. Natural Boston Conference 2005 | Page 41 ACE - MU / PE Fields Access to MU / PE fields Insert = Update? Yes, Inserts into Adabas rotated array fields are actually translated into an update of the existing record adding the new occurrence. ISN field required When issuing a SQL Update against a rotated table, the ISN field # is required Deletes not possible for PE fields because of Adabas ISN field required. When issuing a SQL Update against a rotated table, the ISN field# is required.

    42. Natural Boston Conference 2005 | Page 42 ACE - MU / PE Fields Update examples update employees set LANG_2 = ENG where ISN_12_11 = 1004 update employees_lang set LANG = ENG where ISN_12_11 = 1004 and cnxarraycolumn = 1

    43. Software AG. Bright ideas, everywhere.

More Related