Parts of the Access Manager administration console are not following the user locale preferences but instead using the browser locale settings. This problem affects the Version, Logout and online help buttons as well as the contents of the Version and online help.
Workaround: Change the browser settings to the same locale as user preferences.
In all European locales (Spanish, German, and French), the online help is not fully accessible when Access Manager is deployed on an IBM WebSphere Application Server instance. The online help displays “Application Error” for these frames:
Upper frame, where the Help and Close buttons should be.
Left frame, where the Contents, Index, and Search buttons should be.
Workaround: Set your browser language setting to English and refresh the page to access the left frame. The upper frame, however, will still display “Application Error.”
In any locale, when Access Manager is deployed on an IBM WebSphere Application Server instance, the product version is not visible when you click the Version button. A blank page is displayed instead.
The Client Detection function is not working properly. Changes made in the Access Manager 7 2005Q4 Console are not automatically propagated to the browser.
Workaround:There are two workarounds:
Restart the Access Manager web container after you make a change in the Client Detection section.
Follow these steps in the Access Manager Console:
Click Client Detection under the Configuration tab.
Click the Edit link for genericHTML.
Under the HTML tab, click the genericHTML link.
Enter the following entry in the character set list: UTF-8;q=0.5 (Make sure that the UTF-8 q factor is lower than the other character sets of your locale.)
Save, logout, and login again.
Multibyte messages in log files in the /var/opt/SUNWam/logs directory are displayed as question marks (?). Log files are in native encoding and not always UTF-8. When a web container instance starts in a certain locale, log files will be in native encoding for that locale. If you switch to another locale and restart the web container instance, the ongoing messages will be in the native encoding for the current locale, but messages from previous encoding will be displayed as question marks.
Workaround: Make sure to start any web container instances always using the same native encoding.