Data connection categories will not get captured in the TIBCO Spotfire action log database when data_con_pro,data_con_wp are used while enabling categories using config-action-logger command

book

Article ID: KB0075397

calendar_today

Updated On:

Products	Versions
Spotfire Server	10.9 and lower

Description

After enabling data connection categories from the TIBCO Spotfire Server command line using the names specified in Action log categories documentation (i.e data_con_pro,data_con_wp) then data connection categories will not get captured in the action log database as expected.

This is applicable only when those categories are enabled using command line config-action-logger. In this case, the action logs database will not capture anything in the database table for these categories. When using the TIBCO Spotfire Server configuration tool (Go to configuration tab > user action log ) the four categories data_con_pro, data_con_wp, data_connector_pro, and data_connector_wp. will be seen and all of them will be disabled.

This behavior is seen only when enabling these categories using the command config-action-logger by following the documented approach. For example:

>config config-action-logger --categories=data_con_pro,data_con_wp,<other categories>

This is because data connection category names (data_con_pro, data_con_wp) specified in documentation Action log categories are incorrect.

Resolution

To resolve, follow one of the approach mentioned below:

1. While enabling action log categories using the command 'config-action-logger', use the category names 'data_connector_pro' and 'data_connector_wp'.

For example:

>config config-action-logger --categories=data_connector_pro,data_connector_wp,<other categories>

2. Enable Action logs categories using configuration tool

Note: Documentation is planned to be updated with correct category names in a future versions.

Issue/Introduction

This article explains why data connection categories will not get captured in the TIBCO Spotfire action log database when enabling using CLI command "config-action-logger" and a resolution to it.