TNPM 1.3.2 Upgrade Browser Support
PatChan 270003GX11 Visits (4798)
TNPM (Wireline)1.3.2 - support for IE9 and Firefox ESR10
TNPM Wireline 1.3.2 now supports Internet Explorer 9 and Firefox ESR10 browsers. To enable this support, user needs to apply
Upgrade steps (in sequence):
The above upgrade steps were verified on a system that has TNPM 1.3.2 GA version installed. In the TNPN 1.3.2 GA version, the TIP installed is version 220.127.116.11 and TCR version is 2.1.1.
KNOWN ISSUES OR LIMI
Workaround is to create a new page for the same portlets and the portlets will render fine.
To create the new page, follow these steps:
a. As admin user, go to Settings > Pages > and click on “New Page” button. A new tab called “Create New Work Page” is started.
b. In Page Settings, key in Page name.
c. Under Page Location, click the Location button. Move the new Page into folder Performance > Network Events.
d. Click OK.
e. Under Page Layout, select Classic.
f. Under Optional Setting, assign access to page to Roles.
g. In “Choose a Portlet” page, click once on Horizontal Split option, in order to get two portlet windows on the same page. Then select
h. Click OK and Save.
Note: To view the AEL portlet content, you must assign roles ncw_user and ncw_admin.
3. Opening the Tivoli Common Reporting (TCR) page or the "User Preference Management" page in certain order may cause some rendering problem
a. If you need to open TCR page and other pages in the same browser, always open the TCR page last. However if you open TCR after opening
b. If you need to open the "User Preference Management" and other pages in the same browser, always open it last.
c. If you encounter page-rendering problem, closing the TCR page or the "User Preference Management" page will instantly restore the other
4. In TIP 18.104.22.168, when you are trying to assign roles to LDAP group, you may receive the following error:
“CWLAA6003: Could not display the portlet at this time, the portlet's module may be being updated.”
The role list will be empty. However, this problem will not occur if you assign roles to non-LDAP groups.
This is a known TIP problem that is tracked in APAR PM66220. Refer to the following Technical Note: