You can use the UMF database conversion utility to convert data stored in a relational database into UMF records that can be processed by the pipeline.
The UMF database conversion utility reads source data from a relational database and produces UMF records as output. It supports the same databases as IBM® Relationship Resolution.
The utility's mapping (XML tags, source database fields, and so on) must be defined in a relational database.
The utility is built using the standard entity database node, and it uses xCME routing for distributing the data to one or more target routes. You can use Microsoft Message Queueing, IBM Websphere MQ, flat files, HTTP, or database tables as route transports.
Queries can be used such that one or many database tables can be combined to produce a single UMF file. For example, a CustomerMaster and a CustomerAddress table can produce a UMF_ENTITY document. This can be achieved by either joining the two tables in a single select statement or using two separate select statements.
UMF segments (for example, <NAME>) can have multiple entities in the UMF file when a one-to-many relationship exists between database tables. These data elements can be mapped into the target UMF documents. For example, if a single CustomerMaster record has multiple CustomerAddress records, you can create one UMF_ENTITY document with multiple address segments by specifying two contiguous select statements in the ACQ_NODE_QUERY table with the same DOC_TYPE, the first being a parent, the second being a child.
Most users pull data from source databases in real-time by applying triggers to source tables and adding a SYNC_LOG table. Record adds, deletes, and changes are captured in the source database by triggers writing to a SYNC_LOG table. Contact IBM Software Support for assistance in implementing this real-time solution.