BASICS

ADMINISTRATION

DEVELOPMENT

SUPER ADMIN

  LAST UPDATED
4/8/2014

About Dependency Manager

Dependency Manager is a service that manages links in files to other pages or directories under management of OU Campus. It maintains the correct link association when files or directories are moved or renamed. All the files that link to a moved or renamed file or directory are automatically republished to maintain the correct link. In the case of directory or file deletion, Dependency Manager creates a notification in the Fix Dependency panel (Dashboard > Fix Dependencies).

Software release v.9.19.7 featured a performance enhancement for Dependency Manager. This involved an improvement in the way that Dependency Manager tags are processed and allows for faster processing of dependency tags. OU Campus sites that include a large number of dependency tags in mega menus, large footers, or other navigation elements be able to take advantage of significant improvement in processing speed resulting in faster rendering of pages; for example, with page previews and publish.

The Dependency Manager is an optional feature set. To utilize the capabilities of the Dependency Manager, please contact Support to have it activated if it is not already on for your account. Please be sure to read the white paper on Dependency Manager prior to contacting Support. It contains information on the benefits, limitations, considerations, and next steps.

To view a Training Tuesday webcast with an overview and a demo of the Dependency Manager, follow this link: Dependency Manager.  This session is appropriate for all OU Campus users.

When pages are published that contain dependency tags links, the dependency tag is replaced with the URL to the target page. The Dependency Manager supports both root relative URL links (e.g., /folder/folder/file.ext) as well as absolute URL links, aka fully qualified URLs, (e.g., http://www.college.edu/folder/folder/file.ext). The Dependency Manager does not create page relative links (although it can read and convert them into dependency tags when the site is scanned). The Dependency Manager will create either root relative or absolute URL links when pages are published based upon what the current access setting for URLs is for each page. Dependency links can be selected across publish targets if Multi-Target Publish is configured and in use for the account.

More about Linking

If a site has the Dependency Manager turned on, then a Dependency Manager tag is created when linking to any file on any site within that account if that target file is under management of OU Campus. This is irrespective of the target site's Dependency Manager setting. The only exception to this is if the file on the target site has never been recorded by the Dependency Manager in the database. Two common causes of this are:

1. The target file existed on the site before Dependency Manager came into being and that file has not been edited in a way that would cause this tag to be properly updated.

2. The target file was uploaded via FTP and also has not been touched in a way to cause the database to assign a Dependency Manager tag to the file.

In these cases, when linking, the appropriate text-type URL to the file is returned.

The other class of selectable files that only return text URLs are files on a target production server that are not under OU Campus management.

So, for example, if Dependency Manager is on for a site within an account, the link to another site with the Dependency Manager off is still tracked with a dependency tag. Likewise, if a site with Dependency Manager off, links to a site with the Manager on, there is not the ability to add a Dependency tag in the first site.

About Binaries

Dependency Manager does not track binaries (e.g., images, documents), with the exception of those that are products of the PCFs (e.g., PDFs generated by a PCF). Therefore, if these are moved or renamed, the linked pages will need to be manually updated as well.

Dependency Manager does not track links to pages or sites not under management by OU Campus. This also applies to sites that are not in the same account as the current site under OU Campus management. The Dependency Manager is account bound and can only track and manage URL changes to pages or directories that are within sites in the same OU Campus account.
Prior to activating Dependency Manager and scanning the sites, it is advised that each site be exported. This will allow for a complete revert, using Zip Import, back to the site’s original state and URL configuration for links should it be decided that utilizing Dependency Manager is not appropriate for the site. It is important to note that this will revert the site to the state it was at the time of export, and if any changes have been made since then, these will be lost.

Please note that upon initial scan (or rescan) of multiple sites within an account, two Dependency Manager scans are required of each site with the exception of the last site scanned, which only requires one scan. The first pass should scan each site one after the other, and the second pass should start from the first site scanned and scan each one again with the exception of the last site. For example, if an account includes 10 sites, 19 total scans would need to be performed in order to ensure that all links among sites include the correct dependency tags.

About HTTP Root

If HTTP Root is changed in the site settings, the entire site should be republished to ensure the links are updated.

About Unpublished Dependencies

Unpublished dependencies publish option — Dependency Manager reports at page publish time if there is dependent content that also has not been published to the target server. This includes content that is linked or referred to by the page that is being published. By selecting to include the unpublished dependencies, those files are published as well. This action prevents broken links (for example) from existing on the current page being published.

This checkbox is only shown if the Dependency Manager is being used on the site, dependency tags are used in the page being published, and one or more of those dependency tags refer to files that have not been published to the target yet. Select the Include unpublished dependencies checkbox during the publish to publish the unpublished content.

Before a file is scanned, OU Campus determines if a file contains HTML according to file extension. The Dependency Manager scanner utilizes this information to determine if a file contains HTML. The list of extensions that determine if a file contains HTML is:

  • .html
  • .htm
  • .xhtml
  • .shtml
  • .shtm
  • .jsp
  • .php
  • .php3
  • .phtml
  • .asp
  • .chtml
  • .cshtml
  • .dna
  • .cfm
  • .inc
  • .aspx
  • .mht
  • .ssi

 

Make sure you read the Important Information and Reminders.


Was this page helpful?

Additional Comments:


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

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