HABE

The following steps show how to implement exporting objects into IBM Tivoli Application Dependency Discovery Manager by using IBM Tivoli Directory Integrator:

1. Download the required package and install IBM Tivoli Directory Integrator:

a. IBM Tivoli Directory Integrator V6.1.1 was previously installed with Fix Pack 6. This integration requires IBM Tivoli Directory Integrator V6.1.1 with Fix Pack 1 or later. For information about installing IBM Tivoli Directory Integrator, see the IBM Tivoli Directory Integrator Administration Guide, SC32-1716, or go to this Web site:

http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/topic/com.

ibm.IBMDI.doc/adminguide.htm

b. From the IBM Open Process Automation Library Web site, download the Discovery Library Integration Framework package:

http://www.ibm.com/software/tivoli/opal/details?catalog.label=1TW 10CC1U

c. From the IBM Open Process Automation Library Web site, download the Discovery Library Integration Framework plug-in for IBM Tivoli Network Manager for IP package:

http://www.ibm.com/software/tivoli/opal/details?catalog.label=1TW 10CC1Y

2. Install the Discovery Library Integration Framework:

a. On the IBM Tivoli Directory Integrator server, copy the Discovery Library Integration Framework DLAtoCCMDB directory to the

$TDI_SOLUTION_DIR/DLAtoCCMDB directory.

b. Verify the Discovery Library Integration Framework version by viewing the

$TDI_SOLUTION_DIR/DLAtoCCMDB/DLAtoCCMDB.xml file. Find the line

<MetamergeConfig line, IDIversion=”TDI6.1.1-DIICommon1.2”.

Note: If loading IBM Tivoli Network Manager for IP data into IBM Tivoli Business Service Manager directly, copy the IBM Tivoli Network Manager for IP IDML book file to the IBM Tivoli Business Service Manager system in the

$TBSM_HOME/discovery/dlbooks directory. Ensure that the Discovery Library Toolkit is configured to not connect to IBM Tivoli Application Dependency Discovery Manager with the property DL_TADDM_Connect=false specified in the xmltoolkitsvc.properties file.

c. Install the Discovery Library Integration Framework plug-in for IBM Tivoli Network Manager for IP. Unzip the plug-in in the

$TDI_SOLUTION_DIR/DLAtoCCMDB directory. Verify that the tdi_ccmdb_itnm_plugin12.jar file exists in the

$TDI_SOLUTION_DIR/DLAtoCCMDB/TMS directory.

3. Configure the Discovery Library Integration Framework:

a. Launch the IBM Tivoli Directory Integrator configuration editor. Open the

$TDI_SOLUTION_DIR/DLAtoCCMDB/DLAtoCCMDB.xml file.

b. Right-click the “Includes” directory, and select Include→ New Include.

Enter the name ITNMDLA, and click OK.

c. Select ibmdiXML as the Config Driver. Under file, enter the full path to the ITNMDLA.xml file. The password is only required if the XML is

password-protected; leave this field blank for the OPAL package.

d. Save the selected configuration, and exit the IBM Tivoli Directory Integrator configuration editor.

e. Edit the $TDI_SOLUTION_DIR/DLAtoCCMDB/DLAtoCCMDB.properties file.

Edit the EnabledALs property. If IBM Tivoli Network Manager for IP is the only Discovery Library Integration Framework plug-in, change the contents to ITNMDLA:/AssemblyLines/ITNMtoCCMDB. If there are other Discovery Library Integration Framework plug-ins installed, append the ITNMDLA configuration to the end of the property. Example 5-9 illustrates the EnabledALs property.

Example 5-9 EnabledALs

#Enabled plug-ins

EnabledALs=ITNMDLA:/AssemblyLines/ITNMtoCCMDB

Remove invalid characters <93> and <94> from the header comments.

IBM Tivoli Directory Integrator will not be able to start with these invalid characters. Example 5-10 illustrates the invalid characters <93> and <94>.

Example 5-10 Remove invalid characters

#Licensed Materials - Property of IBM <93>Restricted Materials of IBM<94>

f. Create a Java wrapper script. Create

$TDI_SOLUTION_DIR/DLAtoCCMDB/calljava with the contents, as shown in Example 5-11 on page 171. Edit the executable location of Java Runtime Environment (JRE™) 1.5 and the full path to the TIPProfile for your environment.

Example 5-11 The calljava wrapper script

#!/bin/sh

/opt/IBM/tdi/jvm/jre/bin/java

-Duser.install.root=/opt/IBM/tivoli/tip/profiles/TIPProfile $*

g. Edit the $TDI_SOLUTION_DIR/DLAtoCCMDB/DLAtoCCMDB.properties file. Add the following properties:

itnmHost Host name of IBM Tivoli Network Manager for IP server

itnmDLADataSinkDir

This directory must match the

ncp.dla.datasink.targetDirectory directory in the

$NCHOME/precision/adapters/ncp_dla/ncp_dla.pr operties file. This directory must be empty every time that the assembly line executes.

itnmRemoteUser System user with access to the itnmDLADataSinkDir

itnmRemotePassword

Password for the system user. To encrypt, prefix the property as {protect}-itnmRemotePassword.

The password will be encrypted when the

Discovery Library Integration Framework process is started.

itnmConnectionType

Protocol to connect to the itnmHost. The options are ANY, SSH, RSH, REXEC, and WIN.

