2 Installation

This chapter describes how to install Oracle WebCenter Collaboration, including running the installer, scripting the databases, configuring the Image Service, configuring Oracle Universal Content Management, importing migration packages, and starting Oracle WebCenter Collaboration.

If you are upgrading from an earlier version, refer first to Chapter 3, "Upgrade."

To install Oracle WebCenter Collaboration:

1. Ensure that you have met the prerequisites for installation. For details, see Prerequisites.

2. Install the Oracle WebCenter Collaboration components. For details, see Installing the Oracle WebCenter Collaboration Components.

3. (Optional) Deploy Oracle WebCenter Collaboration on WebLogic Server. By default, Oracle WebCenter Collaboration is deployed on the Embedded Servlet Engine. You only must perform this step if you want to deploy Oracle WebCenter Collaboration on WebLogic Server instead of the Embedded Servlet Engine. For details, see Deploying Oracle WebCenter Collaboration on WebLogic Server.

4. Script the portal and Oracle WebCenter Collaboration databases. For details, see Scripting the Oracle WebCenter Collaboration and Portal Databases.

5. (Image Service on IIS only) Configure the Image Service to work properly with the Notification Service. For details, see Configuring the Image Service for Notification Emails.

6. (Optional) Configure Oracle WebCenter Collaboration integration with Oracle Universal Content Management. You only must perform this step if you want to export ­Oracle WebCenter Collaboration projects or documents to Oracle Universal Content Management. For details, see Configuring Oracle WebCenter Collaboration Integration with Oracle Universal Content Management.

7. Import the Oracle WebCenter Collaboration migration package. For details, see Importing the Oracle WebCenter Collaboration Migration Package.

8. Start Oracle WebCenter Collaboration and verify operation. For details, see Starting and Verifying the Installation.

Installing the Oracle WebCenter Collaboration Components

This section describes how to install the Oracle WebCenter Collaboration components.

The Oracle WebCenter Collaboration components are:

1. Collaboration Web UI: This is the core Oracle WebCenter Collaboration application. It is required.

2. Image Service Files: This required component installs the necessary images, styles, user interface controls, Java applets, and online help for Oracle WebCenter Collaboration. Install these files on the same machine on which the portal's Image Service is installed.

When performing a clean install, you can install the Oracle WebCenter Collaboration components in any order; however, you should not start any of the components until all components are installed.

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 is 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.

Launching the Oracle WebCenter Collaboration Installer

This section describes how to launch the Oracle WebCenter Collaboration installer.

To install Oracle WebCenter Collaboration, you must have administrator rights on the machine where you are running the installer.

Note:

If you have previously run the installer and a properties file has been created, you may run the installer silently based on the values in the file. Refer to Appendix B, "Silent Properties File" for information on how to run a silent install.

To install Oracle WebCenter Collaboration, launch the Oracle WebCenter Collaboration installer:

• UNIX/Linux:

  1. 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 you specified in the procedure 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.

  2. Copy the WebCenterCollaboration_10.3.3.0.0 installer to a temporary location and run it as follows: $ ./WebCenterCollaboration_10.3.3.0.0

• Windows:

  1. Log in to the Oracle WebCenter Collaboration host machine as the local administrator.

  2. Copy the WebCenterCollaboration_10.3.3.0.0.exe installer to a temporary location.

  3. Close all unnecessary windows and applications.

  4. Double-click WebCenterCollaboration_10.3.3.0.0.exe to launch the installer.

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 2-1 Oracle WebCenter Collaboration Installer Wizard Pages

