Considering an upgrade from TM1 10.2.2 to Planning Analytics? Since IBM support for TM1 10.2.2 ends in September 2019, it makes sense to plan for an upgrade. But there are some key items to take into consideration. In this blog, I will explain the high-level upgrade process as well as the items you need to address during an upgrade. I will also provide some tips and tricks to help make your transition from TM1 10.2.2 to Planning Analytics as smooth as possible.
When upgrading from TM1 10.2.2 to Planning Analytics you can set up the new environment on a different server or uninstall the old version before installing the new version. This also applies to the installation of Planning Analytics for Microsoft Excel (PaX). After the system architect completes the setup of the Planning Analytics environment, the initial migration of a model from TM1 10.2.2 to Planning Analytics is straight forward. First, take a backup of the existing model in the TM1 10.2.2 environment. Second, copy the data folder from the TM1 10.2.2 environment to the new Planning Analytics environment data folder. Include any relevant import/export files and the config file.
After copying over the applicable files, restart the TM1 service to bring up the model in the new Planning Analytics environment. Once the service restarts, there are some adjustments to make to subsets, TI processes, and websheets to ensure your model functions properly. If you use Contributor, delete and recreate your Contributor applications.
Subsets
Identify any dynamic subsets that reference alias attributes in the MDX expression. In TM1 10.2.2, all attribute types can be referenced in dynamic subset MDX expressions. However, Planning Analytics only supports references to numeric or string attributes in dynamic subset MDX expressions. Two options exist to resolve this issue. First, does the alias attribute name need to be referenced? If you can reference the principal element name, modify the expression to use that instead. In cases where the alias attribute needs to be referenced, create a new text attribute that contains the same values as the alias attribute. In your MDX expression, replace the reference to the alias attribute with a reference to the new text attribute.
TI processes
Deactivate all chores and adjust all the TI processes. Adjust all file folder path references from the old to the new locations. Including all data source file references and any ascii or text output logic. If the initial set up of Planning Analytics is in a new DEV environment, I recommend setting all data source paths to point to the import files from the new PROD folder location. This ensures that all data being loaded into the DEV model mirrors the data in PROD. Thereby facilitating troubleshooting and testing of new enhancements.
For all ascii and text output logic, I recommend pointing those references to the new DEV folder location. This will ensure that the output files generated from PROD are not overwritten with data from DEV. The best practice here would be to have a field in the Control cube where you can identify the folder location for any exports in each environment. You will then want to point to that field in the Control cube anywhere where you are exporting data via TI processes. This will allow you to set the location in each environment correctly. And without having to adjust the logic in the TI processes when migrating between Dev and Prod.
Websheets
Websheets created in Perspectives should migrate over to Planning Analytics for Microsoft Excel (PaX) seamlessly. You will need to update any action buttons used on the websheets. Open each websheet, and where action buttons are present, delete and recreate the action button to perform the desired action through Planning Analytics for Microsoft Excel (PaX). All other references within the websheets should function properly in the new Planning Analytics environment as they did in the old TM1 10.2.2 environment.
Contributor applications
Run the ‘}tp_admin_delete_all’ process to reset the deployed applications. After running this process, make note/take screenshots of the current Contributor application details before deleting each application. Next recreate, validate, and deploy all Contributor applications in the new Planning Analytics environment. Once all Contributor applications are deployed, export the workflow rights file out of Architect and import it into the application in Contributor to set up security in the new Planning Analytics environment.
Therefore, taking the steps listed above and focusing on the key items identified enhances the prospects of a seamless migration. These are the key items we found over several different migrations. IBM support is available to guide you through any roadblocks you may hit during your upgrade. This upgrade enables you to experience the advanced functionality that Planning Analytics provides. Above all, resulting in a better plan for your business.
