This section helps you to understand your starting place when designing a data integration solution. Although the design strategy is incremental, it is suitable for any size of integration and systems deployment project, including large ones.
The answer is, one bite at a time. This is also the best approach for digesting large integration and systems deployment projects. The key to success is to reduce complexity by breaking the problem up into smaller, more manageable pieces. Once this is done, you then begin work on a portion of the overall solution, preferably one that can be deployed independently. That way, it’s already providing return on investment while you tackle the rest.
After isolating the piece you are going to work with, simplify it further by focusing on the basic units of communication: the data flows themselves. You are now poised to start the implementation. Integration development is done using the IBM Tivoli Directory Integrator Configuration Editor (abbreviated as 'CE') through a series of try-test-refine cycles, making the process an iterative and even exploratory one. This not only helps you to discover more about our own installation, but also lets you evolve your integration solution as your understanding of the problem set and its impact on your infrastructure grows.
Parent topic: Introduction