Product:
Planning Analytics 2.0.9.19
Microsoft Windows 2019 server
Issue:
Do you have a checklist to help out with the upgrade/installation of Planning Analytics?
Solution:
Best is if you create a checklist that cover the needs of your environment, but here is a suggested to be used as a starting point.
Download from here: https://www.ibm.com/support/pages/ibm-planning-analytics-local-20919-now-available-download-fix-central-0
Detail upgrade instruction here: https://www.ibm.com/docs/bg/planning-analytics/2.0.0?topic=configuration-upgrading-planning-analytics-local
| Action | Date | |
| Copy the media to local hard disk on server | d:\install | |
| Export configuration from cognos configuration to backup folder | d:\temp\backup | |
| Backup samples folder D:\Program Files\ibm\cognos\tm1_64\samples\tm1 | ||
| Backup the tm1web_config.xml for TM1WEB from:
D:\Program Files\ibm\cognos\tm1web\webapps\tm1web\WEB-INF\configuration |
||
| Backup server.xml and jvm.options and bootstrap.properties files from folder:
D:\Program Files\ibm\cognos\tm1web\wlp\usr\servers\tm1web |
||
| Backup of your PAA Agent bootstrap.properties file in folder:
D:\Program Files\ibm\cognos\tm1_64\paa_agent\wlp\usr\servers\kate-agent |
||
Export the TM1 applications as a backup – the data is saved in the TM1 data folder.
|
||
| Backup home.jsp in folder D:\Program Files\ibm\cognos\tm1web\webapps\tm1web | ||
| Backup CommonMessages.js in folder D:\Program Files\ibm\cognos\tm1web\webapps\tm1web\scripts\tm1web\common\nls\sv | ||
| Backup Tm1WebAppCam.js in folder D:\Program Files\ibm\cognos\tm1web\webapps\tm1web\scripts\tm1web\standalone | ||
| Backup pa_header.svg file in D:\Program Files\ibm\cognos\tm1web\webapps\tm1web\scripts\tm1web\themes\carbon\standalone\images\login | ||
| If HTTPS is used, backup all certificate stores | ||
| Ensure that anti-virus or Windows Defender SmartScreen is turned off on the server during installation | ||
| Uninstall Planning Analytics Performance modeler from the windows server before you install the upgrade of TM1 | ||
| Check that firewall ports between servers are open
https://cogknowhow.tm1.dk/archives/4147 https://www.ibm.com/support/pages/client-shows-list-tm1-servers-cannot-connect-any-them |
Port 25, 80, 9300, 9362, 1433, 389 etc for BI. Port 5495, 5498, 5895, 5898, 8888,9510,9511,9012, 12345, 12346 , 12366 etc for PAL | |
| Stop all related IBM Cognos TM1 and IBM Planning Analytics services and set to MANUAL | ||
| Reboot Microsoft Windows server | ||
| Install PAL from file tm1_winx64h_2.0.919.10_ml.tar (run as administrator) | ||
| Install TM1WEB from file tm1web-11.0.93-24020517-winx64h_bundle | ||
| Go into cognos configuration and click save | ||
| Reboot the Windows server | ||
| Modifications are required when FIPSOperationMode set to 1 (Basic)
— Remove or deprioritise TLS RSA CipherSuites — TLS V1.2 or higher must be enabled — EDCHE CipherSuites must also be enabled |
||
| Restore configuration files that were backed up before | ||
| Start the IBM planning services (start CA11 if needed) | ||
| Check that you can login to TM1 Architect | ||
| Check that you can login to TM1WEB | ||
| Set all related IBM Cognos TM1 and IBM Planning Analytics services to AUTOMATIC start | ||
| Reboot windows server | ||
| Check that you can run Cognos Analytics reports against the upgrade TM1 cubes |
In older versions, this was also needed to be done:
Planning Analytics often uses Cognos Analytics for authentication. If CAM security is used and an SSL certificate has been enabled in Cognos, then we need to add the certificate from Cognos Analytics into Planning Analytics. This post explains the steps required to integrate Cognos Security with SSL for Planning Analytics Local, TM1Web (Planning Analytics Spreadsheet Services) and Planning Analytics Workspace.
https://exploringtm1.com/configure-planning-analytics-to-recognise-cognos-ssl-certificate/
https://exploringtm1.com/cognos-analytics-configure-ssl-certificate/
https://www.sempreanalytics.com/blog/increasing-reporting-capabilities-from-planning-analytics-using-cognos-analytics/
Extract from above websites:
Navigate to the Planning Analytics server and to the directory < PA install location> \bin64\ssl and copy the ibmtm1.arm file to the Cognos Analytics server. You can copy the file anywhere, but I recommend creating a directory for it in the installation location.
In order to import this certificate we use an executable on the Cognos Analytics server called ikeyman.exe which resides in the <CA install location> \ibm-jre\jre\bin directory. Simply double click this file to open it.
Click the Open icon on the toolbar, ensure the Key Database type is set to JKS, navigate to the directory <CA Install Location> \ibm-jre\jre\lib\security, and open the file called cacerts.
Now you have loaded the certificate file it’s time to import the Planning Analytics certificate. Under the ‘key database content’ section change the drop-down value to ‘Signer Certificates’ and press the ‘Add’ button….
| Planning Analytic Workspace upgrade | Date | |
| Copy the media to the server | d:\install | |
| Unzip the file ipa_workspace_win_2019_2.0.92.156.zip | ||
| Check free disk space on the PAW windows server | ||
| Rename folder to PAW92 and place it at root | ||
| Exclude new folder d:\paw92 from anti-virus scanning | ||
| Copy the <paw_install_location>/config/paw.ps1 file from your current installation to the new installation location | ||
| Copy the <paw_install_location>/config/certs directory from your current installation to the new installation location. | ||
| If you configured SSL, copy the <paw_install_location>/config/ssl directory from your current installation to the new installation location. | ||
| Take screen capture of the configuration today in PAW administration – any existing errors will not be solved by upgrade. | ||
| Take a backup | ||
| Stop the docker containers | Paw.ps1 stop | |
| Check that no running dockers containers | Docker ps | |
| Go to the new folder | ||
| Run installation ./start.ps1 | Start.ps1 | |
| Check that admin settings are correct | ||
| Check you can login to PAW website | ||
| Stop the docker containers | Paw.ps1 stop | |
| Reboot windows server, this to ensure the system will work after a reboot. | ||
| Check you can login after 30 min | ||
| Download the new kate agent https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=idt-install-configure-planning-analytics-administration-agent-local-only | ||
| Unzip to a temp folder | ||
| To update the Planning Analytics Administration agent Windows service, run UpdatePAAAgent.bat, passing in the full path to <PA_install_location>, that is, the parent of the paa_agent directory. | ||
| Check that bootstrap.properties contain the settings for smtp email as before | ||
| Running the /clean.ps1 script removes images for the release in which it is run. Run from old folder e.g. d:\paw90 | ||
| Check free disk space | ||
More information:
https://www.ibm.com/support/pages/ibm-planning-analytics-20-fix-lists
https://code.cubewise.com/blog/determine-the-version-of-ibm-planning-analytics/
https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=features-whats-new-in-planning-analytics
https://exploringtm1.com/planning-analytics-version-management/
Due to a security update included in Planning Analytics 2.0.9.19, customers who have the non-default FIPSOperationMode=1 set in their Tm1s.cfg should remove or deprioritize the TLS RSA CipherSuites for a successful handshake to occur. This includes all CipherSuites that are prefixed with TLS_RSA_. This also means that TLS V1.2 or later must be enabled, as TLS 1.1 and prior do not support alternatives. In the case of TLS V1.2, the ECDHE CipherSuites must also be enabled.
https://www.ibm.com/support/pages/whats-coming-next-ibm-planning-analytics-2093-sc
https://www.ibm.com/support/pages/troubleshooting-tm1bi-data-source-connections
https://exploringtm1.com/forcing-cognos-bi-use-native-tm1-engine/