Table of Contents
Advertisement
Unable to create AdminNamespace. java.lang.NoClassDefFoundError when
authenticating on SLES 9.
Work around: Install
before installing iManager 2.7.
compat-libstdc++-33-3.2.3-61.i386.rpm
4.5 Plug-In Compatibility
Because of changes to class structure and organization, iManager plug-ins must be recompiled to
work with iManager 2.7. The iManager 2.7 Web site contains all currently available plug-ins, and
will be regularly updated with additional plug-ins when they are available. If you add an older plug-
in using Add Plug-in link, it does not display an error even though the plug-in is not added. You can
view specific error information in the debug log.
Similarly, the OES 2 download includes the currently available iManager 2.7 plug-ins.
NOTE: iManager 2.7 does not allow the user to install old plug-ins that iManager 2.6 supported.
4.6 iManager Login Page Issues
Be aware of the following login-related issues with iManager 2.7:
4.6.1 iChain Single Sign-On (SSO)
The iChain Single Sign-On functionality (including Forward authentication, OLAC, and Form Fill)
does not work in a multi-tree environment. iManager 2.7 requires a user name, password, and tree
name for login, whereas iChain requires only user name and password.
Form Fill from iChain also fails because the Exit button in the iManager toolbar directs you back to
the initial login form. When Form Fill is active, you are simply logged back in to iManager.
In a single server environment, it is possible to use the iManager default settings and iChain will
work correctly.
4.6.2 NetIdentity Login
For the same reasons as iChain SSO, NetIdentity can cause problems with iManager login.
When using iManager 2.7 on a NetWare 6.5 SP3 server that was previously running iManager 2.x
and Virtual Office, NetIdentity clients see a NetIdentity login dialog box that only requires user
name and password, instead of the iManager login dialog box that requires user name, password,
and tree name.
4.7 International Characters Might Not Display Correctly
During Install
If, during the installation, there are problems with the display of the characters, you might need to
change the system's character encoding to UTF-8.
Installing remotely through an ssh client might also require UTF-8 character encoding on the client
to display characters properly.
For example, set the system variable LC_ALL=de_DE.utf8, then try running the install again.
8
iManager 2.7.3 Field Patch (FTF) 4 Readme
Advertisement
Table of Contents
