Set up logging in Nexus Card SDK
This article describes logging in Nexus Card SDK.
Logging in Card SDK is made in two categories:
- Generated by Card SDK itself: event log, system log and card jobs logging.
- Not generated by Card SDK: the general "Java Console" output. This is not specific to Card SDK. Instead it is a general debugging technique for all client side Java programs.
Card SDK does NOT use the Windows Event Logging system.
As a general rule for logging in Card SDK, try to keep the logs as small as possible in size. To achieve this, consider the following:
- Set up: When you are facing a reproducible error, it is a good idea to do all the preparation that you need to do, except for the final action that triggers the error. So click all the buttons you need to click, except for the final one.
- Cleanse: Before you do that error inducing action, completely DELETE/EMPTY the existing log files. (Or, if you wish, instead of deleting, move them to a backup directory.)
- Trigger: Do that error inducing action.
- Remember: Note down the EXACT time that you did the error inducing action. (Hint: take a screenshot and make sure to include the Windows system clock in it.)
- Collect: Collect the log files immediately. (So that they don't grow after the part that was actually interesting to you.)
Clean up the logs
After you're done, turn down the Log-Levels again (see "Set up System log" and delete any large logs. There is no automatic log rotation and no automatic log truncation. The logs will grow to be huge.
Logging generated by Card SDK
Card SDK event log
System log
Production job log
Java console logging
Copyright 2024 Technology Nexus Secured Business Solutions AB. All rights reserved.
Contact Nexus | https://www.nexusgroup.com | Disclaimer | Terms & Conditions