Skip Headers
Oracle® Collaboration Suite Upgrade Guide
10g Release 1 (10.1.2) for hp-ux PA-RISC (64-bit), Linux x86 and Solaris Operating Environment (SPARC)

Part Number B25495-07
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

3 Preparing to Upgrade

This chapter discusses steps you perform before starting the upgrade depending on your configuration and the version you have installed. It includes the following sections:

3.1 Preparing to Upgrade from Oracle Collaboration Suite Release 1 (9.0.3.1)

Perform the steps in this section if you are upgrading from Oracle Collaboration Suite Release 1 (9.0.3.1).

3.1.1 Applying the Oracle9iAS Portal 9.0.2.3 Patch to the Release 1 (9.0.3.1) Middle Tier

The Oracle9iAS Portal 9.0.2.3 patch is required if you are upgrading from Oracle Collaboration Suite Release 1 (9.0.3.1).

Oracle Collaboration Suite Release 1 (9.0.3.1) corresponds to Oracle9iAS Portal 9.0.2. This release requires applying patches to the:

  • Oracle9iAS Portal schema in the Oracle9iAS Metadata Repository database.

  • Oracle Collaboration Suite Release 1 (9.0.3.1) middle tier installation. The patch copies files (portal.ear, ptlshare.jar, jpdk.ear and other files) to the appropriate locations in the middle tier Oracle home directory.

You use the Oracle Universal Installer packaged with the patch set to install the patch.

3.1.1.1 Preinstallation Steps

To prepare for installing the patch:

  1. Log in to the system running the Oracle Collaboration Suite middle tier as the same user who installed Oracle Collaboration Suite. Make sure the ORACLE_HOME environment variable is set to the Oracle Collaboration Suite middle tier installation.

  2. Shut down all existing Oracle9iAS processes and instances and all other processes running in or against the Oracle home where this patch is to be installed. See Chapter 7 for instructions.

  3. Back up your Oracle9iAS Metadata Repository database. To help you recover from any errors that may occur while applying this patch, Oracle recommends that you perform a database backup of your Oracle9iAS Portal schema. The only way to undo the changes is to restore from your backup.

  4. Back up the middle tier Oracle home where you are applying the patch.

  5. On the system running Oracle Internet Directory, enter the following command to retrieve the Oracle9iAS Portal password from Oracle Internet Directory:

    ORACLE_HOME/bin/ldapsearch -h oidhost -p oidport -D "cn=orcladmin" -w oiduser_password
    -b "cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext"
     -s sub "orclResourceName=portal" orclpasswordattribute
    
    

    where

    • oidhost is the name of the system running Oracle Internet Directory

    • oidport is the port where Oracle Internet Directory is running

    • oiduser_password is the password for the Oracle Internet Directory administrative user

  6. Make sure that a TNS connect string for the Oracle9iAS Metadata Repository database is defined in tnsnames.ora. If not, create it by running the netca tool. See Section 9.5.1 for instructions.

    The patch installation requires the TNS string.

3.1.1.2 Installing the Oracle9iAS Portal Release 2 (9.0.2.3) Patch

To install the patch:

  1. Locate the patch on the Supplemental DVD under .

    Unpack the patch zip file. It will create a directory with the name:

    portal_patch9023unix
    
    
  2. Start the installer packaged with this patch set by entering the following commands:

    cd portal_patch9023unix/Disk1/install/solaris/
    ./runInstaller
    
    
  3. Provide the file locations when prompted. In the Source field, select the products.jar file from the directory where you unpacked the patch zip file.

    portal_patch9023unix/Disk1/Stage/products.jar
    
    
  4. In the Destination field, select your Oracle Collaboration Suite Release 1 (9.0.3.1) middle tier installation.

  5. Click Next. From the Available Products screen, select the option Oracle Portal Patch Set 9.0.2.3.0.

  6. Click Next. Answer the remaining questions asked by the installer to install the patch such as the Oracle9iAS Portal password and the TNS connect string.

3.1.1.3 Postinstallation Information

Following the patch installation, you should be aware of the following items:

  • The installer restarts your Oracle HTTP Server after the patch application completes. If it is still down, restart it manually. See Section 7.1.1 for instructions.

  • The log file, patch.log, is located at .

  • There is no automatic mechanism for deinstalling the patch set. To undo the patch, restore the middle tier ORACLE_HOME from your backup. Restore the database containing Oracle9iAS Metadata Repository from your database backup.

  • If your 9.0.2 web.xml file contains a non-default value for the cacheDir variable, the value is lost after upgrading to 9.0.2.3. The workaround is to rewrite the cacheDir entry manually, ensuring the entry has an absolute path.

3.2 Preparing to Upgrade from Oracle Collaboration Suite Release 2 (9.0.4.2)

Before upgrading Oracle Collaboration Suite Release 2 (9.0.4.2), make sure to do the following:

3.2.1 Upgrade the OracleAS Portal

Perform the steps to upgrade Oracle9iAS Portal 9.0.2 to Oracle9iAS Portal 9.0.2.6 if the following conditions apply to your environment:

  • A Release 2 (9.0.4.2) middle tier configured with Oracle9iAS Portal

  • A single Oracle9iAS Metadata Repository used by both Oracle Internet Directory and your middle tier applications

  • Your Oracle9iAS Portal application needs to continue working after each stage of the upgrade process.

To upgrade the existing Oracle9iAS Portal 9.0.2 to Oracle9iAS Portal 9.0.2.6, apply the appropriate patches before starting the rest of the upgrade. See Chapter 10 for instructions on applying the patches.

