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