We are currently doing a few changes in the data model that implies database schema changes.
source table is removed. This means simpler manual modification of orgunits.
calculateddataelement table is removed. This means that all your calculated data elements will be lost so make sure you migrate to normal data elements or indicators if you have some you want to retain.
olapurl table is gone.
Please be aware these changes are not backwards compatible and means that you cannot downgrade from trunk to version 2.2 on the same database.
These changes will be made automatically in the database by the application so no action is required on your side.
Thanks for the updates. I’ve installed 2.2 on our server and my local machine without many issues.
In the GIS module some of our computers, there is a message that pops up saying that Google Maps needs to get a different Google Maps API key. When the user clicks on ok, the software loads fine.
Also, the Google normal layer appears on top of the DHIS Healthmapper overlay map and we can’t figure out how to move it behind.
We are currently doing a few changes in the data model that implies database schema changes.
source table is removed. This means simpler manual modification of orgunits.
calculateddataelement table is removed. This means that all your calculated data elements will be lost so make sure you migrate to normal data elements or indicators if you have some you want to retain.
olapurl table is gone.
Please be aware these changes are not backwards compatible and means that you cannot downgrade from trunk to version 2.2 on the same database.
These changes will be made automatically in the database by the application so no action is required on your side.
You can just go to the URL described in the message, put in the URL of your server (apparently hmis.moh.gov.rw) and Google will generate an API key for you. You can then paste this into the Administrator module of the GIS, and this message will disappear. This process should be described in the user manual, but I do not think it has made it into the documentation yet.
You may want to read section 7.4.2 of the implementation guide which describes how to set a reverse proxy with Tomcat and Apache, so that your server will run on port 80 (normal HTTP port) instead of port 8080.
Not sure about the other issue you mention. Have not seen this.
Regards,
Jason
···
On Mon, Apr 25, 2011 at 4:58 PM, Wilson,Randy rwilson@msh.org wrote:
Thanks for the updates. I’ve installed 2.2 on our server and my local machine without many issues.
In the GIS module some of our computers, there is a message that pops up saying that Google Maps needs to get a different Google Maps API key. When the user clicks on ok, the software loads fine.
Also, the Google normal layer appears on top of the DHIS Healthmapper overlay map and we can’t figure out how to move it behind.
Sent: Sunday, April 24, 2011 5:50 PM To: DHIS 2 developers; dhis2-users@lists.launchpad.net Subject: [Dhis2-users] Database changes
We are currently doing a few changes in the data model that implies database schema changes.
source table is removed. This means simpler manual modification of orgunits.
calculateddataelement table is removed. This means that all your calculated data elements will be lost so make sure you migrate to normal data elements or indicators if you have some you want to retain.
olapurl table is gone.
Please be aware these changes are not backwards compatible and means that you cannot downgrade from trunk to version 2.2 on the same database.
These changes will be made automatically in the database by the application so no action is required on your side.
Thanks for the updates. I’ve installed 2.2 on our server and my local machine without many issues.
In the GIS module some of our computers, there is a message that pops up saying that Google Maps needs to get a different Google Maps API key. When the user clicks on ok, the software loads fine.
Also, the Google normal layer appears on top of the DHIS Healthmapper overlay map and we can’t figure out how to move it behind.
Sent: Sunday, April 24, 2011 5:50 PM To: DHIS 2 developers; dhis2-users@lists.launchpad.net Subject: [Dhis2-users] Database changes
We are currently doing a few changes in the data model that implies database schema changes.
source table is removed. This means simpler manual modification of orgunits.
calculateddataelement table is removed. This means that all your calculated data elements will be lost so make sure you migrate to normal data elements or indicators if you have some you want to retain.
olapurl table is gone.
Please be aware these changes are not backwards compatible and means that you cannot downgrade from trunk to version 2.2 on the same database.
These changes will be made automatically in the database by the application so no action is required on your side.
