Hi Team,
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.
Pulse manages migration through its internal Version Control System (VCS) through a GIT compliant internal repository by TM1 instance, the VCS is fed by Documentation and the Change Tracking Jobs of Pulse. Usually if Documentation is not being executed, the Change Tracking should take the change, the frequency of the latter depends in the Track for Changes setting in Instance Settings. Is Change Tracking working in Dev? Did Pulse picked the Change after the change was done?
Hi ecarmona,
Thanks for your reply. Change tracking was not working in Dev (I forgot to mention that in the post), I believe documentation update triggered it to work properly. However, curious to know what made it stop working in the first place ? Why was it working fine in Test ?
This is set in the frequency of the Change Tracking in Instance Settings, setting this value to Zero will deactivate it. There are other occasions that the Change tracking is blocked due environment settings, constraints or updates. If the latter seems to be the case, I suggest to contact your local support office so we can follow up with a support session.
Hi Eric,
Thanks for your reply. The change frequency setting is set to a non zero value.
However, is there any log that we can refer to verify if it was changed ?
Once we rule out that change we can check if it was blocked due to environment settings, constraints or updates.
If the setting is not zero, that means that something in your environment might be blocking it, Could you please contact your local support office? So that we can follow up with a support session.
We wanted to rule out that it was not changed, that’s why if there’s a log file where it gets recorded every time a setting is changed that will be great. We we’ll contact your local office after we rule this out.