I recently came across a situation where an MDM extension was working in the local development environment, but was failing on a remote test server. Bharat posted a remote debugging tip on our internal team blog a couple of years ago which can be useful when this sort of thing happens.

 

If you're using a remote server instead of a local development and test environment, as described in an earlier post, you may be able to simply restart the server in debug using the Servers view in the same way you would for a local server, as shown below:

 

 

If that's not possible, for example you need to debug something on a test server, you'll need to restart the server in debug or ask someone to do it for you. In the WebSphere administration console, click Servers > Server Types > WebSphere application servers and select server1. Click on Debugging service under Additional Properties. Check the Enable service at server startup option on this screen:

 

 

Note that I'm not using the default port here, which would be 7777 according to the documentation. Restart the server before continuing.

You should be ready to connect the debugger from your workbench using a new debug configuration. Click on the Run > Debug Configurations... menu option and create a new Remote Java Application configuration as shown below:

If you're debugging a specific project, enter it now, otherwise leave the project field blank. Before clicking Debug, make sure you provide the correct host and port details for the server you configured earlier.