You are on page 1of 2

IBM introduced a tool called FastTrack that is a source to target mapping tool that is plugged

straight into the Information Server and runs inside a browser.

The tool was introduced with the Information Server and is available in the 8.1 version.

As the name suggests IBM are using it to help in the analysis and design stage of a data
integration project to do the source to target mapping and the definition of the transform rules.
Since it is an Information Server product it runs against the Metadata Server and can share
metadata with the other products and it can run inside a browser.

I have talked about it previously in New Product: IBM FastTrack for Source To Target
Mapping and FastTrack Excel out of your DataStage project but now I have had the chance to see it in
action on a Data Warehouse project. We have been using the tool for a few weeks now and we
are impressed. It’s been easier to learn than other Information Server products and it manages to
fit most of what you need inside frames on a single browse screen. Very few bugs and it has
been in the hands of someone who doesn’t know a lot about DataStage and they have been able
to complete mappings and generate DataStage jobs.

I hope to get some screenshots up in the weeks to come but here are some observations in how
we have saved time with FastTrack:

1. FastTrack provides faster access to metadata. In an Excel/Word mapping environment


you need to copy and paste your metadata from a tool that can show it into your mapping
document. FastTrack can see metadata imported through any of the Information Server
import methods such as DataStage plugin imports, the import bridges from Meta
Integration Technologies Inc (MITI): ErWin, InfoSphere Data Architect, Cognos, Business
Objects, Informatica etc. The imports via the database connectors from any other
Information Server product such as the table definitions imported and profiled by
Information Analyser. You can import an entire database in a few minutes and drag and
drop it onto your various mappings.
2. FastTrack lets you map columns from XML and Cobol Copybook hierarchies to flat file
relational database targets without any metadata massaging. In Excel you would spend
days cutting and chopping XML and Cobol complex flat file definitions. With FastTrack
you can access a definition imported through the DataStage Cobol or XML importers and
map away.
3. FastTrack lets you do source to target mapping straight out of your modelling tool. You
can import your model straight into the Metadata Server via a bridge and start mapping
it. No mucking around with database DDLs and no need to get access to create
database schemas. This can be handy in the early days of a project.
4. FastTrack has some great auto mapping functions. There is a discovery functions where
you drag and drop the source or target table onto one side of the mapping and then use
the discover function to find candidate matches for the other side – then choose the “Best
Match” to take the first of the candidates. If you choose multiple columns you can
Discover and Best Match all the columns in your table. It searches through for matching
column names against the candidate tables.
5. FastTrack can map auto match on the business glossary terms attached to those
columns. It is one of the few products in the Information Server that makes productive
use of the Business Glossary to speed things up. Of course you need to create your
Glossary and fill it with terms and map those terms to physical metadata first! FastTrack
lets you add Glossary terms to physical columns as you map.
6. FastTrack lets you balance the mapping between business analysts and ETL
developers. Both can use the tool – it’s an Excel style interface – but business analysts
may be faster at mapping early in the project as they gather requirements and rules and
ETL This can help avoid bottlenecks on your team if anyone can do mapping and can
push the results straight into DataStage.
7. FastTrack creates DataStage jobs. These jobs have the source and target connectors
already loaded and configured and stages such as lookup, join and transformer already
built. It even lets you add Transformer derivations such as macros, job parameters and
functions from a function list.
8. FastTrack handles DataStage naming conventions. FastTrack holds a set of rules for
naming DataStage stages and links that you can configure to match your naming
convention. Normal DataStage development means dragging and dropping stages and
links onto a canvas and renaming every one. FastTrack does the naming for you.
9. FastTrack lets you add the links for joins and lookups. I don’t know if you’ve tried to map
joins and lookups in Excel but it’s not pretty – you have room to map the extra columns
but there is no easy way to show the key fields that join the two sources together.
Generally you make a note of it under the mapping. In FastTrack you choose the
join/lookup table, choose the key fields that do the join and bring in the extra columns for
mapping to the output table and it generates the required stages in DataStage.
10. FastTrack shows progress of mapping tasks. Once you have created a mapping for all
interfaces FastTrack will produce a report showing how much of each mapping has been
finished saving you the time of tracking progress manually.

What FastTrack can do better.

1. Better bulk export and import functions – preferably XML and Excel. Excel for when we
produce documentation. XML for when we want to back it up or move it between
repositories. (Or export, run a search and replace to globally rename a transform value
and import it again).
2. Global search and replace on transformation values, similar to the search and replace in
the DataStage Transformer, for globally renaming things like function names and job
parameter values.
3. More DataStage stages – it currently lets you configure settings for Lookup, Join,
Connectors and Transformers. Would like to see Surrogate Key, Change Data Capture
and Slowly Changing Dimension support – though it’s debatable whether those are
business analyst functions for FastTrack or developer functions for DataStage. It would
be cool to define Type 1 Type 2 and key fields for dimension table mapping.
4. Let you run Discover and Best Match on Business Glossary terms so you can find terms
that suit the column name you are mapping.
5. Discover transformation rules as well as mappings … oh hang on, that’s in the next
release!
6. Reverse engineer DataStage Server jobs so you can generate DataStage Enterprise jobs
from a Server job mapping.
7. More flexible licensing. You buy licenses in packs of 10 – and that’s too many for a