Refreshing tenant data
When you refresh a tenant for the Infor OS environment only, these components are included:
- IFS
- Infor Ming.le
- Homepages
- ION API
- ION
- Data Lake
- Infor Document Management
You cannot refresh these components individually.
- Business Vault: A full reload is required to ensure that OLAP data is consistent with publishing jobs in Business Vault.
- Landmark: A full cube reload is required to ensure that OLAP data is consistent with publishing jobs in Landmark.
In addition,
- Infor Ming.le: Some IFS roles might not be
present. Users and roles must be re-registered in Infor Ming.le
Administration.
Infor Federation Services (IFS) requires additional special handling because it stores the user information. IFS creates new users when a snapshot is being restored. These new users being created in the target tenant are identical to those in the source tenant except that they have a different tenant ID. IFS preserves the GUID of the users from the source to the target system.
End users needing to log in to the restored tenant may be different from the end users in the source tenant. It is important that one or more administrative users have the ability to log in to the target tenant after a snapshot restore is completed. To enable this, when the createsnapshot API call is made to the source tenant, IFS returns to CSP the current list of administrative users in the source tenant.
As part of the restoration process, CSP provides an option where the administrators’ email addresses from the source tenant can be replaced with new email addresses, but IFS maintains the same GUID when restoring these users. IFS resets the password for administrative users whose email is changed in CSP to allow these new administrative users to log in to the target tenant. If email addresses for non-administrative users must also be changed, the administrative users can change the addresses within IFS
- Homepages: Home pages must be reconfigured to ensure that they point to existing reports or dashboards.