Pervasive Integration Architecture

A Products White Paper

September 2005
Pervasive Software
2 Pervasive Integration Architecture
Table of Contents
Introduction 3
Style and Source 4
Deployment Styles 4
Connectivity Sources 6
Pervasive Integration Architecture 8
Design 9
Integration Architect 9
Process Designer 10
Map Designer 11
Expression Builder 12
Structured Schema Designer 13
Document Schema Designer 14
Extract Schema Designer 15
Data Proler 16
Deploy 17
Integration Services & Engines 17
Integration Engines 18
Integration Manager 18
Manage 19
Repository 20
Repository Manager 21
Integration Manager 22
Industry-Specic Solutions 23
3 Pervasive Integration Architecture
Introduction
This white paper provides a comprehensive overview of the Pervasive Integration product line
architecture. Users of the Pervasive Data Integrator and Pervasive Business Integrator products
will benet from understanding the design-time and run-time aspects of the technology.
Integration is broadly dened as the act of bringing data and information together and sharing it
between repositories, applications, business processes, and organizations. The broad Pervasive
toolset helps developers and business users bring together highly varied and often hard-to-
reach data sources, vital applications, and business processes. Successful integration allows a
companys entire organization to be brought into a cohesive, responsive infrastructure for making
better decisions, driving the organization toward new business opportunities, and adapting to
change in the marketplace.
Pervasive integration products are built upon a common integration architecture that enables
ETL, EII, EAI and SOA deployment models. This common architecture brings together the best
in productivity tools for maximizing developer efciency, project scalability, and ease of project
management with open repositories to house large-scale, organic integration designs. Powerful,
low-TCO Pervasive integration engines also enable wide-scale corporate deployments.
Pervasive provides a platform for integration products that drives down the cost of development,
which is the most expensive cost contained in any integration project. Custom coding and
development is frequently employed to tackle the wide variety of situations that an integration
team encounters during the course of an integration project. As a result of these additional,
custom needs, integration projects frequently start small, but grow more quickly than initially
expected.
Integration teams face many critical issues during integration projects. Issues include determining
how to access all the critical data stored in obscure systems needed to fuel a mission-critical
decision process; how to bring together partners in the supply or demand chains that employ
widely disparate systems and business processes; how to integrate technology the applications
living in the infrastructure to the human business processes, and then quickly adapt when
factors change inside and outside the organization; and how to comply with industry standards
such as ACORD, HIPPA, EDI, HL7, SWIFT, etc.
Not surprisingly, these are the same challenges that result in higher development costs, when
more and more highly-skilled developers are thrown at integration projects to handle connectivity
issues, refactoring custom code as situations change, and chasing down ever-changing
standards requirements.
4 Pervasive Integration Architecture
Style and Source
Integration projects are often dened by two parameters: deployment style and data
sources. For integration projects to be successful, the selected integration tool must
support both parameters fully.
Deployment Styles
The starting point for any integration project is analyzing the business requirements to
identify the primary type of integration required. Pervasive Integration Solutions support
the three primary integration use cases: Data Level (ETL and EII), Fine-Grained (EAI), and
Coarse-Grained (SOA/ESB) integration models.
Data Level Integration
Data Level Integration represents the ability to tie together database or data le sources
with targets by manipulating data one or more records at a time. In order to feed data
warehouses and business intelligence applications, this capability is the foundation upon
which to build batch-oriented Extract Transform and Load (ETL) projects. In this model, the
project team collects data from a wide range of sources around the company, rationalizes
and cleans that data into a common format and structure, and then loads it into a repository.
Project Time Line
Migration Data Records
New
Acctg
Old
Acctg
Optional Cleansing
Data Records
Data
Collection
Framework
ETL (Extract,
Transform & Load)
Reporting
Tools
Custom
File Output
Portal
Data
Warehouse
(BI Tools)
Mainframe
VSAM
Data
Base
COBAL
Flat File
Data Level Example 1 Migrations
Data Level Example 2 ETL/Data Warehousing
5 Pervasive Integration Architecture
Fine-Grained Integration
Fine-Grained Integration is the model that much of the world uses for many Enterprise
Application Integration (EAI) projects, wherein two applications are tied together through
their native Application Programming Interfaces (APIs). Pervasive supports this model with
the deployment and design tools available today, by leveraging connectors to many current
interfaces such as BAPIs from SAP, and through custom scripting within the Process and
Map design tools.
Coarse-Grained Integration
The Service Oriented Architecture (SOA) and Enterprise Service Bus (ESB) movement
toward loosely coupled systems interacting via dened messages is a response to the
ne-grained models inherent limitation of 1:1 connections. The rigidity of ne-grained
connections is acceptable for point-to-point integration but becomes brittle for more complex
projects for two reasons: 1) the link between applications must be maintained as APIs
change over time and 2) the link does not scale beyond a 1:1 relationship between the
applications.
Many companies seek to tie their applications and organizations together with a
message-based approach to integration. In this model, also called Coarse-Grained
Integration, messages containing data from a variety of sources are passed between
two or more applications, and the data in a message is used or otherwise updated by
the applications as part of a larger business process. This approach typically relies on
a backbone such as SonicMQ or MQSeries for sharing messages between the various
points of integration. The Pervasive architecture (shown as blue circles on the diagram
below) supports all of these scenarios with rich connectivity to many available messaging
environments and to alternative queues like email or FTP servers, where a mail
message or a le represents the message for Coarse-Grained Integration. This type of
integration is then viable across a wide range of infrastructure models at a low total cost
of ownership, since all the connectivity and intelligence for designing Coarse-Grained
Integration is already available in the product.
Data sent through APIs
Point to Point API Integration
New
Acctg
Old
Acctg
Fine-Grained Integration Example Point-to-point application integration
6 Pervasive Integration Architecture
Connectivity Sources
Connectivity is the core of any integration project. The Pervasive Integration Engines include
more than 200 factory-supplied connectors that provide deep connectivity right out-of-
the-box. Connectivity components can be accessed during both design tasks (eg. reading
metadata for a database) and runtime tasks (eg. loading transformed data into a database).
While generic connectivity is supported for formats such as ODBC and ASCII delimited
at le, nearly all of the integration connections from Pervasive have been written to take
advantage of native APIs. This feature increases performance and increases functionality
options in a design by taking advantage of the native hooks a database vendor offers. Many
of the connectors are cross-platform and support a range of modes, including client/server
access, local database access, multimode where a single data stream can be rapidly spread
across multiple tables in a target database, and even mass-insert for high-speed bulk
loading of data.
Combine this rich native connectivity with the Integration Architect tools for accessing data
in non-traditional, unstructured formats (Extract Schema Designer, Structured Schema
Designer see pages 13-15) and the Pervasive Integration solution can reach nearly any
data in your organizations infrastructure, including email, print reports, and print les.
Acctg
Supply
Chain
Demand
Chain
HR
ERP
EDI XML
CRM
Clearing
house
Adapter
for SOA
Adapter
for SOA
Adapter
for SOA
Adapter
for SOA
B2Bi
Hub
ESB/SOA
Web-Services
Orchestration
Coarse-Grained Integration Example Multi-point, message-based integration with adapters for SOA.
7 Pervasive Integration Architecture
File Adapters
Access
Access 97
Access 2000
Access XP
Alpha Four
ASCII (Delimited)
ASCII (Delimited) Join
ASCII (Fixed)
Clarion
Clipper
CLF Webserver
DataEase
DataFlex
DJ Log FileData
dBASE II, III (III+)
dBASE IV dBASE V (IDAPI)
DIF
Enable
Excel
Excel 2000
Excel XP
Folio Flat File
Foxbase
FoxPro
LDIF
Lotus 1-2-3
Lotus Notes
Lotus Notes 5
Lotus Notes Structured Txt
Lotus Works Mac ASCII Delimited
Magic PC
MAILERS+4 (dBASE)
Microsoft Word (Mail Merge)
Paradox v5 (IDAPI)
Quattro Pro Windows v5
Rich Text Format (RTF)
Unicode (Delimited)
Unicode (Fixed)
WordPerfect 6.0 (Mail Merge)
Wordstar (Mail Merge)
WordPerfect 4.2/5.0
Visual FoxPro
Visual dBASE 5.5
Database Adapters
Oracle 7.x
Oracle 8.x
Oracle 8.x Mul mode
Oracle 9i
Oracle 9i Mul mode
Oracle 10g
Oracle Direct Path
Oracle SQL Loader
Access
Access 97
Access 2000
Access XP
Alpha Four
ASCII (Delimited)
ASCII (Delimited) Join
ASCII (Fixed)
Clarion
Clipper
CLF Webserver
DataEase
DataFlex
DJ Log FileData
dBASE II, III (III+)
dBASE IV
dBASE V (IDAPI)
DIF
Enable
Excel
Excel 2000
Excel XP
Folio Flat File
Foxbase
FoxPro
LDIF
Lotus 1-2-3
Lotus Notes
Lotus Notes 5
Lotus Notes Structured Txt
Lotus Works
Mac ASCII Delimited
Magic PC
MAILERS+4 (dBASE)
Microsoft Word (Mail Merge)
Paradox up to v5 (IDAPI)
Quattro Pro Windows v5
Rich Text Format (RTF)
Unicode (Delimited)
Unicode (Fixed)
WordPerfect 6.0 (Mail Merge)
Wordstar (Mail Merge)
WordPerfect 4.2/5.0
Visual FoxPro
Visual dBASE 5.5
Database Adapters
Oracle 7.x
Oracle 8.x
Oracle 8.x Mul mode
Oracle 9i
Oracle 9i Mul mode
Oracle 10g
Oracle Direct Path
Oracle SQL Loader
Pervasive.SQL
Pervasive.SQL v8
Pervasive.SQL v8 Mul mode
PostgreSQL
PostgreSQL (ODBC 3.x)
Btrieve v5
Btrieve v6
Btrieve v7
Btrieve v8
CA dB-Fast
C-ISAM
Cloudscape
CWM
DB2 7.2 Univ. DB
DB2 7.2 Univ. DB Mul mode
DB2 Loader
DB2 UDB Mass Insert
DB2 (ODBC)
DB2 UDB
DB2 UDB Mul mode
eXcelon
eXcelon XIS 3.0
Hitachi Hi-RDB
IDAPI
Informix DB Loader
Informix (ODBC)
Informix DB Loader
Informix (ODBC)
Informix Online DS
Informix/SE Ingres (ODBC 3.x)
Interbase (IDAPI)
MUMPS (ODBC)
MySQL
NonStop SQL/MX
ODBC 3.x
ODBC 3.x Mass Insert
ODBC 3.x Mul mode
ODBC 3.5
ODBC 3.5 Mul mode
RBase 4.5 (ODBC)
Red Brick
Scalable SQL
SQLBase
Sybase 11.x
Sybase 11.x Mass Insert
Sybase 11.x Multimode
Sybase 12.x
Sybase 12.x Mass Insert
Sybase 12.x Multimode
Sybase BCP
Sybase (ODBC)
Sybase SQL Anywhere
Sybase SQL Anywhere 6
Sybase SQL Mass Insert
Sybase SQL 11
Sybase SQL 11 Mul mode
SQL Script
SQL Server 6.x
SQL Server 7 Mass Insert
SQL Server 7 (OLEDB) Multimode
SQL Server 7 (OLEDB)
SQL Server 2000
SQL Server 2000 Mass Insert
SQL Server 2000 Multimode
SQL Server BCP
SQL Server Mass Insert
SQL Server (ODBC)
Teradata (Fastload)
Velocis (ODBC 3.x)
Watcom SQL v5
Watcom SQL (ODBC)
Application Adapters
Application Adapters
AccountMate
ACT! for Windows
Champion Acct.
CYMA Acct.
GoldMine
Great Plains DOS
Great Plains UNIX/Mac
Navision Financials
Macola Acct.
Microsoft IIS ELF
PayChex DJF
Peachtree Acct.
Platinum Acct.
RealWorld Acct.
Remedy ARS
Sales Ally
Salesforce.com
SAP (BAPI, RFC, IDoc)
SAS
SBT Acct.
Solomon Acct.
SPLUS Statistica
SYSTAT
Apache CLF
Market Force
Personal Librarian
SPSS
USMARC
Technology Adapters
BizTalk XML
Erwin
FF Queue
FTP
HTTP
HTML
JMS
LDAP
MSMQ (Extractor)
MSMQ (Fixed ASCII)
MSMQ (XML)
MQSeries (Extractor)
MQSeries (Fixed ASCII)
MQSeries (XML)
SGML TCP/IP
URL
URI
XML
XML Schema
XML DTD
XML XDR
Legacy Adapters
Acucobol (ODBC 3.x)
BAF
Binary
Binary Line
Sequential
COBOL Copybook
COBOL Flat File
C-tree Plus
C-tree 4.3
Fujitsu COBOL
ISAM
Micro Focus COBOL
Microsoft COBOL
QSAM
Sequential Binary
Tape Drive Sequential
VSAM
Variable Sequential (MVS)
Variable Sequential (Record-V
UniKix)
Variable Sequential (SyncSort)
Variable Sequential (User Defined)
B2B Adapters
EDI (EDIFACT)
EDI (X12)
HCFA1500-NSF
HIPAA
HL7
Text (Delimited - EDI)
Text (Delimited - EDIFACT)
Text (Delimited - EDI)
TRADACOMS
UB92-NSF
A sampling of connectors
8 Pervasive Integration Architecture
Pervasive Integration Architecture
The Pervasive integration architecture comprises a unied set of design time and runtime
tools that satisfy all three deployment styles mentioned. The integration architecture can be
separated into three distinct phases: design, deploy, and manage.
The design components boost developer efciency, which is often the largest cost in an
integration project.
Integration Architect The Pervasive Integrated Development Environment (IDE) is a
bundle of components that supplies developers with the tools required to design effective
multi-step integration processes. Access and data transformations across hundreds of
data sources and targets, as well as a highly differentiated set of schema design tools,
are included to help access even the most remote and obscure data types in a typical
data infrastructure.
Data Proler A powerful tool to analyze batch data that provides developers with
information about the structure, shape, and quality of data to be integrated, enabling
those developers to more efciently transform and cleanse data into the desired formats.
The runtime components enable centralized or distributed deployments inside and across
enterprises.
Integration Engine The workhorse of the Integration product line, this engine provides
the processing power to execute integration process and data mappings created by
developers with the Integration Architect. These engines can be run locally for quick
access to view data and test designs and can then be distributed into the production
infrastructure to run designs in the corporate environment.
Integration Manager This component provides a single point of administration and
control for managing distributed Integration Engines. Through a user-friendly, browser-
based interface, Integration Manager performs deployment, scheduling, ongoing
monitoring, and real-time reporting on individual or groups of distributed Integration
Engines.
The management components tie the design time and runtime components together.
Integration Repository The repository is an open, XML-based design le storage facility
that developers can use to track and store work across multiple projects. The XML-
formatted documents represent everything from schema designs and data transforms to
business process models.
9 Pervasive Integration Architecture
Design
Integration Architect
Pervasive Integration Architect is a comprehensive integrated development environment
(IDE) for distributed integration solutions. Integration Architect comprises a suite of tools and
designers, described below, for connectivity to a wide range of sources and targets: Process
Designer, Map Designer, Data Proler, Structured Schema Designer, Document Schema
Designer, Extract Schema Designer, Repository Explorer, Repository Manager, and the
Universal Data Browser.
The benets of the comprehensive design environment in the Pervasive Integration
Architect:
A single IDE reduces training costs and increases overall productivity.
Increased reuse of processes through import/export repository sharing reduces
development costs.
Wide variety of connectivity to hundreds of types of data sources and targets helps
reduce custom code requirements and enables integration to reach into a wide range of
previously disparate systems.
The Integration Architect toolset is designed to help reduce overall development labor for
creating and maintaining integration across the enterprise.
Integration Architect tools are designed for maximum code reuse across projects.
Integration processes can be distributed to remote engines and applications to increase
exibility.
10 Pervasive Integration Architecture
Process Designer
Process Designer has an intuitive interface available for drag-and-drop integration process
design. Using simple owchart symbols, Process Designer links multi-step integration
processes together in a single, automated integration task. Key uses range from simple
integration ows, to multi-step business process control, to parallel processing of large data
loads, even to integration orchestration across message queues.
Easy-to-use tree style navigation for managing and opening all process objects
Message Connector Steps with queue session management
HTTP, FTP, TCP transport support
Validation Step
Export object connection Wizard
Execution of XSLT scripts as a process step
Visual SQL query builder
Macro denition support
Wizards for InCore memory and Dynamic SQL lookups
Process Designer aligns integration projects with business processes
11 Pervasive Integration Architecture
Map Designer
Map Designer is a powerful data mapping and transformation designer, which provides
a visually appealing user interface and Wizards for increased simplicity. The XML-based
capabilities that dene the integration process enable substantially more re-use by
separating Map objects, such as sources and targets, into discrete objects, promoting
greatly enhanced reusability in medium to large-scale production environments.
Visually control data ow within any transformation regardless of complexity.
Dene rules for mapping complex hierarchical structures such as EDI and XML data.
Debug transformations on the y.
Innovative, event-based data transform metaphor.
Map Designers tools put the power of transformation at a developers ngertips
12 Pervasive Integration Architecture
Expression Builder
Expression Builders are used throughout the design environment to assist the integration
developer in building integration designs. Expression Builders use a rich scripting language
called Real-time Integration Flow Language (RIFL), designed to promote developer
efciency on many common tasks encountered during integration projects. The RIFL
language includes hundreds of pre-built functions to automate developer tasks, including
activities such as automatic conversion of different date formats to Boolean logic for creating
smart decision points in a transformation or integration process and math functions that
provide useful information about the execution statistics of any particular integration process.
The RIFL language has similar structure to Visual Basic, making it easy to learn and a
quick path to productivity. Even non-programmers can quickly learn how to execute simple
integration tasks. This powerful, modular, reusable coding environment does not require
customer exits from the development environment to reach external custom code,
supporting better code reusability, project management, and debugging for any unexpected
problems that occur.
The Expression Builder pre-congures functions onto to the main expression-editing
window complete with expected parameters. Data elements, including source elds, target
elds, and global variables, are all available through this interface. Events/Actions such
as AfterRecord reads, BeforeTransformation, and OnError provide critical processing
ow control points where additional logic can be built and incorporated for performance
optimization, error trapping, etc.
The GUI-based Expression Builder is used to quickly build Real-Time Integration Flow Language (RIFL) scripts
13 Pervasive Integration Architecture
Structured Schema Designer
The Structured Schema Designer provides a visual interface for creating, saving, and
manipulating denition les (metadata) of structured data sources. The resulting metadata is
stored as XML-based Structured Schema les that include schema, record recognition rules,
and record validation rule information. With the Structured Schema Designer you can arrange
eld order, assign eld names and type, and specify data size.
Visually dene and adjust all record and eld properties.
Parse binary data record structures and dene eld length, data type, offsets, etc.
Create an external metadata denition from any data format.
14 Pervasive Integration Architecture
Document Schema Designer
The Document Schema Designer gives you an easy-to-use graphical display for the
denition of trading standards (or subsets), so you can edit or create new Document
Schemas (the metadata for document-oriented data such as EDI and XML). The Schema
Designers offer many benets as follows:
Signicantly reduces time and effort to dene and modify complex hierarchical document
structures.
Allows the creation of document structures from all master schema standards, including
EDI, EDIFACT, SWIFT, FIXML, TRADACOMS, HIPAA, HCFA 1500, UB92, HL7, Idocs,
etc.
Enables users to visually select specic segments and elements, then adjust all
properties, references, and code tables to dene the precise document structure needed
for a trading partner.
Generates a validation rules le for ensuring that future messages received in this format
include complete data, to prevent data quality problems and miscommunication with
partners.
Document Schema Designer provides the exible structure to visually interpret and manipulate standard and proprietary message formats
15 Pervasive Integration Architecture
Extract Schema Designer
The Extract Schema Designer is used for integrating unstructured text data into business
processes. Exclusive to Integration Architect, the Extract Schema Designer is the only
alternative to manual coding scripts for integrating data sources such as email, report data,
HTML, print data, or any other raw text.
Incorporate valuable data such as email or Internet content into the data warehouse for
improved business decision-making.
Easy-to-use visual design interface allows business users to create extraction processes
eliminating expense and reliance on skilled IT staff and outside consultants to
manually write coded routines.
Self-documenting visual designer ensures that extraction processes are maintainable
and adjustable by anyone.

