The platform is configured rather than coded, so moving changes between instances — for example from a development instance to production — does not follow a traditional software deployment process. In many cases, creating an instance copy is the most efficient approach. Where only recent configuration changes need to be transferred, you can instead export and import configuration based on a specified date and time.
This approach moves configuration items (ES_ objects) that were created or modified on or after a defined date.
Processes Used for Migration
Three predefined processes handle the export and import:
ENERGYSYS Export Config Since Date — exports configuration items where the created or modified date is on or after the specified parameter date.
ENERGYSYS Import Config Since Date Step 1 — imports configuration items using the same date parameter. Any imported Virtual Objects must be published before running Step 2.
ENERGYSYS Import Config Since Date Step 2 — completes the import of configuration items based on the specified date parameter.
Importing the Migration Processes
These processes can be imported into an instance using the ENERGYSYS Import Process within the Configuration application. Each process requires both a configuration file and, where applicable, a process logic workbook.
When prompted by the ENERGYSYS Import Process, provide the relevant configuration file as the parameter.
The required files are:
ENERGYSYS Export Config Since Date: configuration file and process logic workbook.
ENERGYSYS Import Config Since Date Step 1: configuration file only.
ENERGYSYS Import Config Since Date Step 2: configuration file only.