User guide

v Verify that the bulk adapter design files (*.js), scripts, other files (if any)
are now in the $ cd DATA_CHANNEL_HOME/scripts/
alcatel_5620_sam_log2file directory.
3. Copy the samOss.jar file to the IBM InfoSphere Information Server. The
samOss.jar file is distributed on a SAM distribution DVD referred to as the
5620 SAM software DVD-ROM, and is in the following directory:
<SAM_ROOT_RELEASE_DIR>/nms/integrations/SAM_O,
You must copy the samOss.jar file from the directory on the DVD to the
/opt/IBM/InformationServer/Server/Projects/UDM/udm/jar directory.
4. Activate data collection requests. During installation of the technology pack, all
predefined data collection requests are promoted to the database and set to
inactive (that is, idle displays in the Active column of the Tivoli Netcool
Performance Manager DataMart Request Editor). You must activate these
predefined data collections requests by using the Request Editor. To set data
collection requests to active, follow these steps:
a. Change your working directory to $PVMHOME/bin (/opt/datamart/bin,by
default) on the DataMart server.
b. Start the DataMart GUI by entering the following command and pressing
Enter:
$ pvm
c. Click the Configuration tab, then click Request Editor to open the Request
Editor.
d. Click the Collection tab.
e. Click Refresh. The predefined data collection requests are loaded into the
Request Editor from the database.
f. Click the Inactive button in the Filter group box to display only idle
requests.
g. In the Sub-Element Groups pane, select all idle data collection requests in
the following group or groups: Root->Sub-Element Collect->Alcatel-
Lucent 5620 SAM
h. Click the Active box under Details. The Request Editor toggles the idle
setting for these data collection requests from idle to active in the Active
column.
i. Click Save.
5. Load the DataChannel environment. In subsequent steps, you can run the
dccmd commands. To ensure that you can run these commands, load the shell
with the DataChannel environment by following these steps:
a. Log in to the DataChannel server as pvuser.
b. Change your working directory to the DataChannel home directory
(/opt/datachannel, by default), by using the following command:
$ cd /opt/datachannel
c. Load the shell with the DataChannel environment, by sourcing the
dataChannel.env file, as follows:
$ . /opt/datachannel/dataChannel.env
6. Restart the DataChannel to activate the UBA and read in changes to the
deployed topology.
a. Open a terminal emulator on the DataChannel server.
b. Use the dccmd command to stop all DataChannel applications:
$ dccmd stop all
c. Use the dccmd command to release all daemons that are running in the
DataChannel:
Chapter 7. Configuring the technology pack 47