a Power Exchange for Db22024

8/2/2019 a Power Exchange for Db22024

1/9

Informatica PowerExchange for DB2Todays IT organizations face growing demand for timely access to critical operational data stored in IBM DB2 UDB transactional

systems on z/OS or OS/390 mainframes and the AS/400. New business initiatives, such as improving customer service, meeting

governance and compliance requirements, consolidating systems, and optimizing integration processes challenge IT to find an

efficient, cost-effective way to leverage data in right time without impacting existing systems. Until now, two common

approaches have been hand-coded programs that extract and process bulk data and hand-coded change-capture solutions that

rely on application logic, triggers, and/or date stamps. Informatica PowerExchange for DB2 offers IT organizations noninvasive

software based on a service-oriented architecture that provides direct, scalable access to bulk or change-only data in real time or

on a scheduled basis without requiring application programming. It removes implementation complexity while reducing overall

costs.

Key Technical Benefits of Informatica PowerExchange for DB2 Integrate DB2 data easily, seamlessly, and safely by deploying direct, native, bidirectional data access software

Meet any on-demand DB2 data requirement from bulk to real-time change-only data in one common architecture

Save development and maintenance costs through visual tools that remove complexity and eliminate hand coding

Use push or pull execution models to ensure appropriate resource control

Adhere to system authentication security requirements for easy deployment

Utilize seamless design and run-time integration with Informatica PowerCenter, EAI, and other data integrationtechnologies to meet comprehensive solution needs

Simplify debugging with dynamic design and testing capabilities

Change Capture Benefits Allow only desired, committed data to be available through a unique capture registration process

Leverage transactional control information (date/time-stamp, insert, update, delete, etc.) during data integration

Employ extract-once, read-many model for efficient resource use

Seamlessly handle errors through robust recovery capabilities

Remove the need to change existing applications to implement change capture

OS/390 and z/OS Specific Benefits

Leverage DB2 Image Copy files as sources for efficient offline data processing Streamline installation and configuration process for minimal operational impact

Optionally condense all changes to a common record into an end representation to minimize overall processing

Deploy a noninvasive solution that uses standard interfaces (IFCID 0306) for change monitoring

Use high-performance IBM Hiperspace subsystem as the storage mechanism for changed data, allowing for near-real-time propagation

AS/400 Specific Benefits Deploy a noninvasive solution that uses DB2/400 Journaling as the source for change data

Optionally condense all changes to a common record into an end representation to minimize overall processing


2/9

Key Benefits of Informatica PowerExchange for DB2

Integrate DB2 data easily, seamlessly, and safely by deploying direct, native,bidirectional data access software

PowerExchange provides solution developers with direct, native, bidirectional access to data stored in DB2 on the mainframe or

AS/400 through open, scalable software. Direct access is achieved through a high-speed, metadata-centric architecture that

uses native DB2 SQL as the execution language. Data can be extracted and/or written using standard SQL, easing data

integration with DB2 on the mainframe and AS/400.

Meet any on-demand DB2 data requirement from bulk/batch to real-time change-onlydata in one common architecture

In a single architecture, PowerExchange supplies three product options (Batch, Change, and Real-Time) that can be configured

to meet any on-demand DB2 data requirement.

Batch OptionThe Batch Option provides direct access to bulk DB2 data by executing native extract or update SQL statements. It then

makes a high-bandwidth stream of data available to a calling program such as Informatica PowerCenter (on or off the

mainframe or AS/400), or PowerExchange can push that data to a message queue, a database, or a file.

Change OptionThe Change Option furnishes direct access to only changed data on a scheduled basis. Additional, patented components of

the PowerExchange architecture can perform change data capture at the database or system level. The Change Option

also moves those changes to disk where appropriate and handles error recovery where required.

Real-Time OptionThe Real-Time Option extends the value of only changed data by delivering that data in near real time to a message queue,

a database, or a calling program. This option leverages the same change capture facility of the Change Option but

leverages additional architecture components to enable real-time delivery.

Save development and maintenance costs through visual tools that removecomplexity and eliminate hand coding

PowerExchange is metadata-centric and powered by a visual design client called Navigator. Navigator handles all aspects of

the data access and delivery process from design to deploy, recover, and maintain. This approach saves time in each phase,

captures metadata and makes it available for reuse, and easily integrates change when business needs require it.

Use push or pull execution models to ensure appropriate resource control

PowerExchange can be configured to push data to a supported database, file, or message queue or act as a client in a data pull