itnmJavaCommand The full path to the java wrapper script that was created in previous step.

itnmDLAJarName The file name of the ncp_dla jar file in the

$NCHOME/precision/adapters/ncp_dla/ directory.

itnmDLAProperties The file name of the ncp_dla properties file in the

$NCHOME/precision/adapters/ncp_dla/ directory.

itnmDLAPath The path to the ncp_dla directory.

Example 5-12 on page 171 illustrates the additional properties that have been added to the DLAtoCCMDB.properties file.

Example 5-12 Added properties in the DLAtoCCMDB.properties file

#ITNM properties

itnmHost=tnmip.itso.ral.ibm.com

itnmDLADataSinkDir=/opt/IBM/tivoli/netcool/var/precision/ccmdb

h. Edit the $TDI_SOLUTION_DIR/DLAtoCCMDB/DLAtoCCMDB.properties file. Edit the following properties:

ccmdbHost Host name of IBM Tivoli Application Dependency Discovery Manager system. This name is not used unless isTdiOnCcmdb is set to false.

isTdiOnCcmdb This property must be set to false when IBM Tivoli Directory Integrator is on a separate system.

ccmdbStagingDir The full path to the remote staging directory on the IBM Tivoli Application Dependency Discovery Manager server. This path must be created for this integration. Nothing else can exist in this directory, because the ccmdbUsername will delete the contents.

ccmdbUsername System user for connecting to the IBM Tivoli Application Dependency Discovery Manager system and invoking the bulk loader. This user must be the user running IBM Tivoli Application Dependency Discovery Manager.

{protect}-ccmdbPassword

The System password for ccmdbUsername. This password will be encrypted when IBM Tivoli Directory Integrator is started.

ccmdbComProtocol Protocol to connect to the ccmdbHost. The options are ANY, SSH, RSH, REXEC, and WIN.

ccmdbProcessedFilesDir

The directory on the IBM Tivoli Application Dependency Discovery Manager server that contains the processedfiles.list file.

bulkLoaderPath The full path to the loadidml executable.

useBulkLoadGraphWritingAlg

This property specifies whether the -g option will

want to use the -g option in the bulk import command, enter false.

logLevel IBM Tivoli Directory Integrator IBM Tivoli Application Dependency Discovery Manager integration log level. The options are DEBUG, INFO, WARN, ERROR, or FATAL.

logFilePath The log file path relative to the $TDI_HOME directory.

tdiStagingDir The staging directory for IBM Tivoli Directory Integrator to store IDML files relative to the

$TDI_HOME directory.

tdiBackupDir The backup directory for IDML files relative to the

$TDI_HOME directory.

scheduleMonth The month to run the bulk import.

January-December or enter * (asterisk) for every month.

scheduleDay The day of the month to run the integration. 1-31 or

* is every day.

scheduleWeekday The day of the week to run the integration.

Sunday-Monday or * is every weekday.

scheduleHour The hour to run the bulk import. 0-24 or * is every hour.

scheduleMinute The minute to run the bulk import.

Optional notification properties

These properties can be configured to send an e-mail when the import fails or succeeds. The notificationEvents property must be set to blank to disable notification.

Example 5-13 illustrates the properties that were edited in the DLAtoCCMDB.properties file.

Example 5-13 Edited properties in the DLAtoCCMDB.properties file

#CCMDB server details

isTdiOnCcmdb=false

i. On the IBM Tivoli Network Manager for IP system, edit the

$NCHOME/precision/adapters/ncp_dla/ncp_dla.properties file. Ensure the ncp.dla.precisionDomain property is set to the IBM Tivoli Network Manager for IP domain from which to export objects.

j. Start IBM Tivoli Directory Integrator. To run the IBM Tivoli Network Manager for IP export to IBM Tivoli Application Dependency Discovery Manager on a scheduled basis as defined in the DLAtoCCMDB.properties file, start IBM Tivoli Directory Integrator:

./ibmdisrv -c DLAtoCCMDB/DLAtoCCMDB.xml -r "Schedule Discoveries" &

To run a single IBM Tivoli Network Manager for IP export to IBM Tivoli Application Dependency Discovery Manager now and shut down, start IBM Tivoli Directory Integrator:

./ibmdisrv -c DLAtoCCMDB/DLAtoCCMDB.xml -r "Perform Discoveries"

4. Verification

To verify a successful import, view the

$TDI_SOLUTION_DIR/DLAtoCCMDB/log/DLAtoCCMDB.log file. Look for a message similar to Example 5-14 on page 174 that indicates a successful bulk load.

Example 5-14 DLAtoCCMDB.log file 2009-05-15 13:28:51,916 INFO

[AssemblyLine.AssemblyLines/ToCCMDB.789982998] - CTJDI0047I The processedfiles.list file indicates that the following file was successfully loaded by the TADDM Bulk Loader:

ITNMIP.9.42.171.29.2009-05-15T17.28.35.377Z.refresh.xml

Verify that the new objects are available in IBM Tivoli Application Dependency

In document QUINTO INFORME SOBRE EL CUMPLIMIENTO EN ESPAÑA DE LA CARTA EUROPEA DE LAS LENGUAS REGIONALES O MINORITARIAS, DEL CONSEJO DE EUROPA 2014 - 2016 ÍNDICE (página 166-174)