Question
· Jul 17

Request for suggestions on how to efficiently replicate a test environment in production

Good morning everyone,
In the facility we're working in, we have two separate installations for testing and production. In the test environment, we have production processes running properly, and we need to replicate production processes and settings in the production environment. Until now, when we move from a test environment to a production environment, we currently export the test classes, import them into production, and manually configure the production environment by connecting Services, Processes, and Operations and configuring the settings. We tried exporting the production environment from the portal to import it into production, but we couldn't find the import functionality. So, we were wondering if there was a more efficient and faster way to move a production environment with all its settings from one environment to the other than what we're currently doing.

Thanks everyone in advance,

Elisa

Product version: IRIS 2024.2
Discussion (2)2
Log in or sign up to continue

To replicate production processes and settings from a test environment to a production environment efficiently:

  1. Export and Import Production Definitions:

    • Use the Management Portal to export the XML definition of the production from the test environment.
    • Import and compile the XML definition in the production environment. This ensures all necessary components and configurations are transferred.
    • Steps involved:
      • Ensure the test environment closely resembles the production environment.
      • The deployment process includes exporting, testing deployment on a test system, and then importing to live production. Importing involves loading the XML to the system, compiling, and enabling the production [1].
  2. System Defaults for Environment Specificity:

    • Leverage System Defaults to define environment-specific settings. This prevents the need to update settings manually for the production environment and allows the same production class to work in multiple environments without risk of incorrect configuration [2].
  3. Automated Deployment with Interoperability Features:

    • For updates, you can use the "Deploy Changes" feature in the Management Portal, which automates export, import, and compilation steps. It also manages enabling and disabling of components, along with rollback in case of errors [1].
  4. Use of Source Control:

    • Manage production definitions in source control to track changes systematically across environments. This can help synchronize configurations and prevent errors during manual adjustments [3].

Using these methods ensures a systematic and secure way to replicate and manage production environments effectively [1][2][3].

Sources: