Data not cloned

Third-party touch points

Messages in transit that exist in the IMS intermediate tables or in SQS queues. If ION is still processing messages while the clone occurs, these messages are missing from the tenant clone.

OneView data

Enterprise Locations:

• An Enterprise Connector is tenant specific, so Enterprise Locations are not cloned.

Connection parameters for Enterprise Connector connection points and File (sFTP from Cloud) connection points:

• To prevent the tenant clone from connecting to an application that integrates with the source tenant, connection point parameters are not cloned.

Infor Ming.le service accounts used in ION API connection points and workflow ION APIs:

• During a clone, the service accounts used for Infor Ming.le and for ION are not cloned.

When a tenant is cloned, the models that were active in the source tenant will also be active in the clone tenant. Due to the missing connection parameters and credentials, some of these models can now generate errors.

Infor Ming.le

ION API

IFS

IO BOX messages

ION API trace logs

Audit data

• Security audits
• ION API audits
• User history

Ping federate connections

ION API client IDs

REDIS cache

ION API metadata

ION API deployment details

• Infor non-provisioned
• Third-party API suites
• Non-Infor

SCIM account data

Tenant Specific Application Registrations

PingFederate

• Identity provider
• Service provider

OAuthGrantmanagementService