DOCSLIB.ORG

Pervasive Integration Engine™ Scalable and Extensible Delivery of Saas, Legacy, and SOA – Style Integration

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Pervasive Integration Engine™ Scalable and Extensible Delivery of Saas, Legacy, and SOA – Style Integration Pervasive Integration Engine™ Scalable and Extensible Delivery of SaaS, Legacy, and SOA – Style Integration The Pervasive Integration Engine is a data transformation to complex, high-volume multi-processor implementations engine used to reliably and quickly power data and that handle millions of transactions at a time. The application integration, generally without any custom Integration Engine assists in data warehousing, data marts programming. This easily embeddable small footprint and data mining projects, populating decision support software allows users to quickly and easily share data systems, legacy data migrations, capturing on-line feeds between multiple databases of nearly any format, as well and Web-based data delivery. as a wide variety of on-premise and SaaS applications. The flexible Integration Engine executes in UNIX, Linux, Agile, Embeddable, and Powerful and Windows environments. More than 20 years of data The Integration Engine is a pure execution engine with no integration expertise has gone into making Pervasive graphical user interface components, giving it a very light Integration Engine a multi-purpose integration platform profile. Its design maximizes opportunities and economics that is reusable across diverse integration scenarios for ISVs, SaaS vendors, resellers, BPOs, and other data such as ETL, B2B, EAI, data migration and conversion, service providers. The embedding process uses simple and data replication. With more than 150 plus data, built-in wizards to support rebranding and to control technology, and application connection adapters, which components are included during the silent, quick, Integration Engine has the power to integrate virtually and simple installation process. The install can display anything. The Pervasive business model and Integration screens normally, or suppress Pervasive screens to Engine technical scalability allow low-cost adoption for provide a seamless, unified offering. light embedded versions of the engine for basic data migrations that generate high ROI for ISVs, all the way up Multiple Integration Engine Interfaces The Integration Engine has multiple interfaces to address the full range of automation scenarios: CONTROL 1 The command line interface enables you to schedule operations and to customize transformations and processes at run time. 2 COM and Java APIs let you call transformations and processes from within your own applications, delivering embedded integration. 3 Pervasive’s Integration Services delivers integration as a robust service for SOA and Web Service environments. 4 The XML Metadata process and map specifications are open, allowing direct, programmatic manipulation of the instructions that control the Integration Engine. EXTEND 5 Message Component Framework allows you to extend the Engine’s functionality by adding custom object processing to integration workflows. 6 Data Mediation Services extends Pervasive connectivity to new applications. 1.800.287.4383 www.pervasive.com 1 2 Scheduled Operations – Command Line Interface Embedding the Integration Engine in Applications The Integration Engine command line interface loads – Java and COM APIs a specified transformation or process, makes the Interaction with applications that embed the Integration overides requested by any command line options, and Engine is generally accomplished via the COM or Java executes. The command line has the ability to issue APIs. In addition to executing pre-defined transformations overrides for many parts of the transformation or process and processes, the API can be used to automatically specifications, including options like SQL pass-through and record selection criteria. The command line also create, map, and run simple default transformations. The supports the notion of a default transformation for very functionality provided by the API provides for tight control simple mapping situations. All the minimum information of connection parameters, error handling, and on-the-fly necessary for specifying a transformation can be entered filtering and parameter changes. The Pervasive Integration directly on the command line, and a map created on the Engine SDK fully documents the capabilities of the APIs. fly dynamically. • All command line options plus the following: • Source and target connection overrides – This can • Configure the Integration Engine environment range from simply pointing to different source or • Manage source and target data connections target files, to enumerating all the options necessary • Execute, terminate, load, unload, and query to connect to multiple SQL tables. Both file and table transformation information wildcards are supported. • Control error trapping and logging levels • Sophisticated error trapping, logging levels, and • Query field attributes, primary key information, field progress checking counts, and values • Dynamic query statements to use on source data • Manage target output through record sampling and • Runtime overrides of record extraction filters operating filtering on the source data, including input variables to Boolean • Manage progress and status handling expressions and record ranges • Set the reject file and query its entries • Control of reject files • Execute transformations in a transaction • Support for return codes and operational information • Set target update or delete operations and query the results The Pervasive Integration Engine API allows seamless integration with other programs and extensive control of the engine process. The Engine Command line provides an interface for launching transformation maps and processes directly from the operating system command line, batch files or system schedulers. Like the API, the Command Line can be used to execute pre-designed conversions, or to automatically create, map, and run default conversions. It also provides less granularity for interrogating or managing engine behavior. 1.800.287.4383 www.pervasive.com Integration Engine Interfaces 3 Integration as a Service (IaaS) and SOA – mechanisms available in the Pervasive tools that work Integration Services in conjunction with J2EE application servers. One, in particular, is a purpose-built Message Driven Bean (MDB) Pervasive integration products can be deployed in a that is configured to listen on a Java Message Service variety of ways depending on customer requirements (JMS) queue for the input message and then invoke – be it a single lightweight embedded engine or a a specific integration specification via the Integration distributed, fully managed set of Service Oriented Services API. The API then finds an available Integration Architecture (SOA) adapters. Pervasive also offers Engine on the local server, invokes the desired integration Integration as a Service, hosted either in the customer’s process, and returns the results. data center for SaaS vendors and BPOs or in our data center for end users who don’t want to deal with the In addition to both a provider and client side hassle of installing and learning a new software tool. implementation of the JCA Resource Adapter, and a purpose-built MDB, Integration Services includes The Pervasive architecture supports SOA frameworks with a generic Web Service. This permits clients such as rich connectivity to many messaging environments such those using Simple Object Access Protocol (SOAP) to as JMS, Sonic MQ, MSMQ, Oracle AQ, and Websphere call any integration process. All SOAP standards for MQ as well as to alternative queue-like technologies WSDL-described and other Web services are supported, such as email or FTP servers, in which an email or a including SOAP encoded arrays. This technology enables file represents the message. In addition, the Integration both SOA and IaaS implementations of the Integration Services API makes integration processes and maps Engine including the Pervasive DataCloud™ platform. exposable as robust standards-based Web Services. Integration Services supports Web Service standards, Each Integration Engine instantiated by Integration allowing Pervasive integration workflows to fit neatly Services runs in its own address space. This isolation into a variety of SOA architectures. When deploying in increases performance and reliability. SOA environments, there are several communication Client Interfaces PERVASIVE INTEGRATION J2EE JCA Framework SERVICES (EJBs) SOAP The Pervasive Integration SOAP Orchestration Engine is a powerful tool SOA for businesses looking to Engine 1 a deliver real-time service- Address Space 1 Jav Applications based integration and gain Wrapper •Instantiate the greater traction in both Integration Engine Optional SaaS and SOA integration. •Pass messages Engine 2 a •Select which Maps Jav processes Address Space 2 Wrapper to run Data Instances •Set global Processes process variables Engines 3, 4 . a Address Jav Wrapper Spaces 3, 4 . Process J2EE XML Message Enterprise Driven Bean Message/ RMI-Proxy Service Bus (Sonic, Integration TIBCO, Service JMS) Process SOA 1.800.287.4383 www.pervasive.com 4 Metadata-driven Integration – 5 Process Flow Plug-ins and Extensions – Direct Specification Control Message Component Framework An open XML repository houses all specifications and The Message Component Framework (MCF) is a rules that define a Pervasive integration task’s execution framework for using Java to make plug-ins, which we and workflow. Storing integration as non-proprietary call “components,” to extend Pervasive functionality to XML provides full compatibility with a variety of source specific integration
Load more

