Oracle® Fusion Middleware Upgrade Guide for Oracle WebCenter Collaboration 10g Release 3 (10.3.0.1) Part Number E13695-02 |
|
|
View PDF |
This chapter describes the process of upgrading from previous versions of Oracle WebCenter Collaboration to the current version.
To upgrade Oracle WebCenter Collaboration:
Review the supported upgrade paths. For details, see Upgrade Paths.
Follow the appropriate upgrade procedure for your existing version of Oracle WebCenter Collaboration.
This section describes the paths that are available to upgrade to Oracle WebCenter Collaboration 10.3.0.1.
Note:
All upgrade paths are between two systems of the same operating system brand, but not necessarily the same operating system version. Check current hardware and software requirements and make any required upgrades to operating system or database software prior to proceeding with the Oracle WebCenter Collaboration upgrade.Upgrade Path | Upgrade References |
---|---|
Oracle WebCenter Collaboration 10.3 to Oracle WebCenter Collaboration 10.3.0.1 | Follow the procedure described in Upgrading from Oracle WebCenter Collaboration 10.3 to Oracle WebCenter Collaboration 10.3.0.1. |
This section describes how to upgrade from Oracle WebCenter Collaboration 10.3 to Oracle WebCenter Collaboration 10.3.0.1.
To upgrade from Oracle WebCenter Collaboration 10.3 to Oracle WebCenter Collaboration 10.3.0.1:
Run the Oracle WebCenter Collaboration installer. For details, see Running the Installer During Upgrade.
Import the Oracle WebCenter Collaboration migration package. For details, see Importing the Oracle WebCenter Collaboration Migration Package.
Start Oracle WebCenter Collaboration and verify the upgrade. For details, see Starting and Verifying the Upgrade.
To run the installer during upgrade:
Back up the portal and Oracle WebCenter Collaboration databases. This allows you to recover your data if there is a problem during upgrade. For more information, see your database documentation.
Stop Oracle WebCenter Collaboration.
Stop the Search Server, Automation Service, and Document Repository Service.
Back up the Document Repository directory on the file system. By default, this directory is located in:
(UNIX/Linux) /opt/bea/alui/ptdr/documents/PTCollab
(Windows) C:\bea\alui\ptdr\documents\PTCollab
Clear the Embedded Servlet Engine's work directory. This allows you to recover your data if there is a problem during upgrade. By default, this directory is located in:
(UNIX/Linux) install_dir/common/container/tomcat/version/work/collaboration
(Windows) install_dir\common\container\tomcat\version\work\collaboration
Copy the installer file to the directory where you installed the previous version of Oracle WebCenter Collaboration. This allows the installer to use the silent properties file created by previous installations. For more information on using the silent properties file, see Appendix B, "Silent Properties File."
If you want to install to a new location or do not want to use the silent properties file, you can launch the installer from any location on the Oracle WebCenter Collaboration host machine.
Launch the Oracle WebCenter Collaboration installer by performing the following:
UNIX/Linux:
Log in to the Oracle WebCenter Collaboration host machine as the local administrator.
Note:
For UNIX/Linux installations, you must run the Oracle WebCenter Collaboration installer as the user that owns the Oracle Inventory Directories.Run the WebCenterCollaboration_10.3.0.1.0 installer as follows: $ ./WebCenterCollaboration_10.3.0.1.0
Windows:
Log in to the Oracle WebCenter Collaboration host machine as the local administrator.
Close all unnecessary windows and applications.
Double-click WebCenterCollaboration_10.3.0.1.0.exe to launch the installer.
Complete the installation wizard pages according to the settings you recorded in the installation worksheets provided inConfiguration Worksheets for Oracle WebCenter Collaboration 10.3.0.1 during your previous installation.
The following tables describe the Oracle WebCenter Collaboration installer wizard pages. The installer wizard pages that appear vary according to your configuration and the selections you choose.
Table 3-1 Oracle WebCenter Collaboration Installer Wizard Pages
The Oracle WebCenter Collaboration installer automatically deploys Oracle WebCenter Collaboration on the Embedded Servlet Engine. You can choose to deploy Oracle WebCenter Collaboration on Oracle WebLogic Server instead of the Embedded Servlet Engine.
Important: If you choose to deploy Oracle WebCenter Collaboration on Oracle WebLogic Server, you should disable the BEA ALI Collaboration Service that is installed by the installer on Windows machines. You will not be able to start and stop Oracle WebCenter Collaboration using Oracle WebCenter Configuration Manager.
To deploy Oracle WebCenter Collaboration on Oracle WebLogic Server:
Identify a domain on which to deploy Oracle WebCenter Collaboration, or create a new domain. Refer to your Oracle WebLogic Server documentation for details on creating a new domain.
In Oracle WebLogic Server's config.xml file for the domain on which Oracle WebCenter Collaboration is deployed, add the following line at the end of the <security-configuration>
tag:
<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>
This disables basic authentication for the domain, and is necessary for WebDAV to work properly.
The <enforce-valid-basic-auth-credentials>
line must be the last entry in the <security-configuration>
tag for the setting to take effect.
Add the following text to the setDomainEnv.sh or setDomainEnv.cmd file of the domain:
On UNIX/Linux, add the following to setDomainEnv.sh. You must add this as one line of code:
JAVA_OPTIONS="${SAVE_JAVA_OPTIONS} -Dbid.application.config=PT_HOME/settings -Dplumtree.application.config=PT_HOME/settings -Dbid.application=PT_HOME/ptcollab/10.3.0 -Dplumtree.application=PT_HOME"
On Windows, add the following to setDomainEnv.cmd. You must add this as one line of code:
set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS% -Dbid.application.config=PT_HOME\settings -Dplumtree.application.config=PT_HOME\settings -Dbid.application=PT_HOME\ptcollab\10.3.0 -Dplumtree.application=PT_HOME
Enter the actual value of PT_HOME in the file. PT_HOME is the same value as install_dir. By default, the value for install_dir is /opt/bea/alui on UNIX/Linux and C:\bea\alui on Windows.
Start the WebLogic domain.
Deploy collab.ear, located in the following location, as an application in the WebLogic domain:
UNIX/Linux: install_dir/ptcollab/10.3.0/webapp/
Windows: install_dir\ptcollab\10.3.0\webapp\
Refer to your Oracle WebLogic Server documentation for details on how to deploy an application.
Update the Oracle WebCenter Collaboration application settings in Oracle WebCenter Configuration Manager to reflect the correct port numbers for the Oracle WebCenter Collaboration UI:
Launch Oracle WebCenter Configuration Manager.
In the application list on the left, under Collaboration, click Application Settings.
Update the values of HTTP port and HTTPS port with the port numbers used by the Oracle WebCenter Collaboration domain in WebLogic.
Click SAVE.
Update the URL of the Oracle WebCenter Collaboration remote server:
Log in to the portal.
Navigate to the Oracle WebCenter Collaboration remote server object in the Admin Object Directory and open it for editing.
On the Main Settings page, set the port number of the Base URL to the port number of the Oracle WebCenter Collaboration application in WebLogic.
Click Finish.
In Oracle WebLogic Server's config.xml file for the domain on which Oracle WebCenter Collaboration is deployed, add the following line at the end of the <security-configuration>
tag:
<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>
This disables basic authentication for the domain, and is necessary for WebDAV and Oracle WebCenter Collaboration RSS Feeds to work properly.
Note:
The<enforce-valid-basic-auth-credentials>
line must be the last entry in the <security-configuration>
tag for the setting to take effect.This section describes how to import the Oracle WebCenter Collaboration migration package.
To import the Oracle WebCenter Collaboration migration package:
Verify that the Search Server is running.
Log on to the portal as a user who has administrative rights.
From the Administration Select Utility drop-down list, use the Migration - Import utility to import the collaboration.pte file, which is located in the following location on the Oracle WebCenter Collaboration host machine:
UNIX/Linux: install_dir/ptcollab/10.3.0/serverpackages/
Windows: install_dir\ptcollab\10.3.0\serverpackages\
Select Overwrite Remote Servers. If necessary, adjust other import settings.
For details on using the Migration - Import utility, see Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Interaction.
This section describes how to start Oracle WebCenter Collaboration and verify the upgrade.
Verify that the following Oracle WebCenter Interaction services are running:
Search Server
API Service
Automation Service
Document Repository Service
LDAP Directory Service
Notification Service
For details on starting Oracle WebCenter Interaction services, see the Installation Guide for Oracle WebCenter Interaction.
This section describes how to start the Oracle WebCenter Collaboration services. Follow the procedure appropriate to your environment. Depending on your configuration, all services may not be installed on the same host machine. In this case, perform each step on the host machine where the service is installed.
To start the Oracle WebCenter Collaboration services on UNIX/Linux:
Start the Search Service used by Oracle WebCenter Collaboration:
cd to /opt/bea/alui/searchservice/1.1/bin
run ./searchserviced.sh start
Start Oracle WebCenter Collaboration:
Verify that the Notification Service is started.
cd to /opt/bea/alui/ptcollab/10.3.0/bin
run ./ptcollaborationd.sh start
Note:
If Oracle WebCenter Collaboration is deployed on Oracle WebLogic Server, start the WebLogic domain on which Oracle WebCenter Collaboration is deployed. Do not start the Oracle WebCenter Collaboration daemon.You can also start and stop the Oracle WebCenter Collaboration services using Oracle WebCenter Configuration Manager. Log in to Oracle WebCenter Configuration Manager using the user name Administrator and the password you specified during upgrade. Follow the instructions in Oracle WebCenter Configuration Manager to start each service. If Oracle WebCenter Collaboration is deployed on Oracle WebLogic Server, you cannot start it from Oracle WebCenter Configuration Manager.
To start the Oracle WebCenter Collaboration services on Windows:
Click Start > Control Panel > Administrative Tools > Services.
Start BEA ALI Search Service.
Verify that the Notification Service is started.
Start BEA ALI Collaboration.
Note:
You can also start and stop the Oracle WebCenter Collaboration services using Oracle WebCenter Configuration Manager. Log in to Oracle WebCenter Configuration Manager using the user name Administrator and the password you specified during upgrade. Follow the instructions in Oracle WebCenter Configuration Manager to start each service. If Oracle WebCenter Collaboration is deployed on Oracle WebLogic Server, you cannot start it from Oracle WebCenter Configuration Manager.If Oracle WebCenter Collaboration is deployed on Oracle WebLogic Server, start the WebLogic domain on which Oracle WebCenter Collaboration is deployed. Do not start the BEA ALI Collaboration service.
To verify that Oracle WebCenter Collaboration is functioning correctly, access and analyze the Collaboration Diagnostics page: http://mycollabserver:mycollabport/collab/admin/diagnostic
For more information on using the Collaboration Diagnostics page, see Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Collaboration.
Check the collaboration.log file for any errors. This file is found in the /opt/bea/alui/ptcollab/10.3.0/settings/logs directory.