Filter
Top Products
Netcool/Precision for Transmission Networks 5.5 Administration Guide40
</properties>
<properties name="Netcool User Authentication">
<property name="jdbcuser" value="root" />
<property name="jdbcpwd" value="null" />
</properties>
-->
3. Replace the default property values in the file with the property values you need to
create a connection from the Netcool/Precision TN database to the ObjectServer
database:
–In the jdbcuser property, enter a valid ObjectServer user name with ISQL access.
The default is root.
–In the jdbcpwd property, enter the ObjectServer password for this user name. The
default is null.
4. Save and close the file.
Whenever Netcool/Precision TN starts, it uses this information to connect to the
ObjectServer database, enabling Netcool/OMNIbus users to log into Netcool/Precision
TN.
Configuring Netcool/OMNIbus probes
This section describes the configuration tasks you must complete for probes to ensure the
alerts are correctly processed by the Netcool/Precision TN server.
By default, Netcool/Precision TN does not forward or process traps and alarms from NEs.
Instead, the trap and alarm information is expected to be forwarded into
Netcool/OMNIbus via probes such as the Muti-threaded Trapd probe or TL1 TSM.
Netcool/Precision TN implements Netcool/OMNIbus gateway functionality in order to
enrich alerts so that they can be displayed in Netcool/Precision TN's alarm summaries,
backplane view, and topology view.
The configuration changes required by Netcool/Precision TN involves minor changes to
the probe rules files. Additionally, the rules file changes for any given probe are dependent
on the method of data collection employed by Netcool/Precision TN for the same NEs. For
example, changes to the Multi-threaded Trapd probe's rules file for NE's in which
Netcool/Precision TN collects data via SNMP will be different than those required for the
same probe when Netcool/Precision TN collects data via the Cisco WAN Manager.