Administrator's Guide

Transcription

1 Sitecre CMS 5.3 t CMS 6 Database Cnversin Tl Administratr's Guide Installatin, cnfiguratin and usage guide fr Sitecre CMS administratrs.

2 Table f Cntents Chapter 1 Intrductin Hw the Cnversin Tl Wrks Manual Cnversin Tasks Limitatins... 6 Chapter 2 Strategies fr Cnverting Sitecre CMS 5.3 Databases t Sitecre CMS Chapter 3 Prerequisites... 8 Chapter 4 Preparatins Decide Which Databases t Cnvert Install Database Cnversin Tl Create Custm Security Dmains Cpy "Security templates.xml" File Cpy Sitecre CMS 5.3 Databases Back Up Sitecre CMS 6 Cnfiguratin Files Add Cnnectin Strings Add Database Definitins Allw the dt (".") in Item Names Increase httptimeut Disable Search Indexes Upgrade Package File Name Chapter 5 Databases Upgrade Steps Select Databases Autmatic Database Cnversin Chapter 6 Manual Database Cnversin Cnvert Database Structure Transfer Archives Cnvert Security Transfer Accunts Cnvert Security Fields Update Fields Cnvert Media Links Cnvert Masters t Branch Templates Mve Field Types Mve Html Editr Prfiles Install Update Package Final Cleanup Chapter 7 Clean Up Databases and Slutin Chapter 8 Further Cnversin Steps Page 2 f 45

3 Chapter 1 Intrductin This dcument describes hw t use the Sitecre CMS 5.3 t CMS 6 Database Cnversin Tl. The purpse f this tl is t cnvert Sitecre CMS databases frm versin rev r later t Sitecre CMS Update-3. Page 3 f 45

4 1.1 Hw the Cnversin Tl Wrks Typically yu will attach all yur Sitecre CMS 5.3 databases (except fr the "web" database) and run the cnversin tl. The result f the cnversin will be: A "master" database that yu can use with versin 6. An upgraded versin 5.3 cre database frm which yu can transfer items t the versin 6 cre database. All security accunts transferred t standard.net security database tables (typically lcated in the versin 6 cre database) Items frm versin 5.3 archive and recycle bin databases mved int the new "Archive" tables in the database frm which the items have been archived/deleted. Page 4 f 45

5 1.2 Manual Cnversin Tasks After cnverting the databases yu need t perfrm sme actins manually t finish the slutin migratin. Yu need t recmpile yur.net cde and cnfigure any custm event handlers, pipeline steps, etc., see Chapter 8, Further Cnversin Steps fr details. Page 5 f 45

6 1.3 Limitatins The tl currently has the fllwing limitatins. Only Micrsft SQL Server and Oracle databases are supprted. The tl cnverts the cntent f Sitecre CMS 5.3 cre database and then yu need t transfer ne r mre items (such as custm applicatins) int a clean Sitecre CMS 6 cre database. The tl cannt upgrade a versin 5.3 cre database and turn it int a wrking versin 6 database. The tl nly supprts transferring users and rles that are stred as items in a standard Sitecre CMS 5.3 security databases t the new.net membership and rle tables. If yu have a custm dmain that stres accunts in a different database structure, yu must write a custm script t transfer the users and rles t the relevant.net tables. Alternatively, yu can implement custm.net prviders t use yur current database structure with versin 6. The tl des nt upgrade PublishQueue. When the cnversin is finished, smart r full republishing is mandatry. Custm fields fr the "Rle" template are nt supprted in Sitecre CMS 6 since yu cannt assign prperties t rles in the ASP.NET 2.0 security mdel. The database cnversin tl will nt transfer values f such fields. Page 6 f 45

7 Chapter 2 Strategies fr Cnverting Sitecre CMS 5.3 Databases t Sitecre CMS 6 There are at least tw different strategies fr cnverting versin 5.3 databases t versin 6: 1. D a "straight cnversin" where yu cnvert the versin 5.3 "master" database and use it as the "master" database fr versin "Start frm scratch" where yu cnvert the versin 5.3 "master" database and then manually transfer templates, cntent, branches, etc. t a clean versin 6 master database. Sme partners even chse t manually build up the templates frm scratch in versin 6 and nly transfer cntent. Ding a "Straight Cnversin" The advantages f a "straight cnversin" are: Yu can use the upgraded versin 5.3 master database directly with versin 6. Yu can fcus n making yur cde run with versin 6 instead f spending time n manually transferring items frm the versin 5.3 t the versin 6 database. Ptential disadvantages Yu might end up with mre "legacy" items in the database, such as bslete branches. Starting frm Scratch The advantages f "starting frm scratch" are: Yu knw that yu are starting ut with a cmpletely clean versin 6 database. Yu will mst likely end up with less "legacy" items in the database. Ptential disadvantages: Deciding which items t transfer frm the versin 5.3 database t the versin 6 database might be time-cnsuming. Yu might have t transfer yur data in smaller prtins t avid timeuts and/r "ut f memry " errrs. Page 7 f 45

