Connector Migration from V1 to V2 - How to generate logging
search cancel

Connector Migration from V1 to V2 - How to generate logging

book

Article ID: 271879

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Manager

Issue/Introduction

The product documentation mentions that the -l parameter can be used with a logging.properties file to generate logging but does not mention what the logging.properties file should contain:

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-management-and-governance-connectors/1-0/connectors/ca-connectors/ca-top-secret/how-to-migrate-data-from-the-plug-in-connector-to-the-new-java-connector/tssv2migrate-migrate-data-from-old-plug-in-connector-to-new-connector.html

Environment

All Identity Manager

Resolution

Create a new file (i.e. logging.properties) which contains the following: and then reference that file with the -l parameter. In this example file contents it will capture ALL logging to a new migration.log file. 

handlers = java.util.logging.FileHandler, java.util.logging.ConsoleHandler
.level = ALL

# File Logging
java.util.logging.FileHandler.pattern = migration.log
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
java.util.logging.FileHandler.level = ALL

# Console Logging
java.util.logging.ConsoleHandler.level = ALL