Question & Answer
Question
When working with the IBM Security Access Manager v2 Connector, issues may occur during interactions with the ISVA API. To assist with troubleshooting and root cause analysis, this document will enable detailed logging to capture diagnostic information related to ISVA API?
Answer
1. Stop all SDI Java processes
If this is a standard SDI Server, stop all java related processes.
If this is an ISVG Dispatcher deployment, stop the Dispatcher service
2. Create the
In the Solution Directory (e.g.,
2. Create the
rgylog.properties fileIn the Solution Directory (e.g.,
timsol for ISVG Dispatcher), create a file named rgylog.properties and populate it with the necessary logging configuration properties.
handlers=java.util.logging.FileHandler, java.util.logging.ConsoleHandler
com.tivoli.pd.rgy.ldap.level=FINEST
com.tivoli.pd.rgy.authz.level=FINEST
java.util.logging.FileHandler.pattern=rgyDirect.log
java.util.logging.FileHandler.limit=50000000
java.util.logging.FileHandler.count=10
java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter
java.util.logging.ConsoleHandler.level=INFO
java.util.logging.ConsoleHandler.formatter=java.util.logging.SimpleFormatter
3. Update the SDI startup script with the logging parameter
Update the
$SDI_Install_Directory/ibmdisrv script to include the following JVM parameter after the $TDI_MIXEDMODE_FLAG argument:
-Djava.util.logging.config.file="$TDI_SOLDIR/rgylog.properties"
ℹ️ NOTE:
$TDI_SOLDIR is an environment variable automatically set when the ibmdisrv script runs. You do not need to modify or replace this value.Example full command:
"$TDI_JAVA_PROGRAM" $TDI_MIXEDMODE_FLAG -Djava.util.logging.config.file="$TDI_SOLDIR/rgylog.properties"
ℹ️ NOTE: Windows Service Deployments:
If the SDI Server or ISVG Dispatcher is running as a Windows service, update the
If the SDI Server or ISVG Dispatcher is running as a Windows service, update the
jvmcmdoptions property in the ibmdiservice.props file to include the following parameter:
-Djava.util.logging.config.file="$TDI_SOLDIR/rgylog.properties"
4. Restart SDI
After applying the changes, restart the SDI runtime or Dispatcher service.
5. Review the generated log
Once the ISVA API is invoked, a log file named
rgyDirect.log.0 will be created in the Solution Directory. This log will capture the API-level diagnostic information.ℹ️ NOTE: If the SDI_Install_Directory is used as the SDI_Solution_Directory, please make proper reference changes to the instructions above.
[{"Product":{"code":"SSCQGF","label":"Tivoli Directory Integrator"},"Business Unit":{"code":"BU008","label":"Security"},"Component":"General","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1.1;7.2","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Was this topic helpful?
Document Information
Modified date:
06 June 2025
UID
swg21976579