8 Chapter 3 Prerequisites Surce installatin A Sitecre CMS 5.3 slutin t be upgraded. The slutin des nt need t be running Target installatin A clean Sitecre CMS 6.X.X slutin. The slutin must be running. Database Cnversin Tl Yu will need t dwnlad the Sitecre CMS 5.3 t CMS 6 Database Cnversin Tl (and any assciated dwnlads) frm the SDN if yu haven't already dne s. Page 8 f 45

9 Chapter 4 Preparatins 4.1 Decide Which Databases t Cnvert Befre yu start the cnversin, yu must decide which databases yu want t cnvert. Nrmally yu will want t cnvert the fllwing V5.3 databases: master security extranet databases If yu have made changes t the "cre" database (such as adding custm applicatins t the start menu) and yu want t transfer sme f these changes, yu shuld als cnvert the "cre" database. Optinally, yu can cnvert the "archive" and "recycle bin" databases. Imprtant Cnverting the "archive" and "recycle bin" databases can take a lng time if the databases cntain a big number f items. We therefre recmmend that yu skip these databases if yu are ding a test cnversin f yur databases in rder t start upgrading yur.net cde. Page 9 f 45

10 4.2 Install Database Cnversin Tl Dwnlad the V6DBCnversinTl-XXXrevXXXXXX zip-file frm the SDN. Nte It must be installed and run n the target clean Sitecre CMS 6.X.X slutin. Install the database cnversin tl: 1. Start the "Installatin Wizard". 2. Uplad the V6DBCnversinTl-1.0.0revXXXXXX.zip package. 3. Install the package. Grant the annymus user access t the /Website/sitecre/admin/upgrade flder (r use Windws Authenticatin) in rder t be able t access the database cnversin tl aspx page. Page 10 f 45

11 4.3 Create Custm Security Dmains Ntice Yu can skip this step if the V5.3 slutin is nly using the "extranet" and "sitecre" dmains. In rder t transfer security accunts crrectly, yu must create any custm dmains. This can be dne using the Sitecre Desktp: 1. Lg in t the Desktp f yur V6 slutin 2. Open the "Dmain Manager" (Sitecre» Security Tls» Dmain Manager) 3. Create the dmain(s) Alternatively, yu can add dmains by manually editing the /App_Cnfig/Security/Dmains.cnfig.xml file. Page 11 f 45

12 4.4 Cpy "Security templates.xml" File Yu must cpy the Security templates.xml file t the Sitecre CMS 6 slutin t transfer security settings: Lcate the Security templates.xml file in the /sitecre/shell/ flder f the CMS 5.3 slutin. Cpy the file t the /sitecre/shell/ flder f the CMS 6 slutin (verwrite the existing file). Page 12 f 45

13 4.5 Cpy Sitecre CMS 5.3 Databases It is strngly recmmended that yu make a cpy f the V5.3 databases and use these cpies when upgrading the database cntent. Apply the Prepare fr cnversin t v6 script.sql script t these cpies. It will ensure that Sitecre SQL databases have the crrect database schema and prevent frm related errrs during the database cnversin prcess. We recmmend that yu d nt try t upgrade yur V5.3 "web" database. Instead, perfrm a Full Publish after the cnversin is finished t publish the upgraded master database t the V6 "web" database. Page 13 f 45

14 4.6 Back Up Sitecre CMS 6 Cnfiguratin Files Make a cpy f the fllwing files in the clean Sitecre CMS 6 slutin: web.cnfig /App_Cnfig/CnnectinString.cnfig if yu cnvert Micrsft SQL Server databases r /App_Cnfig/CnnectinStringOracle.cnfig if yu cnvert Oracle databases. Page 14 f 45

