This chapter describes post-upgrade steps required for upgrading your Oracle WebCenter Content.
Section 5.1, "Post-Upgrade Tasks and Considerations for Oracle WebCenter Content"
Section 5.2, "Post-Upgrade Tasks and Considerations for Oracle WebCenter Content: Records"
You must perform the following additional post-upgrade tasks after you have completed the procedure in Section 4.6, "Task 6: Use the Upgrade Assistant to Upgrade the Oracle WebCenter Content Middle Tier":
Section 5.1.3, "OracleTextSearch with External Database or SES"
Section 5.1.4, "Oracle Universal Content Management and Connection Server"
Section 5.1.5, "Content Server User Logins and Oracle WebLogic Server"
Section 5.1.6, "Oracle Oracle WebCenter Content Internal User Logins"
Section 5.1.7, "Customized Properties in Previous Oracle WebCenter Content Versions"
Section 5.1.8, "Microsoft SQL Server Schema Name and JDBC Username"
Section 5.1.11, "Changing the Folders Configuration to Contribution Folders"
To start the managed server for Oracle WebCenter Content, follow the instructions described in "Starting Managed Servers" in the Oracle WebCenter Content Installation Guide.
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 WebCenter Content. It also presents a list of 10g components and how the Upgrade Assistant managed each component. For more information, see "Completing the WebCenter Content Configuration" in the Oracle WebCenter Content Installation Guide.
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.
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.
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.
Click Submit to save these configuration changes. After successfully saving these changes, a page appears explaining that this node must be restarted.
Restart the managed servers.
If your Oracle Universal Content Management 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.
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 Oracle WebCenter Content 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 Oracle WebCenter Content 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).
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.
In prior versions of Oracle WebCenter Content, there were two types of users defined:
External users: In Oracle Universal Content Management 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 Universal Content Management 10g, when a local user logged in, Content Server validated the login by comparing the hashed passwords. In Oracle WebCenter Content 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.
If the properties of metadata fields used by standard components have been customized in a previous version of Oracle WebCenter Content, 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.
When upgrading Oracle Universal Content Management with a Microsoft SQL Server database, the schema name and the JDBC username must be the same or the schema upgrade will fail.
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.
After upgrading to 11g, the web root value for your 10g system is used as the context root for your 11g system.
Oracle WebCenter Content Server provides a hierarchical folder interface, through either the Folders or Contribution Folders feature, for organizing and managing content in the repository. You cannot have both Folders (FrameworkFolders component) and Contribution Folders (Folders_g component) enabled on a Content Server instance.
Having both features enabled is not a supported configuration because some features, including the CoreWebdav system component, would not work correctly with both enabled. On a production system, you need to disable the Folders_g component and enable the FrameworkFolder component for Oracle WebCenter Content.
To change the Folders configuration to Contribution Folders:
In the Content Server Administration tray or menu, click Admin Server.
On the Component Manager page, select Folders to display the Folders category of components.
Deselect the Folders_g component.
Click the Update button, and click OK when prompted to confirm disabling the component.
In the first paragraph of the Component Manager page, click advanced component manager.
In the Disabled Components box on the Advanced Component Manager page, select FrameworkFolders, and click the Enable button.
Restart Content Server, as described in "Restarting a Managed Server" in the Oracle WebCenter Content Installation Guide.
If you have upgraded the DefaultFileStore provider in Enterprise Content Management 10g, then after upgrading to WebCenter Content 11g, the default storage rules are not available. In Enterprise Content Management 10g for using the file storage rules upgrading the DefaultFileStore provider was required.
You can enable the storage rule by performing the following:
Open the config.cfg file (Located at intradoc dir/config) in a text editor and edit it as: UpdateFilestoreProvider=true.
After you complete editing the config.cfg file, restart your server.
After upgrading from 10g to 11g a new document attribute, dDocCreatedDate is introduced. The resulting attribute needs to be manually configured to support sorting from a search query.
Complete the following steps to configure it:
To access the running Content Server instance, start a web browser and enter the following URL: http://managedServerHost:managedServerPort/cs
For managedServerHost, specify the name of the computer that hosts the Oracle WebLogic Server Managed Server for the WebCenter Content domain where the Content Server instance is installed. For managedServerPort, specify the listen port number for the Oracle WebLogic Server Managed Server for the WebCenter Content domain where the Content Server instance is installed.
Log in with the administrator user name and password for Oracle WebLogic Server. The default port number for WebCenter Content with the Content Server instance is 16200. For example: http://myHost.example.com:16200/cs
Expand Administration on the left pane and select Admin Applets.
Click Configuration Manager.
Ensure that the Information Fields tab is selected, and then click Advanced Search Design.
In the Advance Search Design window, select dDocCreatedDate and click Edit.
Select the Is sortable option and click OK.
For Oracle WebCenter Content: Records post-upgrade tasks, follow the same steps as described in Section 5.1, "Post-Upgrade Tasks and Considerations for Oracle WebCenter Content."
For more information about post-installation tasks for Oracle WebCenter Content: Records, See "Setting Up The Software" in Oracle WebCenter Content Setup Guide for Records.
You must perform the following additional post-upgrade tasks after you have completed the procedure in Section 4.6, "Task 6: Use the Upgrade Assistant to Upgrade the Oracle WebCenter Content Middle Tier.":
Section 5.2.3, "Oracle WebCenter Content: Records Content Basket Creation"
Section 5.2.4, "Oracle WebCenter Content: Records Scheduled Jobs"
Section 5.2.5, "Oracle WebCenter Content: Records Custom Dispositions"
Section 5.2.7, "Oracle WebCenter Content: Records Enable Features Display"
Section 5.2.9, "Oracle WebCenter Content: Records Set Scripts Option"
Section 5.2.10, "Oracle WebCenter Content: Records Simple Profile Settings"
To start the managed server for Oracle WebCenter Content, follow the instructions described in "Starting Managed Servers" in the Oracle WebCenter Content Installation Guide.
In previous versions of Oracle WebCenter Content: Records, 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.
If any jobs were scheduled in previous versions of Oracle WebCenter Content: Records, 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.
If custom dispositions were previously created using an older version of Oracle WebCenter Content: Records, 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.
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.
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.
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.
When creating a simple profile Oracle WebCenter Content: Records11g, the Set Scripts option where you can enter pre-submit and post-submit scripts using idocscripts, is no longer available in Oracle WebCenter Content: Records 11g.
Verify all settings for Simple Profiles after upgrading. Some settings are not carried over automatically during the upgrade process.
After upgrading to Oracle WebCenter Content: Records you must open the config.cfg file (Located at intradoc dir/config) in a text editor and update HttpRelativeWebRoot parameter to HttpRelativeWebRoot=/urm/.
Note:
You must enter/urm/ as the default value. If you specify any other value, the Oracle WebCenter Content: Records server will not start.After you complete editing the config.cfg file you must restart your server.
If you import an archive from a 10g version of the software to the 11g version that includes a Related Content table, the import must be done in two steps. First import the content items in an archive. Then import the Related Content table.
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.
Log in to the server through the Content Server UI.
Click the Admin Server link under the Administration menu, and select the UCM Admin Server.
For each 10g component to install in 11g, do the following:
Click the advanced component manager link under the Component Manager heading.
Click the Browse button in the Install New Component section.
Navigate to the $IntradocDir/upgrade/components/ directory and select the component zip file.
Click the Install button.
Click the Continue button.
Click one of the Click here links to return to the Component Manager and optionally enable this component.
Once all desired components are installed, restart the managed server once more.