Install Bahmni on CentOS (Advanced Installation Options)

To install Bahmni, you require to now install the "bahmni" command line tool, which provides various options for installing / configuring Bahmni. This command line tool uses Ansible under-the-hoods to setup a Bahmni server on a local machine, or across multiple machines. This page documents the various options available to you – from choosing your own implementation config, to setup of passive secondary servers, to choosing specific databases, etc.

For production purposes, of Bahmni version 0.92, CentOS 7.6 64bit is the recommended & tested platform for running the Bahmni server. Create a fresh CentOS V6.x box. Please refer for additional details. For other purposes, for instance to evaluate and install Bahmni on Windows or Ubuntu, one can install the .관련 문서: System RequirementsBahmni Virtual Box

For Bahmni version 0.91 or earlier, we recommend CentOS6.9 64 bit.

The bahmni-installer rpm will install a command line utility called 'bahmni'. Use the steps mentioned here to install the bahmni command line tool.

• Copy OpenMRS mysql dump to /etc/bahmni-installer/deployment-artifacts. The dump file should be named "openmrs_backup.sql"For versions prior to 0.82, the file is actually the entire mysql databases dump and named as 'mysql_dump.sql'.

• LAB (OpenELIS) - openelis_backup.sql
• ERP (Odoo) for Bahmni 0.92 and above - odoo_backup.sql
• ERP (OpenERP 7) for Bahmni v 0.91 or earlier - openerp_backup.sql.
• For versions prior to 0.82, the file is the entire postgres databases dump and named 'pgsql_dump.sql'. NOTE: These steps are not needed if databases already exists. 

Example: If implementation_name is 'jss', then app config will be picked up from the /etc/bahmni-installer/deployment-artifacts/jss_config folder

• Please refer to this , for the installation variables that can be overriden. It is strongly recommended to change default user passwords for better security of your Bahmni server.관련 문서: List Of Configurable Installation Variables
• Create an override file for the properties at /etc/bahmni-installer/setup.yml as detailed below

The bahmni installer uses Ansible under-the-covers to perform installation. We need to provide an Inventory file to the installer to tell which all bahmni sub-systems need to be installed, and on which servers / IP should bahmni sub-components get installed. If you do not specify the inventory file, it defaults to a local setup with all the bahmni components (mrs, elis, erp, pacs) installed as part of setup. You can see the default local inventory file in /etc/bahmni-installer/local.관련 문서:  Inventory file

You are free to create a new inventory file at /etc/bahmni-installer/<inventory_file_name>. If you create a new inventory file, then you will need to always use the "-i <filename>" option while invoking the bahmni command. Use the attached sample_inventory_file as reference. Or you can see one here on github.

To install only specific components, please add the host entry only in respective groups of the inventory file. For example, to install only bahmni-emr and bahmni-reports components, the host entry should be present only in the bahmni-emr and bahmni-reports group.

To start the installation, execute the following command if custom inventory file is added:

When there is no custom inventory file to be used, the following command can be used which will default to single machine local installation.

Access the emr app at https://<ip_address>/home

Access the OpenMRS app at https://<ip_address>/openmrs

Access Bahmni Lab (openelis) app at https://<ip_address>/openelis

Access Odoo/OpenERP app at https://<ip_address>:8069

To start all the services related to Bahmni, one can use the following command.This command is available from 0.82 version of Bahmni.

To stop all the services related to Bahmni, use the following command. This command is available from 0.82 version of Bahmni.

When there is no custom inventory file to be used, the following command can be used which will default to single machine local installation.

To check more about individual service statuses refer to the following documentaion:

1. Ensure ssh access to remote server from the provisioning machine. That means ssh-ing into the machines at least once using the ansible_ssh_user specified in the inventory file to create known_hosts entry (since Ansible works out of ssh).
2. The ssh user should have sudoer permissions.
3. Ensure the inventory does not use localhost/127.0.0.1. The exact public IP address should be specified.&nbsp;This is because one host has to talk to the other host with multi machine setup.&nbsp;For example, the app server should communicate with the db server. &nbsp;When localhost is given, it will try to communicate with itself, rather than the other server.

An inventory file with remote setup should look something like this: https://github.com/Bahmni/bahmni-playbooks/blob/master/dev/dev

Then trigger the installation, using the "bahmni" command with -i option.

To update only specific components of Bahmni, the following command can be used:

Ideally, the above command should be used for patch release in which only specific component is changed and others are not. Please note that the version to which a specific component is to be upgraded should be compatible with other component versions.

To update all the components except specific components, the following command can be used:

Certain manual steps have to be done if you are migrating from an old sh based installation to a rpm based installation.

The link to the documentation is available here:관련 문서: Migrating to bahmni-installer rpm based installation

