...
Impact:
Mobile Apps will not work any more
GOTHOMSIS GOTHOMIS & Payment Layer in TZ
stuck to MS SQL because of stored procedures that are called from REST API (ca. 45)
Discussion:
C#-part can be re-used, but depend on stored procedures
done - needs to be compiled for .net core per Windows and Linux (done in Docker)
Mobile App on REST
Need new mobile app
ePayment on REST
migrate APIs to python
Interoperability on REST
e.g. GOTHOMISs & afyacare
done - Added to Docker packaging
done - issue with env variables (ex. DB connection string)
done - sharing of files (ex. Insuree pictures)
Test REST API against PostgreSQL
list of interactions with DB: https://docs.google.com/spreadsheets/d/1Qg9sv90-cOIlt4bgTsusAQtIhWITl2XTkIPghIULUtE1XdamXxLejmPRzM5xN8dCSPSIbfNv1PgJ/edit#gid=01496686413
create/modify payment layer adapter on the openIMIS side for TZ
Custom Modifications
Impact: depends, will have to be collected per country by implementation partners
push for customizations based on module configuration
...
Impact: depends
Discussion: need to list remaining stored procedures that will not be migrated
https://docs.google.com/spreadsheets/d/18XxbBsPXvHrq7Enu7Bj02WpE1GiIaslNP1aMK6ECQcU/edit#gid=0
Lock Mechanism
will need to be migrated to PostgreSQL?
testing - PostgesSQL uses low isolation level by default - might solve the problem
wip
...