This upgrade is optional, but if you choose not to perform it, the Oracle9iAS Portal may not function correctly after the Oracle9iAS Infrastructure upgrade until the entire upgrade process is complete.

3.2.2 Set Attributes

Prior to upgrading the Oracle Collaboration Suite middle tiers from 9.0.4 to 10.1.2, the following attribute should be set as described:

  • orclpwdencryptionenable=1

  • orclpwdpolicyenable=1

These attributes can be queried using the following ldapsearch:

$ORACLE_HOME/bin/ldapsearch -h <ldap host> -p <ldap port>-D cn=orcladmin -W

<password> -b "cn=PwdPolicyEntry,cn=common,cn=products,cn=oraclecontext" -s

base "objectclass=*"

3.2.3 Remove Oracle Web Conferencing from Oracle Collaboration Suite Release 2 (9.0.4.2)

Oracle Web Conferencing must be removed from Oracle Collaboration Suite Release 2 (9.0.4.2) prior to upgrading to Oracle Collaboration Suite 10g Release 1 (10.1.2).


Note:

Oracle Web Conferencing must be removed from Oracle Collaboration Suite Release 2 (9.0.4.2) even if it is not configured. If Oracle Web Conferencing is not configured, certain steps in the following procedure will be unnecessary, such as removing configured components.

To remove Oracle Web Conferencing from Oracle Collaboration Suite Release 2 (9.0.4.2):

  1. Stop all servers on all Oracle Collaboration Suite middle tiers as follows:

    1. Set the following variables:

      ORACLE_HOME=<middle tier home>
      PATH = $ORACLE_HOME\bin:$PATH
      
      

      where <middle tier home> is the path of the Oracle Collaboration Suite middle tier home.

    2. Execute the following command:

      $ORACLE_HOME\bin\opmnctl stopall
      
      
    3. Execute the following command as a root user:

      $ORACLE_HOME\imeeting\bin\imtctl stop
      
      
    4. Navigate to the active Oracle Enterprise Manager directory home and stop the Oracle Enterprise Manager server as follows:

      emctl stop
      
      
  2. Undeploy oc4j_imeeting on all Oracle Collaboration Suite middle tiers as follows:

    dcmctl undeployApplication -a imeeting -co oc4j_imeeting
    dcmctl updateconfig
    
    
  3. Remove the iMeeting and OC4J entries from the file <active EMD Oracle home>\sysman\emd\targets.xml on all Oracle Collaboration Suite middle tiers as follows:

    1. Back up the original targets.xml file.

    2. Execute the following commands:

      <SOURCE_ORACLE_HOME>\jdk\bin>java -jar 
      <SOURCE_ORACLE_HOME>\jlib\emConfigInstall.jar deletetarget imeeting <middle_tier.organization.com> 
      <SOURCE_ORACLE_HOME>\jdk\bin>java -jar 
      <SOURCE_ORACLE_HOME>\jlib\emConfigInstall.jar deletetarget oc4j <middle_tier.organization.com>_OC4J_imeeting 
      
      

      where <middle_tier.organization.com> is the URL of the Oracle Collaboration Suite middle tier.

    3. In a text editor, open targets.xml to confirm that the imeeting and oc4j entries have been removed.

  4. Remove the relevant entries from Oracle Internet Directory as follows:

    1. On the OracleAS Infrastructure computer, navigate to <INFRASTRUCTURE_HOME>\bin\oidadmin and connect to the Oracle Internet Directory.

    2. Login as an orcladmin user.

    3. Under EntryManagement, navigate to cn=rtc , cn=Products, cn=OracleContext.

    4. Right-click the entries in this section and select Delete.

  5. Delete the Oracle Web Conferencing portlet from OracleAS Portal as follows:

    1. Login to OracleAS Portal as an administrator.

    2. Click Builder.

    3. Search for providers, then select and delete all providers related to iMeeting or Oracle Web Conferencing.

    4. In a text editor, open the file <ORACLE_HOME>\Apache\Apache\conf\oracle_apache.conf and comment out any lines listing mod_imeeting.conf.

  6. Drop the Oracle Web Conferencing schemas as follows:

    1. On the Information Storage computer, set the OracleHome, Sid, and Path environment variables.

    2. Execute the following commands:

      sqlplus 'connect  <sys>/<sys-passwd> as sysdba'
      sql>select username from dba_users where username like 'RTC%';
      
      

      where <sys>/<sys-passwd> are the system database administrator username and password.

      This select statement returns RTC, RTC_APP, and RTC_REP database users.

      Note the passwords for the RTC, RTC_APP, and RTC_REP schemas, as you will be asked to verify the passwords while upgrading the Oracle Collaboration Suite middle tier.

    3. Execute the following commands to drop the users:

      sql>drop user rtc_app cascade;
      sql>drop user rtc cascade;
      sql>drop user rtc_rep cascade;
      
      
  7. Remove imeeting entries from <ORACLE_HOME>\opmn\conf\opmn.xml as follows:

    1. Back up the original opmn.xml file.

    2. In a text editor, open opmn.xml and remove all target entries where the target type is imeeting, rtc, or imtpm (for example, <"Target TYPE="imeeting">).

  8. Do the following when configuring Oracle Real-Time Collaboration through Oracle Enterprise Manager:

    • Set the HTTP listen port to the HTTP port, and the HTTPS listen port to the HTTPS port. Do not use the listen ports listed in %ORACLE_HOME%\install\portlist.ini.

    • When configuring Oracle Real-Time Collaboration through Oracle Enterprise Manager, a drop-down list of available databases displays, including OracleAS Infrastructure database and Information Storage Database. Select the database that has been upgraded to Oracle Collaboration Suite 10g Release 1 (10.1.2).