scenario. This flexibility ensures that the appropriate resource control is placed in the right hands. If database owners want to

maintain control of execution, they can do so by initiating the data extraction and delivery process. When data integration tools

drive the data acquisition process, PowerExchange can be passed an SQL statement for execution and data returned.


3/9

Adhere to system authentication security requirements for easy deployment

PowerExchange provides security checking controlled by user-defined configuration settings and support for mainframe security

packages, including RACF, ACF/2, and Top Secret. The PowerExchange Listener attaches to the DB2 subsystem via one of two

methods based on configuration settings:

Call Attach Facility

Resource Recovery Service Attach Facility

By providing multiple security strategies, PowerExchange can be easily integrated into your current system's environment.

Utilize seamless design and run-time integration with Informatica PowerCenter, EAI,and other data integration technologies to meet comprehensive solution needs

PowerExchange is based on an SQL-driven, service-oriented architecture that integrates easily with EAI and data integration

technologies. As examples, PowerExchange can push data directly to an EAI-based message queue, or a data integration

product can pull data through PowerExchange using an SQL request. This inherent flexibility is achieved through the benefits of

PowerExchange, which is an Informatica UDS smart data service.

End users enjoy additional design and run-time advantages when

using PowerExchange for DB2 with Informatica PowerCenter.

Design Time Solution design is streamlined through simplifiedsource import and mapping design

Run Time PowerCenter s Data Server uses optimized, parallelread/write APIs for best performance

Figure 1: PowerCenter Designer Client leverages PowerExchange Design Time integration

Simplify debugging with dynamic design and testing capabilities

With the Navigator interface, design is greatly simplified through the ability to monitor and receive live, flowing data after making

configuration changes. This capability, called a Row Test, is enabled for the Change and Real-Time options. It allows a solution

designer to see the real data as it is captured from the source to ensure that the column alignment and metadata are accurate.


4/9

Figure 2: Dynamic Row Sampling Test

Change Capture BenefitsPowerExchanges unique, patented architecture for the change capture process removes the need to change existing

applications to implement change capture.

Figure 3: DB2 Change Capture Architecture Used by Change and Real-Time Options for OS/390 and z/OS

Collector The Collector is a platform-specific module that leverages published application programming interfaces (APIs)or technology to perform the Changed Data Capture function. Details on the platform-specific Collectors are outlined insections that follow for OS/390 and z/OS and for the AS/400. An additional role of the Collector is to manage thedistribution, persistence, and/or condensing of changed, committed transactions. It also manages "change stream" recoveryand synchronization for subscribing applications.

PowerExchange Listener The PowerExchange Listener is a generic architecture module that coordinates activitiesacross modules, initiates a request, or processes a request from a third party application. The Listener also processesrequests for metadata in the design process. As the term Listener implies, the PowerExchange Listener waits on a TCI/IPport for requests.


5/9

Allow only desired, committed data to be available through a unique captureregistration process

Through the PowerExchange Navigator, solution developers identify the specific data elements (tables, columns, etc.) ofinterest for a data integration scenario. This process is called Capture Registration and results in a solution-specificmapping or Registration Group of the elements to be monitored for transactional change. Multiple Registration Groupscan all be active simultaneously for different integration scenarios, thereby providing high scalability. Using this visual,metadata-centric approach improves developer productivity and ensures that only the right data is monitored for changecapture.

Figure 4: Capture Registration Choosing the appropriate Change Capture data elements

Leverage transactional control information (date/time-stamp, insert, update, delete,etc.) during data integration

Along with the data, control information is captured and made available as part of each complete record. Control information can

be leveraged downstream by Informatica PowerCenter, EAI, and other data integration products to determine what to do with

each row of data. This capability provides a unique benefit when deploying an integrated solution between PowerExchange and

a data integration product.


6/9

Figure 5: PowerCenter Mapping that executes based on control information passed from PowerExchange

Figure 6: PowerCenter Update Strategy Transformation acting on PowerExchange control Information

Employ extract-once, read-many model for efficient resource use

Changes are captured once and then can be consumed by different applications and at different time intervals. For example,

certain applications or downstream requirements may have different business requirements that need to have the changes

propagated immediately, whereas others may require the changes periodically in bulk. As the changes are consumed, they can

incrementally update a remote system while intelligent information is also tracked about the data captured, such as date/time-

stamp information and if the row was an insert, an update, or a delete. This approach reduces latency, network traffic, and use of

CPU time.


7/9

Seamlessly handle errors through robust recovery capabilities

