User guide

The UBAs handle processing of both inventory and metric data. Any number of
UBAs can be configured to handle this process with each UBA designated either as
accounting UBA or performance UBA. The number of UBAs are best scaled up to
load.
These XML files are then collected and processed, with the results presented in a
set of web-based reports. These reports are listed and described in Alcatel-Lucent
5620 SAM LogToFile 2.3.0.0 Technology Pack Reference.
Inventory
The Alcatel-Lucent 5620 SAM contains an object database that represents
the network resources and their relationships to other network resources. It
also represents some abstract resources and relationships. Services and
their subscribers are represented, along with their relationships to each
other and to the Service Access Point Queues.
Metrics
DataStage periodically receives the metrics file. The DataStage is notified
on every period about the metrics file availability. The SAM statistics are
then passed to the UBA for parsing and processing into Tivoli Netcool
Performance Manager metrics.
Figure 1 shows that the Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology
Pack manages the inventory of the resources and metrics, real, and abstract, in two
ways:
v Complete data collection for inventory
v Event-driven data collection for inventory
Complete data collection
In the complete data collection, DataStage sends SOAP/XML requests to
the Alcatel-Lucent 5620 SAM server for each SAM object type that is
needed to run the inventory and metric data collection. Specifically, the
request is for XML files that contain information about all instances of that
object type and metrics. The requests from DataStage specify result filter of
property values that are returned for each SAM object type. This filter
operation limits the set of property values to the values that matter to the
technology pack inventory.
DataStage partitions the Proviso database on IP address and merge metrics
and inventory into one CSV file per period per subchannel that is then
delivered to the UBAs in CSV format.
When the inventory and metrics are in separate bulk input files (as is the
case in the Alcatel-Lucent 5620 SAM environment), a technology pack
developer typically implements several types of bulk adapter design files,
as described in “Bulk adapter design files” on page 8.
Event-driven data collection for inventory
The Alcatel-Lucent 5620 SAM LogToFile uses the JMS to view real-time
events and alarm feed information from the managed network. For more
information, see the Alcatel- Lucent 5620 SAM-O OSS Interface Developer
Guide. DataStage establishes a JMS connection with SAM to receive
inventory updates and notices of metric data file availability. SAM JMS
client daemon listens for JMS messages from SAM and passes them to
Apache ActiveMQ queue. DataStage job reads the messages from the
queue and processes them.
Chapter 1. Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack overview 3