Wizard Page	Description
Introduction	Provides general information on using the installer.
Choose Components	Select Custom or Complete. If you select Complete, a full set of Oracle WebCenter Collaboration components are installed. If you select Custom, you can select individual components to install according to your deployment plan.
Choose Install Folder	Accept the default installation folder or select a different folder in which to install Oracle WebCenter Collaboration. Default: UNIX/Linux: /opt/oracle/middleware/wci Windows: C:\Oracle\Middleware\wci In the rest of this guide, the default installation folder will be referred to as install_dir.
Portal Settings: Portal Database	Enter the type of database used by the portal. Oracle WebCenter Collaboration must use the same database type as the portal.
Portal Settings: Portal Database	Enter the name of the computer that hosts the Oracle WebCenter Interaction database, the port used by the database, the name of the database, and the database user.
Collaboration: Database Connection	Enter the Oracle WebCenter Collaboration database user and the name of the database.
Configuration Manager - Update	This page is displayed if an existing installation of Oracle WebCenter Configuration Manager 2.0 is detected. Select if you want to update the password or port information for Oracle WebCenter Configuration Manager or use the existing settings.
Configuration Manager - Port and Password	Type the port number on which you want Oracle WebCenter Configuration Manager to service Oracle WebCenter Collaboration requests. By default, the port number is 12345. After running the installer, you will be able to access Oracle WebCenter Configuration Manager by using the following URL: https://local_host:port_number. Also type and confirm the Administrator password that you will use to log into Oracle WebCenter Configuration Manager. The password is case-sensitive.
Path to Image Service Files	Install Image Service files on the computer on which the Image Service is installed. The path should lead to the directory where the Image Service is installed. C:\Oracle\Middleware\wci\ptimages (Windows) /opt/oracle/middleware/wci/ptimages (UNIX) Before clicking Next, verify that security for the Image Service directory is appropriately configured to allow for installation of the Image Service files. After you have entered the required information, click Next.
Pre-Installation Summary	Review the list of components to be installed. Click Install.
Launch Configuration Manager	Launch Oracle WebCenter Configuration Manager. Log in to Oracle WebCenter Configuration Manager using the user name Administrator and the password you specified. Follow the instructions in Oracle WebCenter Configuration Manager to complete all configurations with missing or incorrect settings. When you have completed all Oracle WebCenter Configuration Manager tasks, return to the installer and click Next.
Application Settings Confirmation	Select Yes if you have completed configuration of the Oracle WebCenter Collaboration settings. Select No, configure later to complete the installer without configuring the Oracle WebCenter Collaboration settings. You must run Oracle WebCenter Configuration Manager and configure your Oracle WebCenter Collaboration settings before starting Oracle WebCenter Collaboration.
Install Complete	If you are prompted to restart your computer, choose to restart the system now or restart it manually. Click Done.

Deploying Oracle WebCenter Collaboration on WebLogic Server

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.

Note:

If you choose to deploy Oracle WebCenter Collaboration on WebLogic Server, you should disable the Oracle WCI 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:

1. 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.

2. 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.

3. Add the following text to the setDomainEnv.sh or setDomainEnv.cmd file of the domain:

   • On UNIX/Linux, add the following entry to setDomainEnv.sh (this entry must be added to the top of the file, before the export JAVA_OPTIONS command). 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.3
     -Dplumtree.application=PT_HOME"
     

   • On Windows, add the following entry to setDomainEnv.cmd (this entry must be added to the top of the file, before the export JAVA_OPTIONS command). 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.3
     -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/oracle/middleware/wci on UNIX/Linux and C:\Oracle\Middleware\wci on Windows.

4. Start the WebLogic domain.

5. Deploy collab.ear, located in the following location, as an application in the Weblogic domain:

   UNIX/Linux: install_dir/ptcollab/10.3.3/webapp/

   Windows: install_dir\ptcollab\10.3.3\webapp\

   Refer to your WebLogic Server documentation for details on how to deploy an application.

6. Update the Oracle WebCenter Collaboration application settings in Oracle WebCenter Configuration Manager to reflect the correct port numbers for the Oracle WebCenter Collaboration UI:

   1. Launch Oracle WebCenter Configuration Manager.

   2. In the application list on the left, under Collaboration, click Application Settings.

   3. Update the values of HTTP port and HTTPS port with the port numbers used by the Oracle WebCenter Collaboration domain in WebLogic.

   4. Click SAVE.

7. Update the URL of the Oracle WebCenter Collaboration remote server:

   1. Log in to the portal.

   2. Navigate to the Oracle WebCenter Collaboration remote server object in the Admin Object Directory and open it for editing.

   3. 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.

   4. Click Finish.

8. 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.

Scripting the Oracle WebCenter Collaboration and Portal Databases

After the Oracle WebCenter Collaboration installer has completed installation, you must script the Oracle WebCenter Collaboration and portal databases. You must have administrator privileges for the portal database. Perform the procedure that is appropriate to your database vendor:

• Scripting the Databases on Microsoft SQL Server

• Scripting the Database on Oracle

• Scripting a DB2 Database on UNIX for Oracle WebCenter Collaboration

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.

Note:

