IBM 4.3-W - page 466

Appendix A: Configuration

444 Netcool/Proviso Cisco IP Telephony Technology Pack User’s Guide, Version 4.3-W

Important: If you do not have a CUCM environment, skip Step 6 through Step 9, and continue

with Step 10.

6. CUCM environment only: On the DataChannel host, create a directory for each CUCM server from which

CDR, CMR, and Perfmon data files will be requested. For example, if you will be requesting data files from

two CUCM servers, you might create the following directories:

/opt/datachannel/cucm1

/opt/datachannel/cucm2

These directories will contain the ProvisoCUCM application and other files needed to send SOAP requests

to each CUCM server.

Note: If you will be requesting CDR and CMR data files through a master CUCM server, you need to create

just one directory for those requests. However, if you will be requesting Perfmon data, you must create a separate

directory for each CUCM server from which you will request Perfmon data.

7. CUCM environment only: Copy the following files into each one of the directories you just created in Step 6:

— ProvisoCUCM.jar

— cucm.properties

— startcucm.sh

— stopcucm.sh

These files were included in the technology-specific files you copied to DATA_CHANNEL_HOME/scripts

in step 2-e on page 441.

8. CUCM environment only: Configure each of the cucm.properties files you copied in Step 7.

Each cucm.properties file is associated with an instance of the ProvisoCUCM application that resides

in the same directory as the file. The ProvisoCUCM instance reads the cucm.properties file to find the

address and login credentials of the associated CUCM server, the address and login credentials of the

DataChannel host for the CUCM server to use when pushing the requested files via FTP back to the

DataChannel host, and other required configuration details.

The following table describes the fields in the cucm.properties files:

[Data Source Name] The configuration of the specified data source.

•[Data Source Name]: for example, [SANFRANCISCO]

•Address: the remote IP address and TCP port of the CallManager Publisher

Database (for example, 192.168.1.1,1433). To verify the remote connection

configuration, establish the connection manually from a shell window: telnet

xx.xx.xx.xx 1433 or telnet xx.xx.xx.xx 1370. The remote TCP

port can be 1433 or 1370 according to the SQL Server configuration.

[ODBC] A global section that defines the global environment for the bridge.

Field Description

cucm.host The IP address of the CUCM server associated with this properties file.

Examples:cucm.host=10.1.2.3

cucm.host=cucm.mycorp.com

cucm.port The port number for SOAP requests sent to the CUCM server.

Example: cucm.port=443