We’ve been using Pulse for live migration lately & we were able to use it without any problems until today.
We faced following problems while creating a package for Migration from Dev to Prod :
a. We created a package from Dev server that contains a new TI process & an updated existing TI process. We excluded all dependencies from package. When we tried to execute package on Prod server, in the ‘View Changes’ step we found that Pulse hadn’t picked the latest TI files but had created a package from TIs that were about a fortnight old.
b. We unzipped the package & could confirm that the package created was containing old TI Processes as mentioned above.
We tried the following steps to correct the problems (in that order) :
- restarted the tm1 server instance - still the same problem
- restarted the pulse server service - still the same problem
- updated documentation on the source pulse instance (we don’t always run documentation on Dev & Test servers) & recreated package - the new package was created with the correct latest files.
We don’t know the reason behind this behaviour of Pulse. In the past we never updated the documentation yet there was no problem in package creation - especially with TI only package.
To confirm the same, we created a package from Test server as follows :
a. Updated a TI process in Test server.
b. Created package using above TI process without updating documentation
c. Checked the package, it contained the correct TI processes with latest changes.
We’re curious to know why the documentation run was not required on Test server database to create package with correct expected content ?
We’d like to know what steps we’ll need to follow each time in order to use pulse migration confidently.
Thanks for your help.