You should have already created and configured the database, as described in Creating and Configuring the Oracle WebCenter Collaboration Database on Microsoft SQL Server.

To script the databases on Microsoft SQL Server:

• Script the Oracle WebCenter Collaboration database by following the steps in Scripting the Oracle WebCenter Collaboration Database on Microsoft SQL Server.

• Script the portal database by following the steps in Scripting the Portal Database on Microsoft SQL Server.

Scripting the Oracle WebCenter Collaboration Database on Microsoft SQL Server

Run the database scripts as the Oracle WebCenter Collaboration database user on the Oracle WebCenter Collaboration database in the following order:

1. To delete previous tables (if they exist) and create the tables required for Oracle WebCenter Collaboration, run the install_dir\ptcollab\10.3.3\sql\mssql\collaboration-server-create-tables.sql script.

2. To create the objects required by Oracle WebCenter Collaboration, run the install_dir\ptcollab\10.3.3\sql\mssql\collaboration-server-data.sql script.

3. To grant the portal database user Read access to tables in the Oracle WebCenter Collaboration database, run the install_dir\ptcollab\10.3.3\sql\mssql\collaboration-server-portal-role-grant.sql script.

Scripting the Portal Database on Microsoft SQL Server

Run the database scripts as the sa user on the portal database in the following order:

1. To grant the Oracle WebCenter Collaboration database user Read access to tables in the portal database, run the install_dir\ptcollab\10.3.3\sql\mssql\portal-collaboration-server-role-grant.sql script.

2. To create Oracle WebCenter Collaboration objects in the portal database, run the install_dir\ptcollab\10.3.3\sql\mssql\portal-collaboration-server-data.sql script.

Scripting the Database on Oracle

This section describes how to run the SQL scripts to create and configure the Oracle WebCenter Collaboration database schema, as well as configure the portal database schema for Oracle WebCenter Collaboration.

These SQL scripts create the Oracle WebCenter Collaboration schema and add specific tables and information. They also grant SELECT access to the Oracle WebCenter Collaboration schema owner.

Note:

You should have already configured the database, as described in Configuring a DB2 Database for Oracle WebCenter Collaboration.

Note:

If you are running the scripts on a local machine you do not must include the command line @<Oracle_SID>, however you do must ensure that the environment variables are set.

Perform the following procedure to run the scripts:

1. Perform the following on the portal database server:

   1. Create the directory %ORACLE_HOME%/ptcollabscripts.

   2. Copy the Oracle WebCenter Collaboration database scripts from the installation location into this folder.

2. Update any required database patches.

3. If you are installing in a production environment, set up the database to archive log files. Using the default configuration, you must shut down the Oracle database to get a read-consistent backup.

4. If you want, you can change the names and locations of the COLLAB_TEMP and COLLAB_DATA tablespaces by modifying the collaboration-server-create-table-space.sql script. Put each tablespace on its own hard drive.

5. By default, the Oracle WebCenter Collaboration schema user name is collab, and the password is collab. You can change the schema user name and password by modifying the collaboration-server-create-user.sql script.

6. Use sql*plus to execute collaboration-server-create-table-space.sql. This script creates the Oracle WebCenter Collaboration schema default tablespaces.

   You must log in as the system user to execute this script. Substitute the correct system password in the following command:

   sqlplus system/<system_pwd>@<ORACLE_SID>
   @collaboration-server-create-table-space.sql
   

7. As the system user, execute collaboration-server-create-user.sql. This script creates the user and password you specified during Oracle WebCenter Collaboration installation. The script prompts you to enter the password again; be sure to enter the correct password.

   sqlplus system/<system_pwd>@<ORACLE_SID>
   @collaboration-server-create-user.sql
   

8. As the Oracle WebCenter Collaboration user, execute collaboration-server-create-tables.sql to create Oracle WebCenter Collaboration tables. Substitute the correct Oracle user name and password; this is the user name and password you specified during Oracle WebCenter Collaboration installation:

   sqlplus <collab_user_name>/<user_pwd>@<ORACLE_SID> 
   @collaboration-server-create-tables.sql
   

   Note:

   This script stops immediately on a SQL error. If this happens, resolve the problem and rerun the script.

9. As the Oracle WebCenter Collaboration user, execute collaboration-server-data.sql to populate the Oracle WebCenter Collaboration tables. Substitute the correct Oracle user name and password; this is the user name and password you specified during Oracle WebCenter Collaboration installation:

   sqlplus <collab_user_name>/<user_pwd>@<ORACLE_SID> 
   @collaboration-server-data.sql
   

