B Upgrading Pre-7.5 Web Sites

B.3.1 Upgrading Sites on a Single Content Server Instance

If your web sites are stored on a single content server, the upgrade consists of:

1. Installing the new Site Studio component (having first uninstalled the old component).

2. Performing a full upgrade on the content server. For more information, see Section B.3.3, "Performing a Full Upgrade."

3. Performing additional steps manually that are not handled by the automated upgrade. For more information, see Section B.4, "Performing Additional Steps Manually."

B.3.2 Upgrading Sites on Multiple Content Server Instances

You may have sites on multiple content servers, each serving a different purpose, such as a development server, a contribution server, and a production server.

Figure B-1 Multiple Content Server Instance Illustration

Description of "Figure B-1 Multiple Content Server Instance Illustration"

The content on each server (source server) gets copied to the next server (target server) using the Archiver/Replicator utility. As such, it is important to carefully plan and upgrade the sites on each server without encountering replication problems.

On the First Two Instances of the Content Server

• Stop replication between the content servers.

• Install the new Site Studio component.

On the Source Instance of the Content Server

• Perform a full upgrade of your sites. For more information, see Section B.3.3, "Performing a Full Upgrade."

  Then:

• Perform additional steps manually (steps not handled by the automatic upgrade). For more information, see Section B.4, "Performing Additional Steps Manually."

On the Target Instance of the Content Server

• Perform a minimal upgrade of your sites. For more information, see Section B.3.4, "Performing a Minimal Upgrade."

On Both Instances of the Content Server