The PowerExchange architecture for DB2 on the mainframe and AS/400 includes a sophisticated logging capability that

facilitates seamless error recovery from a connection, software, or hardware failure. A unique sequence number and time-stamp

are logged for each changed data record. Recovery uses this logging infrastructure to ensure that all change stream subscribers

pick up where they left off when a session is restarted.

OS/390 and z/OS Specific Benefits

Leverage DB2 Image Copy files as sources for efficient offline data processing

For bulk data scenarios, PowerExchange supports the DB2 Image Copy file format as a source. This capability allows for offline,

high-bandwidth delivery of data and also facilitates initialization of data sets before turning on change capture.

Streamline installation and configuration process for minimal operational impact

Initial PowerExchange installation and configuration is powered by a visual client that automates the process and ensures

completion of configuration. Administrators have all options available to them in one user interface that makes it easy to install

software into an existing systems environment. This approach saves time and resources and allows for rapid time to design.

Figure 7: PowerExchange MVS Install Assistant

Optionally condense all changes to a common record into an end representation tominimize overall processing

The PowerExchange Change Option provides a way to condense a set of changed data transactions that can deliver operational

efficiencies, lower data volumes, and allow design flexibility. This option collapses all updates to common records into a single

final representation of the data. This capability reduces data volume and ensures that only the final, committed result of each

record is made available.


8/9

Deploy a noninvasive solution that uses standard interfaces (IFCID 0306) for changemonitoring

DB2 on OS/390 and z/OS systems provides an interface called the "Instrumentation Facility Interface" (IFI). IFI uses the

standard security mechanisms that DB2 uses, including connection authorization and plan authorization. For

access to log data, IFCID 0306 is provided. PowerExchange monitors for change through this standard, published interface. By

using a high-performance, noninvasive interface, PowerExchange can handle high transactional volume and perform change

capture without requiring application logic change.

Use high-performance IBM Hiperspace subsystem as the storage mechanism forchanged data, allowing for near-real-time propagation

As changes are captured by the Capture Agent from the DB2 subsystem, they are written to Hiperspace or high-speed expanded

storage, a system facility that can dramatically increase data write and access time. This strategy ensures high-speed end-to-enddelivery of data without intermediate DASD storage.

AS/400 Specific Benefits

Deploy a noninvasive solution that uses DB2/400 Journaling as the source forchange data

Journaling is a key capability of DB2/400 that furnishes a secure audit trail of the changes to database files as they occur. Part of

the Journaling subsystem is the Retrieve Journal Entries (QjoRetrieveJournalEntries) API. PowerExchange for DB2/400 uses

this API to monitor and retrieve changed data. By leveraging this published, system-level interface, no changes to existing

applications are necessary, and impact to system performance is minimal.

Optionally condense all changes to a common record into an end representation tominimize total processing

The PowerExchange Change Option supplies a way to condense a set of changed data transactions that can deliver operational

efficiencies, lower data volumes, and allow design flexibility. This option collapses all updates to common records into a single

final representation of the data. This capability reduces data volume and ensures that only the final, committed result of each

record is made available.

Why PowerExchange?PowerExchange for DB2 is ideal for any organization seeking to leverage mainframe and/or AS/400 DB2 data for data

integration initiatives. IT can significantly improve its ability to fully use this critical resource to address new business initiativeswhile dramatically improving current integration methods. It provides significant end-to-end cost savings and fits easily into

existing IT environments. PowerExchange for DB2 is a clear choice for organizations that require on-demand data access to

meet business objectives.


9/9

System Requirements

Common Requirements

A minimum of one TCP/IP port must be available for PowerExchange usage.

Port 2480 has been registered with IANA

OS/390, z/OS SystemsOS/390 2.6 and above

z/OS 1.1 and above

DB2 Version 5.1DB2 Version 6.1

DB2 Version 7.1

DB2 Version 8.1 with some data type exceptions

Stored Procedures not supported

DATA CAPTURE CHANGES option must be enabled on desired tables for change capture

DISPLAY, TRACE, and MONITOR2 authority required by PowerExchange database user

AS/400OS/400 4.5 to 5.2

Journaling enabled for Change and Real-Time options

Local Journaling supported

Stored Procedures not supported

2004 Informatica Corporation. All rights reserved. Printed in the U.S.A. Informatica, the Informatica logo, Turning integration into insight, Informatica,PowerCenter, and PowerExchange are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout theworld. All other company and product names may be tradenames or trademarks of their respective owners.

J50078 6512 (12/08/04)

Documents

a Power Exchange for Db22024