15 4.7 Add Cnnectin Strings The purpse f this step is t make the V5.3 databases available t yur V6 slutin s that the cnversin tl has access t the databases. Ntice that all V5.3 databases shuld be attached using the database names that were used in V5.3, except fr the cre database which must be attached as "v53_cre". If yu cnvert Micrsft SQL Server databases, attach them by perfrming the fllwing steps: 1. Open the /App_Cnfig/CnnectinStrings.cnfig file in the V6 slutin. 2. The file shuld cntain 3 cnnectin strings. They culd fr example lk like this: <add name="cre" cnnectinstring="user id=user;passwrd=passwrd;data Surce=(server);Database=Sitecre_Cre" /> <add name="master" cnnectinstring="user id=user;passwrd=passwrd;data Surce=(server);Database=Sitecre_Master" /> <add name="web" cnnectinstring="user id=user;passwrd=passwrd;data Surce=(server);Database=Sitecre_Web" /> 3. Rename "master" t "v6_master": <add name="v6_master" cnnectinstring="user id=user;passwrd=passwrd;data Surce=(server);Database=Sitecre_Master" /> 4. Add cnnectin strings fr the V5.3 databases that yu want t upgrade. Each database name in the cnnectin string must be the same it was in V5.3, except the case if yu wish t upgrade data in the V5.3 cre database; in this case yu must attach it as "v53_cre". If yu are using aut attached databases, the cnnectin strings culd lk like this: <add name="master" cnnectinstring="user id=user;passwrd=passwrd;data Surce=.\SQLEXPRESS;AttachDBFileName=C:\Inetpub\wwwrt\Sitecre 6.0\Databases_v53\sc53Master_Data.mdf"/> <add name="security" cnnectinstring="user id=user;passwrd=passwrd;data Surce=.\SQLEXPRESS;AttachDBFileName=C:\Inetpub\wwwrt\Sitecre 6.0\Databases_v53\sc53Security_Data.mdf" /> <add name="extranet" cnnectinstring="user id=user;passwrd=passwrd;data Surce=.\SQLEXPRESS;AttachDBFileName=C:\Inetpub\wwwrt\Sitecre 6.0\Databases_v53\sc53Extranet_Data.mdf" /> <add name="v53_cre" cnnectinstring="user id=user;passwrd=passwrd;data Surce=.\SQLEXPRESS;AttachDBFileName=C:\Inetpub\wwwrt\Sitecre 6.0\Databases_v53\sc53Cre_Data.mdf" /> <add name="recyclebin" cnnectinstring="user id=user;passwrd=passwrd;data Surce=.\SQLEXPRESS;AttachDBFileName=C:\Inetpub\wwwrt\Sitecre 6.0\Databases_v53\sc53RecycleBin_Data.mdf" /> <add name="archive" cnnectinstring="user id=user;passwrd=passwrd;data Surce=.\SQLEXPRESS;AttachDBFileName=C:\Inetpub\wwwrt\Sitecre 6.0\Databases_v53\sc53Archive_Data.mdf" /> If yu cnvert Oracle databases, attach them by perfrming the fllwing steps: 1. Open the /App_Cnfig/CnnectinStringsOracle.cnfig file in the V6 slutin. 2. The file shuld cntain 3 cnnectin strings. They culd fr example lk like this: <add name="cre" cnnectinstring="user id=sccre; passwrd=sccre; Data Surce=XE" /> <add name="web" cnnectinstring="user id=scweb;passwrd=scweb; Data Surce=XE" /> Page 15 f 45

16 <add name="master" cnnectinstring="user id=scmaster; passwrd=scmaster; Data Surce=XE" /> 3. Rename "master" t "v6_master": <add name="v6_master" cnnectinstring="user id=scmaster; passwrd=scmaster; Data Surce=XE" /> 4. Add cnnectin strings fr the V5.3 databases that yu want t upgrade. Each database name in the cnnectin string must be the same it was in V5.3, except the case if yu wish t upgrade data in the V5.3 cre database; in this case yu must attach it as "v53_cre". If yu are using aut attached databases, the cnnectin strings culd lk like this: <add name="master" cnnectinstring="user id=sc53master; passwrd=sc53master; Data Surce=XE" /> <add name="security" cnnectinstring="user id=sc53security; passwrd=sc53security; Data Surce=XE" /> <add name="extranet" cnnectinstring="user id=sc53extranet; passwrd=sc53extranet;data Surce=XE" /> <add name="v53_cre" cnnectinstring="user id=sc53cre; passwrd=sc53cre; Data Surce=XE" /> <add name="recyclebin" cnnectinstring="user id=sc53recyclebin; passwrd=sc53 recyclebin; Data Surce=XE" /> <add name="archive" cnnectinstring="user id=sc53archive;passwrd=sc53archive; Data Surce=XE" /> Page 16 f 45

