Mailing-List: contact dev-help@fineract.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@fineract.incubator.apache.org
From: Thynn Win <thynn.win@thitsaworks.com>
To: "'mifos-developer@lists.sourceforge.net'"
	<mifos-developer@lists.sourceforge.net>, "dev
 (dev@fineract.incubator.apache.org)" <dev@fineract.incubator.apache.org>
Subject: Mifos upgrade (Multi tenant env) and how to handle schema changes (if
 any)
Thread-Topic: Mifos upgrade (Multi tenant env) and how to handle schema
 changes (if any)
Thread-Index: AdJAa8MQn4hAbXZrRbe5cEginwAdUg==
Date: Thu, 17 Nov 2016 01:47:36 +0000
Message-ID: <CY4PR19MB0903C2A6C0666BFCACF0DE0FEFB10@CY4PR19MB0903.namprd19.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: thitsaworks.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_CY4PR19MB0903C2A6C0666BFCACF0DE0FEFB10CY4PR19MB0903namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Nov 2016 01:47:36.0885
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 016bae49-9fb2-449e-b368-94c076e8fbdb
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR19MB0902
archived-at: Fri, 18 Nov 2016 22:00:45 -0000

--_000_CY4PR19MB0903C2A6C0666BFCACF0DE0FEFB10CY4PR19MB0903namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

We are planning to upgrade from 16.03.03 to 16.09.01 (windows env). We woul=
d like to know if the upgrade scripts are run at the re-start of tomcat ser=
ver and will the data structure changes be applied to all tenant databases?=
 Suppose we have 5 tenants using the same application server but a differen=
t database server for their tenant databases. We understand the application=
 will be upgraded with new war files but would like to know -

1) whether the data structure (dll statements) changes will be applied to a=
ll tenants also

2) how to find out which release has database changes and which not. This w=
ay, we can pay attention to which release has structure changes and also ve=
rify them after the upgrade.

For instance: We see that 16.08.01 has a feature for capturing client addre=
ss and we assume it will have some database structure changes.

If you could provide us advise or directions on how the upgrade generally w=
ork in multi-tenant environment and how we can verify the changes, we would=
 appreciate it.

Thank you,
Thynn


--_000_CY4PR19MB0903C2A6C0666BFCACF0DE0FEFB10CY4PR19MB0903namp_--