Designer 10.7 | webMethods Service Development Help | Debugging Java Services | About Debugging a Java Service while it Runs in Integration Server | Drawbacks of Debugging Java Services Running in Integration Server
 
Drawbacks of Debugging Java Services Running in Integration Server
The drawbacks of debugging a Java service that is running in Integration Server are:
*It requires more manual setup both in Integration Server and in Designer.
*If Integration Server and Designer run on different machines:
*You must logically map a drive from Designer to the Integration Server. For more information, see Creating a Java Project for an IS Package in Designer .
*If you use a firewall, you might need to open a firewall port to use while debugging. For more information, see either Setting Up Integration Server Version 9.7 or Later for Remotely Debugging a Java Service or Setting Up Integration Server Version 9.0, 9.5.x, or 9.6 for Remotely Debugging a Java Service.
*If you set breakpoints in a Java service, the execution suspends every time you execute the Java service, whether you are debugging it from Designer, running it from Integration Server Administrator, or running it from an IS client.
*Running Integration Server with the debug port enabled degrades the server’s performance.
Related Topics
Benefits of Debugging Java Services Running in Integration Server
About Debugging a Java Service while its Class Runs in Designer