Pervasive Integration Architecture

8/11/2019 Pervasive Integration Architecture

http://slidepdf.com/reader/full/pervasive-integration-architecture 1/23

Pervasive Integration Architecture

A Products White Paper

September 2005Pervasive Software



2 Pervasive Integration Architecture

Table of Contents

Introduction 3

Style and Source 4

Deployment Styles 4Connectivity 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 17Integration Services & Engines 17

Integration Engines 18

Integration Manager 18

Manage 19

Repository 20

Repository Manager 21

Integration Manager 22

Industry-Specic Solutions 23




IntroductionThis white paper provides a comprehensive overview of the Pervasive Integration product linearchitecture. Users of the Pervasive Data Integrator and Pervasive Business Integrator productswill 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 itbetween repositories, applications, business processes, and organizations. The broad Pervasivetoolset helps developers and business users bring together highly varied and often hard-to-reach data sources, vital applications, and business processes. Successful integration allows acompanyʼs entire organization to be brought into a cohesive, responsive infrastructure for makingbetter decisions, driving the organization toward new business opportunities, and adapting tochange in the marketplace.

Pervasive integration products are built upon a common integration architecture that enablesETL, 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 projectmanagement 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 anddevelopment is frequently employed to tackle the wide variety of situations that an integrationteam 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 initiallyexpected.

Integration teams face many critical issues during integration projects. Issues include determininghow to access all the critical data stored in obscure systems needed to fuel a mission-criticaldecision process; how to bring together partners in the supply or demand chains that employwidely disparate systems and business processes; how to integrate technology – the applicationsliving in the infrastructure – to the human business processes, and then quickly adapt whenfactors change inside and outside the organization; and how to comply with industry standardssuch as ACORD, HIPPA, EDI, HL7, SWIFT, etc.

Not surprisingly, these are the same challenges that result in higher development costs, whenmore and more highly-skilled developers are thrown at integration projects to handle connectivityissues, refactoring custom code as situations change, and chasing down ever-changingstandards requirements.




Style and SourceIntegration projects are often dened by two parameters: deployment style and datasources. For integration projects to be successful, the selected integration tool mustsupport both parameters fully.

Deployment StylesThe starting point for any integration project is analyzing the business requirements toidentify the primary type of integration required. Pervasive Integration Solutions supportthe three primary integration use cases: Data Level (ETL and EII), Fine-Grained (EAI), andCoarse-Grained (SOA/ESB) integration models.

Data Level Integration

Data Level Integration represents the ability to tie together database or data le sourceswith targets by manipulating data one or more records at a time. In order to feed datawarehouses and business intelligence applications, this capability is the foundation uponwhich 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, rationalizesand 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

DataCollection

Framework

ETL (Extract,Transform & Load)

ReportingTools

CustomFile Output

Portal

DataWarehouse(BI Tools)

Mainframe VSAM

DataBase

COBALFlat File

Data Level Example 1 – Migrations

Data Level Example 2 – ETL/Data Warehousing




Fine-Grained Integration

Fine-Grained Integration is the model that much of the world uses for many EnterpriseApplication Integration (EAI) projects, wherein two applications are tied together throughtheir native Application Programming Interfaces (APIs). Pervasive supports this model withthe 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 andMap design tools.

Coarse-Grained Integration

The Service Oriented Architecture (SOA) and Enterprise Service Bus (ESB) movementtoward loosely coupled systems interacting via dened messages is a response to thene-grained modelʼs inherent limitation of 1:1 connections. The rigidity of ne-grainedconnections is acceptable for point-to-point integration but becomes brittle for more complexprojects for two reasons: 1) the link between applications must be maintained as APIschange over time and 2) the link does not scale beyond a 1:1 relationship between theapplications.

Many companies seek to tie their applications and organizations together with amessage-based approach to integration. In this model, also called Coarse-GrainedIntegration, messages containing data from a variety of sources are passed betweentwo or more applications, and the data in a message is used or otherwise updated bythe applications as part of a larger business process. This approach typically relies ona backbone such as SonicMQ or MQSeries for sharing messages between the variouspoints of integration. The Pervasive architecture (shown as blue circles on the diagrambelow) supports all of these scenarios with rich connectivity to many available messagingenvironments and to alternative “queues” like email or FTP servers, where a mailmessage or a le represents the “message” for Coarse-Grained Integration. This type ofintegration is then viable across a wide range of infrastructure models at a low total costof ownership, since all the connectivity and intelligence for designing Coarse-GrainedIntegration 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




