Refreshing application Data with Federated systems

Hi JimY - We don't use ISS, but we are federated between Landmark/TM and LSF/S3 and we do data refreshes all the time (actually, Infor Managed Services does them for us). I don't know why ISS federation would be an issue, other than the fact that the federation configuration is stored in tables on the Landmark system, and they are copied down during the data refresh - which obviously won't work. Maybe someone else knows why ISS would be an issue?

In our case, we have a list of tables that we have to save off the destination system, and then after the data refresh is complete those tables are truncated and restored from the destination backup (services, pficonfigurations, flows, etc).

We also have a list of tables we have them truncate after the data refresh (workunits, actions, etc) so that our DEV system doesn't continue to send "live" emails based on old actions.

Finally, we have them update all email addresses on the destination system to a generic email address, so we don't send DEV emails to live addresses. The current email addresses are updated with SQL, and then a script is run that fixes all of the emails that are hidden in CLOB fields - like future dated, etc.

These lists were built over time as we identified "problem" tables. I wish I had a list to send you, but I don't have access to it, sorry.

Good Luck

Thank you Kelly. Infor says if you are not federated through ISS then you can use the daexport/daimport process. All I am copying though is the application data not gen. I was told by someone else that if you are just copying LTM for instance then it should work. I will continue to work on this and hope for the best. If not then I do have a backup using daexport that I hope will restore properly and allow us access again to EMSS.

FYI, the latest release of Landmark now includes a tool to sync the certificates, allowing refresh of data between two ISS Federated Landmark environments. I have not used it yet, so I'm not making any claims that it works well

Hi Carl,
Thank you for the info. We just installed 10.1.1.21 in our test environment and have 10.0.0.6 environment on the LSF side. Do you know what version of ISS this is allowed?

I did some digging and found that you have to be on Landmark Technology 10.1.1.17 or higher to do this. There is an updated Infor Landmark Technology Server Setup And Maintenance Guide that was put out in April that has the steps to perform this. Once we have our test and production systems on the same versions I will test it. Has anybody attempted this yet? I am curious as to how it went. Thank you.

Finally getting around to doing a data refresh from prod to test of our Landmark applications and I have some questions.
1. When we use daexport/daimport to copy the data can I assume that it will also copy
the flows for each data area that we copy and will they run based on the schedule
that is set up in prod?

2. If the answer to question one is yes then if I use cdexport on the destination system
prior to refreshing the data and then use cdimport to re-import the configurations back
in will that copy our test flows back in and replace the ones from the production
system? Will this also take care of the schedule for flows?

3. Can I run daexport on the prod system while users have access? I would be doing
this late at night so there would be very few.

4. Does anybody know of a way to update all of the users email addresses to a
generic one so that when we are testing they don't receive it? I was thinking of a
flow, but not sure what business class to use.

5. Anything else I should consider?

Thank you.

JimY
when we do the data refresh, we run the copy process while users are online as the data copy for us takes close to two days. we have over 600GB of data. it would copy the data, i don't for sure on flows.
2. i don't know
3 yes
4. we had our DBA update the email addresses with generic address on lower environments
our biggest struggle is actors/roles/etc getting wiped out each time we do data refresh and it creates a big problem for any active testing being done. if anyone has any tips to save the security and configuration on destination as we import the data that would help us.