System information

Using the Profiler to Troubleshoot Performance Problems
Page 176 Identity Manager 7.1 Update 1 • Release Notes
Using the Identity Manager IDE Debugger
Q: The Identity Manager IDE Debugger is sluggish. What could be causing this problem?
A: To improve the Debugger’s performance:
•Always disable Tomcat's HTTP Monitor, as follows:
a. Select the Identity Manager IDE Runtime Tab.
b. Expand the Servers node and right-click Bundled Tomcat > Properties.
c. Disable the Enable HTTP Monitor option, and then close the dialog.
The next time you start Tomcat, the HTTP Monitor will be disabled.
• If you are not debugging Java, select Project > Run Project, and then select
Attach Debugger > Identity Manager XML Object Debugger to use just the XPRESS
Debugger.
Selecting Project > Debug Project for a non-remote Identity Manager IDE project starts both
the XPRESS Debugger and Java Debugger, and the Java Debugger adds substantial
overhead.
Q: I cannot set a breakpoint in the Debugger. What could be causing this problem?
A: The following conditions might prevent you from setting a breakpoint:
• You just installed the NBM, but did not restart Netbeans.
• Your XML contains a
<Waveset> wrapper element.
The Identity Manager IDE basically ignores any file that starts with a
<Waveset> wrapper
element because the Identity Manager IDE parses that element as a multi-object file.
The following features do not work on multi-object files:
❍ Debugger
❍ Rule Tester
❍ Form Previewer
❍ Any of the editors
❍ Import file generator
❍ Upload Object
❍ Diff Object
Basically, all you can do with multi-object files is import them. The only files that should
contain
<Waveset> wrapper elements are your project’s top-level import files.