17 4.8 Add Database Definitins Nw that the cnnectin strings are in place, yu need t add database definitins s that Sitecre CMS knws abut each database. The easiest way t d this is t use the new "include.cnfig files" functinality in Sitecre CMS 6, which allws yu t mdify the cnfiguratin withut changing the web.cnfig file. As a part f the database cnversin tl, we prvide a number f include files t make the task f adding databases easier. Imprtant Ntice that the "db_master.cnfig" file will temprarily change the name f the V6 "master" database t "v6_master". S fr the rest f this dcument, we assume that "v6_master" database is the clean Sitecre CMS 6 master database, while "master" is the Sitecre CMS 5.3 master database being cnverted. Perfrm the fllwing steps t add the database definitins: 1. Cpy files frm "/sitecre/admin/upgrade/includefiles" int "/App_Cnfig/Include" (including the ItemNameValidatin.cnfig file which is explained in Sectin 4.9, Allw the dt (".") in Item Names). 2. By default, these include files will add database definitins fr the fllwing databases: a. master b. security c. extranet 3. If yu want t upgrade the cntents f the V5.3 cre database r migrate data frm the archive r the recycle bin database, rename the apprpriate "db_*.cnfig.disabled" files t "db_*.cnfig". a. Fr example, rename "db_recyclebin.cnfig.disabled" t "db_recyclebin.cnfig" if yu want t migrate data frm the V5.3 recycle bin database. 4. If yu have any custm V5.3 databases that yu want t cnvert, yu must create an include file fr each database. a. Cpy ne f the existing include files (fr example "db_security.cnfig" if yu want t cnvert a custm security database) b. Open the include file and lcate the fllwing line: <database id="security" singleinstance="true"...> c. Change the database id t the name f yur custm database, fr example: <database id="intranet" singleinstance="true"...> d. Imprtant: If yu have made a cpy f "db_master.cnfig", yu must remve the fllwing lines frm the tp f the file fr yu custm database definitins: <!-- make sure v6 master database is renamed --> <database id="master"> <patch:attribute name="id">v6_master</patch:attribute> </database> 5. Optinally lg in t the Sitecre CMS 6 desktp (default lgin credentials: lgin: Admin, passwrd: b) t verify that yu can see the databases. Page 17 f 45

18 a. Ntice hwever that trying t see data in any f the V5.3 databases might nt wrk, since their database structure has nt been updated yet. Page 18 f 45

19 4.9 Allw the dt (".") in Item Names In Sitecre CMS 6, the default value fr the "ItemNameValidatin" has been changed s that it is n lnger pssible t create items with the dt characters (".") in item names. Many Sitecre CMS 5.3 slutins have item names with dts, s we prvide an include file that changes the ItemNameValidatin setting t "^[\w\*\$][\w\s\-\$\.]*$" which will allw item names with dts. If yu d nt need this functinality, feel free t remve this include file r rename it t ItemNameValidatin.disabled. Nte If yu prvide a custm pattern fr the ItemNameValidatin setting, insert this pattern int the include file (r remve the file), since the include file verrides the value that is specified in the web.cnfig file. Page 19 f 45

20 4.10 Increase httptimeut By default ASP.NET has a 10 minute respnse timeut. Fr sme peratins, fr example archive cnversin, this time is nt enugh. When installing the Update Package Installatin Wizard, a Web.cnfig file which increases the timeut t 170 minutes is installed int the /sitecre/admin flder. If that time is still nt enugh, change the fllwing setting in the /sitecre/admin/web.cnfig file: <httpruntime maxrequestlength=" " executintimeut="21600" /> Page 20 f 45

21 4.11 Disable Search Indexes There are tw reasns t turn the searching functinality ff: Optimizatin purpse Sitecre CMS 6.0 des nt supprt Oracle databases frm versin 5.3 T disable search indexes, special cnfiguratin file is prvided which is lcated by the fllwing path: sitecre\admin\upgrade\includefiles\disablesearch.cnfig. Cpy this file int App_Cnfig\Include flder and restart Sitecre applicatin t make cnfiguratin settings wrk. If this recmmendatin was skipped, yu wuld bserve an exceptin like ORA-00942: table r view des nt exist right after starting f Sitecre applicatin with versin 5.3 Oracle databases attached. Page 21 f 45