10. As the Oracle WebCenter Collaboration user, execute collaboration-server-portal-role-grant.sql. This script grants the portal schema user SELECT access to required tables in the Oracle WebCenter Collaboration schema. Substitute the correct Oracle user name and password; this is the user name and password you specified during Oracle WebCenter Collaboration installation. The script prompts for other required passwords.

    sqlplus <collab_user_name>/<user_pwd>@<ORACLE_SID> 
    @collaboration-server-portal-role-grant.sql
    

11. As the portal user, execute portal-collaboration-server-role-grant.sql. This script grants the Oracle WebCenter Collaboration schema user SELECT access to required tables in the portal schema. Substitute the correct portal database user name and password in the following command. The script prompts for other required passwords.

    sqlplus <portal_user_name>/<portal_pwd>@<ORACLE_SID> 
    @portal-collaboration-server-role-grant.sql
    

12. As the portal user, execute portal-collaboration-server-data.sql. This script creates views in the portal schema that allow it to see Oracle WebCenter Collaboration tables. Substitute the correct portal database user name and password in the command:

    sqlplus <portal_user_name>/<portal_pwd>@<ORACLE_SID> @portal-collaboration-server-data.sql
    

13. Restart the portal.

Scripting a DB2 Database on UNIX for Oracle WebCenter Collaboration

This topic describes how to script a DB2 database on UNIX for use with Oracle WebCenter Collaboration.

Note:

For this release, we do not support scripting a DB2 database on Windows for Oracle WebCenter Collaboration.

Before scripting a DB2 database for Oracle WebCenter Collaboration:

• Ensure that you have already configured the database, as described in Configuring a DB2 Database for Oracle WebCenter Collaboration.

• 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 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 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:

1. 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.3/sql/db2

2. As a user with administrative privileges, run the these scripts in the following order:

   1. create_collab_schema.sql

   2. create_collab_tablespace_unix.sql

   3. grant_collab_user.sql

   4. collaboration-server-create-tables.sql

   5. collaboration-server-data.sql

   6. collaboration-server-portal-role-grant.sql

   7. portal-collaboration-server-role-grant.sql

   8. portal-collaboration-server-data.sql

Configuring the Image Service for Notification Emails

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:

1. On the machine hosting the Image Service, open the Internet Information Services (IIS) Manager, right-click the local computer name, and click Properties.

2. Click MIME Types.

3. Click New. This opens the MIME Type dialogue box.

4. Type .nst in the Extension box.

5. Type text/plain in the MIME type box.

6. Click OK in the MIME Type dialogue box.

7. Repeat steps 3-6, entering inc in the Extension box.

8. Click OK to save the new settings.

9. Click OK in the Properties dialogue box.

10. Restart the World Wide Web Publishing Service so that the changes take effect.

Configuring Oracle WebCenter Collaboration Integration with Oracle Universal Content Management

You can export ­­Oracle WebCenter Collaboration projects and documents to ­Oracle Universal Content Management. To do so, you must perform the following tasks:

• Configuring Oracle Universal Content Management to Auto-Assign Content IDs

• Configuring Oracle Universal Content Management Settings in Oracle WebCenter Configuration Manager

Configuring Oracle Universal Content Management to Auto-Assign Content IDs

To configure ­Oracle Universal Content Management to auto-assign content IDs:

1. Log in to ­Oracle Universal Content Management.

2. Click Administration, then Admin Server.

3. Click the server name. Figure 2-1 shows the options for the server named "idc."

4. On the left of the options dialog box, click General Configuration.

5. On the General Configuration page, select Automatically assign a content ID on check in. You do not must edit the Auto Number Prefix.

   Figure 2-1 Oracle Content Admin Server dialog box - General Configuration Page

   
   Description of "Figure 2-1 Oracle Content Admin Server dialog box - General Configuration Page"
   
   

6. Click Save.

7. On the left, click Start/Stop Content Server.

8. On the Start/Stop Content Server page, click Restart.

Configuring Oracle Universal Content Management Settings in Oracle WebCenter Configuration Manager

You must configure the settings inOracle WebCenter Configuration Manager that tell Oracle WebCenter Collaboration how to communicate with Oracle Universal Content Management.

