What is perfectly acceptable to one person is a potential disaster for another. The concept of availability is closely related to risk tolerance. This document illustrates the options and capabilities that an integration designer can use when planning, developing, and deploying an integration solution using IBM Tivoli® Directory Integrator.

The challenges discussed in this IBM® Redpaper™ publication are not unique to Tivoli Directory Integrator, nor are the approaches to mitigate them. However, Tivoli Directory Integrator is an unusually flexible product, and understanding its capabilities can significantly reduce the time and cost of developing a solution, and provide a better answer for the organization in terms of risk, performance, and scalability.

The audience that can benefit from this document ranges from the casual Tivoli Directory Integrator developer with simple integration requirements to the data center manager with 24x7 availability requirements on everything in the infrastructure.

The casual Tivoli Directory Integrator developer can find approaches in the document that, with little effort, can significantly increase the resiliency of the integrations. Similarly, advanced users and architects can recognize patterns and learn about Tivoli Directory Integrator services that enable the building of highly available, resilient, and scalable Tivoli Directory Integrator solutions.

Introduction

Potential sources of trouble are all around us

Handle trouble proactively

Architectural styles for increased availability

Make message queues and events work for you

Highly available queues and databases

Monitor Tivoli Directory Integrator

Planning for availability: tips and tricks

Change detection

Proper Tivoli Directory Integrator design and scripting

Summary