22 4.12 Upgrade Package File Name Upgrade package, which prvided with the database cnversin tl, culd have different names depending n the target versin f Sitecre CMS 6 it is ging t be used fr. Cnfiguratin file \sitecre\admin\upgrade\includefiles\upgradepackagefilename.cnfig is prvided with the database cnversin tl and must be cpied int App_Cnfig\Include flder befre starting a cnversin prcess. Unless yu prperly cpied cnfiguratin file yu wuld see file nt fund exceptin during the Install Update Package step. Page 22 f 45

23 Chapter 5 Databases Upgrade Steps The database cnversin frm V5.3 t V6 is perfrmed with the help f a series f aspx pages. Yu get access t these aspx pages by pening the fllwing URL: /sitecre/admin/upgrade/main.aspx Page 23 f 45

24 5.1 Select Databases This step allws yu t select which databases t cnvert. The chices yu make n this page determine which databases will be cnverted in the subsequent steps. The cnversin tl recgnizes the standard V5.3 database names, and will make apprpriate selectins autmatically (database type and dmain/archive name). Usage Guide 1. Verify that all databases that yu want t cnvert are listed n the page. 2. Make sure yu put checkmarks nly next t the databases that yu want t cnvert. 3. Select the relevant database type fr each database. a. "Cntent" is used fr cntent databases (master, cre, custm cntent databases). b. "Security" is used fr security databases. c. "Archive/recycle bin" is used fr archive databases, including the Recycle Bin. 4. Fr all security databases, make sure that the crrect V6 dmain is selected. The users and rles will be transferred t this dmain. Page 24 f 45

25 5. Fr all archive databases, make sure that the crrect archive is selected in the Archive name field. By default, all cnversin steps will be perfrmed autmatically. This is the recmmended cnversin mde. If yu want t perfrm a step-by-step manual cnversin, select the relevant radi buttn in the cnversin mde sectin. Page 25 f 45

26 5.2 Autmatic Database Cnversin This page will cnvert the selected Sitecre CMS 5.3 databases s that they can be used with Sitecre CMS 6. Imprtant It is strngly recmmended t read the "Manual Database Cnversin" chapter fr a descriptin f each step. Pay special attentin t the sectins marked with "Ntice:" and "Imprtant". Usage Guide 1. Click "Start cnversin". 2. A reprt with the status f all the executed cnversin steps will be displayed in the right-hand side f the page. 3. When the cnversin has been cmpleted, yu shuld review the reprt fr infrmatin abut cnversin errrs and warnings. Page 26 f 45

27 Chapter 6 Manual Database Cnversin When perfrming a manual cnversin, yu will be presented with a list f the cnversin steps: Always run the cnversin steps in the rder that they are listed n the Manual Database Cnversin page. Page 27 f 45

28 6.1 Cnvert Database Structure This page will perfrm the fllwing actins n the V5.3 databases: Cnvert database tables t new schema Cnvert "blb" values (binary bjects are stred differently in the database in V6) Cnvert prxy definitins (the prxy type is stred differently in the database in V6) Usage Guide: Click "Cnvert" t start the database cnversin. Status fr the database cnversin will be displayed in the right-hand side f the windw. Please wait until this frame has fully laded befre returning t the Main Page. Page 28 f 45

29 6.2 Transfer Archives In Sitecre CMS 5.3, items in the Archive and the Recycle Bin databases are serialized and stred as an XML chunk. In Sitecre CMS 6, the archived items and fields are stred in 3 database tables (Archive, ArchivedItems, ArchivedFields). This page will deserialize the infrmatin in the V5.3 archive databases and stre it in the new frmat. Imprtant Cnverting the "archive" and "recycle bin" databases can take a lng time if the databases cntain a big number f items. We therefre recmmend that yu skip this step if yu are ding a test cnversin f yur databases in rder t start upgrading yur.net cde. Usage Guide: Click "Prcess" t start the peratin. Page 29 f 45

