BASICS

ADMINISTRATION

DEVELOPMENT

SUPER ADMIN

  LAST UPDATED
11/15/2012

Go-live Procedures

The following instructions detail how to update a site that has been built on a development server and the domain name for the live website will be repointed to the development server. No files will be moved and the site does not need to be republished in its entirety. In the following examples, the development server was dev.domain.edu and the production domain is www.domain.edu.

Site Setup

Updating FTP Settings

  1. Navigate to the site record: Setup > Sites > Edit (for the site).
  2. Edit the Production Server FTP/SFTP Settings as follows:

    Server: Change from development server to live production server URL; e.g., s:dev.domain.edu:222 becomes s:www.domain.edu:222. If an IP address is used, no change is necessary.

    FTP Root: May be unchanged if the site does not change server locations, but this should be verified by your server administrators.

    HTTP Root: Update from development to production; e.g., http://dev.domain.edu becomes http://www.domain.edu.

    FTP Root Relative:  The following settings may be unchanged if the site does not change server locations, but this should be verified by your server administrators.
    --FTP Home
    --FTP Directory
    --Image Directory
    --LDP Gallery Directory
    --Template Directory

3. Edit the LDP Settings as follows:
LDP Admin Host: The OU Server Side Module (SSM) may be installed on the same web server as your published files, or it may be on a separate server. If installed on development, update host URL to production. If not, leave unchanged.

Updating Links

If possible, it is recommended to keep the development subdomain active for a period following the go-live to ensure that all links are updated. There are multiple instances where absolute links to the development domain may need to be updated manually. For example, this may occur in RSS items, Assets, and Content.

Updating RSS Feeds and Items

If RSS items have been created prior to going live there are several manual updates. If there are too many items built out to edit by hand, OmniUpdate has a tool to automate this process. Please contact your Project Manager about scheduling the best time prior or after "go-live" to make these updates.

Updating Links for RSS feeds

  1. Navigate to Setup > RSS > Edit (for the feed).
  2. Edit each feed and change the Link from http://dev.domain.edu to http://www.domain.edu.
  3. Click Update.
  4. Click the Rebuild icon for a feed to rebuild the feed.

Updating Links for RSS Items

  1.  Setup > RSS > Items > Edit (for each item).
  2. Change the Link from http://dev.domain.edu to http://www.domain.edu.
  3. For each Media Content item, click the item link to edit it. Update Link and Thumbnail to update file URLs from http://dev.domain.edu/_resources/img/image.jpg to http://www.domain.edu/_resources/img/image.jpg.

Updating Assets

Assets are excluded from Global Find and Replace, so any links to pages at http://dev.domain.edu will need to be manually updated to http://www.domain.edu. Assets must be republished for changes to take effect.

Updating Content

Use Global Find and Replace for any instances of http://dev.domain.edu with http://www.domain.edu in page content. Pages must be republished for changes to take effect.

  1. Please read the Global Find and Replace documentation:
    Find and Replace
  2. Navigate to Content > Find and Replace.
  3. Choose Literal Text search. Review the results with a "find-only" search before doing a full-scale replace.
  4. Example settings:

    Find: dev.domain.edu
    Replace with: www.domain.edu
    Comment: Switch to production domain

Republishing Assets

To enable LDP Gallery assets to be used across multiple sites they are given absolute URLs to the thumbnail and image locations based on current HTTP Root. After the HTTP Root has been updated, gallery assets will need to be checked-out and republished. Republishing the assets will republish all pages on which they are deployed.

Updating Gallery Assets

  1. Navigate to Content > Assets.
  2. Click the header for the Type column. This sorts all assets by type and groups galleries together.
  3. Check-out and publish each gallery asset.

Enabling Analytics

To prevent skewing of analytics data (e.g., Google), the code is typically hidden during development. Enabling analytics will depend on your implementation and what was decided during the specifications process. The most common implementation is for an analytics.inc file to be included on each page.

Updating a Includes File

  1. Navigate to Content > Pages.
  2. Use the HTML Source Editor to view the source of include file, which is commonly located at /_resources/includes/analytics.inc/. Keep in mind the location may be unique to your site.
  3. Remove <!-- ... --> from around code. If no code has been provided, this include will be empty. Existing analytics code can be retrieved from the current website or from http://support.google.com/analytics/bin/answer.py?hl=en&answer=1008080.
  4. Save and publish. This will update all pages where that file is being included.

Finishing Details

  • Test search functionality
  • Test "Share This" links
  • Verify all necessary robots.txt files have been uploaded or updated
  • Verify favicon icon (next to browser address bar) is enabled.

Tips

  • Prepare to go live at a time when you believe the fewest amount of viewers will be visiting the website.
  • Schedule the go-live with OmniUpdate so that members of the OmniUpdate support team can be standing by.
  • Ensure that the production server is set up to parse everything the site's pages need (i.e., server-side includes, PHP, live delivery platform [LDP], etc.).

Contacting Support

Please feel free to contact the Support team with any questions about the process:

support@omniupdate.com


Was this page helpful?

Additional Comments:


(Include your email address if you would like a reply)

Procede to http://support.omniupdate.com/