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 projects, populating decision support software allows users to quickly and easily share data systems, legacy data migrations, capturing on-line feeds between multiple 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, , 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 uses simple and data . 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 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 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 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 , 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 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 tasks that formerly could not be done, control systems for shared development projects. It or execute a repetitive task more efficiently than before. also enhances flexibility by allowing integration project Once MCF components have been created, they can be designs to be easily and directly manipulated by dropped into the appropriate directory and immediately other applications. This essentially provides another used within the Process Designer interface as if they were programmatic interface to alter the instructions that a standard part of the suite. control the behavior of the Integration Engine. MCF allows development of components to process a The metadata repository itself is an open system of variety of message objects with binary or string content. files for storing the various components that comprise The framework provides a uniform run-time environment an integration design. Designs are divided into distinct, for message handling and provides services during data reusable components that exist independently of one integration execution. It also manages the component life another and are saved as individual XML files. These files cycle and component actions. MCF simplifies the job of can be arranged into workspaces that can be further the component writer by eliminating certain component grouped by user or by project names. and message object management issues. The MCF Component Tool is an Eclipse platform tool that provides By increasing the availability of reusable integration simple wizards to create the skeleton code for the six rules, costs associated with development time are often types of MCF components. Components are useful to greatly reduced since individual components are sharable developers, systems integrators, ISVs, and solution between users and integration tasks. Reuse greatly providers as a quick method to create new reusable increases the efficiency with which new projects are services for data integration projects, or for any customer implemented and lowers development costs associated who needs additional functionality. with a project.

Design Tools OPEN METADATA REPOSITORY Metadata Interfaces Repository Explorer ip.xml Process spec Process Designer .rifl Data transformation and flow control spec map.xml Field mapping spec tf.xml Transformation spec Map Designer 3rd Party Designers, sc.xml Source spec UIs, Programs, Web Services tc.xml Target spec JAVA, VB, C++, PERL .cxl Unstructured text Extract Import/Upgrade Schema Designer Extraction schema from Competitors

ss.xml Structured schema MANAGEMENT & ACCESS Visual Parser Metadata Exchange

Structured ATA XML, XMI, XIF, CWMI, etc.

Schema Designer ds.xml Document schema AD dsc.xml Document schema codeset Document Schema Designers Schema Designer (EDI, HIPAA, SWIFT, etc.) dsl.xml Document segment library dfl.xml Document field library dcl.xml Document code library MET OPEN

1.800.287.4383 www.pervasive.com Integration Engine Interfaces

MCF and its Java API are used to build components of six basic types:

• Aggregator – Builds a complex message object from a collection of simpler message objects, such as assembling multiple transactions into a single batch HIPAA file. • Iterator – Iterates over a single message that contains smaller messages and breaks them into their component message objects, such as breaking a batch HL7 file into its component transactions. • Transformer – Transforms a message object into another type of message object, such as converting a flat ASCII NCPDP script file into an NCPDP XML file. • Validator – Validates a message object based on set criteria. • Invoker – Provides an adapter for external application interfaces, such as calling an email application to send mail. • Queue – Provides connectivity to a message channel, generally a message queue, such as MSMQ, Websphere MQ, Oracle AQ, JMS Queues, etc.

MESSAGE COMPONENT FRAMEWORK (MCF) Component Component Component Creation Types Implementation Example: Aggregator Eclipse MCF Wizard Validator

Queue

My HL7 Aggregator Skeleton Code Iterator

My HL7

Aggregator

Java Code completes functionality Invoker

My HL7 Aggregator Transformer 1. Mouse click drops component into workflow process. 2. Double-click icon, configuration dialog appears. 3. Select your new component from drop-down list. New component dropped in plug-in directory 4. Configure.

