Data Transformation Engine Intelligent Business Integration Reference Guide

76 Pages·2004·1.43 MB·English

HP NonStop Data Transformation Engine
Intelligent Business
Integration Reference
Guide
Abstract
This document details the components of the HP NonStop™ Data Transformation
Engine (NonStop DTE) and Mercator product architecture.
Product Version
NonStop Data Transformation Engine 6.7.1
Version Updates (RVUs)
N/A

Part Number Published
528258-02 October 204
Document History
Part Product Version Published
Number
528258-001 NonStop Data Transformation Engine June 2004
6.7.1
528258-002 NonStop Data Transformation Engine October 2004
6.7.1
Contents
About This Document
Related References........................................................................................... 5
Chapter 1 - Introduction
Mercator Technology......................................................................................... 7
Design Environment – Design Studio....................................................................... 8
Type Designer ............................................................................................ 9
Map Designer ............................................................................................ 13
Integration Flow Designer............................................................................. 17
Database Interface Designer.......................................................................... 20
Source Control .......................................................................................... 22
Chapter 2 - Integration Maps
Anatomy of a Mercator Map ...............................................................................24
Input and Output Cards................................................................................ 25
Transformation, Routing, and Business Logic Rules .............................................. 25
Adapter Configuration for Input and Output....................................................... 26
Map Behavior During Execution ...........................................................................28
Input and Output Card Settings ...................................................................... 29
Map Settings ............................................................................................. 33
Resource Registry....................................................................................... 35
Chapter 3 - Methods of Execution
Servlet Execution Model....................................................................................37
Servlet Integrator....................................................................................... 38
Enterprise JavaBean Execution Model ...................................................................39
Command-Driven Execution Model .......................................................................40
Execution Command Overriding a Database Target Example................................... 41
Event-Driven Execution Model.............................................................................42
Event Server Architecture............................................................................. 42
Event Server System Example ........................................................................ 44
Audit and Transaction Logging Example............................................................ 46
Application-Embedded Execution Model ................................................................51
Chapter 4 - Developing Custom Adapters
XML Descriptor File..........................................................................................53
Chapter 5 - Operation Management & Monitoring Capabilities
Management Console........................................................................................56
Event Server Administration.......................................................................... 59
SNMP Support.................................................................................................60
Chapter 6 - High-Availability and Load-Balancing Architecture
Server Clustering ............................................................................................61
Enterprise JavaBeans .......................................................................................63
I n t e l l i g e n t B u s i n e s s I n t e g r a t i o n R e f e r e n c e G u i d e
3
Contents
Chapter 7 - Securing HTTP Communications
What is SSL?...................................................................................................64
Encryption ............................................................................................... 64
Digital Signatures and Certificates .................................................................. 65
Implementing an SSL Environment .......................................................................65
Event Agent.............................................................................................. 65
Chapter 8 - Web Services
What is a Web Service? .....................................................................................67
Why Use Mercator Products to Implement Web Services?....................................... 67
Technologies Used in Web Services ......................................................................68
SOAP ...................................................................................................... 68
WSDL...................................................................................................... 68
UDDI....................................................................................................... 69
Web Services Architecture.................................................................................70
Consumer Architecture ................................................................................ 71
Provider Architecture.................................................................................. 72
Web Services Example ......................................................................................73
Index

I n t e l l i g e n t B u s i n e s s I n t e g r a t i o n R e f e r e n c e G u i d e
4
About This Document
This document details the components of Mercator’s product architecture.
This document also details Mercator’s transformation, connectivity, flexibility, and
scalability capabilities, demonstrating how Mercator products can be the robust
backbone of your critical business operations.
Related References
The Mercator Online Library contains information about all products. Refer to the
following references for more information about topics frequently discussed in this
document.

Related Reference Description
Command Server Reference Guide Using the Command Server to execute
maps on various operating system
platforms.
Event Agent Reference Guide Using the Event Agent to securely send
external HTTP requests to the Event
Server.
Event Server Reference Guide Using the Event Server to help automate
the execution of your systems of maps
and the Management Console to remotely
monitor systems running.
Integration Flow Designer Reference Using the Integration Flow Designer as a
Guide Design Studio companion and graphical
facility to manage collections of related
maps. Also graphically organizing these
maps, based upon your requirements,
into logical collections called systems.
Introduction to the Design Studio Introduction of the concepts, terminology,
interfaces, and functionality of the Design
Studio client components. A companion
book to the Design Studio Tutorial.
I n t e l l i g e n t B u s i n e s s I n t e g r a t i o n R e f e r e n c e G u i d e
5
About This Document Related References
Related Reference Description
Map Designer Reference Guide The Map Designer user interface and
instruction on specifying mapping rules,
configuring map sources and targets,
defining map-level settings, and executing
a compiled map.
Mercator Integration for Java How to use the components included with
Reference Guide the Mercator Integration for Java product,
which allow for server-independent map
execution. The guide includes detailed
instructions for running the Servlet
Integrator. (SDK Online Library only)
Mercator Programming Interface The Mercator Programming Interface
offers an object-oriented approach that
enables applications to invoke Mercator
maps, thus removing reliance on
command lines. (SDK only)
Platform API Reference Guide Using a platform-specific API with your
application to tightly integrate the
Enterprise Broker with your application.
(SDK Online Library only)
Resource Adapters Reference Guide Using adapters as map sources and map
targets in general. More specific
information can be found in the respective
reference guides for each adapter.
Resource Registry Reference Guide Using name aliases for source and target
resources that are specified in map cards.
SNMP Agent Reference Guide Provides standardized network
management framework for controlling
and monitoring the internetwork, an
interconnected system of computer
networks.
Type Designer Reference Guide Using the Type Designer to create and
edit type trees that describe your data.