16 Pervasive Integration Architecture
Data Proler
Pervasive Data Proler is a rich data analysis tool that provides integration developers with
a proven method by which to measure data quality before loading, preventing disruptive
problems in the future. Pervasive Data Proler can also assess/prole existing databases to
provide objective and actionable results.
This tool accurately and efciently analyzes each data set, automatically generates detailed
reports on the quality of the data, and delivers summary charts backed by drill-down
analysis, including percentages of success rate and frequency counts. Standard metrics
include data-type compliance testing, conversion testing, and statistics collection. Input
records can also be segregated into clean and dirty les, allowing developers to focus
on failed records, or even include identied problems in downstream data remediation
process ows.
17 Pervasive Integration Architecture
Deploy
Integration Services & Engines
Pervasive integration products can be deployed in a variety of ways depending on customer
requirements (see diagram below) from a single, lightweight embedded engine to a
distributed, fully managed set of Service Oriented Architecture (SOA) adapters.
When deploying in SOA environments there are several communication mechanisms that
work in conjunction with J2EE application servers. Collectively, the capabilities below are
called the Integration Services SDK.
A purpose-built Message Driven Bean (MDB) that is congured to listen on a JMS queue
for the input message, then invoke a specic integration specication via the Integration
Server. The Integration Server, in turn, will nd an available Integration Engine on the
local server and invoke the desired integration specication and return the results.
A JCA RA for synchronous invocation of integration specs via the Integration Server
(as above).
A Java API for synchronous invocation of integration specs via the Integration Server
(as above).
An HTTP WS-I compliant services interface to the Integration Server to accept SOAP
invocations from any application (not only J2EE).
18 Pervasive Integration Architecture
At runtime, the Integration Services SDK provides a communications broker called the
Integration Server, that manages a pool of one or more local Integration Engines.
Integration Engines
The Integration Engine is the workhorse of the integration product line. The Integration
Engine can handle projects varying widely in complexity, from extract, transform, and load
(ETL) projects to B2B integration (e.g. HIPAA, HL7, ACORD, X12 and SOA adapters).
Furthermore, the Integration Engine is easy to embed with rich SDKs and with command
line interfaces for pinpoint control by external applications. The Pervasive engine can be
congured to meet the scalability requirements any integration project.
Integration Engines are currently available on the following platforms:
Windows
Linux
HP-UX
Sun Solaris
AIX
OS/390; z/OS
T1
DBMS
Load
File
T4
T2
T3
Database Connectors (SQL, ODBC 2.x, 3.x, IDAPU, Pervasive SQL, etc.)
File Format Connectors (ASCII, Binary, Unicode, XML, etc.)
Native API Connectors (COBOL, iSAMs, etc.)
DBMS Bulk Load Connectors
I
N
T
E
R
F
A
C
E
SOAP
INVOCATION
JAVA
JCA
MDB
B
U
S
I
N
E
S
S

