IBM Tivoli Directory Integrator
Parsers, connectors and function components
Understand the new and enhanced parsers, connectors, and
function components.
New parsers, connectors and function components
IBM Tivoli Directory Integrator version 7.1 increases functionality by providing new functional
components, as well as enhancements to existing components (Connectors, Parsers, and Function Components). The following connectors and parsers
are new in IBM TDI version 7.1.
- TDI provides an integration service for Service Management
deployments. It is bundled with both the Service Request Manager and
the Asset Management products CCMDB (which includes TADDM) that again
provide the foundations for TAMIT in Maximo .
This release strengthens this relationship through embedded support
for the CDM (Common Data Model). TDI is already used for this purpose
through components developed by the ISM SWAT organization, but this
enables TDI to play a general role for any product that needs to integrate
using CDM by improving and hardening the existing components as well
as add new components to take advantage of IT Registry capabilities.
The new Integration Suite includes the following items:
- Bundles the following Data Integration Services 1.1: CDM Meta-Data
service and Naming and Reconciliation service
- Provides Connectors and/or Parsers to handle CDM/IdML to do the
following:
- IdML Creation - Update existing IdML components to be easier to
use as well as optionally read the CDM.jar for classes or call the
upcoming IT Registry meta data service .
- IdML Reading - Update component to read IdML, with a configured
XML parser that is configured to deal with this format/syntax
- Provides documentation and components which shows how TDI can
act as a data retrieval layer for IT Registry to perform the CMDBf
queries on behalf of IT Registry (IT Registry is the front end service
provider for the CMDBf requests)
Enhanced parsers, connectors and function components
The
following connectors, parsers and function components are improved
in IBM TDI version 7.1.
- The JDBC Connector has been enhanced to provide a way
to set a prepared statement in the override parameters for that connector.
- HTTP Client Connector:
In Tivoli Directory Integrator v7.1
the HTTP Client Connector has been modified to automatically send
an HTTP "Connection" header with value "close" when it does not intend
to reuse the TCP connection for more HTTP requests. The reason for
this modification is to comply with the HTTP 1.1 specification (http://tools.ietf.org/html/rfc2616#section-14.10).
This behavior is mandatory according to the HTTP 1.1
spec and previously we needed to code this yourself in the AssemblyLine.
- HTTP Server Connector:
In Tivoli Directory Integrator v7.1
HTTP Server Connector has been modified to use persistent HTTP connections
by default. This means that one TCP connection can be used by the
same HTTP client for multiple HTTP requests (http://tools.ietf.org/html/rfc2616#section-8.1).
HTTP clients may still send a "Connection" header with value "Keep-Alive", but it is no longer required in order to use a persistent connection.
Idle TCP connections will be closed automatically after 20 seconds
of inactivity.
Parent topic: Overview of IBM TDI version 7.1