Skip Headers
Oracle® Fusion Middleware Upgrade Guide for Oracle Enterprise Content Management Suite
11g Release 1 (11.1.1)

Part Number E16451-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

5 Oracle Enterprise Content Management Suite Post-Upgrade Tasks and Considerations

This chapter describes post-upgrade steps required for upgrading your Oracle Enterprise Content Management Suite.

5.1 Post-Upgrade Tasks and Considerations for Oracle Universal Content Management

Perform these tasks after you have completed the procedure in Section 4.6, "Task 6: Use the Upgrade Assistant to Upgrade the Oracle Enterprise Content Management Suite Middle Tier."

Start the Managed Servers

For Oracle UCM, follow the instructions described in Chapter 5, "Configuring Oracle Universal Content Management," in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite to start the managed server.

Post-Upgrade Configuration Page

Instead of a post-installation Content Server Configuration page, a post-upgrade Content Server Configuration page appears. This page, which is available at http://server:16200/cs/, includes options for final configuration of Oracle UCM. It also presents a list of 10g components and how the Upgrade Assistant managed each component. For more information, see "Completing the Oracle UCM Configuration" in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.

  1. Under Instance Information, the original 10g weblayout and vault directories are shown. If you wish to move these directories, enter the new locations in this form.

  2. Because the 11g server is running inside WebLogic Server, the HttpServerAddress may need to be changed. For example, if the 10g server was running under Apache, or any another Web server, it may have been running on port 80 (the default for Web servers). The default port number inside WebLogic Server for Content Server is 16200, (in the Configuration Wizard, there was an option to change this value), so the HttpServerAddress must be updated to contain the correct TCP port number. The hostname portion of the server address may also need to be updated to reflect any changes. The default value for HttpServerAddress is derived from the current WebLogic Server settings after you start the managed server.

  3. A list of components installed on the 10g server appears below the form fields. Many of these components are packaged with the 11g server, so those components are not copied during the upgrade. Some components may no longer be supported, and are not copied over for other reasons. This table describes the reason for each component. Custom components are also included in this list. The upgrade process builds each 10g custom component using the same mechanism that the Component Manager's "Download" uses to build a component (the same mechanism that Component Wizard's "Build" uses). The resulting components' zip files are copied into the 11g server but are not installed or enabled. Below the table is a description of where these component zip files are located. Take note of this location.

  4. Click Submit to save these configuration changes. After successfully saving these changes, a page appears explaining that this node must be restarted.

  5. Restart the managed servers.

5.1.1 OracleTextSearch with External Database or SES

If your Oracle UCM 10g instance has OracleTextSearch set up with an external database or SES, you must edit the associated database to remove the value in the Configuration Class setting, and restart the managed server.

5.1.2 Oracle UCM and File Store Provider

Using File Store Provider to spread content among multiple disk partitions is not supported in Oracle UCM 11g.

5.1.3 Oracle UCM and Connection Server

In 10g, the Connection Server component enabled content to be registered with a Content Server Archive, to be published by the Connection Server. This component is not supported in this UCM 11g release.

Note that the following features of Connection Server 10g are still available and are supported as long as Connection Server 10g is supported:

  • Connection Server 10g enabled the publishing of files from a file system to multiple file systems. This is still supported. In future releases the same functionality will be provided by Deployment Server.

  • Connection Server 10g can still be used to crawl an 11g Site Studio Web Site. However, a new component in UCM 11g, Site Studio Publisher, is the preferred method to crawl Site Studio web sites and produce static file representations of these sites. After the representation is made, the Connection Server can be used to publish the files or any other tool can be used to move the files from one server to another. (Note that Site Studio Publisher is not the same as the Site Studio Publishing Utility 10g).

5.1.4 Content Server User Logins and Oracle WebLogic Server

Although user logins can still be created and managed on Content Server with the User Admin applet, they are not valid for authentication purposes unless they also have been created on Oracle WebLogic Server.

If you use an LDAP server and create a user login with the same name as a local user defined in Content Server with the User Admin applet, the LDAP user is authenticated against LDAP when logging in, but receives roles assigned to the local user.

5.1.5 Oracle UCM Internal User Logins

In prior versions of Oracle UCM, there were two types of users defined:

  • External users: In Oracle UCM 10g, when an external user logs in, Content Server used the external storage mechanism to validate the login, for example checking the username and password. In 11g with oracle WebLogic Server, the administrators must configure WebLogic Server to use the same storage mechanism. Once that is working, those users can log in to WebLogic Server just as they did in UCM 10g. Their UCM username, password, saved preferences, and other information will be the same.

  • Local users: In Oracle UCM 10g, when a local user logged in, Content Server validated the login by comparing the hashed passwords. In Oracle UCM 11g, with Oracle WebLogic Server, those users will not be able to login until WebLogic Server logins are created for each of the UCM logins. Once administrators somehow create those WebLogic Server logins, (using an external storage mechanism, or by creating accounts using Enterprise Manager), those users will be able to login to WebLogic Server using their new password. Their old UCM username, saved preferences, and some other information will remain the same; though the password will likely be changed.

