...

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.

...

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 Moving a DHIS2 Configuration to Production (Deployment)

https://psi.atlassian.net/wiki/pages/resumedraft.action?draftId=52723718

Versions

...