• Start replication again between the content servers.

  Once the new component has been installed on all instances of the content server and web sites have been upgraded as indicated above, you can begin replicating your sites again.

  You can use the replication feature in Site Studio (see the Oracle Fusion Middleware Administrator and Manager's Guide for Site Studio). Or, if you have been using Archiver/Replicator and want to continue using it, you can do so as long as you modify the archive query to include Site Studio project files.

On the Next Target Content Server (Downstream in Replication)

• Stop replication between the source and target content servers.

  Note:

  In this case, your source server (Box 2) was the target server in the previous steps, and your target server (Box 3) is the next server down the line (downstream) in your replication.

• Install the new Site Studio component.

  Then:

• Perform a minimal upgrade of your sites. For more information, see Section B.3.4, "Performing a Minimal Upgrade."

  Then:

• Start replication again between the source and target content servers.

Repeat this last procedure for each target instance of the content server downstream in your replication.

B.3.3 Performing a Full Upgrade

A full upgrade of the content server is required in the case of single-server setup. It is also required for the source server in the case of a multi-server setup. (All other servers in a multi-server setup require a minimal upgrade.)

When you upgrade your site, Site Studio turns your existing folder-based site into a project-based site. When it does this, it creates a project file as a managed item in the content server. As such, you must identify the metadata that you would like assigned to the project file that will represent each web site.

During the upgrade process, the content server attempts to index content that gets changed, which could take considerable time and resources. You may want to temporarily disable automatic indexing before you begin the upgrade process and then re-enable it when you are done. (See the Oracle Content Server administration documentation for further details.)

You should have already installed and enabled the new Site Studio component on the server before you start a full upgrade.

To perform a full upgrade, perform these tasks:

1. Log on to the content server as an administrator, open the Administration page, and then the Site Studio Administration page.

2. Click Set Project Default Document Information.

   The Set Project Default Document Information page opens. This is where you assign the default metadata for the new projects that you create in Site Studio.

3. Once you have specified the metadata values, click Update.

   This returns you to the Site Studio Administration page, where you can begin the upgrade process.

4. Click Manage Web Sites.

5. Click Go to Web Sites Update Page. (This option displays only when older web sites are detected.)

6. Click Advanced Options to specify site upgrade options.

   Figure B-2 Advanced Upgrade Options Screen

   
   Description of "Figure B-2 Advanced Upgrade Options Screen"
   
   

7. Choose the following for a full upgrade:

   • Select Create Project files.

   • Select Upgrade Layouts.

   • Select Upgrade Data Files.

   • Select Convert Hyperlinks and choose a link format:

     • To Server-Side Links: Links contain the coded identity of the target location using server-side script.

     • To Path-Based URLs: Links contain the full path to the target location.

8. Click Set Options to return to the Upgrade Legacy Web Sites page.

9. Click Start Upgrade.

   You see the individual files that must be upgraded on this page. Wait until you see the message that says that the upgrade process was completed.

   Note:

   The site upgrade automatically updates the site hierarchy and its many links, and the Web Sites menu in the content server now lists your sites.

B.3.4 Performing a Minimal Upgrade

A minimal upgrade is required in the case of a multi-server setup and applies to all target servers; that is, the server that has web sites being replicated to it.

You should have already installed and enabled the new Site Studio component on the server before you start a minimal upgrade.

To perform a minimal upgrade, perform these tasks:

1. Log onto the content server as an administrator, open the Administration page, and then the Site Studio Administration page.

2. Click Set Default Project Document Information.

   The Set Project Default Document Information page opens. This is where you assign the default metadata for the new projects that you create in Site Studio.

3. Once you have specified the metadata values, click Update.

   This returns you to the Site Studio Administration page, where you can begin the upgrade process.

4. Click Manage Web Sites.

5. Click Go to Web Sites Update Page. (This option displays only when older web sites are detected.)

6. Click Advanced Options to specify site upgrade options (Figure B-2).

7. Select Create Project files.

   Note:

   This upgrades project files and populates the "Web Site Section" metadata value.

8. Click Set Options to return to the Upgrade Legacy Web Sites page.

9. Click Start Upgrade.

   Wait until you see the message that says that the upgrade process was completed.

The Web Sites menu in the content server now lists your sites.

B.4.1 Updating the Site Navigation

After upgrading a pre-7.5 web site, you must update its navigation files. You can do this in Designer (using the Update Navigation button) or on the Site Studio Administration page (specifically, the Manage Web Sites page). This step is necessary for Contributor to function correctly on the site.

B.4.2 Rebuilding the Content Server Index

After upgrading a pre-7.5 web site, you may need to rebuild the content server index. If your content server has been set up to use database search and indexing (full-text or metadata-only), you do not need to rebuild the search index. If you are using a different search engine, you must rebuild the search index. This is necessary because Site Studio updates the xWebsiteSection metadata field for all content items residing in folders on your site.

See the Oracle Content Server administration documentation for more information on rebuilding the index.

B.4.3 Updating Your Custom Fragments

Most of the manual updates you must perform after upgrading your pre-7.5 web site involve modifying your custom fragments. If you are currently using the predefined fragments that came with Site Studio, you do not have to do this because an updated version of each fragment is included with each Site Studio release.

Most likely, you have customized the fragments or introduced new ones to meet a specific purpose for your organization. There are three things you must do with the fragments so that they work in the latest version:

• Section B.4.3.1, "Modifying Links That Rely on the <base> Tag"

• Section B.4.3.2, "Modifying Obsolete SS_GET_PAGE / JavaScript Links"

• Section B.4.3.3, "Updating GET_SEARCH_RESULTS"

<img src="groups/public/documents/adacct/logo.gif">

<img src="<!--$HttpRelativeWebRoot-->groups/public/documents/adacct/logo.gif">

<a href="javascript:nodelink(42);">link</a>

<a href="<!--ssServerRelativeSiteRoot-->products/servers/index.htm">link</a>

<!--$QueryText=eval(ssQueryText)-->
<!--$if ssLimitScope like "true"-->
    <!--$if strEquals(QueryText, '')-->
      <!--$QueryText='xWebSiteID=' & siteId-->
    <!--$else-->
      <!--$QueryText='(' & QueryText & ') and (xWebSiteID=' & siteId & ')'-->
    <!--$endif-->
<!--$endif-->

<!--$QueryText=eval(ssQueryText)-->
<!--$if ssLimitScope like "true"-->
    <!--$if strEquals(QueryText, '')-->
      <!--$QueryText='xWebsites &lt;contains&gt; ' & siteId-->
    <!--$else-->
      <!--$QueryText='(' & QueryText & ') and (xWebsites &lt;contains&gt;' & siteId & ')'-->
    <!--$endif-->
<!--$endif-->

<!--$if strEquals(QueryText, '')-->
    <!--$QueryText= 'not(xDontShowInListsForWebsites &lt;contains&gt; ' & siteId & ')'-->
<!--$else-->
    <!--$QueryText='(' & QueryText & ') and not(xDontShowInListsForWebsites &lt;contains&gt; ' & siteId & ')'-->
<!--$endif-->

<!-- New params for SS_GET_SEARCH_RESULTS -->
<!--$ssLimitScope="true"-->
<!--$ssDontShowInLists="true"-->
<!--$ssTargetNodeId=""-->
<!--$ssTargetSiteId=""-->
<!--$ssSourceNodeId=nodeId-->
<!--$ssSourceSiteId=siteId-->
<!--$ssWebsiteObjectType=""-->
<!--$ssUserText=""-->

<!--$executeService("SS_GET_SEARCH_RESULTS")-->

<!--$loop SearchResults-->
   <a href="<!--$ssUrl-->?ssSourceSiteId=<!--$siteId-->&ssSourceNodeId= <!--nodeId-->">
      <!--$dDocTitle-->
   </a><br><br>
<!--$endloop-->

B.4.4 Updating Your Custom Elements

Any custom element forms created using a Site Studio release before 7.5 are not compatible with Site Studio 11gR1. They must be manually upgraded and re-authored. The primary reason for not maintaining backward compatibility is Site Studio's prior dependency on Internet Explorer's proprietary window.external functionality (due to the ActiveX control used for the Contributor). This functionality was removed from Site Studio as a result of the browser-independent, JavaScript-based Contributor application that is used in Site Studio 10gR3 (10.1.3.3.3) and higher.

B.4.5 Assigning a Web Site Section to Your Folders

Site Studio no longer uses the Oracle Content Server folder features (Folders component) to organize and manage your site hierarchy. If a web site created in a Site Studio release before 7.5 is upgraded, content that resides in a folder has a new metadata value (Web Site Section) assigned to it so that it is recognized as part of the upgraded site.

Any new content added to the folder, after the upgrade, will not receive this metadata value. As such, if you want to continue using folders to add content to your site, you must assign a Web Site Section value to each folder.

To assign a Web Site Section value, perform these tasks:

1. Log onto the content server as a user with write (RW) access to the folder you want to update.

2. Open the Browse Content tray or menu, and then open the Web Sites tree.

3. Select the web site to want to update.

4. Click Folder Information for the folder you want to change.

5. Select the Update action.

6. Click Browse next to the Web Site Section field.

7. Choose the corresponding web site section.

8. Click OK.

9. Click Update.

10. Repeat these steps for each folder that you want to map to a web site section in Site Studio.

B.4.6 Updating JSP Code

If you have created JSP code based on SiteStudio.SSNavigationBean and SiteStudio.SSNavigationNode objects, references to these objects must be changed so that "sitestudio" is all lowercase, as follows:

• sitestudio.SSNavigationBean

• sitestudio.SSNavigationNode