After you upgrade DXmanager, you must restart all Internet Explorer sessions running DXmanager before you can see the new functionality.
In addition, if you switch back and forth between different versions of DXmanager on the same computer, you must clear the Java cache each time you go back to the older version. For more information about how to clear the Java cache, see the Administration Guide.
In Internet Explorer 7, if you have logged in to DXmanager, closing the tab does not terminate the session. This means that if you re-open the tab, or open a new tab to the same address, the browser continues the session without requiring you to log in again. This can present a security risk.
To work around this issue, log out of DXmanager before you close the tab, or close the browser, not just the tab.
DXmanager can store only one port number and password for the DXadmind processes on every computer.
This means that during installation, you should set the same values for these on each host.
After installation, when you are using DXmanager to set up the directory backbone, you will specify the DXadmind port and password that you set during the installation.
After deploying a new configuration, DXmanager may incorrectly show a DSA as initializing, when the DSA is, in fact, stopped or running.
To update the state of the DSA and correct the display, do the following:
If these options are not available, restart CA Directory Webserver.
This will change the DSA to the selected state, and the display will be correct.
The following DXmanager chart issues exist:
To work around this issue, re-request the chart. To do this, navigate to a configuration page and then back to the main tabbed page for charts on the dashboard. Alternatively, clear then redefine a chart request for the charts tab.
If you deploy a configuration with invalid settings, DXserver will not start. Take care when entering configuration values.
Some second level drop-down menus display the options you can select at a random location on the screen. To work around this, select the second level tabs directly.
Monitoring in a pure IPv6 environment does not work. This means that DXmanager does not provide:
Note: Monitoring does work in an IPv4 or IPv4/IPv6 hybrid environment.
The following settings are not valid anymore and you must remove them before you upgrade:
set limit-list = true|false; set limit-search = true|false; set eis-count-attr = dxentrycount;
Copyright © 2009 CA. All rights reserved. | Email CA about this topic |