Programming Guides › Connector Programming Guide › Packaging and Deploying a Connector › Building and Debugging

Building and Debugging

After installing the SDK for CA IAM CS, refer to the README.txt file in the cs-sdk-home directory. The file explains how the ANT build harness works, and the recommended procedure for debugging.

However, to debug a production connector server remotely, there are some flags you are required to provide on the "java" command-line used to run CA IAM CS. You can refer to these flags in the following file:

cs-sdk-home/build/apache-servicemix-4.3.1-fuse-00-00/bin/servicemix_debug.bat

Use this file to invoke a development CA IAM CS. The flags are "-Xdebug -Xrunjdwp:server=y,transport=dt_socket,address=5005,suspend=n".

Note: For more information, see http://www.ibm.com/developerworks/opensource/library/os-eclipse-javadebug/index.html which is a useful reference article.

Be aware of the following:

• The example port chosen in this configuration (5005) can be varied as long as the Remote Java Application used to connect to the remote CA IAM CS server is also updated to match.
• The debug support in the JVM uses this port and is independent of the port on which CA IAM CS can be contacted, which is configured in server_jcs.properties and defaults to 20412 / 20413 (TLS) for SDK instances, and 20410 / 20411 for production CA IAM CS instances.
• If "suspend=y" is used instead of "suspend=n" then CA IAM CS does not proceed with its start-up sequence until a Remote Java Application attaches to it. This is useful if you want to debug the start-up sequence.
• The production CA IAM CS install uses procrun to launch JVM as a Windows service. To configure its command-line arguments use the Regedit operating system utility to change the following key:
  • 32-bit Windows: LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Identity Manager\Procrun 2.0\im_jcs\Parameters\Java
  • 64-bit Windows: LOCAL_MACHINE\Software\Wow6432Node
• The Options key contains the list of all options passed to the target JVM, add the debug arguments described previously.
• Restart the CA IAM CS service (or development JVM) after you change the command-line arguments.