Welcome to my repository
Written by Cezary Opacki
The wf_i5OS_CDC workflow demonstrates how to use “i5/OS Data queue & CDC connector” to build replication solution which reads changes from a transaction journal (change data capture). The workflow reads changes from tables on as/400 (iSeries) machine. The changes collected from transaction journal are applied to tables in relational database. Target database can be any database supported by Power Center.
AS/400 DATA QUEUE & CDC connector for Informatica PowerCenter has been improved.
Published in Latest
On the site is available i5/OS CDC connector for Informatica PowerCenter which is able to read transaction journal entries from i-System (old As/400) in real time. This entries can be used to replicate changes to other database, to audit database changes made by users or to compare two processes.
Use Case Description.
There are two identical databases on two different i - Systems (As/400 Systems) and two application sets, which calculates actuarial reserve. One set of applications is the old one. The second applications set must give the same results but is optimised in order to run faster. The challenge is, how to compare what the two sets do the same and what they do differently.
Version 1.2.3 of the Data Queue connector for Power Center support all data queue types and enables reading i5/OS database changes in real time. New name of the product is "Data Queue & CDC Connector for i5/OS". Data available in the i5/OS journal are propagated to Informatica Power Center. Power Center real time edition is the only licence requirement.
The Data Queue & CDC Connector for i5/OS is a real time connector. Below I present Change Data Capture solution for i5/OS(AS/400) which does not stop in case of table structure alteration as table structures are discovered in real time.
It is common to use the shell command redirection in PowerCenter. The feature allows one to use the ldapmodify command to load data to LDAP. To achieve this it is necessary to create an LDIF flat file. Some data in the file must be in UTF-8 code page and Base64 encoded.
Published in Java Transformations
The solution shows how to:
· use shell command to generate input flat file list.
· each flat file with name <name>.<extension> from the list above is processed and written to output file under the name <name>_O.<extension>.
· to achieve that transaction control transformation is required. For every transaction it is generated flat file with new name.
· expression transformation shows how to check whether new input file is processed. If new file is processed port NewFile is set to 1 (0 in other case). This is used in transaction control transformation to generate new transaction. One of more interesting issues is using local variables in the expression transformation.
Published in Flat Files
Written by Cezary Opacki
PowerExchange for Websphere MQ returns RFH2 message in binary format. Convert the RFH2 message in binary format to something readable by mapping transformations.
These tools enable one to develop mapping, which reads requests through the “PowerExchange for Websphere MQ” connector and sends replies, if required to temporary, dynamic queues. Messages are exchanged in RFH2 format, which is compliant with JMS. Source queues and queue managers are defined by PowerExchange for MQ connector. Target queues and queue managers are dynamically calculated in the mapping.
Published in Informatica extensions for IBM MQ Series