Professional Documents
Culture Documents
Todays 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.
Meet any on-demand DB2 data requirement from bulk/batch to real-time change-only data 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 Option
The 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 Option
The 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 Option
The 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 remove complexity 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.
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 simplified source import and mapping design Run Time PowerCenter s Data Server uses optimized, parallel read/write APIs for best performance
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 in sections that follow for OS/390 and z/OS and for the AS/400. An additional role of the Collector is to manage the distribution, persistence, and/or condensing of changed, committed transactions. It also manages "change stream" recovery and synchronization for subscribing applications. PowerExchange Listener The PowerExchange Listener is a generic architecture module that coordinates activities across modules, initiates a request, or processes a request from a third party application. The Listener also processes requests for metadata in the design process. As the term Listener implies, the PowerExchange Listener waits on a TCI/IP port for requests.
Allow only desired, committed data to be available through a unique capture registration process
Through the PowerExchange Navigator, solution developers identify the specific data elements (tables, columns, etc.) of interest for a data integration scenario. This process is called Capture Registration and results in a solution-specific mapping or Registration Group of the elements to be monitored for transactional change. Multiple Registration Groups can 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 change capture.
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.
Figure 5: PowerCenter Mapping that executes based on control information passed from PowerExchange
Optionally condense all changes to a common record into an end representation to minimize 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.
Deploy a noninvasive solution that uses standard interfaces (IFCID 0306) for change monitoring
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 for changed 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-end delivery of data without intermediate DASD storage.
Optionally condense all changes to a common record into an end representation to minimize 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 initiatives while 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.
System Requirements
Common Requirements
A minimum of one TCP/IP port must be available for PowerExchange usage. Port 2480 has been registered with IANA
AS/400
OS/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 the world. All other company and product names may be tradenames or trademarks of their respective owners. J50078 6512 (12/08/04)