Hi everyone, I have a TDI question (maybe a bit trivial, I hope).

I have a Java class that I developed, which is called by a TDI assembly. I would like to debug this class when it is invoked by TDI itself.

Now, the main issue is this: I want the TDI server (the one launched from the Configuration Editor) to run with the correct JVM parameters so that remote debugging is enabled. Assuming that the parameters I would pass to the JVM are correct, the question is: where should these parameters be set?

I tried looking into the solution.properties file and searching online, but with little success.

The idea is to launch the server in debug mode and perform remote debugging from Eclipse.

Thanks in advance for your time and your guidance.

Wauvv ! - I have not expected anybody going down this route - I am not alone anymore ! :-) 

You need to specify it in the ibmdisrv file - in my windows 7.2 system I have done this successfully with Eclipse using this line to start the SDI server : 

"%TDI_JAVA_PROGRAM%" -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8888 -classpath "%TDI_HOME_DIR%\IDILoader.jar" %ENV_VARIABLES% com.ibm.di.loader.ServerLauncher %* 

This is just working very nicely (I really love the Eclipse debugger - I would like to be able to improve the SDI a little bit so that e.g. breakpoints was as easy to manage as in Eclipse - there is so much potential in the SDI debugger for making it even better than it is today...)

HTH

Hi everyone, I have a TDI question (maybe a bit trivial, I hope).

I have a Java class that I developed, which is called by a TDI assembly. I would like to debug this class when it is invoked by TDI itself.

Now, the main issue is this: I want the TDI server (the one launched from the Configuration Editor) to run with the correct JVM parameters so that remote debugging is enabled. Assuming that the parameters I would pass to the JVM are correct, the question is: where should these parameters be set?

I tried looking into the solution.properties file and searching online, but with little success.

The idea is to launch the server in debug mode and perform remote debugging from Eclipse.

Thanks in advance for your time and your guidance.

Great! I can't wait to try it (as soon as possible).

I'll let you know of course.

Thank you!

Wauvv ! - I have not expected anybody going down this route - I am not alone anymore ! :-) 

You need to specify it in the ibmdisrv file - in my windows 7.2 system I have done this successfully with Eclipse using this line to start the SDI server : 

"%TDI_JAVA_PROGRAM%" -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8888 -classpath "%TDI_HOME_DIR%\IDILoader.jar" %ENV_VARIABLES% com.ibm.di.loader.ServerLauncher %* 

This is just working very nicely (I really love the Eclipse debugger - I would like to be able to improve the SDI a little bit so that e.g. breakpoints was as easy to manage as in Eclipse - there is so much potential in the SDI debugger for making it even better than it is today...)

HTH

Hi everyone, I have a TDI question (maybe a bit trivial, I hope).

I have a Java class that I developed, which is called by a TDI assembly. I would like to debug this class when it is invoked by TDI itself.

Now, the main issue is this: I want the TDI server (the one launched from the Configuration Editor) to run with the correct JVM parameters so that remote debugging is enabled. Assuming that the parameters I would pass to the JVM are correct, the question is: where should these parameters be set?

I tried looking into the solution.properties file and searching online, but with little success.

The idea is to launch the server in debug mode and perform remote debugging from Eclipse.

Thanks in advance for your time and your guidance.

It works like a charm!

Thank you!

Great! I can't wait to try it (as soon as possible).

I'll let you know of course.

Thank you!

Wauvv ! - I have not expected anybody going down this route - I am not alone anymore ! :-) 

You need to specify it in the ibmdisrv file - in my windows 7.2 system I have done this successfully with Eclipse using this line to start the SDI server : 

"%TDI_JAVA_PROGRAM%" -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8888 -classpath "%TDI_HOME_DIR%\IDILoader.jar" %ENV_VARIABLES% com.ibm.di.loader.ServerLauncher %* 

This is just working very nicely (I really love the Eclipse debugger - I would like to be able to improve the SDI a little bit so that e.g. breakpoints was as easy to manage as in Eclipse - there is so much potential in the SDI debugger for making it even better than it is today...)

HTH

Hi everyone, I have a TDI question (maybe a bit trivial, I hope).

I have a Java class that I developed, which is called by a TDI assembly. I would like to debug this class when it is invoked by TDI itself.

Now, the main issue is this: I want the TDI server (the one launched from the Configuration Editor) to run with the correct JVM parameters so that remote debugging is enabled. Assuming that the parameters I would pass to the JVM are correct, the question is: where should these parameters be set?

I tried looking into the solution.properties file and searching online, but with little success.

The idea is to launch the server in debug mode and perform remote debugging from Eclipse.

Thanks in advance for your time and your guidance.