30 6.3 Cnvert Security In Sitecre CMS 5.3, users and rles were stred as items in a Sitecre database. In versin 6, users and rles are by default stred in standard ASP.NET 2.0 Membership and Rle tables (depending n the prvider cnfiguratin in the web.cnfig file). In versin 6, all users and rles are stred in the same database tables, nt in different databases fr each dmain. Therefre, users and rles will nw have their dmain as a prefix. Fr example, the user named "Annymus" in the "extranet" dmain will nw have the username "extranet\annymus". TIP By default, Sitecre CMS 6 will use the Membership and Rle tables in the "cre" database. If yu wish, yu can cnfigure Sitecre t use a separate database fr string users and rles by changing the relevant cnnectin strings fr the security prviders in the web.cnfig file. Ntice The Cnvert Security page can nly transfer security accunts and rle assignments frm standard V5.3 databases where users and rles are stred as Sitecre items. If yu have a custm dmain that stres accunts in a different database structure, yu must write a custm script t transfer users and rles t the relevant.net tables. Alternatively, yu can implement custm.net prviders t use yur current database structure with V6. The "Cnvert Security" page cnsists f tw different steps: Page 30 f 45

31 6.3.1 Transfer Accunts This step will create users and rles using the ASP.NET Membership and Rle prviders. The dmain f the users and rles will be added t their V5.3 username t make the dmain assciatin wrk crrectly in V6. Users in the "sitecre" dmain will autmatically be added as members f the "Sitecre Client Users" rle, therwise they wuld n lnger be able t lg int the Sitecre clients (Desktp, Page Editr, etc.). Imprtant Ntes Existing users (such as "sitecre\admin") will be updated t match the infrmatin in the Sitecre CMS 5.3 database. All prperties (fr example name, and passwrd) will be verwritten, and the rle assignments will be updated. By default, blank passwrds are nt supprted in Sitecre CMS 6. If ne r mre users have a blank passwrd, their passwrd will be changed t their username in versin 6. This includes the "sitecre\admin" user, s if the Admin user had a blank passwrd in Sitecre CMS 5.3, yu must use "Admin" as the passwrd after the cnversin. During the cnversin, the "extranet\guest" rle will be renamed t "extranet\guests" t avid cnfusin with the "extranet\guest" user. Usage Guide: Click "Prcess" t start the peratin. Infrmatin abut the added user/rles and their assignments will be utput n the page. Page 31 f 45

32 6.3.2 Cnvert Security Fields In Sitecre CMS 6, security assignments are stred in a new frmat that supprts the creatin f custm access rights. As a cnsequence f this change, field security assignments are nw stred in the standard " Security" field and the special "Field Security" field in template fields has been bslete. This step will update the assignments stred in the " Security" field t use the new frmat (including mving assignments in the "Field Security" t the " Security" field). Ntice This page will nt upgrade custm security fields. We recmmend that yu write a custm upgrade script t upgrade such fields and that yu use custm access rights in V6 fr this purpse. Usage Guide: Click "Prcess" t start the peratin Infrmatin abut the cnversin will be utput n the page. Fr assigned access rights in the security field, nly warnings and errrs will be utput. These warnings will typically just mean that sme rights have been assigned t a user/rle that n lnger exists. Fr "Field Security", a list f all template fields with assigned field security permissins will be utput. Ntice If access rights have been assigned t a user r rle that desn't exist in the security database, the access rights fr this accunt will still be cnverted. In this case, a special frmat will be used fr the accunt name (using a prefix + the dmain name + the GUID f the accunt). Example: unknwn: sitecre\{9d305e97-6e64-4aad-8bb7-5d7adafaa8fb} In mst cases, such assignments are nly useful during the cnversin, where they can be used t d trubleshting in relatin t missing accunts. The assignments can be remved autmatically after cnversin as part f the "Final Cleanup" step. Page 32 f 45

33 6.4 Update Fields This step will cnvert the fllwing fields: "Layut" fields. The 'uid' attribute will be added t the XML f all layut fields. Fields that stre references t masters. Sme masters that existed in V5.3 have been remved in V6, since it is nw pssible t insert items directly frm templates. References t the bslete masters in the "Master" fields will be remved. Als, the "Masters" field (nw called "Insert Optins") will be updated s that references t the bslete masters are changed t pint t the relevant templates. "Surce" fields fr html prfiles. The names f sme f the standard prfiles have been changed, and will therefre be updated: Rich Text Default» Rich Text Medium Default» Rich Text Medium Full» Rich Text Full Ntice Since Sitecre CMS V6 n lnger supprt Cute Editr, the standard V5.3 html editr prfiles "Default" and "Full" n lnger exist in V6. References t these prfiles will be changed t "Rich Text Medium" and "Rich Text Full" as described abve. Usage Guide: Click "Prcess" t start the peratin. Infrmatin abut the cnversin will be displayed n the page: Page 33 f 45

