Platform Analytics 7 Dataflow

WI_LICENSEDENIALBYFEATUREMART table

This describes the wi_licensedenialbyfeaturemart table and how each column of data arises from the FLEXLM_LICENSE_EVENTS table.
The wi_licensedenialbyfeaturemart get its data from the FLEXLM_LICENSE_EVENTS table.
The record from the data file will go through the "Denial transformer" for calculating the number of denial for the license server. Once the time between the events is over the duration time, this transformer will output records for the number of denials for the server. Then, the ETL will aggregate these records for the hour and the count for the different feature for this hour is the number of denial and the result being put into this table.
This is the column description of each data column of WI_LICENSEDENIALBYFEATUREMART and how each column is filled with data.
Column Name
Description
Key
TIME_STAMP
This is in GMT and is always end in the hour such as 02:00:00. This marks the time that this record is aggregated. For example, 02:00:00 means that all the records between 02:00:00 and 02:59:00 are aggregated into this record.
Primary key
LIC_FEATURE_CODE
This comes from the "LIC_FEATURE_NAME" field in the FLEXLM_LICENSE_EVENTS table. Once we get the license feature, we then look it up in the wi_licfeaturecode table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the wi_licfeaturecode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing code+1.
Primary key
LIC_VENDOR_CODE
This comes from the "LIC_VENDOR_NAME" field in the FLEXLM_LICENSE_EVENTS table. Once we get the license vendor, we then look it up in the wi_licvendorcode table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the wi_licvendorcode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing code+1.
Primary key
USER_CODE
This comes from the "USER_NAME" field in the FLEXLM_LICENSE_EVENTS table. Once we get the user name, we then look it up in the wi_usercode table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the wi_usercode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing code+1.
Primary key
HOST_CODE
This comes from the "HOST_NAME" field in the data fileFLEXLM_LICENSE_EVENTS table. Once we get the host name, we then look it up in the wi_hostcode table to see if we have already has a record of it in there. If we do, then we'll get the code back, otherwise, we will insert it into the wi_hostcode table and generate the code. The code itself is a positive integer and each new code is equal to the maximum of the existing code+1.
Primary key
DENIALS
The number of denial for this feature, host, user from this server for the hour.

LOCAL_SERVERTIME
This comes from the "Time_stamp" in this table. This is transformed into local server time.

INSERT_SEQ
This is a system generated sequence number. For each new record inserted, a unique sequence number is being assigned to this column.