6 Post-Configuration

Applying Patch

Apply patch ARU 4797874 for bug number 3143044 on the database-tier Calendar Server Oracle home and the middle-tier Calendar Web client Oracle home. On the middle-tier Calendar Web client Oracle home, do not run the uniclean and unistart commands as documented.

Post-Configuration Steps for Files

Use the following to perform post-configuration for Files.

Post-Configuration Steps for Infostore Databases

Perform the following post-configuration steps for Infostore databases:

1. Run SQL*Plus against the Email or Real-Time Collaboration Infostores, and log in as the system user, using the password that you selected during configuration.

   $ sqlplus system/<password>
   
   SQL> select job, schema_user, broken from dba_jobs;
   
          JOB SCHEMA_USER                    B
   ---------- ------------------------------ -
            4 RTC_APP                        N
            2 RTC_APP                        N
            3 RTC_APP                        N
            5 IFSSYS                         N
            6 IFSSYS                         N
            7 OWF_MGR                        N
            8 OWF_MGR                        N
   
   SQL> exit;
   
   

2. In the Email Infostore, you can set the jobs owned by IFSSYS, OWF_MGR and RTC_APP to ÒbrokenÓ. In the Real-Time Collaboration Infostore, only set the jobs owned by IFSSYS and OWF_MGR to ÒbrokenÓ.Log in to the Infostore as the schema user of these jobs to disable the jobs. For example, the preceding table shows that the IFSSYS user owns job id 5 and 6.

   $ sqlplus IFSSYS/welcome1
    
   SQL> exec dbms_job.broken(JOB_ID, true);
   e.g.
   SQL> exec dbms_job.broken(5, true);
   SQL> exec dbms_job.broken(6, true);
   SQL> exit;
    
   $ sqlplus OWF_MGR/<sys user password>
    
   SQL> exec dbms_job.broken(JOB_ID, true);
   e.g.
   SQL> exec dbms_job.broken(7, true);
   SQL> exec dbms_job.broken(8, true);
   SQL> exit;
    
   $ sqlplus RTC_APP/welcome1
    
   SQL> exec dbms_job.broken(JOB_ID, true);
   e.g.
   SQL> exec dbms_job.broken(4, true);
   SQL> exec dbms_job.broken(2, true);
   SQL> exec dbms_job.broken(3, true);
   SQL> exit;
   
   

3. After you have disabled all the unnecessary jobs, verify that the jobs are disabled by logging in as the system user. The following table is an example of the output from running the following command:

   $ sqlplus system/<password>
    
   SQL> select job, schema_user, broken from dba_jobs;
    
          JOB SCHEMA_USER                    B
   ---------- ------------------------------ -
            4 RTC_APP                        Y
            2 RTC_APP                        Y
            3 RTC_APP                        Y
            5 IFSSYS                         Y
            6 IFSSYS                         Y
            7 OWF_MGR                        Y
            8 OWF_MGR                        Y
    
   SQL> exit;
   

Refreshing ONS Configuration

Use the corresponding instructions depending on your deployment type.

Creating a Subscriber Administrator for Files

Use the following to create a subscriber administrator for Files:

1. As the root user, start Files using ifsctl.

2. Run the following command to start the OC4J component:

   # dcmctl start -co OC4J_ifs_files
   
   

3. Go to the following URL:

   http://<hostname.domain>:7778/files/app/AdminLogin
   
   

4. Log in as the site_admin user.

5. Click on New Subscriber, then click Next.

6. Enter the subscriber quota (at least 2 GB), maximum number of users and the subscriber expiration date.

7. Enter cst_admin as the user ID. The E-mail address should be cst_admin@<your email domain>.

8. Enter the number of days before a user is disabled, and the user quota (depending on the customer contract.)

9. Select the appropriate value for Display Language.

10. Select the Default Document Properties that you want:

    For example:

    Default Document Language: English
    Default Document Character Set: Western (ISO-8859-1)
    
    

11. Set the Workspace Quota.

12. Review the settings and click Finish to create the subscriber administrator user.

    The cst_admin user should then receive an email at http://<midtier-host>:7778/um/traffic_cop containing a password. The cst_admin user can log in to http://<midtier-host>:7778/files/app/AdminLogin as cst_admin/<received password to perform administrative tasks.

Removing Old Partner Applications

If you used the gold image to deploy your Oracle Collaboration Suite CC, then use the following to remove old partner applications on the system. This fix is not required for the deployments installed and configured from the Product CD-ROMs.

1. Log into the Single Sign On (SSO) Server at:

   http://<hostname:<port/pls/orasso
   
   

2. Click SSO Server Administration.

3. Click Administer Partner Applications.

4. In the Edit/Delete Partner Application section, delete the following old partner applications:

   Oracle Portal (portal)
   cgoldc_ocscal.<hostname.<domainname
   cgolds_infraoidsso.<hostname.<domainname
   cgoldu_ocsmtemail.<hostname.<domainname
   wireless_deviceportal
   
   

   If there are two application entries with the same name (for example, wireless_deviceportal), then use the following procedure to identify the old application:

   1. Click on the Edit icon against the partner application.

   2. Note the ID of the application in the Edit Partner Application page.

      The application ID with the lesser value is the old partner application

Restarting Oracle Collaboration Suite

