| Oracle® WebCenter Collaboration Installation and Upgrade Guide, Volume 1 10g Release 3 (10.3) for Adobe FrameMaker 7.2 or higher, on Windows E13695-01 |
|
 Previous |
 Next |
| Oracle® WebCenter Collaboration Installation and Upgrade Guide, Volume 1 10g Release 3 (10.3) for Adobe FrameMaker 7.2 or higher, on Windows E13695-01 |
|
Previous |
Next |
This chapter provides brief, high level instructions for the installation and upgrade of Oracle WebCenter Collaboration, and is intended to quickly guide experienced administrators through the installation or upgrade procedure.
This chapter is divided into two major sections:
Installation. This section covers installing the Oracle WebCenter Collaboration components, scripting the database, and starting and verifying the installation. The organization of this section maps directly to detailed instructions in Chapter 4, "Installation."
Upgrade. This section covers upgrading Oracle WebCenter Collaboration to the latest version. The organization of this section maps directly to detailed instructions in Chapter 5, "Upgrade."
This section describes how to install Oracle WebCenter Collaboration.
Refer to the section that applies to your database vendor.
Section 3.1.1.2, "Configuring an Oracle Database for Oracle WebCenter Collaboration"
|
Note: The Oracle WebCenter Collaboration and portal databases must be the same vendor and version, and must reside on the same physical machine. |
For more information on these steps, see Section 4.1, "Creating the Oracle WebCenter Collaboration Database."
To create the Oracle WebCenter Collaboration database and database user:
Configure the SQL Server instance to use SQL Server and Windows Authentication mode.
Create the Oracle WebCenter Collaboration database with the Oracle WebCenter Collaboration database name you designated when you completed the worksheets provided in the Configuration Worksheets for Oracle WebCenter Collaboration 10.3.
Create the Oracle WebCenter Collaboration database user login with the login name and password you designated when you completed the worksheet provided in the Configuration Worksheets for Oracle WebCenter Collaboration 10.3.
Configure the Oracle WebCenter Collaboration database user login to use SQL Server Authentication.
Set the Oracle WebCenter Collaboration database user login's default database to the Oracle WebCenter Collaboration database.
Grant the Oracle WebCenter Collaboration database user login the db_owner role for the Oracle WebCenter Collaboration database.
Create a schema for the Oracle WebCenter Collaboration database with the schema name you designated when you completed the worksheets provided in the Configuration Worksheets for Oracle WebCenter Collaboration 10.3. This name must be the same as the Oracle WebCenter Collaboration database user name.
In the Oracle WebCenter Collaboration database user's login properties, navigate to the User Mapping page.
Set the default schema of the Oracle WebCenter Collaboration database user login to the new schema of the same name.
The Oracle WebCenter Collaboration schema is added to the existing Oracle database that contains the portal schema. Confirm that the open_cursors parameter in the Oracle initialization file is set to greater than 1000. This parameter should have been set correctly during the portal database set up.
(Linux/UNIX only) Oracle Inventory contains files that provide the Oracle Universal Installer with the locations of the ORACLE_HOME directories on a particular machine. For Oracle Inventory to function properly, the user that installs Oracle WebCenter Collaboration must have access rights to the directories that contain Oracle Inventory's files. This section describes how to run the ouais.sh shell script, which sets user and group access rights for these directories.
|
Note: You do not need to perform this procedure if you are installing Oracle WebCenter Collaboration on Windows.If you are installing Oracle WebCenter Collaboration on Linux or UNIX operating systems, you do not need to perform this procedure if, as the same user that is installing Oracle WebCenter Collaboration, you have already installed at least one of the following products on the same machine on which you are installing Oracle WebCenter Collaboration:
|
To grant user and group access rights to Oracle Inventory directories:
Log in to the remote server host computer as the root user.
Copy the ouais.sh script to the machine onto which you will be installing Oracle WebCenter Collaboration.
This script is located in the same location as the Oracle WebCenter Collaboration installer file.
Change the current directory (cd) be the directory to which you copied the ouais.sh script.
Run the ouais.sh shell script.
As arguments to the script, specify the user and group that will be running the Oracle WebCenter Collaboration installer. For example, you would use the following command to run the ouais.sh script from the root shell:
./ouais.sh -u <oracleuser> -g <oraclegroup>
The ouais.sh script creates the Oracle Inventory directory if it did not exist before you ran the script. Additionally, the script grants user and group ownership to the directories that contain the files that are used by Oracle Inventory.
To install Oracle WebCenter Collaboration, launch the Oracle WebCenter Collaboration installer as a local administrator:
|
Note: For UNIX/Linux installations, you must run the Oracle WebCenter Collaboration installer as the user that you specified in the procedure Section 3.1.2, "Granting User and Group Access Rights to Oracle Inventory Directories" . You specified the user who will run the product installer as an argument to the ouais.sh script. |
On a UNIX/Linux host the installer is WebCenterCollaboration_10.3.0.0.0.
On a Windows host the installer is WebCenterCollaboration_10.3.0.0.0.exe.
The installer prompts you for specific information about your system and configuration. For more information, see Section 4.3, "Installing the Oracle WebCenter Collaboration Components."
|
Note: Oracle WebCenter Collaboration uses the Notification Service to send emails from Oracle WebCenter Collaboration to end users and to serve RSS feeds if that feature has been enabled. The Notification Service is included with the Oracle WebCenter Interaction installer and is a required component of Oracle WebCenter Interaction. The Notification Service should be installed and configured as part of your Oracle WebCenter Interaction installation. |
The Oracle WebCenter Collaboration installer automatically deploys Oracle WebCenter Collaboration on the Embedded Servlet Engine. You can choose to deploy Oracle WebCenter Collaboration on WebLogic Server instead of the Embedded Servlet Engine.
Important: If you choose to deploy Oracle WebCenter Collaboration on 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 WebLogic Server:
Identify a domain on which to deploy Oracle WebCenter Collaboration, or create a new domain. Refer to your WebLogic Server documentation for details on creating a new domain.
In the portal's config.xml file for the domain on which the portal 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.
|
Note: 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 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 WebCenter Collaboration'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. |
Refer to the section that is appropriate to your database vendor.
This section describes how to create and configure the Oracle WebCenter Collaboration database schema, as well as configure the portal database schema for Oracle WebCenter Collaboration.
To script the databases on Microsoft SQL Server:
Run the following database scripts as the Oracle WebCenter Collaboration database user on the Oracle WebCenter Collaboration database:
install_dir\ptcollab\10.3.0\sql\mssql\collaboration-server-create-tables.sql
install_dir\ptcollab\10.3.0\sql\mssql\collaboration-server-data.sql
install_dir\ptcollab\10.3.0\sql\mssql\collaboration-server-portal-role-grant.sql
Run the following database scripts as the sa user on the portal database:
install_dir\ptcollab\10.3.0\sql\mssql\portal-collaboration-server-data.sql
install_dir\ptcollab\10.3.0\sql\mssql\portal-collaboration-server-role-grant.sql
For more information on these steps, see Section 4.5.1, "Scripting the Databases on Microsoft SQL Server."
This section describes how to create and configure the Oracle WebCenter Collaboration database schema, as well as configure the portal database schema for Oracle WebCenter Collaboration.
To script the database on Oracle:
Locate the versions of the database scripts appropriate to your database platform:
install_dir/ptcollab/10.3.0/sql/oracle/unix/
install_dir\ptcollab\10.3.0\sql\oracle\windows\
Run the following database scripts as the system user on the portal database:
collaboration-server-create-table-space.sql
collaboration-server-create-user.sql
Run the following database scripts as the Oracle WebCenter Collaboration database user on the portal database:
collaboration-server-create-tables.sql
collaboration-server-data.sql
collaboration-server-portal-role-grant.sql
Run the following database scripts as the portal database user on the portal database:
portal-collaboration-server-data.sql
portal-collaboration-server-role-grant.sql
For more information on these steps, see Section 4.5.2, "Scripting the Database on Oracle."
This topic describes how to script a DB2 database for use with Oracle WebCenter Collaboration.
|
Note: For this release, Oracle does not support scripting a DB2 database on Windows for Oracle WebCenter Collaboration. |
Before scripting a DB2 database for Oracle WebCenter Collaboration:
Ensure that the data for the Oracle WebCenter Interaction and ALUI Directory applications is stored in distinct schemas on the same DB2 database.
Create a distinct schema for the Oracle WebCenter Collaboration database on the same DB2 database that contains the schemas for the Oracle WebCenter Interaction and ALUI Directory applications.
Have your DB2 database administrator examine and, if necessary, customize the SQL scripts before you use them. Each SQL file contains comments that describe the customizations that might be necessary.
|
Note: The Oracle WebCenter Collaboration SQL scripts for DB2 include hard-coded schema names for the Oracle WebCenter Collaboration and portal databases. In the collaboration-server-create-tables.sql, collaboration-server-data.sql, and collaboration-server-portal-role-grant.sql scripts, the hard-coded name for the Oracle WebCenter Collaboration schema is COLLAB. If you updated the Oracle WebCenter Collaboration schema name to anything other than COLLAB, you must navigate to Oracle WebCenter Configuration Manager, Collaboration application, Collaboration Database component, and update the Schema Name setting to match the updated Oracle WebCenter Collaboration schema name.In the portal-collaboration-server-role-grant.sql and portal-collaboration-server-data.sql scripts, the hard-coded name for the portal schema is ALUI. If you updated the portal schema name to anything other than ALUI, you must update these scripts to match the updated portal schema name. Additionally, you must navigate to Oracle WebCenter Configuration Manager, Collaboration application, Collaboration Settings component, and update the Linked database alias setting to match the updated portal schema name. Make sure to add .dbo. to the end of the portal schema name. For example, if the portal schema name is alidbuser, the value that you type into the Linked database alias setting should be alidbuser.dbo. |
Use the DB2 command line processor to run the SQL scripts against your DB2 database. Comments in the header of each SQL file contain recommended syntax for the DB2 command line processor.
To script a DB2 database for Oracle WebCenter Collaboration:
Copy SQL scripts from the Oracle WebCenter Collaboration installation directory to your DB2 database server.
The scripts are located in: install_dir/ptcollab/10.3.0/sql/db2
As a user with administrative privileges, run the these scripts in the following order:
create_collab_schema.sql
create_collab_tablespace_unix.sql
grant_collab_user.sql
collaboration-server-create-tables.sql
collaboration-server-data.sql
collaboration-server-portal-role-grant.sql
portal-collaboration-server-role-grant.sql
portal-collaboration-server-data.sql
For more information on these steps, see Section 4.5.3, "Scripting a DB2 Database on UNIX for Oracle WebCenter Collaboration."
If your Image Service is deployed on IIS, you must register two new MIME types in IIS so that email notifications will work properly.
To configure IIS for notification emails:
In IIS, register the extensions ".nst" and ".inc" with a MIME type of "text/plain".
Restart the World Wide Web Publishing Service so that the changes take effect.
For more information on these steps, see Section 4.8, "Starting and Verifying the Installation."
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\
For details, see Section 4.8.2, "Starting the Oracle WebCenter Collaboration Services."
This section describes how to start Oracle WebCenter Collaboration and verify operation.
Verify that the following Oracle WebCenter Interaction services are started:
Search Server
API Service
Automation Service
Document Repository Service
LDAP Directory Service
Notification Service
Start the Search Service used by Oracle WebCenter Collaboration.
Start Oracle WebCenter Collaboration. If Oracle WebCenter Collaboration is deployed on WebLogic Server, start the domain on which Oracle WebCenter Collaboration is deployed.
To verify that Oracle WebCenter Collaboration is functioning correctly, access and analyze the Collaboration Diagnostics page: http://<mycollabserver>:<mycollabport>/collab/admin/diagnostic
This section provides brief, high level instructions for the process of upgrading previous versions of Oracle WebCenter Collaboration to the latest version.
This section provides the paths that are available to upgrade to Oracle WebCenter Collaboration 10.3.
|
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 portal upgrade. |
| Upgrade Path | Upgrade References |
|---|---|
| Collaboration 4.2, 4.2 MP1 to Oracle WebCenter Collaboration 10.3
Collaboration 4.1, 4.1 SP1, 4.1 SP2 to Oracle WebCenter Collaboration 10.3 Collaboration 4.0.2 to Oracle WebCenter Collaboration 10.3 |
Follow the procedure described in Section 3.2.2, "Upgrading from Collaboration 4.x to Oracle WebCenter Collaboration 10.3." |
| Collaboration Server 3.x to Oracle WebCenter Collaboration 10.3 | Follow the procedure described in Section 3.2.3, "Upgrading from Collaboration Server 3.x to Oracle WebCenter Collaboration 10.3." |
| Collaboration Server 2.x to Oracle WebCenter Collaboration 10.3 | Follow the procedure described in Section 3.2.4, "Upgrading from Collaboration Server 2.x to Oracle WebCenter Collaboration 10.3." |
This section describes how to upgrade from Collaboration 4.x to Oracle WebCenter Collaboration 10.3.
To upgrade from Collaboration 4.x to Oracle WebCenter Collaboration 10.3:
Stop Collaboration.
If you have an existing Notification Service from your previous installation of Collaboration, disable or uninstall it. The Notification Service that was previously included in the Collaboration installer has been replaced by the Notification Service and is included in the Oracle WebCenter Interaction installer. The Notification Service is a required component of Oracle WebCenter Interaction and should be installed and configured as part of your Oracle WebCenter Interaction installation.
Stop the Search Server, Automation Service, and Document Repository Service.
Back up the portal database, Oracle WebCenter Collaboration database, and Document Repository.
Clear the Embedded Servlet Engine's work directory.
(Linux/UNIX only) Grant group and user access to Oracle Inventory directories. For details, see Section 4.2, "Granting User and Group Access Rights to Oracle Inventory Directories."
Install the Oracle WebCenter Collaboration components. For details on launching the installer and completing its screens, see Section 4.3.1, "Launching the Oracle WebCenter Collaboration Installer."
(Optional) Deploy Oracle WebCenter Collaboration on WebLogic Server. By default, Oracle WebCenter Collaboration is deployed on the Embedded Servlet Engine. You only need to perform this step if you want to deploy Oracle WebCenter Collaboration on WebLogic Server instead of the Embedded Servlet Engine. For details, see Chapter 3, "Deploying Oracle WebCenter Collaboration on WebLogic Server."
Upgrade the portal and Oracle WebCenter Collaboration databases. For details, see Chapter 3, "Deploying Oracle WebCenter Collaboration on WebLogic Server."
Import the Oracle WebCenter Collaboration migration package. For details, see Section 3.1.7, "Importing the Oracle WebCenter Collaboration Migration Package."
(Image Service on IIS only) Configure the Image Service to work with the Notification Service. For details, see Section 3.1.6, "Configuring the Image Service for Notification Emails.".
Start Oracle WebCenter Collaboration and verify operation. For details, see Chapter 3, "Starting and Verifying the Installation.".
Rebuild the Oracle WebCenter Collaboration search collection. For details, see Section 5.8, "Rebuilding the Oracle WebCenter Collaboration Search Collection."
For more information on these steps, see Section 5.2, "Upgrading from Collaboration 4.x to Oracle WebCenter Collaboration 10.3."
This section describes how to upgrade from Collaboration Server 3.x to Oracle WebCenter Collaboration 10.3.
If you are currently running Collaboration Server 3.x, you must first upgrade to Collaboration Server 4.0.2. Refer to the Installation Guide for Plumtree Collaboration Server 4.0.2 for information on this upgrade path.
After upgrading to Collaboration Server 4.0.2, upgrade to Oracle WebCenter Collaboration 10.3 according to the instructions described in Oracle WebCenter CollaborationSection 3.2.2, "Upgrading from Collaboration 4.x to Oracle WebCenter Collaboration 10.3."
This section describes how to upgrade from Collaboration Server 2.x to Oracle WebCenter Collaboration 10.3.
If you are currently running Collaboration Server version 2.x, you must first upgrade to Collaboration Server 3.0.2. Refer to the Installation Guide for Plumtree Collaboration Server 3.0 for information on this upgrade path.
After upgrading to Collaboration Server 3.0.2, you must upgrade to Collaboration Server 4.0.2. Refer to the Installation Guide for Plumtree Collaboration Server 4.0.2 for information on this upgrade path.
After upgrading to Collaboration Server 4.0.2, upgrade to Oracle WebCenter Collaboration 10.3 according to the instructions described in Section 3.2.2, "Upgrading from Collaboration 4.x to Oracle WebCenter Collaboration 10.3."
|
Note: UNIX/Linux users - Collaboration 3.x was released only on Windows. The installation of 3.0.2 must take place on a Windows machine. |
This section describes how to upgrade the portal and Oracle WebCenter Collaboration databases.
|
Note: If you are upgrading Oracle from 10.1.x to 10.2.x or SQL Server from 2000 to 2005, you should perform the Oracle or SQL Server upgrade before upgrading the databases. |
Run the upgrade scripts appropriate to your database platform. The upgrade scripts are located in:
Microsoft SQL Server:
install_dir\ptcollab\10.3.0\sql\mssql
Oracle:
install_dir\ptcollab\sql\oracle\unix
install_dir\ptcollab\10.3.0\sql\oracle \windows
Follow the database upgrade instructions appropriate to your previous version of Oracle WebCenter Collaboration, as described in the following table:
| Upgrade Path | Database Upgrade Instructions |
|---|---|
| 4.2 MP1 to 10.3
4.2 to 10.3 |
As the Oracle WebCenter Collaboration database user, run the following script on the Oracle WebCenter Collaboration database:
collaboration-server-4.2.0-to-10.3.0-upgrade.sql |
| 4.1 SP2 to 10.3 | As the Oracle WebCenter Collaboration database user, run the following scripts in sequential order on the Oracle WebCenter Collaboration database:
As the portal database user, run the following script on the portal database:
|
| 4.1 SP1 to 10.3
4.1 to 10.3 |
As the Oracle WebCenter Collaboration database user, run the following scripts in sequential order on the Oracle WebCenter Collaboration database:
As the portal database user, run the following script on the portal database:
|
| 4.0.2 to 10.3 | As the Oracle WebCenter Collaboration database user, run the following scripts in sequential order on the Oracle WebCenter Collaboration database:
As the portal database user, run the following script on the portal database:
|
For more information on upgrading the portal and Oracle WebCenter Collaboration databases, see Section 5.7, "Upgrading the Portal and Oracle WebCenter Collaboration Databases."