To configure Oracle Universal Content Management settings in Oracle WebCenter Configuration Manager:

1. Log in to Oracle WebCenter Configuration Manager.

2. Expand Collaboration, and click Collaboration Settings.

3. In the Project and Document export to UCM section:

   Figure 2-2 Oracle Universal Content Management Settings in Oracle WebCenter Configuration Manager

   
   Description of "Figure 2-2 Oracle Universal Content Management Settings in Oracle WebCenter Configuration Manager"
   
   

   • Select Enabled to enable users to export Oracle WebCenter Collaboration projects and documents to Oracle Universal Content Management. This adds an Export to UCM option on the Manage Project and Publish menus in the Oracle WebCenter Collaboration user interface.

   • In the UCM User box, type the name of the user used to content to Oracle Universal Content Management. This user must have sufficient rights to create and delete folders.

   • In the IDC Url to UCM box, type the URL used to connect to Oracle Universal Content Management programmatically: idc://server_name:server_port. The default port is 4444.

   • In the Project parent folder id box, type the name of the folder to use as the root folder. This folder is used in document export as the root of the folder tree. To obtain the root folder ID, browse content in Oracle Universal Content Management, then open the desired folder in a new tab or window. The ID appears in the query string as the value for the dCollectionId parameter.

4. Click Save.

5. Restart Oracle WebCenter Collaboration for the settings to take effect.

Importing the Oracle WebCenter Collaboration Migration Package

This section describes how to import the Oracle WebCenter Collaboration migration package to create the portal objects used by Oracle WebCenter Collaboration.

To import the Oracle WebCenter Collaboration migration package:

1. Verify that the Search Server is running.

2. Log on to the portal as a user who has administrative rights.

3. 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.3/serverpackages/

   • Windows: install_dir\ptcollab\10.3.3\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.

Starting and Verifying the Installation

This section describes how to start Oracle WebCenter Collaboration and verify the installation. It includes the following sections:

• Verifying Oracle WebCenter Interaction Services

• Starting the Oracle WebCenter Collaboration Service

• Running the Diagnostics Utility

Verifying Oracle WebCenter Interaction Services

Verify that the following Oracle WebCenter Interaction services are running:

• Search Server

• API Service

• Automation Service

• Document Repository Service

• LDAP Directory Service

• Notification Service

• Search Service

For details on starting Oracle WebCenter Interaction services, see Oracle Fusion Middleware Installation Guide for Oracle WebCenter Interaction for Windows or Oracle Fusion Middleware Installation Guide for Oracle WebCenter Interaction for Unix and Linux.

Starting the Oracle WebCenter Collaboration Service

This section describes how to start the Oracle WebCenter Collaboration service. Follow the procedure appropriate to your environment.

Starting the Oracle WebCenter Collaboration Service on UNIX/Linux

To start the Oracle WebCenter Collaboration service on UNIX/Linux:

1. Verify that the Notification Service is started.

2. cd to /opt/oracle/middleware/wci/ptcollab/10.3.3/bin

   run ./ptcollaborationd.sh start

   Note:

   If Oracle WebCenter Collaboration is deployed on 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 installation. Follow the instructions in Oracle WebCenter Configuration Manager to start each service. If Oracle WebCenter Collaboration is deployed on WebLogic Server, you cannot start it from Oracle WebCenter Configuration Manager.

Starting the Oracle WebCenter Collaboration Service on Windows

To start the Oracle WebCenter Collaboration service on Windows:

1. Click Start, Control Panel, Administrative Tools, then Services.

2. Verify that the Notification Service is started.

3. Start Oracle WC Collaboration.

   Note:

   You can also start and stop the Oracle WebCenter Collaboration service using Oracle WebCenter Configuration Manager. Log in to Oracle WebCenter Configuration Manager using the user name Administrator and the password you specified during installation. Follow the instructions in Oracle WebCenter Configuration Manager to start the service. If Oracle WebCenter Collaboration is deployed on WebLogic Server, you cannot start it from Oracle WebCenter Configuration Manager.

If Oracle WebCenter Collaboration is deployed on WebLogic Server, start the WebLogic domain on which Oracle WebCenter Collaboration is deployed. Do not start the Oracle WCI Collaboration service.

Running the Diagnostics Utility

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/oracle/middleware/wci/ptcollab/10.3.3/settings/logs directory.