<img src="https://trc.taboola.com/1278851/log/3/unip?en=page_view" width="0" height="0" style="display:none">
finding octane
Content_Cut_Icon Twitter_Brands_Icon

Config parameters in PA on Cloud - Caveats

Mode_Comment_Icon_white0
Alarm_Icon_1_white3 min

As per the IBM’s guidelines, the following points must be taken into considerations pertaining to Planning Analytics on Cloud. The tm1s.cfg file must exist in the base directory Any folders that you create must be below the base directory The location or the name of the base directory cannot be changed The existing tm1s.cfg file must not be replaced from another server. Link: ...

down-arrow-blue
Book_Open_Solid_Icon

As per the IBM’s guidelines, the following points must be taken into considerations pertaining to Planning Analytics on Cloud.

  1. The tm1s.cfg file must exist in the base directory
  2. Any folders that you create must be below the base directory
  3. The location or the name of the base directory cannot be changed
  4. The existing tm1s.cfg file must not be replaced from another server.

IBM cloud.png

Link: https://www.ibm.com/support/knowledgecenter/SSD29G_1.0.0/com.ibm.swg.ba.cognos.tm1_cloud_mg.10.3.0.doc/c_tm1_cloud_faq.html

In addition to the above, the following config parameters in tm1s.cfg file must not be modified by the users as otherwise it would create server issues:

  1. ServerName
  2. LoggingDirectory
  3. DatabaseDirectory
  4. PortNumber
  5. MessagePortNumber
  6. HTTPPortNumber
  7. ServerCAMURI
  8. ClientCAMURI
  9. SSLCertificateID
  10. SSLCertAuthority
  11. UseSSL
  12. CAMUseSSL

Finally, as a matter of due diligence, it is always advised to take the backup of the existing config file before making any updates to config file.

Note: In case you’ve inadvertently updated one of the above config parameters and do not remember the previous value nor have taken the backup of config file, do not worry, you can still get the old config file reinstated from backup that is taken daily by Cloud Ops. Since the config file resides within the shared directory, it will automatically be included in the daily backups.

Simply raise a request to Cloud Ops for the config file to be reinstated from the latest backup and that should fix the issue.

Planning Analytics Backup Policy: https://www-03.ibm.com/software/sla/sladb.nsf/pdf/6227-03/$file/i126-6227-03_10-2015_en_US.pdf

 

 

Written by:

Amin Mohammed [Senior TM1 Consultant]

logo (1).jpg    IBM.png

Leave a comment

Got a question? Shoot!

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

Get more articles like this delivered to your inbox