IBM CISCO R2E2 User Manual page 53

5. environment only: Configure the Data Direct SQL Server Bridge
CCM
The Tivoli Netcool/Proviso Cisco IP Telephony Technology Pack collects data from SNMP devices and,
through SQL for Call Detail Records, from each CCM database.
The technology pack UBA is responsible for retrieving CCM data, using the Data Direct SQL server bridge
to do so. This bridge is part of the UBA installation. No additional software is required.
You need to set up the Data Direct SQL server bridge to get Call Detail Records from each CallManager
Publisher. The complete configuration is done by editing the
.
pvuser
[ODBC Data Sources]
Your_Data_Source1=DataDirect 4.20 SQL Server Wire Protocol
Your_Data_Source2=DataDirect 4.20 SQL Server Wire Protocol
Your_Data_SourceN=DataDirect 4.20 SQL Server Wire Protocol
[Your_Data_Source1]
Driver=PVmsss20.so
Description=DataDirect 4.20 SQL Server Wire Protocol
Address=xx.xx.xx.xx,1433
AnsiNPW=Yes
Database=CDR
QuoteId=No
[Your_Data_Source2]
Driver=PVmsss20.so
Description=DataDirect 4.20 SQL Server Wire Protocol
Address=xx.xx.xx.xx,1370
AnsiNPW=Yes
Database=CDR
QuoteId=No
[Your_Data_SourceN]
Driver=PVmsss20.so
Description=DataDirect 4.20 SQL Server Wire Protocol
Address=xx.xx.xx.xx,1433
AnsiNPW=Yes
Database=CDR
QuoteId=No
[ODBC]
IANAAppCodePage=4
InstallDir=/opt/datachannel/
Trace=0
TraceDll=/opt/datachannel/lib/odbctrac.so
TraceFile=odbctrace.out
UseCursorLib=0
All fields above which appear in italics must be configured according to your CallManager Publisher
environment, as follows:
Field
[ODBC Data
Sources]
IBM Tivoli Netcool/Proviso Cisco IP Telephony 2.4.0.0 Technology Pack
Description
One entry per CallManager Publisher.
Note:
The data source name must match the data source name specified in the corresponding
URI (Uniform Resource Identifier) parameter in the dc.cfg file. Each line in this
section should also be associated with a subsection that configures the data source.
Chapter 4: Configuring the technology pack
$DC_HOME/conf/odbc.ini
file as user
49