CMDBuild Forum

Migration to new version of my CMDBuild application

Old Versions
#1

Dear team, 

Do you have some "New Version Installation" script not concerning the CMDBuild new version, but my application version. 

For example I have my application in version 1.0 based on CMDBuild deployed in production environment with live production data. 

I have developed  my application in version 2.0 and tested it, filled with testing data. I need to migrate production instance to version 2.0. It means I need to:

EITHER:

- to keep the existing production data
- add new classes, processes, attributes, views, filters, reports, lookups etc. into the production DB
- reflect all changes made to existing objects in the production DB including changes my code lists

OR:

- take the new DB version
- delete all testing data excluding my code lists
- transform the data from the production DB (excluding code lists) into the new version DB

No of the above variants is simply. How do you solve the application versions migration?

Thanks for your answer in advance,

Best regards,
Jiří

#2

I suggest you follow the CMDBuild Technical Manual, page 19.
CMDBuild Team

#3
Daer team, 
I am sorry, you did not understand me. I do not need to update CMDBuild version. It is very simple and it works very well.
I have both versions of my application based on the CMDBuild version 2.4. 
But the old version of my application 1.0 is in production with production data, that has to be kept.
And the new version of my application 2.0 is in testing environment with new functionalities, but it contains only testing data. 
So, my problem is EITHER how to migrate my application in production form version 1.0 to version 2.0 and keep the production data, OR how to migrate production data from application v. 1.0 into application v. 2.0. 
Thanks and regards, 
Jiří
 
 
 
Previously Tecnoteca wrote:
I suggest you follow the CMDBuild Technical Manual, page 19.
CMDBuild Team
#4

The changes to the system tables are resolved with the standard update procedure.

The changes to classes and domains of your data model can be derived, starting with version 2.1.4, from the cmdbuild_dd_sql.log file (or similar, depends on how you configured the name in log4j.conf file).

Apart from this, there are no automatic procedures available.

CMDBuild Team

1 Like
#5
Thank you very much. The file cmdbuild_dd_sql.log is very good knowledge for me. I can find there changes to classes, attributes, processes, domains and lookups.
 
How can I understad the sentence "The changes to the system tables are resolved with the standard update procedure."? It is not clear to me. What is the standard update procedure?
 
Is it possible to copy the content of other CMDBuild tables as _Filter, _View, _Widget etc.? Or should I manually create / change the objects in the administration module? 
 
Thanks and regards,
Jiří
 
Previously Tecnoteca wrote:
The changes to the system tables are resolved with the standard update procedure.

The changes to classes and domains of your data model can be derived, starting with version 2.1.4, from the cmdbuild_dd_sql.log file (or similar, depends on how you configured the name in log4j.conf file).

Apart from this, there are no automatic procedures available.

CMDBuild Team