34 6.5 Cnvert Media Links In Sitecre CMS 6, links t media items are stred in a new frmat that allws the CMS t dynamically generate apprpriate URLs t media based n the current site, language, etc. The new frmat uses the GUID (in the frm f a 'shrt' GUID) when inserting links in the HTML. Fr example: <a href="~/media/be9e50f7f9dc4c4687bbede567bca2aa.ashx">dwnlad PDF</a> The link will be expanded t a 'nrmal' link with the path t the resurces n the published website. T make this wrk crrectly, existing links must be cnverted t the new frmat. Usage Guide: Click "Prcess" t start the peratin. Infrmatin abut the cnversin will be displayed n the page, including any warnings abut links that culd nt be cnverted t the new frmat (mst likely because the item being linked t des nt exist): Ntice After cmpleting all the database cnversin steps, yu can use the "Brken Link Reprt" in Sitecre CMS t get infrmatin abut the items and fields that cntain references t media items. Page 34 f 45

35 6.6 Cnvert Masters t Branch Templates In Sitecre CMS V6, the branch template replaces the cncept f a master. Existing masters will be cnverted t branches with a single sub-item fr backwards cmpatibility. Ntice Executing this step will take sme time (several minutes) t cmplete, depending n the number f masters t be cnverted. Usage Guide: Click "Prcess" t start the peratin Infrmatin abut the cnversin will be displayed n the page: Yu might get errr messages during the cnversin, fr example if a master exists but the template it is based n has been deleted. Page 35 f 45

36 6.7 Mve Field Types In Sitecre CMS 6, the definitins f supprted field types have been mved t the "cre" database. This step will mve custm field types frm any cntent databases (typically the V5.3 master and cre database) t the V6 cre database. Als, if yu have made custm changes t any f the standard Sitecre field types, these changes will be cpied t the V6 cre database. Ntice If yu have added custm fields t the "Template Field" template, these fields will be autmatically transferred t the cre database. The field type definitins in the V5.3 cntent databases will autmatically be remved frm the selected databases after being mved t the cre database. Page 36 f 45

37 Usage Guide: Click "Prcess" t start the peratin. Infrmatin abut the field types that have been mved t r updated in the V6 cre database will be displayed n the page. If yu have changed the definitin f a field type in mre than ne database (fr example bth in the "master" and "v53_cre" database), an errr message will be utput. Such cnflicts must be reslved manually. Page 37 f 45

38 6.8 Mve Html Editr Prfiles In Sitecre CMS 6, the definitins f Html Editr Prfiles have been mved t the "cre" database. Imprtant This page will verwrite the Html Editr Prfiles in the "cre" database. If yu prcess multiple databases, yu may lse data! We therefre recmmend that yu nly prcess the "master" database. If yu have custm Html Editr Prfiles defined in the V5.3 cre database, we recmmend that yu manually transfer them t the V6 cre database. Ntice CuteEditr is n lnger supprted as rich text editr in V6. The default CuteEditr prfiles named "Default" and "Full" will therefre nt be mved t the cre database. Page 38 f 45

39 Usage Guide: Make sure that the "master" database is selected. Click "Prcess" t start the peratin. It can take several minutes, s please be patient. Ntice: If yu have ther cntent databases with custm Html Prfiles, yu can select them as well, but these prfiles will verwrite any already transferred prfiles. We therefre recmmend that yu manually transfer any additinal prfiles t the V6 cre database. Infrmatin abut the field types that have been mved t r updated in the V6 cre database will be displayed n the page. Page 39 f 45