1. &nbsp;Passive app servers can be setup by adding passive host IP to respective app-server groups in the inventory file. Passive host can be added to following app-server groups: &nbsp;bahmni-emr, bahmni-reports, bahmni-lab, bahmni-erp, pacs-integration.
2. Tag passive host with 'passive=yes'&nbsp;Note:&nbsp; During failover, to make passive server as active, remove the active host from inventory and remove 'passive=yes' tag from the passive host and trigger installation as in step 2.&nbsp; &nbsp;Example:Inventory file with active/passive setup
   Inventory file with active/passive setup

   [bahmni-emr]
   192.168.33.10
   192.168.33.11 passive=yes
    
   [bahmni-reports]
   192.168.33.10
   192.168.33.11 passive=yes

When DCM4CHEE passive app server and slave DB server are same, postgres replication would not work.

The workaround that is available is, before setting up postgres-replication, the passive server entry has to be removed in dcm4chee group and can be proceeded with postgres replication setup. Once the replication is setup, the passive server entry has to be added back in dcm4chee group.

1. &nbsp;Add slave host ip to [*-slave] group in the inventory file.&nbsp; Example:Inventory file with master/slave setup
   Inventory file with master/slave setup

   [bahmni-emr-db]
   192.168.33.10
    
   [bahmni-emr-db-slave]
   192.168.33.11
    
   [bahmni-lab]
   192.168.33.10
    
   [bahmni-lab-db-slave]
   192.168.33.11
    
   [bahmni-erp-db]
   192.168.33.10
    
   [bahmni-erp-db-slave]
   192.168.33.11
   
   [bahmni-reports-db]
   192.168.33.10
    
   [bahmni-reports-db-slave]
   192.168.33.11

To setup replication, separate command needs to be triggered for the mysql database and postgres database.

• To setup mysql replication, following command needs to be executed: bash setup-mysql-replication ]]>&nbsp;

  bahmni -i <inventory_file_name> setup-mysql-replication

• To setup postgres replication, following command needs to be executed: bash setup-postgres-replication]]>

  bahmni -i <inventory_file_name> setup-postgres-replication

1. &nbsp;Move slave host from [bahmni-emr-db-slave] group to &nbsp;[bahmni-emr-db] group&nbsp;in the inventory file. (mysql)
2. &nbsp;Move slave host from [bahmni-lab-db-slave] group to&nbsp;&nbsp;[bahmni-lab-db] group, [bahmni-erp-db-slave] &nbsp;to [bahmni-erp-db] group, [pacs-integration-db-slave] to [pacs-integration-db] group in the inventory file. (postgres)

To update just the implementation config without triggering the entire installation, replace the old <implementation_name>_config folder present in /etc/bahmni-installer/deployment-artifacts with new one and trigger update-config command like below:

To setup nagios, add the nagios server host in inventory file like below:

Now add below email configuration in the "setup.yml" on path /etc/bahmni-installer/setup.yml

Now, run the installer.

Bahmni bundles OpenERP with HTTP by default. It runs on 8069 port with plain HTTP. The Bahmni landing page will have url to access the OpenERP with this port.

To enable HTTPS:

We need subdomain for OpenERP to enable HTTPS and this is mandatory to do that. The openerp_url configuration is used for enabling HTTPS.

(Location of setup.yml is /etc/bahmni-installer)

This will be updated in the Bahmni landing page and rules will be updated in Apache so that it will redirect the requests to https.

There are couple of issues:

1. If the machine has multiple network interfaces (multiple IP address), there is a possibility that during installation it might pick up a wrong IP address to show on the Bahmni landing page.
2. If you are installing OpenERP in a separate machine or multi machine setup in cloud, it is possible that the machine in which OpenERP is installed is not publicly accessible.

LetsEncrypt is a free and automated Certificate Authority. You can read more about it here. Currently Bahmni supports DNS challenge based certificate generation. This eliminates the need of hosting the server on the Internet using a public IP address. Please note that, you still need an internet connection to run the process, except that there is no need to have a public IP address for your server.

Prerequisites:

1. You must own a domain name.
2. Active internet connection.

Installation:

The command must be run on the server which is present in the [bahmni-emr] group in inventory file. If you have passive machine setup, please run the command again in the passive machine.

Things to note:

1. This command will backup the current certificate and private key.
2. This command needs manual interaction as DNS records have to be updated.
3. The command will ask you to add TXT record for your domain in your DNS settings.
4. You'll get a prompt like the below one. You have to manually update the given NAME and VALUE in your DNS settings. After you are done, press ENTER to continue. text and VALUE = as DNS TXT record. Wait for sometime to let the TXT records sync with other DNS servers. Press ENTER after you are done]]>

Add NAME = <acme_challege_key> and VALUE = <random_generated_value> as DNS TXT record. Wait for sometime to let the TXT records sync with other DNS servers. Press ENTER after you are done