1.800.287.4383 www.pervasive.com 6 Adding New Connectivity – DMS follows the Service Data Objects (SDO) Data Mediation Services (DMS) specification. It enables simple create, retrieve, update, and delete (CRUD) operations, focusing on extracting Pervasive Data Mediation Services (DMS) is a technology and loading large sets of record-oriented data including for extending the connectivity of Pervasive integration relational, hierarchical, and multi-record types. It is products. DMS implementations are embedded in the well-suited to remote, disconnected, or asynchronous Pervasive Integration Engine making them usable in environments such as Web Services or SOA architectures. Pervasive Data Integrator™ and Pervasive Data Profiler™ to provide connectivity to a huge variety of applications The DMS SDK provides Java classes for data and data formats. Any new DMS connector will show up manipulation. It also offers a number of helper functions in the drop-down list in the Map Designer interface and to make it easy to generate or consume the SDO objects will have all the properties and metadata visible, as well used to handle data. Internally, Pervasive has used the as the data itself in the browsers, just like Pervasive’s own DMS technology to create its own connection adaptors connectors. ISVs, SaaS vendors, and system integrators for various applications. A sample connection adapter for can use the DMS SDK to build new connection adaptors JDBC Derby is provided with the SDK to help make the for specific application APIs that they wish to connect to implementation of this technology more transparent. using Pervasive integration software.

PERVASIVE DATA MEDIATION SERVICE (DMS)

Merchant ERP Services NetSuite, QuickBooks Payroll Intuit . . . OnDemand . . . Marketing Xactly, Centive . . . Eloqua . . .

CRM

.com, Siebel . . . SDO Compliant

DMS Application

Applications Create Read Update Delete

Legacy Data, Applications

Unstructured Data Message Flat Files Queues Databases

Each new DMS connector provides instant connectivity through Pervasive Data Integrator to a whole world of applications and data sources.

1.800.287.4383 www.pervasive.com Integration Engine Interfaces

Platform Portability

The Pervasive Integration Engine supports the following operating systems: Windows XP, Windows Server 2003, Windows Vista Enterprise, Business, and Ultimate, as well as Linux, Suse, RHEL, AIX, HPUX, and Solaris.

Pervasive Integration Engine Versatility

Data integration in heterogeneous environments provides both challenges and opportunities. Pervasive can get you past the hurdles to deliver market-winning results, time and time again. The Pervasive Integration Engine already has a proven history of success helping ISVs, BPOs, SaaS providers, and SIs grow their business opportunities, reduce TCO, and speed time to success. Service-driven, with an easy-to-use command line interface and client API to fuel dynamic distribution, the Pervasive Integration Engine is easily scalable. With a small footprint, support for multiple operating systems, and open XML metadata, it’s highly portable. It’s also fully extensible both in functionality through MCF and connectivity through DMS.

1.800.287.4383 www.pervasive.com Comprehensive Connectivity Pervasive connectors enable rapid access to heterogeneous data. A comprehensive set of 150+ connectors allows a broad range of seamless connectivity to file systems, databases, message buses, EDI networks, Web-enabled applications, business applications and industry-standard protocols on numerous platforms. Also included is Pervasive’s unique capability to process non-relational and semi-structured content buried in most companies.

Access Clarion dBASE IV Folio Flat File Lotus Works (Delimited) Access 97 Clipper dBASE V (IDAPI) Foxbase Mac ASCII Delimited Unicode (Fixed) Access 2000 CLF Webserver Dialog FoxPro Magic PC WordPerfect 6.0 (Mail Merge) Access XP DataEase DIF LDIF MAILERS+4 (dBASE) Wordstar (Mail Merge) Alpha Four DataFlex Enable Lotus 1-2-3 Microsoft Word (Mail Merge) WordPerfect 4.2/5.0 ASCII (Delimited) DJ Document Schemas Excel 95, 97 Lotus Notes Paradox v5 (IDAPI) Visual FoxPro ASCII (Delimited) Join DJ Log File Data Excel 2000 Lotus Notes 5 Quattro Pro Windows v5 Visual dBASE 5.5 ASCII (Fixed) dBASE II, III (III+) Excel XP Lotus Notes Structured Text Rich Text Format (RTF)