R
U
L
E
S
I
N
T
E
G
R
A
T
I
O
N

E
N
G
I
N
E
S
I
N
T
E
G
R
A
T
I
O
N

S
E
R
V
E
R
I
N
T
E
G
R
A
T
I
O
N

M
A
N
A
G
E
R
(
M
a
n
a
g
e
s

M
a
n
y

E
n
g
i
n
e
s
)
APPLICATION
LAYER
J2EE
APPLICATION
SERVERS
DATA
LAYER
Invoker
B
U
S
Native Connector (e.g. SAP BAPI)
(API - Methods/Calls)
FINE-GRAINED
Tightly Coupled
Synchronous
(Message/Documents)
COURSE-GRAINED
Loosely Coupled
Asynchronous
(Message/Documents)
COURSE-GRAINED
Loosely-Coupled
Asynchronous
XML
XML In
Synchronous
Synchronous
http SOAP
Input Message
Output Message
Return Message
XML out
Get Msg
Put Msg
Connector
Data
Connector
Message
Connector
Pervasive Integration Engine Deployment Options
19 Pervasive Integration Architecture
Integration Manager
The Integration Manager is a browser-based console that allows many distributed
Integration Engines to be managed centrally or from remote locations (e.g. via VPN
connections). At deployment time, the Integration Manager is used to deploy integration
specications (packaged as DJARs in Pervasive terminology) to remote Integration
Engines via the remote management services provided by the Integration Server. Integration
Engines do not communicate directly to the Integration Manager, but rather rely on a local
Integration Server to behave as the information broker.
Manage
The Pervasive architecture provides an open XML repository for housing all specications
and rules that dene the execution and ow of integration tasks. Storing integration rules as
non-proprietary, XML provides enhanced exibility and allows integration project designs to
be easily manipulated as integration needs change and develop in each organization.
The repository itself is an open system of XML les for storing the various components
that comprise an integration design. For easy housekeeping of large or numerous projects,
designs can be arranged into workspaces that can be further grouped by user or by
project names.
20 Pervasive Integration Architecture
Repository
Designs are divided into distinct, reusable components that exist independent of one another
and are saved as individual XML les. By increasing the availability of reusable integration
rules, costs associated with development time are often greatly reduced since individual
components can be shared between users and integration tasks. This reuse theme greatly
increases the efciency of new project implementations and lowers development costs
associated with projects.
dennis.hall@pervasive.com
<mailto:dennis.hall@pervasive.com>
12365-B Riata Trace Parkway
ENGINES
Design Tools & Languages
S
c
h
e
m
a

