Audience | System Administrators | Version/ Date | v0.1 | Nov 25/2022 |
Collection | DHIS2 PSI SOPs |
|
|
...
v0.2 | Sep 11/2022 - small edits |
DHIS2 configurations are created and modified on designated development environemnt/testing environment. Only after a full testing
When your DHIS2 configuration has been fully developed and tested and passed UAT, you should plan the deployment to production
This text should include
Purpose
Scope
Pre-requisites
Workflow (if applicable)
See also
text cycle, and with the final approval from the product owner during UAT, they can be moved to a production environment.
Moving a configuration
Moving a configuration (DHIS2 Program or Dataset) consist in obtaining an export configuration file (also referred as metadata) in the form of a JSON file from the /wiki/spaces/DHM/pages/13271088, to be subsequently imported into another DHIS2 server, including the /wiki/spaces/DHM/pages/13271088.
...
Configuration (metadata) export
You can export a DHIS2 configuration by using the build-in metadata export, with dependancies, or PSI’s Program Configuration App (PCA). If you use the build-in metadata export, you will need to ensure that you exclude sharing data, Org Unit assignments and any other UIDs that may not exist in the production server. If you use the PCA, simply select ‘clean export’, option that produce a file that can be imported into any server.
| Info |
|---|
Ensure that your destination server uses the same Default Cat Option/ Cat Combo/ Cat Option Combo - otherwise, edit your export file before attempting to import it. |
Configuration (metadata) import
Very few users have the rights to import a metadata file into PSI’s production environment. The permission is only granted Global System Admins. You should test your metadata file in either PSI’s DHIS2 Clone or Staging /wiki/spaces/DHM/pages/13271088. If your program or dataset perform adequately, you should submit a request ticket to PSI’s help desk with the request “DHIS Production Deployment” . You can attach your source file to the ticket, or provide the link/name of the server and program/ dataset that needs to be moved.
Data move
Normally, there is no need to move data from a testing/staging environment to a production machine. If you need to move data, see [future link].
See also
Testing DHIS2 configurations and apps
https://psi.atlassian.net/wiki/pages/resumedraft.action?draftId=52723718
Versions
0.1 | Nov 2529/ 2022 | R. Melia - first draft |
0.2 | Sept 11, 2023 | R. Melia - small, minor edits |