Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
admin:server_installation_3 [2022/11/09 20:17] – [Configure backups] Adam Dewey | admin:server_installation_3 [2023/08/02 00:31] (current) – [SSL Certificate] Mark Glover | ||
---|---|---|---|
Line 4: | Line 4: | ||
\\ **These steps need to be carried out after completing the steps described in:\\ [[admin: | \\ **These steps need to be carried out after completing the steps described in:\\ [[admin: | ||
+ | ==== Obtaining a data file ==== | ||
+ | |||
+ | If you are setting up a sync site for a synced system, then you will need to: | ||
+ | - Generate the XML file for the sync site from the central server - refer [[synchronisation: | ||
+ | - If creating a single-user sync site: | ||
+ | - Transfer the XML file to the sync site. The Dropbox that you configured in [[admin: | ||
+ | - Create the datafile from this XML file through [[synchronisation: | ||
+ | - If creating a server sync site: | ||
+ | - Create the datafile from this XML file through [[synchronisation: | ||
+ | - Transfer the datafile to the sync site. The Dropbox that you configured in [[admin: | ||
==== Installing mSupply Server software ==== | ==== Installing mSupply Server software ==== | ||
=== If you are upgrading from a previous version... === | === If you are upgrading from a previous version... === | ||
Line 62: | Line 72: | ||
<WRAP center round alert 60%> | <WRAP center round alert 60%> | ||
- | There is no point in carrying out the following steps unless: | + | * There is no point in carrying out the following steps unless |
- | * You are ready to create a new mSupply data file, or you have one to load. | + | * If this is a satellite site on a synced system, you should have one to load - refer [[admin: |
</ | </ | ||
Line 117: | Line 127: | ||
=== Configure backups === | === Configure backups === | ||
- | * **Edit** > **Settings** > **User settings for Data file** > **Database | + | * **Edit** > **Settings** > **User settings for Data file** > **Backup |
* **Scheduler**: | * **Scheduler**: | ||
* **Configuration**: | * **Configuration**: | ||
Line 166: | Line 176: | ||
=== Configure cache === | === Configure cache === | ||
- | **Edit** > **Database | + | **Edit** > **Settings** > **User settings for Data file** |
{{ : | {{ : | ||
Line 266: | Line 276: | ||
+ | ==== SSL Certificate ==== | ||
+ | The mSupply server also has a webserver as mentioned [[web_interface: | ||
+ | |||
+ | It is recommended that a public facing web server should have an SSL certificate installed. For the mSupply server a ' | ||
+ | |||
+ | Theses files needs to be stored inside the folder C:\Program Files\mSupply\mSupply Server\Server Database | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The cert.pem file contains the certificate in the following format and can have the root as well as the intermediate certificate. | ||
+ | |||
+ | < | ||
+ | -----BEGIN CERTIFICATE----- | ||
+ | MIIGUzCCBTugAwIBAgIRAP9nsdfsfdsdfYH0oEZgg3k28WUoYQgQwDQYJKoZIhvc | ||
+ | gY8xCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAO | ||
+ | BgNVBAcTB1NhbGZvcassdsdmQxGDAWBgNVBAoTsdfsD1NlY3RpZ28gTGltaXRlZD | ||
+ | AxMuU2VjdGlnbyBSU0EgRG9tYWluIFZhbGlkYXRpb24gU2VjdXJlIFNlcnZlciBD | ||
+ | QTAeFw0yMzA2MTYwMDAwMdsadsdDBaFw0yNDA2MTUyMzU5NTlaMCExHzAdBgNVB | ||
+ | Junk | ||
+ | -----END CERTIFICATE----- | ||
+ | |||
+ | -----BEGIN CERTIFICATE----- | ||
+ | MIIGEzdddhuyuyuyuCCA/ | ||
+ | iDELMAkGA1UEBhMCVVMxEzARBgNVBAgTCk5ldyBKZXJzZXkxFDASBgNVBAcTC0pl | ||
+ | cnNleSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxLjAsBgNV | ||
+ | BAMTJVVTRVJUcnVzdCBSU0EgQsdsd2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhc | ||
+ | MTAyMDAwMDAwWhcNMzAxMjMxMjM1OTU5WjCBjzELMAkGA1UEBhMCR0IxGzAZBgNV | ||
+ | Junk | ||
+ | -----END CERTIFICATE----- | ||
+ | </ | ||
+ | |||
+ | The the key.pem file contains | ||
+ | |||
+ | < | ||
+ | -----BEGIN PRIVATE KEY----- | ||
+ | MIIEvAIBADANBgkasasdfqhkiG9w0BhgghAQEFAASCBKYwggSiAgEAAoIBAQCqPA | ||
+ | TZB5GnFAODhHMTU+pqGD8eS6NOzWwhoyb2dvZv1w2Gh6fcprPUpATltvcMe8q+fe | ||
+ | +ITiYylKfcs2nNYyirr2sdfsdfSPGMKR277MW6G7etFCGjBH/ | ||
+ | e9oRf/ | ||
+ | CTvUxUF6Niul/ | ||
+ | iC20nTBKweefzPg4Uo9d6DdhQD7xdklD1SXlcTgEXpa0Cc/ | ||
+ | junk== | ||
+ | -----END PRIVATE KEY----- | ||
+ | </ | ||
+ | |||
+ | More recently we have moved towards using Caddy server software which setup a reverse proxy server which use Let's Encrypt to automatically update SSL certificates. This will avoid the need to manually watch and update expiring SSL | ||
==== Installing mSupply Client ==== | ==== Installing mSupply Client ==== | ||
Needed: | Needed: | ||
Line 381: | Line 437: | ||
As part of the installation, | As part of the installation, | ||
</ | </ | ||
+ | |||
+ | === Forcing mSupply client to connect to a specific mSupply Server === | ||
+ | |||
+ | Within an organisation it is possible to have multiple mSupply server running like in the image shown below. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Now you as a administrator may require a particular mSupply client to connect to one of the server and to ignore the others. To reduce confusion to the user you may require the user to connect to a particular mSupply client. | ||
+ | |||
+ | It is possible to direct a mSupply client application to look out for a particular mSupply server only. Let us assume that you want a certain computer to access the mSupply server with a IP address of : 192.168.3.200 | ||
+ | |||
+ | * Install the mSupply Client. | ||
+ | * Navigate to `C:\mSupply client\Database` | ||
+ | * You will see the `EnginedServer.4DLink` | ||
+ | * For the server path `server_path=": | ||
+ | * save the `EnginedServer.4DLink` | ||
+ | * Now when you start the mSupply client, it will know where the mSupply server is and will look for the IP : 192.168.3.200 | ||
+ | |||
+ | {{ : | ||
==== mSupply Server configuration ==== | ==== mSupply Server configuration ==== |