Environment
- Product: SOLABS QM10
- Versions: All versions
- Source Environment: Production
- Target Environment: Validation
Issue/Symptoms
A client wants their Validation environment to contain the same data and configuration as their Production environment. This operation, referred to as a “flash” or environment refresh, is typically requested in the following situations:
- The client needs to test and qualify changes in an environment representative of Production before installing them in Production.
- The client wants, for any other reason, to have their Production data available in the Validation environment.
Cause
This is a standard procedure, not an error. The environment refresh is an integral part of the SOLABS QM10 structure: it allows clients to test and qualify changes in an environment that accurately reflects Production before deploying them to Production.
In certain circumstances, SOLABS may also need to copy a client’s Production environment to an internal sandbox in order to perform testing.
Resolution
During a refresh, the Production environment is copied over another environment, typically the Validation environment. The following details describe how the process works.
How the Process Works
- Automated process: The refresh is performed automatically.
- Data replacement: The data in the Validation environment is erased and replaced with the Production data.
- System files (program files) replacement: The Validation environment version is aligned with the Production version. For example, if the Validation environment is running version R10.9.1 and the Production environment is running version R10.8.1, the Validation environment will be reverted to version R10.8.1 once the operation is complete.
- Configuration replacement: Any Validation environment configuration that differs from the Production configuration is overwritten.
- Environment identification: An on-screen banner clearly indicates that the environment is the Validation environment.
- Instance identifier (ID) retained: The unique identifier (ID) of the SOLABS QM10 Validation instance is retained.
- Impact on Production: The Production environment is not affected unless a new backup must be taken immediately. In that case, the Production environment is unavailable for the duration of the backup. Otherwise, the most recent available backup is used; the data copied to Validation then reflects the state of Production at the time of that backup.
Available Options
- Removal of user email addresses: “Yes” by default. This prevents users from receiving notifications from the Validation environment. Email addresses can be added back after the operation.
- Collaborative Review: The Collaborative Review feature can be enabled and pointed to a Validation library, provided it is already active in Production.
- Replacement of documents with blank files: “Yes” by default. All SOLABS QM10 documents are replaced with blank files for security and confidentiality reasons.
Mandatory Settings
- Connection type: The connection type is set to Database. Single Sign-On (SSO) configurations are not supported in the Validation environment.
- Password reset: All user passwords are reset to the same value. This password can be generated automatically or provided by the client. Each user can then change their password as usual.
Additional Information
- Validation and Qualification Requirements: Because the data, configurations, and version of the Validation environment are replaced, any testing or qualification activities in progress in that environment will be lost. Schedule the refresh around planned validation activities (for example, before installing a new version to be qualified, not during qualification).
- Known Limitation: Single Sign-On (SSO) is not supported in the Validation environment after a refresh; users must log in with their username and the reset password.
Comments
0 comments
Please sign in to leave a comment.