![\"\"](\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_d2.jpg\")
<\/p>\n<\/p>\n
During a migration from D2-Config 3.0 to D2-Config 4.1, we have encountered 2 issues. In order to have a clean installation and the insurance of being able to backup the configuration, we have decided to perform a full config export on D2-Config 3.0 and a full import with a configuration reset to D2-Config 4.1.<\/p>\n
The first issue we experienced was regarding docapps existing in the repository. As you can see in following screenshot,\u00a0D2-Config crashes very quickly.<\/p>\n
<\/p>\n
But we were quickly able to find a solution. We just had to unselect the docapps check boxes and wait a little bit.<\/p>\n
<\/p>\n
After the first import we discovered that some conditions in the menu management were not manageable anymore. But they still applied to D2-Client.<\/p>\n
Actually, a class name is seen – i. e. \u201ceu.c6.web.conditions.permits.HasPermit\u201d – instead of the real condition: \u201cUser has minimum \u201cwrite\u201d permit on the selection\u201d.<\/p>\n
<\/p>\n
We have this result because no migration path was anticipated between the 2 releases of D2-Config and some configuration items kept its old class names…<\/p>\n
Class names now have to start with \u201ccom.emc\u201d instead of \u201ceu.c6\u201d<\/p>\n
In fact (and this was confirmed by C), we need to change the menu, toolbar, and tree configuration items manually.<\/p>\n
Manually here mean to export the full configuration and perform the changes directly inside the zip-archived XML files of the related configuration items. After a quick assessment, we counted around 100 occurrences to be changed in our case. That was too much to be done during an upgrade. So we decided to automatize the process.<\/p>\n
We used a tailor-made Linux script to do that:<\/p>\n
$> .\/updateConfig.sh <config archive name><\/strong><\/span><\/span><\/span><\/strong><\/p>\n After execution, the result was a new D2-Config archive, ready to be deployed, with \u201cUpdate_\u201d as a prefix for the archive name given in parameter.<\/p>\n You can see the content of the script, executed and tested under RHEL 5.10:<\/p>\n \u00a0#!\/bin\/sh <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0# <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0# Script to update D2-config from 3.0 objects level to 3.1\/4.1 <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0if [[ $# -ne 1 ]] ; then <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0echo “ERROR usage : “$0 “” <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0exit 1 <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0fi <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0root_dir=”work”<\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0mkdir -p ${root_dir}<\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0unzip -d ${root_dir} “$1” <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0for file in `grep -RH -i eu.c6 ${root_dir}\/* | cut -d “:” -f 1` <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0do<\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0echo $file <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0mv $file ${file}_old <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0sed -e s\/eu.c6\/com.emc\/g ${file}_old > $file <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0rm ${file}_old <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0done <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0cd $root_dir <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0zip -r “..\/UPDATED_$1” * <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0cd .. <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0chmod 777 “UPDATED_$1” <\/strong><\/span><\/span><\/span><\/strong><\/p>\n \u00a0rm -rf $root_dir<\/strong><\/span><\/span><\/span><\/strong><\/p>\n You can now try to import the updated configuration archive and see the difference.<\/p>\n Be careful, a full config import with configuration reset implies the deletion and recreation of some objects like plublic searches (d2c_query with new r_object_id).<\/p>\n Thanks for reading!<\/p>\n","protected":false},"excerpt":{"rendered":" During a migration from D2-Config 3.0 to D2-Config 4.1, we have encountered 2 issues. In order to have a clean installation and the insurance of being able to backup the configuration, we have decided to perform a full config export on D2-Config 3.0 and a full import with a configuration reset to D2-Config 4.1. 1. […]<\/p>\n","protected":false},"author":40,"featured_media":3945,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[443,129,419,391],"type_dbi":[],"class_list":["post-3955","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-application-integration-middleware","tag-d2","tag-documentum","tag-emc","tag-enterprise-content-management"],"acf":[],"yoast_head":"\n