Connectivity SourcesConnectivity is the core of any integration project. The Pervasive Integration Engines includemore than 200 factory-supplied connectors that provide deep connectivity right out-of-the-box. Connectivity components can be accessed during both design tasks (eg. readingmetadata 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 delimitedat le, nearly all of the integration connections from Pervasive have been written to takeadvantage of native APIs. This feature increases performance and increases functionalityoptions in a design by taking advantage of the native hooks a database vendor offers. Manyof the connectors are cross-platform and support a range of modes, including client/serveraccess, local database access, multimode where a single data stream can be rapidly spreadacross multiple tables in a target database, and even mass-insert for high-speed bulkloading of data.

Combine this rich native connectivity with the Integration Architect tools for accessing datain non-traditional, unstructured formats (Extract Schema Designer, Structured SchemaDesigner – see pages 13-15) and the Pervasive Integration solution can reach nearly anydata in your organizationʼs infrastructure, including email, print reports, and print les.

Acctg

SupplyChain DemandChain

HR

ERP

EDI XML

CRM

Clearinghouse

Adapter

for SOA

Adapterfor SOA

Adapter

for SOA

Adapterfor SOA

B2BiHub

ESB/SOA

Web-ServicesOrchestration

Coarse-Grained Integration Example – Multi-point, message-based integration with adapters for SOA.




File Adapters

AccessAccess 97

Access 2000Access XPAlpha Four

ASCII (Delimited)ASCII (Delimited) Join

ASCII (Fixed)

ClarionClipper

CLF WebserverDataEaseDataFlex

DJ Log FileDatadBASE II, III (III+)

dBASE IV

dBASE V (IDAPI)DIF

EnableExcel

Excel 2000Excel XP

Folio Flat FileFoxbaseFoxProLDIF

Lotus 1-2-3Lotus Notes

Lotus Notes 5Lotus Notes Structured Txt

Lotus Works

Mac ASCII DelimitedMagic PC

MAILERS+4 (dBASE)Microsoft Word (Mail Merge)

Paradox up to v5 (IDAPI)Quattro Pro Windows v5Rich Text Format (RTF)

Unicode (Delimited)Unicode (Fixed)

WordPerfect 6.0 (Mail Merge)Wordstar (Mail Merge)

WordPerfect 4.2/5.0Visual FoxPro

Visual dBASE 5.5

Database Adapters

Oracle 7.xOracle 8.x

Oracle 8.x Mul modeOracle 9i

Oracle 9i Mul modeOracle 10g

Oracle Direct PathOracle SQL Loader

Pervasive.SQLPervasive.SQL v8

Pervasive.SQL v8 Mul mode

PostgreSQLPostgreSQL (ODBC 3.x)Btrieve v5Btrieve v6Btrieve v7Btrieve v8CA dB-Fast

C-ISAMCloudscape

CWMDB2 7.2 Univ. DB

DB2 7.2 Univ. DB Mul modeDB2 Loader

DB2 UDB Mass InsertDB2 (ODBC)

DB2 UDB

DB2 UDB Mul modeeXcelon

eXcelon XIS 3.0Hitachi Hi-RDB

IDAPIInformix DB Loader

Informix (ODBC)Informix DB Loader

Informix (ODBC)Informix Online DS

Informix/SE Ingres (ODBC 3.x)Interbase (IDAPI)MUMPS (ODBC)

MySQLNonStop SQL/MX

ODBC 3.xODBC 3.x Mass InsertODBC 3.x Mul mode

ODBC 3.5ODBC 3.5 Mul modeRBase 4.5 (ODBC)

Red BrickScalable SQL

SQLBaseSybase 11.x

Sybase 11.x Mass InsertSybase 11.x Multimode

Sybase 12.xSybase 12.x Mass InsertSybase 12.x Multimode

Sybase BCPSybase (ODBC)

Sybase SQL AnywhereSybase SQL Anywhere 6Sybase SQL Mass Insert

Sybase SQL 11Sybase SQL 11 Mul mode

SQL ScriptSQL Server 6.x

SQL Server 7 Mass InsertSQL Server 7 (OLEDB) Multimode

SQL Server 7 (OLEDB)SQL Server 2000

SQL Server 2000 Mass InsertSQL Server 2000 Multimode

SQL Server BCPSQL Server Mass Insert

SQL Server (ODBC)Teradata (Fastload)Velocis (ODBC 3.x)

Watcom SQL v5Watcom SQL (ODBC)

Application Adapters

Application AdaptersAccountMate

ACT! for Windows

Champion Acct.CYMA Acct.GoldMine

Great Plains DOSGreat Plains UNIX/Mac

Navision FinancialsMacola Acct.

Microsoft IIS ELF

PayChex DJFPeachtree Acct.Platinum Acct.

RealWorld Acct.Remedy ARS

Sales AllySalesforce.com

SAP (BAPI, RFC, IDoc)SAS

SBT Acct.

Solomon Acct.SPLUS Statistica

SYSTATApache CLF

Market ForcePersonal Librarian

SPSSUSMARC

Technology Adapters

BizTalk XMLErwin

FF QueueFTP

HTTPHTMLJMS

LDAPMSMQ (Extractor)

MSMQ (Fixed ASCII)MSMQ (XML)

MQSeries (Extractor)MQSeries (Fixed ASCII)

MQSeries (XML)

SGML TCP/IPURLURIXML

XML SchemaXML DTDXML XDR

Legacy Adapters

Acucobol (ODBC 3.x)

BAFBinaryBinary LineSequential

COBOL CopybookCOBOL Flat File

C-tree Plus

C-tree 4.3Fujitsu COBOLISAM

Micro Focus COBOLMicrosoft COBOL

QSAM

Sequential Binary

Tape Drive SequentialVSAMVariable Sequential (MVS)

Variable Sequential (Record-VUniKix)

Variable Sequential (SyncSort)Variable Sequential (User Defined)

B2B Adapters

EDI (EDIFACT)EDI (X12)

HCFA1500-NSFHIPAA

HL7Text (Delimited - EDI)

Text (Delimited - EDIFACT)

Text (Delimited - EDI)TRADACOMS

UB92-NSF

A sampling of connectors




Pervasive Integration ArchitectureThe Pervasive integration architecture comprises a unied set of design time and runtimetools that satisfy all three deployment styles mentioned. The integration architecture can beseparated into three distinct phases: design, deploy, and manage.

The design components boost developer efciency, which is often the largest cost in anintegration project.

Integration Architect – The Pervasive Integrated Development Environment (IDE) is abundle of components that supplies developers with the tools required to design effectivemulti-step integration processes. Access and data transformations across hundreds ofdata 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 typicaldata infrastructure.

Data Proler – A powerful tool to analyze batch data that provides developers withinformation 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 acrossenterprises.

Integration Engine – The workhorse of the Integration product line, this engine providesthe processing power to execute integration process and data mappings created bydevelopers with the Integration Architect. These engines can be run locally for quickaccess to view data and test designs and can then be distributed into the productioninfrastructure to run designs in the corporate environment.

Integration Manager – This component provides a single point of administration andcontrol for managing distributed Integration Engines. Through a user-friendly, browser-based interface, Integration Manager performs deployment, scheduling, ongoingmonitoring, and real-time reporting on individual or groups of distributed IntegrationEngines.

The management components tie the design time and runtime components together.

Integration Repository – The repository is an open, XML-based design le storage facilitythat developers can use to track and store work across multiple projects. The XML-formatted documents represent everything from schema designs and data transforms tobusiness process models.



9Pervasive 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: ProcessDesigner, Map Designer, Data Proler, Structured Schema Designer, Document SchemaDesigner, Extract Schema Designer, Repository Explorer, Repository Manager, and theUniversal Data Browser.

The benets of the comprehensive design environment in the Pervasive IntegrationArchitect:

• A single IDE reduces training costs and increases overall productivity.

• Increased reuse of processes through import/export repository sharing reducesdevelopment costs.

• Wide variety of connectivity to hundreds of types of data sources and targets helpsreduce custom code requirements and enables integration to reach into a wide range ofpreviously disparate systems.

• The Integration Architect toolset is designed to help reduce overall development labor forcreating 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 increaseexibility.




Process Designer

Process Designer has an intuitive interface available for “drag-and-drop” integration processdesign. Using simple owchart symbols, Process Designer links multi-step integrationprocesses together in a single, automated integration task. Key uses range from simpleintegration 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




Map Designer

Map Designer is a powerful data mapping and transformation designer, which providesa visually appealing user interface and Wizards for increased simplicity. The XML-basedcapabilities that dene the integration process enable substantially more re-use byseparating 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 Designer’s tools put the power of transformation at a developer’s ngertips




Expression Builder

Expression Builders are used throughout the design environment to assist the integrationdeveloper in building integration designs. Expression Builders use a rich scripting languagecalled Real-time Integration Flow Language (RIFL), designed to promote developerefciency on many common tasks encountered during integration projects. The RIFL

language includes hundreds of pre-built functions to automate developer tasks, includingactivities such as automatic conversion of different date formats to Boolean logic for creatingsmart decision points in a transformation or integration process and math functions thatprovide 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 aquick path to productivity. Even non-programmers can quickly learn how to execute simpleintegration tasks. This powerful, modular, reusable coding environment does not requirecustomer “exits” from the development environment to reach external custom code,supporting better code reusability, project management, and debugging for any unexpectedproblems that occur.

The Expression Builder pre-congures functions onto to the main expression-editing

window complete with expected parameters. Data elements, including source elds, targetelds, and global variables, are all available through this interface. Events/Actions suchas AfterRecord reads, BeforeTransformation, and OnError provide critical processingow control points where additional logic can be built and incorporated for performanceoptimization, error trapping, etc.

The GUI-based Expression Builder is used to quickly build Real-Time Integration Flow Language (RIFL) scripts




Structured Schema Designer

The Structured Schema Designer provides a visual interface for creating, saving, andmanipulating denition les (metadata) of structured data sources. The resulting metadata isstored 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.




Document Schema Designer

The Document Schema Designer gives you an easy-to-use graphical display for thedenition of trading standards (or subsets), so you can edit or create new DocumentSchemas (the metadata for document-oriented data such as EDI and XML). The SchemaDesigners offer many benets as follows:

• Signicantly reduces time and effort to dene and modify complex hierarchical documentstructures.

• Allows the creation of document structures from all “master” schema standards, includingEDI, EDIFACT, SWIFT, FIXML, TRADACOMS, HIPAA, HCFA 1500, UB92, HL7, Idocs,etc.

• Enables users to visually select specic segments and elements, then adjust allproperties, references, and code tables to dene the precise document structure neededfor a trading partner.

• Generates a validation rules le for ensuring that future messages received in this formatinclude 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 fo




Extract Schema Designer

The Extract Schema Designer is used for integrating unstructured text data into businessprocesses. Exclusive to Integration Architect, the Extract Schema Designer is the onlyalternative 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 forimproved 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 tomanually write coded routines.

• Self-documenting visual designer ensures that extraction processes are maintainableand adjustable by anyone.




Data Proler

Pervasive Data Proler is a rich data analysis tool that provides integration developers witha proven method by which to measure data quality before loading, preventing disruptiveproblems in the future. Pervasive Data Proler can also assess/prole existing databases toprovide objective and actionable results.

This tool accurately and efciently analyzes each data set, automatically generates detailedreports on the quality of the data, and delivers summary charts backed by drill-downanalysis, including percentages of success rate and frequency counts. Standard metricsinclude data-type compliance testing, conversion testing, and statistics collection. Inputrecords can also be segregated into “clean” and “dirty” les, allowing developers to focuson failed records, or even include identied problems in downstream data remediationprocess ows.




Deploy

Integration Services & Engines

Pervasive integration products can be deployed in a variety of ways depending on customerrequirements (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 thatwork in conjunction with J2EE application servers. Collectively, the capabilities below arecalled the Integration Services SDK.

• A purpose-built Message Driven Bean (MDB) that is congured to listen on a JMS queuefor the input message, then invoke a specic integration specication via the IntegrationServer. The Integration Server, in turn, will nd an available Integration Engine on thelocal 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 SOAPinvocations from any application (not only J2EE).




At runtime, the Integration Services SDK provides a communications broker called theIntegration 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 commandline interfaces for pinpoint control by external applications. The Pervasive engine can becongured 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

DBMSLoadFile

T4T2

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

SOAPINVOCATION

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

)

APPLICATIONLAYER

J2EE APPLICATION

SERVERS

DATA LAYER

Invoker

B U S

Native Connector (e.g. SAP BAPI)

(API - Methods/Calls)

FINE-GRAINEDTightly Coupled

Synchronous

(Message/Documents)

COURSE-GRAINEDLoosely Coupled Asynchronous

(Message/Documents)

COURSE-GRAINEDLoosely-Coupled

Asynchronous

XML XML In

Synchronous

Synchronous

http SOAP

Input Message

Output Message

Return Message

XML outGet Msg

Put Msg

Connector

DataConnector

MessageConnector

Pervasive Integration Engine Deployment Options




Integration Manager

The Integration Manager is a browser-based console that allows many distributedIntegration Engines to be managed centrally or from remote locations (e.g. via VPNconnections). At deployment time, the Integration Manager is used to deploy integrationspecications (packaged as “DJARs” in Pervasive terminology) to remote Integration

Engines via the remote management services provided by the Integration Server. IntegrationEngines do not communicate directly to the Integration Manager, but rather rely on a localIntegration Server to behave as the information broker.

ManageThe Pervasive architecture provides an open XML repository for housing all specicationsand rules that dene the execution and ow of integration tasks. Storing integration rules asnon-proprietary, XML provides enhanced exibility and allows integration project designs tobe 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 componentsthat 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 byproject names.




Repository

Designs are divided into distinct, reusable components that exist independent of one anotherand are saved as individual XML les. By increasing the availability of reusable integrationrules, costs associated with development time are often greatly reduced since individualcomponents can be shared between users and integration tasks. This “reuse” theme greatly

increases the efciency of new project implementations and lowers development costsassociated with projects.

[email protected]<mailto:[email protected]>12365-B Riata Trace Parkway

ENGINES

Design Tools & Languages

S c

h e m a

D e s

i g n e r s

ExtractSchema Designer Extract Schemas/.CXL

3rd Party Designers,UIs, Programs,Web Services

Import/Upgradefrom Legacy IDE

Metadata Exchange XML,XMI, XIF, CWMI, etc.sc.xml & tc.xml

map.xml

tf.xml

.rifl

.rifl

ip.xml

StructuredSchema Designer

Map Designer

Process Designer

ds.xmldsc.xmldsr.xml

ExtractSchema 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 ParserJAVA, 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 acrossproject groups.

• Improved code “reuse” features enhance developer efciency and project scalability.

• All designs may be additionally altered or even generated through any XML-compliantdevelopment 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 evenexecute integration designs from within their applications.

The Integration Architect also includes the Repository Explorer as the front-end for adevelopment project, providing a consolidated view of design processes and managingthe repository contents created by the various design tools. The exploration and controlcapabilities can be executed across multiple repositories, and a simple double click on anydesign component opens the appropriate Integration Architect design tool.




Repository Manager

The Repository Manager helps the developer and project manager get more out of theirPervasive Integration development experience and coordinate across multi-developerintegration projects.

• Dependency impact analysis – tracks dependencies between design components andoffers insight into the impact of proposed changes within a projectʼs work plan. Helpsavoid creating problems in one design component while working on another and offersvital 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 securepackage 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 toeffectively manage projects.




Integration Manager

Pervasive Integration Manager was discussed as a deployment tool – however, it alsoprovides a single point of administration and monitoring for a set of deployed engines.This capability improves operational efciency, especially with geographically distributedintegration 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 toincrease the security of integration infrastructure, a powerful role-based authentication andauthorization mechanism is in place.