If you installed Oracle Collaboration Suite CC from the gold image, then the running OPMN processes may contain outdated information. You must restart Oracle Collaboration Suite services to ensure the information in the OPMN processes is up to date. See "Starting and Stopping Oracle Collaboration Suite Components" for details on how to start or stop services in a specific Oracle home.

Stop and start Oracle Collaboration Suite in the following sequence:

1. Stop the Oracle Collaboration Suite mid-tier components Oracle home

2. Stop the Infrastructure Oracle home

3. Start the Infrastructure Oracle home

4. Start the Oracle Collaboration Suite mid-tier components Oracle home

Configuring Search Features

Refer to "Configuring Search Features" in Oracle Collaboration Suite Installation and Configuration Guide (B10874-01) for instructions.

Changing the Datafiles in Oracle Files

By default, the database datafiles used by Oracle Files are not autoextensible in Oracle Collaboration Suite CC release 9.0.4.1. You can change this setting by performing the following:

1. Log in to the Files Infostore database as the system database user.

   $ sqlplus system/<password>@<connect_string>
   SQL> select FILE_NAME, TABLESPACE_NAME, AUTOEXTENSIBLE from dba_data_files where TABLESPACE_NAME like 'FILES_%';
   
   

   You will see an output like the following, listing seven datafiles and their corresponding tablespace names:

   FILE_NAME--------------------------------TABLESPACE_NAME-------------AUT
   /tclona/oradata/data01/files_main.dbf     FILES_MAIN                 NO
    
   /tclona/oradata/data01/files_lob.dbf      FILES_LOB                  NO
    
   /tclona/oradata/data01/files_ilob.dbf     FILES_ILOB                 NO…
    
   

2. If the ÒAUTÓ column is already set to YES, then you can skip this operation. If not, perform the following for each of the non-autoextensible datafile:

   SQL> alter database datafile '/<SID>/oradata/data01/<filename>.dbf' autoextend on;…
   
   

3. After completing the changes, exit SQL*Plus:

   SQL> exit;
   

Setting Up cron Job to Back Up Calendar

If you want to set up a cron job to back up Calendar data, refer to the /admin/mwcc/ocs/904/utils/calbackup/README.txt file.

Applying Patches

Apply the following patches.

• Apply patch ARU 4746420 for bug number 2811897 to fix an issue with the v$session view.

• Apply patch ARU 4797874 for bug number 3143044 on the database-tier Calendar Server Oracle home and the middle-tier Calendar Web client Oracle home. On the middle-tier Calendar Web client Oracle home, do not run the uniclean and unistart commands as documented.

Starting Databases in Archive Mode

Use the following to start all the databases in archive mode:

$ sqlplus ‘/ as sysdba’
startup mount;
alter database archivelog;
alter database open;
shutdown immediate;
startup;
exit

Changing temp Tablespaces to Autoextensible to ’YES’

Use the following to change temp tablespaces to autoextensible to ’YES’ in the Infrastructure database:

$ sqlplus ‘/ as sysdba’
   alter database tempfile ‘/<SID>/oradata/data02/temp01.dbf’ 
autoextend on;
  alter database tempfile ‘/<SID>/oradata/data02/ptltmp.dbf’ 
autoextend on;
  alter database tempfile ‘/<SID>/oradata/data02/discotemp1.dbf’ 
autoextend on;

Applying the Workaround for Bug Number 3136600

Use the following to apply the workaround for bug number 3136600:

1. Set the ORACLE_HOME variable to the Oracle Collaboration Suite CC middle-tier Oracle home.

2. Edit the $ORACLE_HOME/webcache/webcache.xml file.

3. Add the following just before the </CACHEABILITY> </GLOBALCACHINGRULES> tags:

   <CACHEABILITYRULE COMMENT="" SSLONLY="NO" COMPRESS="YES" 
   CANOUTPUTESI="YES" COMPRESSFORNETSCAPE="YES" CACHE="NO">
               <SELECTORS>
                 <URLEXP EXP="\/um\/view_atttachment$"/>
                 <HTTPMETHODS SIMPLEGET="YES" GETWITHQUERYSTRING="YES" 
   POST="NO"/>
               </SELECTORS>
   

Applying the Workaround for Email Bug Number 3093934

Use the following to apply the workaround for bug number 3093934:

1. Set the ORACLE_HOME variable to the Oracle Collaboration Suite CC middle-tier Oracle home.

2. Set the oracle.mail.sdk.esmail.encryption value to false in the $ORACLE_HOME/j2ee/OC4J_UM/config/oc4j.properties file.

Applying the OUI Workaround for Oracle Collaboration Suite CC Middle-Tier

Use the following to apply the OUI workaround for Oracle Collaboration Suite CC middle-tier:

1. Set the ORACLE_HOME variable to the Oracle Collaboration Suite CC middle-tier Oracle home.

2. Edit the $ORACLE_HOME/oui/oraparam.ini file to change the JRE_LOCATION to ../../jre/1.4.1.

Configuring Search Features

Refer to "Configuring Search Features" in Oracle Collaboration Suite Installation and Configuration Guide (B10874-01) for instructions.

Setting Up Oracle Collaboration Suite Home Page for Portal Users

Use the following to set up the Oracle Collaboration Suite home page for Portal users.

Setting Up cron Job to Back Up Calendar

If you want to set up a cron job to back up Calendar data, refer to the /admin/mwcc/ocs/904/utils/calbackup/README.txt file.