Part of our solution includes custom tables within XI that ensure the integrity of the data that we allow into the mapping tables. We’ve created several transactions that allow our administrators and end-users to easily configure and load our mapping data. All of these transactions and our key mapping functionality is exposed & accessible via our portal front-end.
How we use our data translation is quite simple. First we load the systems (agencies) and data objects (schemes) for which we require translations. We link our data objects to the systems in which they are recognized. We further link source system & object combinations to target system & object combinations. Again, we do this to ensure the integrity of the mapping entries before we actually write them into UKMS. Next we load all of our key mappings. All of this ‘setup’ work is easily delivered via our custom utility programs accessible through our user-friendly web front-end.
Once our custom data translation solution has been configured and the mapping values loaded, we insert our modular user-defined Java function into the XI interface maps. This function is performed at interface run-time. As an interface message enters XI, the required data translation parameters are passed to the function and the translation is performed automatically and in real-time. Now each time our interfaces run, our data translation solution automatically translates the disparate system keys, writes the translated values into the XI message payload and passes the message into the receiving system with key values that are recognizable to that system. A major benefit of our solution is the web portal which exposes the mapping data to our end users in a user-friendly and logical manner. End users don’t need any XI experience to be able to map and view disparate system key pairings! Being coupled with our integration layer (XI), this data translation solution is very efficient and powerful.