Oracle 7.x v5 eXcelon ODBC 3.x Mass Insert SQL Server 2000 Mass Insert Sybase (ODBC) Oracle 8.x Btrieve v6 eXcelon XIS 3.0 ODBC 3.x Multimode SQL Server 2000 Multimode Sybase SQL Anywhere Oracle 8.x Multimode Btrieve v7 Hitachi Hi-RDB ODBC 3.5 SQL Server 2005 Sybase SQL Anywhere 6 Oracle 9i Btrieve v8 IDAPI ODBC 3.5 Multimode SQL Server 2005 Mass Insert Sybase SQL Mass Insert Oracle 9i Multimode CA dB-Fast Informix DB Loader RBase 4.5 (ODBC) SQL Server 2005 Multimode Sybase SQL 11 Oracle 10g C-ISAM Informix (ODBC) Red Brick SQL Server BCP Sybase SQL 11 Multimode Oracle Direct Path Cloudscape Informix Online DS Scalable SQL SQL Server Mass Insert Teradata (Fastload) Oracle SQL Loader CWM Informix/SE SQLBase SQL Server (ODBC) Velocis (ODBC 3.x) Pervasive.SQL DB2 7.2 Univ. DB Ingres (ODBC 3.x) SQL Script Sybase 11.x Watcom SQL v5 Pervasive.SQL v8 DB2 7.2 Univ. DB Multimode Interbase(IDAPI) SQL Server 6.x Sybase 11.x Mass Insert Watcom SQL (ODBC) Pervasive.SQL v8 Multimode DB2 Loader JDBC SQL Server 7 Mass Insert Sybase 11.x Multimode Pervasive PSQL v9 DB2 UDB Mass Insert MUMPS (ODBC) SQL Server 7 (OLEDB) Sybase 12.x Pervasive PSQL v10 DB2 (ODBC) MySQL Multimode Sybase 12.x Mass Insert PostgreSQL DB2 Univ. DB NonStop SQL/MX SQL Server 7 (OLEDB) Sybase 12.x Multimode PostgreSQL (ODBC 3.x) DB2 Univ. DB Multimode ODBC 3.x SQL Server 2000 Sybase BCP

AccountMate Great Plains DOS Microsoft IIS ELF Personal Librarian Sales Ally SPLUS ACT! for Windows Great Plains UNIX/Mac NetSuite Pivotal CRM Salesforce SPSS ADABAS (NatQuery) Navision Financials Oracle Applications Platinum Acct. SAP IDoc Statistica Apache CLF Macola Acct. Oracle Siebel CRM RealWorld Acct. SAP BAPI SYSTAT Champion Acct. Market Force On Demand Remedy ARS SAS USMARC CYMA Acct. Microsoft Dynamics CRM PayChex DJF Sage CRM SalesLogix SBT Acct. GoldMine Microsoft Dynamics GP Peachtree Acct. Sage MAS 90/200 Solomon Acct.

BizTalk XML File Folder LDAP MQSeries (XML) TCP/IP XML DTD Email FTP MSMQ (Extractor) Oracle AQ URL XML XDR Email Attachments HTTP MSMQ (Fixed ASCII) Oracle BPEL URI Erwin HTTPS MSMQ (XML) Progress Sonic ESB WebSphere FF Queue HTML MQSeries (Extractor) SGML XML File Transfer Builder JMS MQSeries (Fixed ASCII) SOAP XML Schema

ACUCOBOL (ODBC 3.x) Binary Line Sequential C-tree Plus Micro Focus COBOL VSAM Variable Sequential ACUCOBOL-GT v7 COBOL 01 C-tree 4.3 QSAM Variable Sequential (MVS) (SyncSort) BAF COBOL Copybook Fujitsu COBOL Sequential Binary Variable Sequential Variable Sequential Binary COBOL Flat File ISAM Tape Drive Sequential (Record-V UniKix) (User Defined)

ACORD HCFA 1500-NSF HR-XML NSF Text (Delimited – EDIFACT) UB92-NSF EDI (EDIFACT) HIPAA MIB SWIFT Text (Delimited – HL7) EDI (X12) HL7 NCPDP Text (Delimited – EDI) TRADACOM

09 About Pervasive Software Pervasive Software provides agile data Contact Us integration software that speeds the flow www.pervasive.com of data between applications and between 1-800-287-4383 (North America) organizations. Our robust technology addresses 1-512-231-6000 (Main Office) SaaS, SOA and traditional integration modes and +32-70-23-37-61 (Europe) allows customers to re-use the same software for integration scenarios that span data warehouses, real-time application integration For other international contacts, please visit and data exchange with trading partners. www.pervasive.com/company/contact/index.asp PN0508B08

©2008 Pervasive Software Inc. All rights reserved. All Pervasive brand and product names are trademarks or registered trademarks of Pervasive Software Inc. in the United States and other countries. All other marks are the property of their respective owners.