User guide

Bulk input file formats
DataStage produces one file for each UBA per period. These files contain records of
inventory and metric data.
The inventory and metrics data records are in the CSV format. The initial integer
identifier of the CSV files specifies a record type, and the subsequent fields contain
the actual data of the record. The output CSV file from the DataStage has two
sections:
1. Header
2. Data
Header starts with 0 (zero), and is called as the 0-record schema. Data starts with
record type, which is identical to the one that is defined in the header.
Sample Header
0,"{""recordType"":17,""dataType"":""C"",""className"":
""equipment.Shelf"",""fieldNames"":[""administrativeState"",
""deviceState"",""displayedName"",""equipmentState"",
""numberOfCardSlots"",""objectFullName"",""operationalState"",
""shelfId"",""shelfName"",""shelfType"",""siteId"",""siteName""]}"
Sample data
17,"noop","deviceStateUnknown","sim242_60","indeterminate","12",
"network:138.120.242.60:shelf-1","unknown","1","sim242_60",
"sr_shelf_12Slot","138.120.242.60","sim242_60"
Bulk input file schema
The UBA input has a schema that works on CSV input files. The general format of
a CSV file is as follows:
0, "{“recordType”: 1, ”dataType”:”input source”, “className”: “TheClassName”,
“fieldNames”: [“field1”, “field2”, ... “fieldn”]}"
recordType
Specifies an integer that is used to identify the record format.
dataType
Specifies the source of the record data. The sources can be "A", "D", "C", or
"M".
The following list contains the definition of 0-Record CSV data type:
v A - Attribute Change
v D - Object Deletion
v C - Object Creation or Full dump
v M - Metrics
Note: The JMS inventory messages are identified by data types of A, D
and C.
className
Specifies the Alcatel-Lucent class name that is used to identify the class
(inventory or metric) that this record belongs to. The class name is used by
the UBA to identify the mapping between the class and the record
identifier.
fieldNames
Specifies an array of the field names that is available within the record that
is defined.
Chapter 2. Devices and services 7