• Share
  • ?
  • Profiles ▼
  • Communities ▼
  • Apps ▼

Blogs

  • My Blogs
  • Public Blogs
  • My Updates

This community can have members from outside your organization. MDM Workbench

  • Log in to participate

▼ Tags

▼ Similar Entries

Wednesday at Think 2...

Blog: The Invisible...
ebl1276 100000J3SK
Updated
0 people like thisLikes 0
No CommentsComments 0

Tuesday at Think 201...

Blog: The Invisible...
ebl1276 100000J3SK
Updated
0 people like thisLikes 0
No CommentsComments 0

Monday at Think 2018...

Blog: The Invisible...
ebl1276 100000J3SK
Updated
0 people like thisLikes 0
No CommentsComments 0

At Think2018? DevOps...

Blog: The Invisible...
ebl1276 100000J3SK
Updated
0 people like thisLikes 0
No CommentsComments 0

Configure & Test the...

Blog: GBS OpenPages...
Sudarsan AVS 50SUGBJBDM
Updated
0 people like thisLikes 0
No CommentsComments 0

▼ Similar Ideas

Global configuration...

Ideation Blog: WebSphere App...
m.fatih 3100001ATT
Updated
No Votes 0 No CommentsComments 0

▼ Archive

  • September 2012
  • January 2012
  • November 2011
  • October 2011
  • September 2011
  • July 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010

▼ Links

  • MDM Workbench FAQ
  • MDM Workbench Forum
  • MDM Developers group

▼ Blog Authors

MDM Workbench

View All Entries
Clicking the button causes a full page refresh. The user could go to the "Entry list" region to view the new content.) Entry list

Debugging a remote MDM Server

jtonline 110000B6Y8 | | Tags:  debugger mdm-workbench mih-workbench test eclipse mih-server websphere mdm-server debugging remote debug ‎ | 1 Comment ‎ | 11,506 Views
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:
 
image 
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:
 
image
 
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:

image
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.

  • Add a Comment Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry
Notify Other People
notification

Send Email Notification

+

Quarantine this entry

deleteEntry
duplicateEntry

Mark as Duplicate

  • Previous Entry
  • Main
  • Next Entry
Feed for Blog Entries | Feed for Blog Comments | Feed for Comments for this Entry