Hi,
actual I 'develop' all TI processes on my local server. Is there a (simple and easy) way to deploy the TI process to the production server? My idea is to copy the corresponding '*.pro'-file into the data directory of the production server. But (as far as I know) the server will find the new TI process files after a restart.
Is there a better way? My problem coulds be the restart of TM1.
THX for every idea and hint.
Regards,
SteveB
How to 'deploy' a TI process
-
rkaif
- Community Contributor
- Posts: 328
- Joined: Fri Sep 05, 2008 6:58 pm
- OLAP Product: IBM Cognos TM1
- Version: 9.1 or later
- Excel Version: 2003 or later
Re: How to 'deploy' a TI process
Yes you are right. You have to copy *.PRO files and have to restart the TM1 service.
Cheers!
Rizwan Kaif
Rizwan Kaif
-
Alan Kirk
- Site Admin
- Posts: 6667
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: How to 'deploy' a TI process
Generally it requires a server restart, though it would be possible (if you had enough time, skill and patience) to write API code to do this without one. Alternatively there's a commercial product called Vizier which will do it for you, but you need to pay for it.SBrenner wrote: actual I 'develop' all TI processes on my local server. Is there a (simple and easy) way to deploy the TI process to the production server? My idea is to copy the corresponding '*.pro'-file into the data directory of the production server. But (as far as I know) the server will find the new TI process files after a restart.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.