Migrating Sites on the UCI Cascade CMS Server

Before You Begin

You must be granted the Global Site_Creators role in order to be able to perform a Site migration. Contact Jim Kreuziger at UCI Communications to acquire this role if you don’t already have it. He has a training session web developers must complete before being given this role.

Create a Group and a Site Role

Groups

Before you begin creating Sites, you should create a division-wide group that will contain all users in your division who will have access to administer all Sites for your division. This should be a very restricted group, with possibly only you in it.

  1. Similarly, create a new Role under Administration –> Users, Groups, & Roles. Make it a Site role, and name it according to the convention below:
    [Division Abbreviation]_SiteAdministrator
    For Student Affairs, the role is named SA_SiteAdministrator.

Migrate from Global to Sites

In this example, the Parents web site is getting migrated to a Site.

  1. In the Global area, go to Administration –> Targets & Destinations.
  2. Navigate to your web site’s targets and make sure that all the targets relating to this web site are children of a single target relating to this web site. In the screen shot below, SA_parents_php and SA_parents_xml used to be direct descendants of SA Internal and now they have been moved to be descendants of a new Parents target.
    Targets
  3. Next, consider how many distinct types of users you will require for your web site. Do you have users who are only Contributors, Approvers, Publishers, or Managers for this web site? For each type, you will need to create a new Site Role for this new Site.
  4. Still in the Global area, go to Administration –> Users, Groups, & Roles.
  5. For each role you need (determined in step 3), create it under New Role, with role type “Site“.;
  6. If this is a Contributor Role, pick “Contributor” under “Based on original role.” Click on “System” and name your role user the following method:
    [Division Abbreviation]_[Site Name][Role] For the Parents Site, the roles would become ­SA_ParentsContributor, SA_ParentsPublisher, etc. With “SA” being the abbreviation for Student Affairs.
  7. You are now ready to migrate the Site. Go to the “Cascade Swirl” menu and select Utilities –> Site Migration Wizard.
  8. For Name, follow this format:
    [Division Abbreviation]_[Site URL, minus the http://] For the Parents Site, this becomes, SA_www.parents.uci.edu.
  9. Site URL is simply the base URL of the site. For Parents, http://www.parents.uci.edu/.
  10. The Target should point to the single parent target of all of web site’s targets, as configured in step 2. Click Next.
  11. For your destinations, select each distinct destination once. You may have several listed, such as below:
    In this example, the destinations Live and Staging appear twice because they were both destinations belonging to the PHP target and the XML target of the web site. Select either Live destination and either Staging destination and click Next. Here, the first two were selected.
  12. The next screen should NOT be skipped, even though it is optional. You must select the roles that are applicable to this new Site, and how they are mapped to regular groups and users.
  13. In the Role Selection area, move your division-wide site administrator role into the right panel. This is the role that you created or already exists from a previous migration (step iii).
  14. Once the role is moved to the right panel, a group mapping area appears below. Under the section for the admin role, select the admin group created in step ii.
  15. Continue and add all the other roles created for this Site and map the correct groups to the appropriate roles. For the Parents Site, we only need to add the other two roles,SA_ParentsContributor and SA_ParentsPublisher, then map the groups that already existed for the web site. Click Next.
  16. Click on Test Migration. This process will take anywhere from 5 to 20 minutes, depending on the size of your web site. Stay on the page, letting it take its time to load, since it doesn’t save the report for you—only displays it when it’s done.
  17. The resulting report may show some errors and warnings about the migration. All the errors must be resolved before the migration can occur. 
    You will get errors regarding Templates or Configuration Sets that are being shared with assets in other base folders. Cascade gives a detailed error description and possible solution in the report. It’s up to you to look at the Subscribers tab of each Configuration Set and modify things to make sure that your Site’s assets are not using Templates or Configuration Sets from outside your base folder. For example, in the Parents site, we have page assets that were using a Configuration Set from a different site (which used a template also from that different site), so we had to change the Configuration set on all of those pages to a new one that used a template within our base folder.
  18. Leave the migration report open and do your corrections in another browser tab, this way you can reload the report page to run it again without having to go through the first steps of the wizard again.
  19. Once all the errors have been resolved, click Continue, and then Submit to start the actual conversion. This will take another 10 to 30 minutes, depending on the number of assets in the Site.
  20. There is a bug in Cascade that prevents you from editing the attributes of the Site after a using the Site Migration Wizard. You will need to contact Jim Kreuziger at UCI Communications to regain access. You need this access to change role/group mappings or attributes like the Site’s name, URL, and default asset factory folder.

Congratulations! You can now select between the Global area and your Site in the drop-down menu at the top of the page.