40 6.9 Install Update Package The purpse f this step is t make the standard Sitecre CMS 5.3 items in the master database match the standard items in a clean V6 database. The package will make required changes t system templates, remve unneeded masters, etc. We recmmend that yu make a backup f yur upgraded master database at this pint, since the Update Package will make changes t the system templates. This means that yu culd ptentially lse data if smething des nt wrk as expected when installing the package n yur slutin. If the Master database has nt been selected n the Select Databases step, then yu just skip Install Update Package step (the Install Package buttn is disabled). T install Update Package, check master check bx and click Install Package. After the installatin is cmplete, yu will be presented with a reprt f errrs, cnflicts and warnings (mst likely a similar number as in the previus step), but ften yu will see mre cllisins due t items having been mved cmpared t V5.3). If yu wish, yu can review the installatin lg file (/data/lgs/upgrade.yyyymmdddd.txt) r yu can exprt the reprt t XML file. When yu are dne, clse the brwser windw t g back t the Main Page After cmpleting this step, yur V5.3 master database will be upgraded t wrk as a Sitecre CMS 6 master database. If yu see file nt fund exceptin during the installatin f the package, check if yu have prperly cpied cnfiguratin file with the name f the upgrade package, see the Upgrade Package File Name sectin fr details. Page 40 f 45

41 6.10 Final Cleanup This page helps yu t clean up yur database after the cnversin frm Sitecre CMS 5.3 t CMS 6. Masters This step will remve references t all nn-existent masters/branches (bth system masters and custm masters). If yu d nt perfrm this step and try t save an item that refers t a nn-existent master, yu'll get a "brken link" warning. Usage Guide: Security Click "Cleanup masters" t start the prcess. This can take a while, s please be patient. The results will be displayed in the right-hand side f the windw. When cnverting security fields (as a part f the "Cnvert Security" step), the cnversin tl ften encunters access rights that have been assigned t a user r a rle that des nt exist in the V5.3 security databases. A special frmat is used fr such accunt names (a prefix + the dmain name + the GUID f the accunt). Example: unknwn: sitecre\{9d305e97-6e64-4aad-8bb7-5d7adafaa8fb} This step will remve all references t such security accunts that culd nt be reslved during the cnversin f the security fields. Page 41 f 45

42 Usage Guide: Click "Cleanup security" t start the prcess. This can take a while, s please be patient. The results will be displayed in the right-hand side f the windw. Page 42 f 45

43 Chapter 7 Clean Up Databases and Slutin Database Cleanup Perfrm the fllwing steps t clean up the databases: Rebuild link database. Rebuild search indexes. Republish t web database (use smart r full publishing mde). Slutin Cleanup Perfrm the fllwing steps t clean up yur slutin after the cnversin. Remve include files (db_*.cnfig) frm the "/App_Cnfig/Include" flder (r rename them t *.disabled). This will remve database definitins fr V5.3 databases. Yu might want t leave "db_v53_cre.cnfig" in place, s that yu still have access t items in the upgraded V5.3 cre database. Remve /App_Cnfig/Include/DisableSearch.cnfig. Remve /App_Cnfig/Include/UpgradePackageFileName.cnfig. Change "/App_Cnfig/CnnectinStrings.cnfig" if yu cnverted Micrsft SQL Server databases r "/App_Cnfig/CnnectinStringsOracle.cnfig" if yu cnverted Oracle databases. Remve cnnectin strings fr the unneeded V5.3 databases (as well as the V6 master database). v6_master (ptinal yu might keep it fr reference) security extranet v53_cre (ptinal) recyclebin archive Restre the web.cnfig file. Remve cnversin tl flders. /sitecre/admin/upgrade (including sub flders). Page 43 f 45

44 /sitecre/admin/packages ( nly the V6DBCnversinTl-XXXrevXXXXXX.zip-file) Remve cnversin tl files /bin/sitecre.v6dbcnversin.dll Optinally detach the databases that yu n lnger need frm the database server and delete the database files: security extranet archive recyclebin any custm security/archive databases Page 44 f 45

45 Chapter 8 Further Cnversin Steps Yur databases have nw been upgraded fr Sitecre CMS 6. Typically yu will nw want t perfrm the fllwing steps: Cpy files frm V5.3 slutin t V6 slutin Layuts XSLT files CSS files Media library files stred n disk (as specified by the "Media.FileFlder" setting, typically "/App_Data/MediaFiles") Other Images and graphics Etc. Make the custm cde in yur.net prject(s) cmpile against Sitecre CMS 6. Nte The upgrade prcedure described in this dcument fcuses n upgrading the data in yur Sitecre slutin. This dcument des nt discuss cde-related changes that will be required in mst slutins that use.net cde in Sublayuts r Web Cntrls. Develpers shuld upgrade their.net cde t use the FieldRenderer class as well as dynamic linking features. Add any event handlers, pipeline steps, etc. HINT: Cnsider using "include files" fr this. Transfer items frm the upgraded V5.3 cre database t the V6 cre database. Page 45 f 45