Cognos Metrics post-uninstall check
About this task
- Everything pertaining to Cognos® in WebSphere® Application Server should be removed. Note: Check the first point in the WebSphere® Application Server administrative console of Deployment Manager and the local node.
- For a federated, clustered node:
- On Deployment Manager, the Cognos® application is removed
- On Deployment Manager, there is no Cognos® server
- On Deployment Manager, there is no Cognos® node
- On Deployment Manager, there is no Cognos® cluster
- On the node where Cognos® was installed, there is no Cognos® application
- On the node where Cognos® was installed, there is no Cognos® server
- For standalone:
- Cognos® application in WebSphere® Application Server administrative console of the node
- Cognos® server in WebSphere® Application Server administrative console of the node.
- For a federated, clustered node:
- Cognos® BI, Transformer installation folders are deleted.
- Power Cube® folder is deleted.
- Scheduled Tasks are removed.Note: To check that scheduled tasks for Metrics have been removed:
- On Windows™: Under ensure that MetricsCubeDailyRefresh and MetricsCubeWeeklyRebuild do not appear in the Active Tasks list.
- On AIX® or Linux™:
- Run #crontab -l in the terminal.
- Ensure that neither %Cognos_Transformer_install_path%/metricsmodel/daily-refresh.sh nor %Cognos_Transformer_install_path%/metricsmodel/weekly-rebuild.sh appear. (%Cognos_Transformer_install_path% is the folder where you installed Transformer.)
Note: After the uninstall of a secondary Cognos® BI
server, a folder with the name of the other nodes (usually the primary node) still will be in
%was_profile_path%/installedApps (for example,
%was_profile_path%/installedApps/%primary_node_name%). These files remain
because of federation. You can delete them after the uninstallation, however there is no harm in
letting them remain and they will not interfere with reinstallation of a secondary BI
server.