D
e
s
i
g
n
e
r
s
Extract
Schema Designer
Extract Schemas/.CXL
3rd Party Designers,
UIs, Programs,
Web Services
Import/Upgrade
from Legacy IDE
Metadata Exchange
XML,XMI, XIF, CWMI, etc. sc.xml & tc.xml
map.xml
tf.xml
.rifl
.rifl
ip.xml
Structured
Schema Designer
Map Designer
Process Designer
ds.xml
dsc.xml
dsr.xml
Extract
Schema Designer
(EDI, HIPAA, SWIFT, etc.)
O
p
e
n

M
e
t
a
d
a
t
a

A
c
c
e
s
s

&

M
a
n
a
g
e
m
e
n
t
Open Metadata Repository Metadata Interfaces
Visual Parser
JAVA, VB, C++, PERL
ss.xml
dp.xml
dp.stats.xml
data profiler
The Pervasive Open XML Metadata Repository
The Repository and XML-based specications offer:
Easy administration of project designs and workspaces for one developer or across
project groups.
Improved code reuse features enhance developer efciency and project scalability.
All designs may be additionally altered or even generated through any XML-compliant
development environment.
Designs are portable to be run on six different Integration Engine platforms.
XML-based specications are both human and machine-readable.
The Repository can be embedded, enabling ISVs to create, manipulate, and even
execute integration designs from within their applications.
The Integration Architect also includes the Repository Explorer as the front-end for a
development project, providing a consolidated view of design processes and managing
the repository contents created by the various design tools. The exploration and control
capabilities can be executed across multiple repositories, and a simple double click on any
design component opens the appropriate Integration Architect design tool.
21 Pervasive Integration Architecture
Repository Manager
The Repository Manager helps the developer and project manager get more out of their
Pervasive Integration development experience and coordinate across multi-developer
integration projects.
Dependency impact analysis tracks dependencies between design components and
offers insight into the impact of proposed changes within a projects work plan. Helps
avoid creating problems in one design component while working on another and offers
vital information to a manager when estimating time impact of project tasks.
Search and Replace any RIFL code or XML element across designs and projects.
Deployment packaging eases the process of collecting related designs into a secure
package for deployment of those designs to the appropriate production or test engines.
Reporting Offers reports on key indicators around designs: when created, last edited,
last executed, designs by author, etc. Provides managers with the information to
effectively manage projects.
22 Pervasive Integration Architecture
Integration Manager
Pervasive Integration Manager was discussed as a deployment tool however, it also
provides a single point of administration and monitoring for a set of deployed engines.
This capability improves operational efciency, especially with geographically distributed
integration engines.
Integration Manager supports the scheduling of integration jobs in a variety of ways,
including the ability to task different engines. The tool also supports managing engines,
including starting, stopping, and even conguring engines from a central console.
Additionally, it collects runtime statistics, and even has real-time reporting ability. In order to
increase the security of integration infrastructure, a powerful role-based authentication and
authorization mechanism is in place.
23 Pervasive Integration Architecture
Industry-Specic Solutions
Pervasive offers a wide range of standard message schemas to enhance application
integration projects. Whether the need is to connect to standards such as HIPAA, HL7,
HCFA, or UB92 in the Healthcare space, EDI, EDIFACT, TRADACOMS, and UCCnet
in Retail and Government sectors, or even SWIFT in the Financial Services market, the
Pervasive Integration products include pre-built schemas and messaging connectivity for
you to work with any of these standards right out of the box.
Pervasive also offers pre-built business process integration scenarios between SAP and
salesforce.com, automating order fulllment, invoice history and account synchronization.
FOR MORE INFORMATION
To learn more about Pervasive Software and our solutions, please visit www.pervasive.com.
To reach the North American sales ofce, call 1.800.287.4383, extension 2.
For Latin, Central and South America, Australia and New Zealand, call +1.512.231.6000.
In Europe, for Belgium, France, Germany, Italy, Luxembourg, The Netherlands, Spain, Sweden, Switzerland
and the United Kingdom, call +800.12.12.34.34.
For any other European, Middle Eastern, African or Asian countries (excluding Japan), call +32.70.23.37.61.
For Japan, please call +81.3.3293.5300, or visit www.pervasive.com.jp.