When a new WebLogic Server login is created, that user can log in through WebLogic Server and Content Server creates a user directory for that user. Content Server uses this directory for maintaining saved preferences and other information about that user. If that directory already exists, the existing preferences will apply to this user. As a result, when an old 10g UCM "local" user logs in to a newly-created 11g WebLogic Server login with the same username, their 10g preferences will already exist and the system will work as expected.

5.1.6 Customized Properties in Previous Oracle UCM Versions

If the properties of metadata fields used by standard components have been customized in a previous version of Oracle UCM, those customizations may need to be reapplied after the upgrade. After upgrading the properties are automatically reset to reflect the default preferences. For example, if a field has been customized to be visible on a checkin page in a previous version, after the upgrade that field may be invisible again because the default rules for the component are applied.

5.1.7 Microsoft SQL Server Schema Name and JDBC Username

When upgrading Oracle UCM with a Microsoft SQL Server database, the schema name and the JDBC username must be the same or the schema upgrade will fail.

5.1.8 Inbound Refinery Upgrade

Oracle does not recommend upgrading Inbound Refinery (IBR) from previous versions. Instead, install and configure the 11g version of Inbound Refinery and adjust the Content Server provider to use the newly installed application.

5.2 Post-Upgrade Tasks and Considerations for Oracle Universal Records Management

For Oracle URM, follow the instructions described in Chapter 9, "Configuring Oracle Universal Records Management," in the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite to start the managed server.

For Oracle URM post-upgrade tasks, follow the same steps as described in Section 5.1, "Post-Upgrade Tasks and Considerations for Oracle Universal Content Management."

For more information about post-installation tasks for Oracle URM, See "Setting Up The Software" in Oracle Fusion Middleware Setup Guide for Universal Records Management.

5.2.1 Oracle URM Content Basket Creation

In previous versions of Oracle URM, each user was automatically assigned a content basket. In the current version of the software, you must create your own content baskets. Any items in your basket prior to upgrading are not retained.

5.2.2 Oracle URM Scheduled Jobs

If any jobs were scheduled in previous versions of Oracle URM, such as Scheduled Screening Reports and URM Agent Scheduled Events, those jobs must be rescheduled. Schedule times and frequency are not automatically assigned during the upgrade process.

5.2.3 Oracle URM Custom Dispositions

If custom dispositions were previously created using an older version of Oracle URM, those dispositions should be re-examined and updated to use the newest services and actions. The Action Service parameters have changed from previous versions of this software and any changes to existing custom dispositions are not mapped automatically.

5.2.4 Oracle PCM Customized Icons

If customized icons were created in a previous version of the Physical Content Management software, they are not automatically transferred during an upgrade. They must be copied after upgrading.

5.2.5 Oracle URM Enable Features Display

After upgrading to 11g, you must navigate to the Enabled Features page, configure your system to the desired installation level, and click the Submit button. If there is a dependency on existing data, some features and actions are auto enabled by the system during the submission of this display. Before performing any type of setup steps following the Configure Installation link in the setup checklist display, you must submit (save) this display, and restart Content Server.

5.2.6 Dropping Oracle URM 10g Tables

When you install RM or URM, several different database tables are created. When you uninstall them, those tables are not automatically removed. You must manually drop the tables to ensure that no data is accidentally lost. If you uninstall RM or URM but do not manually drop the tables, the upgrade process does not modify in any way. If you then attempted to reinstall RM or URM after the upgrade the old tables (from 10g) would conflict with the new 11g system.

5.2.7 Oracle URM Set Scripts Option

When creating a simple profile Oracle URM 11g, the Set Scripts option where you can enter pre-submit and post-submit scripts using idocscripts, is no longer available in Oracle URM 11g.

5.2.8 Oracle URM Simple Profile Settings

Verify all settings for Simple Profiles after upgrading. Some settings are not carried over automatically during the upgrade process.

5.3 Installing Custom Components

Oracle recommends testing all custom components in a development environment with an 11g content server before implementing them in a production environment. Changes in the content server may cause 10g customizations to behave differently or incorrectly.

  1. Log in to the server through the Content Server UI.

  2. Click the Admin Server link under the Administration menu, and select the UCM Admin Server.

  3. For each 10g component to install in 11g, do the following:

    1. Click the advanced component manager link under the Component Manager heading.

    2. Click the Browse button in the Install New Component section.

    3. Navigate to the $IntradocDir/upgrade/components/ directory and select the component zip file.

    4. Click the Install button.

    5. Click the Continue button.

    6. Click one of the Click here links to return to the Component Manager and optionally enable this component.

  4. Once all desired components are installed, restart the managed server once more.