Recommended publications
  • Sage 300 Ops Inquiry and Sales Analysis Database Conversion Guide
    Sage 300 Ops Inquiry and Sales Analysis Database Conversion Guide July 2017 This is a publication of Sage Software, Inc. © 2017 The Sage Group plc or its licensors. All rights reserved. Sage, Sage logos, and Sage product and service names mentioned herein are the trademarks of The Sage Group plc or its licensors. All other trademarks are the property of their respective owners. Last updated: July 5, 2017 Table of contents Introduction 3 System requirements 3 Converting databases to Microsoft SQL Server format 4 Step 1: Activate Ops Inquiry and/or Sales Analysis 4 Step 2: Set up a new Microsoft SQL Server database 4 Step 3: Set up access to your Pervasive database 4 Step 4: Copy data from your Pervasive database to your Microsoft SQL Server database 6 Step 5 (optional): Set up a pictures directory in Ops Inquiry 8 Ops Inquiry and Sales Analysis Database Conversion Guide ii Introduction Beginning in Sage 300 2016, only databases in Microsoft SQL Server format are supported. If you are upgrading from a previous version of Sage 300 and you have Ops Inquiry or Sales Analysis databases in Pervasive format, follow the steps in this guide to convert your databases to Microsoft SQL Server format. Note: You must convert your databases before installing your new version of Sage 300. System requirements To complete the steps in this guide, you must have: • Pervasive PSQL Client or Server • MS SQL Server 2008 or later • SQL scripts provided by Sage: – ActivateData.sql – DisableIndexes.sql – EnableIndexes.sql Ops Inquiry and Sales Analysis Database Conversion Guide 3 Converting databases to Microsoft SQL Server format Follow the procedures in this section to convert a database from Pervasive format to Microsoft SQL Server format.
    [Show full text]
  • Information Technology
    UPTEC IT 09 009 Examensarbete 30 hp Maj 2009 Database Performance and Complexity in Visual DataFlex Håkan Johansson Abstract Database Performance and Complexity in Visual DataFlex Håkan Johansson Teknisk- naturvetenskaplig fakultet UTH-enheten This report is meant to be used when choosing a third-party database management system in combination with Visual DataFlex. The database managers that are included Besöksadress: in this test are Microsoft SQL Server, Pervasive.SQL, Oracle and Embedded Database. Ångströmlaboratoriet Lägerhyddsvägen 1 It will cover the pros and cons with each tested database manager when using Hus 4, Plan 0 applications created with Visual DataFlex. It will also cover the fault-tolerance when using clustering, the backup possibilities with minimal downtime and the complexity of Postadress: installing and configuring the database manager. Box 536 751 21 Uppsala Visual DataFlex is a framework for developing database applications aimed at Telefon: Windows or web platforms. The framework is owned and developed by Data Access 018 – 471 30 03 Worldwide, Inc. Telefax: 018 – 471 30 00 Visual DataFlex provides a database manager called Embedded Database which is not suitable to be used in a multi-client environment. Therefore, in multi-client Hemsida: environments, a third party database management system is normally used. http://www.teknat.uu.se/student Visual DataFlex is primarily used in smaller and midsized environments. Database administrators are normally not wanted in these environments and therefore it is important that the third-party database management system is easy to set up and configure. For database independency, Visual DataFlex uses connectivity kits which are an abstraction layer between the internal interface in Visual DataFlex and the client software of the database manager in use.
    [Show full text]
  • Pervasive PSQL V11 4 Optimized for Multi-Core Servers 4 64-Bit Windows ODBC Driver 4 Support for Ipv6 4 ADO.NET 3.5 Provider with .NET Entity Framework Support
    PRODUCT SHEET Pervasive PsQL v11 4 Optimized for Multi-Core servers 4 64-bit windows ODBC Driver 4 support for iPv6 4 aDO.Net 3.5 Provider with .Net entity Framework support 4 PDaC for raD studio 2010 and 2009 Overview Benefits Pervasive PSQL™ is one of the most reliable, low-maintenance, high-performance database management systems (DBMSs) in the world. Pervasive PSQL v11 offers • Multi-core performance without changing important additions — multi-core optimization, enhanced 64-bit support, IPv6 your application support and updated developer tools. • Improved scalability—more users, more cores, more data processing power New Features • Simple transition to IPv6 • More 64-bit relational support Optimized for Multi-core – Pervasive PSQL v11 is a parallel implementation of Pervasive PSQL that includes several enhancements for multi-core: • Updated developer tools • Simple migration from previous versions • Improvements to the low-level synchronization mechanisms in the transactional interface • Multiple users can read the same cached file pages simultaneously and their operations can proceed on multiple cores supported Platforms • Multiple users accessing independent files can proceed on different cores • Windows 7 • Non-user activity such as checkpoint and log management can also use • Windows Server® 2008 and 2008 R2 additional cores • Windows Vista® 64-bit ODBC – Pervasive PSQL v11 supports the ODBC interface on native 64-bit • Windows Server 2003 Windows operating systems with 64-bit architecture. The transactional and relational • Windows® XP interfaces for 64-bit Pervasive PSQL Server are now in the same common address space. • Red Hat® Enterprise Linux 4 and 5 • SUSE™ Linux Enterprise 9 and 10 IPv6 Support – IPv6 (Internet Protocol version 6) is the Internet protocol that will follow • Citrix the current version - IPv4.
    [Show full text]
  • Tested and Supported Environments
    Tested and Supported Hertzler Systems Inc. Turning Data into Knowledge Environments GainSeeker® Suite v9.2 Definitions Tested: Operating systems, networking systems and databases listed as tested are the systems on which Hertzler Systems has extensively tested our program in our test environment. We are confident that our program will operate with normal parameters, in environments using these components, for most users. Supported: Operating systems, networking systems and databases listed as supported are the systems on which we have done little or no in‐house testing recently. Most of these components have been tested on previous releases, but are no longer part of the testing program (due to the march of progress and limited testing resources) or are too new to have been included in the testing program. We feel we can reasonably expect our program to run in environments using these components (in conjunction with other supported or tested components) with no issues. Note: Every reasonable effort will be made to correct any issues that arise in Tested and Supported operating environments. Unsupported: Operating systems, networking systems and databases not listed as tested or supported are considered unsupported at this time. Hertzler Systems makes no assumptions that the program will run in environments containing one or more unsupported components and may not provide customer support services for these environments. If support is provided, it may be a chargeable service, even for customers with support contracts. Systems Tested Operating
    [Show full text]
  • Accessing Zen/PSQL Data from ODBC Or Other Applications
    Accessing Zen/PSQL Data From ODBC Or Other Applications A White Paper From For more information, see our web site at http://www.goldstarsoftware.com Accessing Zen/PSQL Data From ODBC (or Other Applications) Last Updated: 02/23/2021 When it comes to "frequently asked questions", this one takes the cake, to be sure. It seems that people are used to databases which provide ODBC access natively (such as FOXPro, Access, etc.) and get confused when they cannot access their own application data immediately. Then, they start “Btrieve-bashing” because they can't get their data out. This document was created to provide some explanation as to what the issues are when it comes to ODBC access and your data, whether it be stored in a current Actian Zen database engine, or one of the older ones, including Actian PSQL, Pervasive PSQL, Pervasive.SQL, and even Btrieve. The material is taken mostly from the PSQL Service & Support classes provided by Goldstar Software. Database Engine Type & ODBC Drivers The first question we have to deal with is the availability of ODBC drivers. If you have a newer engine, then you can skip this section entirely. If you have an older engine, though, then you should read on. Old DOS applications may be using Btrieve 5.x or older for DOS, 5.x for Windows, or even Btrieve 5.x or 6.10 for NetWare. These engines do NOT contain an ODBC driver and will not support 32-bit ODBC access. (MS Access 2.0 had limited support for Btrieve 6.10, but only from 16-bit Windows applications.) If this is the case, then you will need to purchase a new database engine to support this access.
    [Show full text]
  • Creating an ODBC Data Source for Zen/PSQL
    Creating an ODBC Data Source for Zen/PSQL A White Paper From For more information, see our web site at http://www.goldstarsoftware.com Creating an ODBC Data Source for Pervasive PSQL Last Updated: 02/05/2021 Many users of Actian Zen/PSQL (formerly Pervasive PSQL) see their data through Btrieve-level applications which access the data natively using low-level (and very high- performance) function calls. However, getting access to this data from other applications, such as Microsoft Access, Crystal Reports, UPS WorldShip, and others may require that you configure an ODBC data source for the database engine. There are actually several ways to do this task, depending on the software version you are using. Using the Control Center may be the quickest way to do it, but the screens look different for each engine version. To use this, check with the online manuals regarding the Control Center. Since database versions tend to share a similar interface at the native ODBC level, we will go through the ODBC Administrator to create the database. Create the Engine DSN on the Server Start by logging into the database server at the console itself. If you must use a Remote Desktop or Terminal Services connection, then you may also need to set the registry key HKLM/Software/Pervasive Software/Utilities Interface/Settings/Restricted Access on WTS Client to 0 (unrestricted access), or this may not work correctly. Start the ODBC Administrator from the Windows Control Panel. In newer versions of Windows, this may be located in different locations, such as under Administrative Tools.
    [Show full text]
  • Pervasive PSQL Vx Server Licensing
    Pervasive PSQL Vx Server Licensing Overview The Pervasive PSQL Vx Server edition is designed for highly virtualized environments with support for enterprise hypervisor features including live application migration (moving a virtual machine from one physical server to another while the application remains running), high availability and fault tolerance. As with other Pervasive PSQL products, it is licensed one instance per server (virtual or physical). Where Pervasive PSQL Vx is significantly different from other Pervasive PSQL products is that PSQL Vx licenses are priced by capacity, or how much work can be performed by the database engine. Capacity is measured by two factors: concurrent sessions (connections to the transactional or relational engine) and data in use (total size of the files opened by the database). Pervasive PSQL Vx Server is available in basic configurations – Small, Medium, Large and SuperSize. Session count and data in use limit increases are both available to allow customers to fine tune database capacity. And, unique to Pervasive PSQL Vx Server, time‐limited 60‐day session count and data in use are available to provide an affordable way for customers to meet peak database demand requirements. What’s New in Licensing for Pervasive PSQL Vx Server Pervasive PSQL Vx Server licensing features were designed with two major goals in mind: 1) ensure that PSQL Vx Server authorization and validation processes enable customers to take advantage of enterprise hypervisor features and 2) offer a licensing model relevant to customers delivering applications in public, private or hybrid cloud environments. The following table highlights some of the differences between Pervasive PSQL Vx Server and Pervasive PSQL Server.
    [Show full text]
  • Product Evaluator's Guide
    INTEGRATION Product Evaluator’s Guide Pervasive Data Integration Platform Release 8.14 July 2007 TABLE OF CONTENTS PURPOSE OF THIS GUIDE ......................................... 4 A COMPREHENSIVE DATA INTEGRATION PLATFORM ........................ 4 ADAptERS – DATA AND AppLICATIONS ................................ 6 PERVASIVE DATA INTEGRATION AND SOLUTION DELIVERY MODES .............. 7 IT AND ENteRPRISE APPLICAtiON DEVELOPMENT ..................................... 7 EMBEDDED DATA INteGRAtiON FOR ON-PREMISE APPLICAtiONS OR SAAS SOLUtiONS ............ 7 SERVICES DELIVERED BY SYSteMS INteGRATORS AND SOLUtiON PROVIDERS .................. 8 PERVASIVE DATA INTEGRATION PLATFORM – PRODUctS .................... 9 PERVASIVE DATA INTEGRATOR ...................................... 9 SCALABLE ETL AND REAL-TIME DATA INteGRAtiON . 9 APPLICAtiON INteGRAtiON .................................................. 10 INteGRAtiNG B2B GAteWAYS ................................................ 11 EXteNDING THE ENteRPRISE SERVICES BUS (ESB).................................. 11 PERVASIVE DATA PROFILER ...................................... 12 PERVASIVE DATA INTEGRATION PLATFORM ............................. 13 DESIGN TOOLS OVERVieW .................................................. 14 PROCESS DESIGNER ............................................................ 14 PROCESS DESIGNER – MESSAGE COmpONENT FRAMEWORK .................................. 14 MAP DESIGNER ............................................................... 15 OTHER PERVASIVE DESIGN TOOLS ............................................
    [Show full text]
  • Determining Your Pervasive, Actian, PSQL Or Btrieve Engine Version
    Determining Your PSQL Engine Version A White Paper From For more information, see our web site at http://www.goldstarsoftware.com Determining Your PSQL Engine Version Last Updated: 12/18/2018 It is very common for people to know that they are using the Btrieve or Pervasive PSQL, or Actian Zen database engine, but to not know exactly which version they are using. Moreover, the list of related files is often a mystery, especially for older versions, and some users are simply without a clue as to what modules are part of the database and what are not. This paper was created so that someone could locate the PSQL-related files on their workstation or server and determine the exact version, including user count, where appropriate. NetWare Server Engines With NetWare servers, it is possible to have any version of Btrieve from 5.x all the way through Pervasive PSQL v9. Many users see the version reported from BREQUEST and assume that this is their Btrieve version -- it just isn't so! You must query the server to determine exactly which version of BTRIEVE.NLM you have. On older versions of NetWare, you can do this with the "MODULES" command, which lists all the loaded modules on the server. Then, watch for the BTRIEVE.NLM to scroll by. For NetWare 4.11 and above, you can use the command "MODULES BTR*" to list only those modules that start with "BTR", which will save some searching. With the release of Pervasive.SQL 7, Pervasive Software started including the SQL engine "in the box" with the Btrieve engine.
    [Show full text]
  • Pervasive PSQL Summit V10 Highlights Performance and Analytics
    Pervasive PSQL Summit v10 Highlights Performance and analytics A Monash Information Services Bulletin by Curt A. Monash, PhD. September, 2007 Sponsored by: Pervasive PSQL Version 10 Highlights Page 2 Introduction PSQL v10 features In September, 2007, Pervasive Software is releasing Pervasive PSQL performance gains Summit v10. As befits a major product release, v10 boasts a broad variety of and new analytic enhancements and new features, especially in the areas of performance and functionality. query-related functionality.* Most important, Pervasive is tapping into two major industry trends: 1. More -- and more affordable -- RAM. 2. The growing importance of analytic (as opposed to purely transactional) technology. *There also are important steps in standards compatibility, specifically with several layers of Microsoft operating software, especially Microsoft Vista. But those aren't covered in this paper; please contact Pervasive directly or go to www.pervasive.com for details. XIO accelerates Major releases of a database management system typically boast multiple performance. performance improvements, and PSQL v10 is no exception. Most important are those delivered through a driver called XIO, for “(e)Xtreme I/O.” XIO contains a number of features, but the core idea is this. If you compress data intelligently, you get two big benefits: Less data has to flow from disk, so the system has to do less I/O (this is more relevant to analytics than to transaction processing). More data fits into cache, so the system often doesn't have to do any I/O at all (this is relevant to all kinds of processing). The DDF Builder As well as boosting performance, PSQL boasts significant improvements in eases business relational functionality.
    [Show full text]
  • Btrieve Error Codes 3000 - 3099 ← Pervasive PSQL Microkernel Router Status Codes
    Btrieve Error Codes 3000 - 3099 ← Pervasive PSQL MicroKernel Router Status Codes This section lists the status codes you can receive from the MicroKernel router, which receives requests from the Btrieve requesters and routes them to the correct version of the MicroKernel. 3000: The MicroKernel router encountered a memory allocation error The MicroKernel router could not internally allocate memory. Check the Pervasive Event Log (PVSW.LOG) for more information. 3001: Local access is unavailable to the MicroKernel router A call to the MicroKernel failed. This is most likely the result of an incorrect configuration. For example, if the MicroKernel is unavailable because of configuration settings and the file to be opened is local, then the MicroKernel router returns this status code. 3002: The MicroKernel router resource DLL is unavailable The MicroKernel resource DLL is either missing or incompatible with the current version of the router. If this happens, the MicroKernel reverts to its default settings and continues to run. Check the Pervasive Event Log (PVSW.LOG) for more information. 3003: The MicroKernel router detected an incompatible network component The networking services component is not compatible with this version of the MicroKernel router. The most likely cause is that the Networking services DLL has been replaced by an older version. Check the Pervasive Event Log (PVSW.LOG) for more information. 3004: The MicroKernel is not responding to the MicroKernel router The MicroKernel is not responding to requests from the MicroKernel router. Verify that the MicroKernel is running. 3005: The MicroKernel router encountered an operating system error The MicroKernel router encountered an unexpected error from the operating system, such as a shared memory failure.
    [Show full text]
  • 9 Reasons to Buy Pervasive PSQL V9
    Product Platforms Highlights Pervasive.SQL Windows, Linux, NetWare Power, Embeddability, Low TCO, Security 9 Reasons to Buy Pervasive PSQL v9 With the release of Pervasive PSQL v9, we have made a number of improve- STRENGTHS: ments to the previous release. With specific improvements to performance, Performance scalability, management, and international capabilities, Pervasive PSQL v9 Embeddability continues to raise the bar for embedded database applications. Low TCO Security Flexibility Improved Performance and Reporting: Easier Development and Management Extensive Standard Support 30 New Performance Optimizations of Applications: Brand New GUI Full Suite Of GUI Utilities Pervasive PSQL v9 includes over 30 separate optimiza- All new Pervasive.SQL Control Center (PCC) has tions that improve performance over previous versions. been rewritten in Java on the Eclipse framework. PCC These optimizations impact all of the SQL interfaces will provide a foundation for all future GUI tools, mean- (ADO.net, JDBC, ODBC, and OLE DB), and the improve- ing that the development and maintenance GUI will be SUPPORTED PLATFORMS: ments result in faster standard and ad-hoc reporting. shared across Pervasive PSQL platforms. • Aggregate queries (those containing GROUP BY • SQL Outline View – provides developers a way to Server clauses) view, dissect, and understand large queries (new • Windows NT 4.0 (SP6a or higher) • Windows 2000/2003 • Sub queries using IN, NOT IN, or =ANY predicates feature) • NetWare 5.1, 6, 6.5 or higher • Sub queries containing expressions
    [Show full text]