Novell has taken some lumps about management tools over the years, and with iManager they may or may not be warranted, that is up to the individual user. However, anyone who has struggled with iManager and adding plug-ins can relate to how frustrating it can be to correct issues once they occur. Locating information for configuring and yes, fixing, iManager can be frustrating to say the least.
Much of this information is available in online documentation, TIDs, and tech tips. Since I recently found a solution to one of the issues that has been plaguing me, I thought it would be “cool” to submit some of the tips and tweaks I’ve come across in one place.
First off, I only use iManager Workstation because 1) it does not require any server-side configuration, and 2) it runs much faster.
Configuring iManager Workstation
Another method is to add the proxy information to the iManager.bat file, see Preycor’s Technical Tip Configuring iManager 2.7 to Use a Proxy Server (http://www.novell.com/communities/node/4530/configuring-imanager-27-use-a-proxy-server)
We geeks always want to try to figure stuff out on our own, but sometimes it pays to check the documentation!
Problem: One of the more exasperating issues we have come across with iManager Workstation is that after unzipping the iManager Workstation files to the local drive and adding one or more plug-ins, iManager would stop showing additional windows such as the Object Selector window to browse for an object.
After much frustration attempting to get a working configuration of iManager (2.7) with plug-ins for Identity Manager 3.6, and no luck finding any help on the interwebz, I finally looked in the online documentation, and there it was in the Troubleshooting section. Whodathunk!!!
The following is from the Troubleshooting section of the iManager 2.7 Administration Guide:
Workaround: to check if the issue is with the embedded Mozilla browser included with iManager Workstation, start iManager and minimize it. Then open Firefox or Internet Explorer and type in http://localhost:48080/nps in the address bar. If iManager works fine in that browser, the above fix will likely be sufficient.
I’m still looking for how to configure iManager Workstation to run in Firefox rather than the embedded version of Mozilla included so if you find it, please share!