Product Documentation
Abstract
After upgrading to IBM Planning Analyltics 2.0.2, you might find that servers that were previously configured for monitoring are no longer visible in Operations Console. Similarly, Watchdog rules might not work as expected after upgrade.
Both of these issues occur when there are spaces in a user name, either the user name used to log into Operations Console or a user name referenced in a Watchdog rule.
Content
Servers no longer visible after upgrade
The Operations Console stores user configuration information in a directory with a name based on the user name. Spaces in that directory name where found to cause a defect in accessing log information. The solution to this was to replace spaces in directory names with the plus sign (+) in Operations Console 2.0.2 directories.
For example, prior to upgrading to Planning Analytics 2.0.2, the user configuration information for a user named "Joe Doe" was stored in a directory named "Joe Doe". After the upgrade, the user configuration information for "Joe Doe" is stored in a directory named "Joe+Doe". Note that the old directory and the configuration information in it is not deleted during the upgrade process.
The consequence of this change is that when a user with a space in the user name logs on after the upgrade, Operations Console looks for configuration information in the directory with the plus sign (+). If the configuration information is not present, Operations Console treats the user as a new user.
To address this issue, copy configuration information for any user with a space in the user name from the old directory to the new directory that includes plus sign (+). This can be done in two ways:
- If you have direct access to the computer where the Operations Console is installed, you can create the new directory on that machine, then copy and paste the user configuration information into that directory. The default location for Operations Console configuration data is <tm1_install_dir>\bin64\opsconsoledata. Directories for each user are under the server or CAM namespace that they log in as.
- It is also possible to use the Action menu on the Operations Console to download and save a user configuration and then upload again as a new user. In this case, you must downloaded the user configuration before the upgrade and then upload as a new user after the upgrade.
Watchdog rules don't work after upgrade
If any of your Watchdog rules reference a user name with spaces, you will see errors similar to this in the tm1_messages.log file, located in the <tm1_install_dir>/logs directory.
[5/19/17 15:04:19:907 EDT] 0000004b com.ibm.ba.pm.opsconsole.monitor.common.utils.XMLUtils E
Unable to get User java.util.ConcurrentModificationException
[5/19/17 15:04:19:909 EDT] 0000004b m1.rest.handlers.OpsConTM1RealtimeMonitorDataEnhancedHandler E Specified server was not found [id] = root$$$<a group defined>$OperationGroup$$$localhost$AdminHost$$$sdata$TM1Server
This error occurs when there is a user name with spaces referenced in the TM1OpsConsoleWatchDog.xml file, located in <tm1_install_dir>\bin64\opsconsoledata. For example, the following Watchdog rule references the user name "joe doe".
<WatchDog id="localhost$$sdata" user="localhost_$_sdata_$_joe doe">
To resolve this issue:
- Stop the IBM Cognos TM1 service.
- Open the TM1OpsConsoleWatchDog.xml file.
- Change any user names that include spaces to use a plus sign (+) in place of spaces. For example, change "joe doe" to "joe+doe".
- Save the TM1OpsConsoleWatchDog.xml file.
- Restart the IBM Cognos TM1 service.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27049952