Hiubert,
There’s actually a way that you can hook Eclipse up to the Integration Server, which allows you to debug Java services without having to use pipeline files and etc.
It’s been a while since I set this up, but I’ll try to remember the details. The basic idea is to create an Eclipse project in the same folder as your IS package folder and with the same name as the package that you’re trying to debug. Set the project’s source folder to the packages code/source folder and set the project’s output folder to the packages code/classes folder. Then, you need to add some parameters to your IS JVM that give Eclipse a hook to connect into. I believe the parameters I used were:
-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,address=4444,suspend=n
Once you start your IS and you’re ready to debug your Java service, you’d open Eclipse’s Debug Dialog box and you’d configure a Remote Java Application and point to the port specified in your JVM parameters (ex.: 4444). Click Debug. Now, when you run, step into, or step over a Java service in the Developer, you should see control being transferred to Eclipse and you can step through your code there.
I first learned about this by looking at an environment that was already setup this way, but I’m sure there’s good documentation out there from Sun and Eclipse that will give you a better understanding of how it all works and how to set it all up. The information I gave you here should be good enough to get you started though.
#Flow-and-Java-services#webMethods#Integration-Server-and-ESB