Tracing

Tracing is available only for those business adapters running in connected mode (that is, on your central application server).

Tracing adds another stream of information, additional to logging outputs, to make debugging easier. It is controlled from the adapter node in the structure tree. Tracing outputs are written to the BusinessImportLogDetail table in the compliance database under FlexNet Manager Suite, regardless of the logging output type that you selected. You can inspect the rows of this table in Microsoft SQL Server Management Studio.

To configure tracing (connected mode only):

Select the adapter node in the structure tree, and scroll down the settings page to see the Tracing group.
Figure: Tracing settings are at the bottom of the settings page for the adapter

Adjust the following settings for tracing:

Setting Notes

Setting	Notes
Activate tracing for	Select as many of the following check boxes as needed for the tracing you require for debugging your adapter. Note that if no check boxes in this group are selected, no tracing records are created. You may create a tracing entry each time that any record in the compliance database is created, updated, or deleted; or when a record in the source data is rejected. Rejected records are incoming data assessed for import but not accepted. A common reason for rejection is that a column (such as a serial number) has been specified for database matching, but that column is blank for a particular record.
Column(s) for tracing	By default, tracing identifies affected records only by their count number within the flow of incoming data from the external source. As this is not a convenient aid to debugging, you may also pick one or more columns from the incoming data to help identify the tracing records. For example, if you selected a column called `Serial No` from this drop-down list of the available columns in the data source, and the computer with serial number 19283645 was rejected, the tracing would identify `Record 238, Serial No 19283645` This is more convenient for identifying the offending record. Best practice is to use an identifying column that contains unique values and is always populated. You may either: Select a single column name (in the external data source) from this drop-down list Directly enter multiple column names in the field, enclosing each in square brackets and separating the bracketed values with a comma.

Activate tracing for

Select as many of the following check boxes as needed for the tracing you require for debugging your adapter. Note that if no check boxes in this group are selected, no tracing records are created. You may create a tracing entry each time that any record in the compliance database is created, updated, or deleted; or when a record in the source data is rejected. Rejected records are incoming data assessed for import but not accepted. A common reason for rejection is that a column (such as a serial number) has been specified for database matching, but that column is blank for a particular record.

Column(s) for tracing

By default, tracing identifies affected records only by their count number within the flow of incoming data from the external source. As this is not a convenient aid to debugging, you may also pick one or more columns from the incoming data to help identify the tracing records. For example, if you selected a column called Serial No from this drop-down list of the available columns in the data source, and the computer with serial number 19283645 was rejected, the tracing would identify Record 238, Serial No 19283645 This is more convenient for identifying the offending record. Best practice is to use an identifying column that contains unique values and is always populated.

You may either:

Select a single column name (in the external data source) from this drop-down list
Directly enter multiple column names in the field, enclosing each in square brackets and separating the bracketed values with a comma.

FlexNet Manager Suite (On-Premises)

2022 R1