I n t e l l i g e n t B u s i n e s s I n t e g r a t i o n R e f e r e n c e G u i d e
6
Chapter 1 - Introduction
Mercator Technology
Mercator products combine leading-edge technology for both external (B2B) and
internal (A2A) application integration, powerful graphical technology for
integrating application content, and management facilities that provide run-time
control of both real-time and event-driven integration activities. They support the
entire integration solution life cycle, beginning with graphical definition of
integration workflows. They provide a feature-rich graphical environment for
creating all integration interfaces without the need to resort to programming. A
fully functional Software Development Kit (SDK) is available, providing the
capability to create tightly coupled application interfaces and custom resource
adapters as required.
Whatever type of integration model is being employed, the Mercator difference is
that a single technology base is used for all integration scenarios.
Mercator products

I n t e l l i g e n t B u s i n e s s I n t e g r a t i o n R e f e r e n c e G u i d e
7
Chapter 1 - Introduction Design Environment – Design Studio
Design Environment – Design Studio
The Mercator Design Studio is the client interface into an extensive array of
functionality that is available to create application integration solutions.
Application integration solutions created with the Design Studio are executed on
transformation servers specific to the Mercator product being used. Separation of
design and execution provides exceptional user flexibility in implementing
enterprise-wide integration solutions. A single Design Studio can deploy
integration solutions to multiple servers, or multiple Design Studios can be used to
create integration solutions for a single production environment.
The Mercator Design Studio consists of multiple user-friendly, GUI-based
applications that run on the Microsoft Windows platforms. These applications
include designers for integration flows, data object definitions, data transformation
maps, intelligent routing rules, and database interface definitions.
The major components of the Mercator Design Studio include:
♦ Type Designer
♦ Type Importers
♦ Type Tree Maker
♦ Map Designer
♦ Integration Flow Designer
♦ Database Interface Designer
I n t e l l i g e n t B u s i n e s s I n t e g r a t i o n R e f e r e n c e G u i d e
8
Chapter 1 - Introduction Design Environment – Design Studio
Type Designer
The Type Designer is a facility for creating, maintaining, and viewing data object
definitions in a graphical form called a type tree. The type tree provides visual
cues for understanding the structure of an object and supports point-and-click
techniques enabling you to “drill down” to uncover an object’s complete definition.
The following is an example of a type tree:

A type tree is a repository of one or more data object definitions. A data object
definition, called a type, describes data object structures in terms of their syntax,
composition, existence, and validity. A composite type, called a group, describes
sequences and choices of other types. An elementary type, called an item,
represents a basic building block such as time, date, numbers, and text. The trees
are arranged in a classification hierarchy to facilitate reuse of type definitions in a
subtype.
I n t e l l i g e n t B u s i n e s s I n t e g r a t i o n R e f e r e n c e G u i d e
9
Chapter 1 - Introduction Design Environment – Design Studio
Type trees can be created in a number of ways:
♦ The Type Designer includes an importer tool for automatically generating type
trees for data described in XML, COBOL, SAP R/3, Tuxedo, and PeopleSoft
formats or application data structures.
♦ The Type Designer enables creation of type trees “from scratch” as well as
modification and customization of existing type trees; including those
generated by importers, DTD, or provided by Mercator. For example, the EDI
type trees provided with the Mercator Integration Broker can be customized to
reflect a trading partner agreement.
♦ Mercator provides type trees for industry-standard formats such as S.W.I.F.T.,
FIX, X12 EDI, EDIFACT, ACORD, Tradacoms, and Odette.
♦ The Database Interface Designer provides a feature that establishes a session
with any relational database management system and automatically imports
definitions from the database catalogs.
Importers define a transformation between well-known metadata formats such as:
ƒ Extensible Markup Language (XML) document type definitions (DTDs)
ƒ Extensible Markup Language (XML) schemas
ƒ Web Services Description Language (WSDL) web service definitions
ƒ OAG Business Object Documents (BODs)
ƒ COM type libraries
ƒ COBOL Copybooks
ƒ Java classes
ƒ Interface definitions for packaged applications such as SAP, PeopleSoft, and
Siebel.
I n t e l l i g e n t B u s i n e s s I n t e g r a t i o n R e f e r e n c e G u i d e
1 0