| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for hp Tru64 UNIX Part Number B12232-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for hp Tru64 UNIX Part Number B12232-02 |
|
|
View PDF |
This chapter contains procedural information for upgrading existing Oracle Collaboration Suite Release 1 (9.0.3) installations and associated components to Oracle Collaboration Suite Release 2 (9.0.4.1).
The sequence of events for a successful upgrade is as follows:
Back up important information
Globalization requirements
Upgrade the infrastructure
Upgrade the information store
Install the Oracle Collaboration Suite Release 2 (9.0.4.1) middle tier
Perform pre-upgrade tasks
Upgrade the middle tier
Perform post-upgrade tasks
This chapter contains these topics:
Enabling Multiple Language Support in Oracle Collaboration Suite Release 2 (9.0.4.1)
Upgrading the Oracle Collaboration Suite Information Storage Database
Upgrading from Oracle Calendar Standalone External to Oracle Collaboration Suite
Upgrading from Oracle Calendar Standalone Internal to Oracle Collaboration Suite
|
Note: Oracle recommends backing up the software in the$ORACLE_HOME, database files, and the Oracle Inventory prior to upgrading the software. |
|
See Also: Oracle9i Application Server 9.0.2 documentation is available on Oracle Technology Network athttp://otn.oracle.com/ |
Back up your Oracle installations.
Back up the Oracle Collaboration Suite Release 1 (9.0.3) information storage database.
Back up the Oracle Collaboration Suite Release 1 (9.0.3) infrastructure.
Back up the Oracle Collaboration Suite Release 1 (9.0.3) middle tier.
Back up the directory (or directories) listed for hp Tru64 UNIX.
Back up Oracle Calendar by logging in as the user unison and backing up the /users/unison directory.
Back up the Oracle Universal Installer inventory located in the oraInventory directory.
Copy the oraInventory subdirectory and all of its contents to another directory.
Oracle Collaboration Suite Release 2 (9.0.4.1) provides translation support for 9 additional languages to that of Release 1 (9.0.3), as shown in Table 3-1.
To enable multiple language support in Oracle Collaboration Suite Release 2 (9.0.4.1), execute the ptlasst.csh script from the Release 1 (9.0.3) middle tier, located in the following directory, before going through the upgrade process:
|
Notes:
|
$ORACLE_HOME/ora9ias/assistants/opca/
The usage of the ptlasst.csh file is as follows:
$ORACLE_HOME/ora9ias/assistants/opca/ptlasst.csh -mode LANGUAGE -s portal -sp portal -o orasso -op orasso -c myhost.domain.com:1521:mySID -lang lang -available -silent- verbose -sso_c myhost.domain.com:1521:mySID
-available: Determines whether the language is available for user translation
-c: Connect string to the target database. The format should be hostname:port:SID
-o: Oracle9iAS Single Sign-On schema name. The default is orasso.
-op: Oracle9iAS Single Sign-On password. The default is orasso.
-lang: Language code for the language to install. Table 3-1 lists the various languages and their associated codes.
-silent: Runs the Oracle9iAS Portal configuration assistant in silent mode. Default is TRUE.
-sp: Oracle9iAS Portal schema password. The default is portal.
-sso_c: Connect string to the target database where Oracle9iAS Single Sign-On is installed. The format should be hostname:port:SID.
-verbose: Enables detailed logging mode. Even if there are errors in the log file, Oracle9iAS Portal configuration assistant install will continue. If this parameter is not set, logging information is brief and Oracle9iAS Portal configuration assistant aborts the install if it encounters any ORA-, PLS-, or SP2 errors. The default is TRUE.
You can retrieve Oracle9iAS Portal and Oracle9iAS Single Sign-On randomized passwords from Oracle Internet Directory with the following distinguished name:
OrclResourceName=PORTAL,orclReferenceName=sid.myhost.domain.com,cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext OrclResourceName=ORASSO,orclReferenceName=sid.myhost.domain.com,cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=OracleContext
Table 3-1 lists the 18 languages supported by Oracle Collaboration Suite Release 2 (9.0.4.1) along with their associated language codes.
Table 3-1 Languages Supported in Oracle Collaboration Suite Release 2 (9.0.4.1)
| Language | Code | Supported in Release 1 (9.0.3) |
|---|---|---|
| Arabic | ar | no |
| Brazilian Portuguese | ptb | yes |
| Danish | dk | no |
| Dutch | nl | no |
| Finnish | sf | no |
| French | f | yes |
| German | d | yes |
| Greek | el | no |
| Italian | i | yes |
| Japanese | ja | yes |
| Korean | ko | yes |
| Norwegian | n | no |
| Portuguese | pt | no |
| Simplified Chinese | zhs | yes |
| Spanish | e | yes |
| Swedish | s | no |
| Traditional Chinese | zht | yes |
| Turkish | tr | no |
|
See Also: Oracle9iAS Globalization Support Guide |
In addition to upgrading the Oracle9iAS Infrastructure at the Oracle Collaboration Suite level, the infrastructure must also be upgraded at the component level for Oracle Email and Oracle9iAS Wireless.
This section contains the following topics:
Perform the following procedures to upgrade Oracle9iAS Infrastructure 9.0.2.0.1, Oracle9iAS Infrastructure 9.0.2.0.0, or the Oracle Collaboration Suite Release 1 (9.0.3) Infrastructure to Oracle9iAS Infrastructure 9.0.2.3:
Apply the Oracle9iAS Infrastructure 9.0.2.3 patch 3038037 to the infrastructure.
|
Note: Contained in the README for patch 3038037 are instructions for applying the Oracle9i 9.0.1.4 database server patch 2517300. You must apply patch 2517300 before patch 3038037. Both of these patches are available at:http://metalink.oracle.com/ |
Copy the files listed in the following table from the CDROM_ROOT/tools /upgrade directory on the Oracle9iAS Infrastructure Installation CD-ROM for Release 2 (9.0.4.1) to the specified target directory in the infrastructure Oracle home directory that you are upgrading:
Download Oracle9iAS Portal patch 2513540 available at:
http://metalink.oracle.com/
Follow the instructions below to apply this patch:
Unzip the contents of the file into a temporary directory. The file contains the following files:
Schedule system downtime to apply the patch (shut down all the infrastructure processes except the infrastructure repository database), because no users should be accessing Oracle9iAS Portal while the patch is being applied.
Log in as the Oracle9iAS Portal schema owner using SQL*Plus, as in the following example:
sqlplus portal/portal_schema_password
In the SQL*Plus shell, execute the following:
set define off
Compile the files in the following order:
@secapi.pks
@secapip.pks
@secoid.pks
@secapi.pkb
@secapip.pkb
@secoid.pkb
@secoidd.pkb
Compilation of the preceding files will invalidate some dependent schema objects. Recompile those objects using the following script:
|
Note: This script takes several minutes to execute. |
@recompile.sql
Restart all the infrastructure processes that were shutdown in step b.
Create an orclguest user using Oracle Delegated Administration Services.
|
Note: You must have sufficient privilege to create new users in the default subscriber. |
Log in to Oracle Delegated Administration Services as a user with privilege to create users.
Select the Directory tab.
In the Search Results section, click Create.
Depending on the configuration, the Create User page prompts for different values. The User Name value in this case should be orclguest. The rest of the values should be filled in, accordingly. Ensure that all of the required fields are filled in.
Click Submit.
Complete the following steps to complete the provisioning of the orclguest user using Oracle Directory Manager.
Locate the DN of the default realm.
Using Oracle Directory Manager, log in as cn=orcladmin. In the Entry Management section, navigate to the cn=common,cn=products, cn=oraclecontext entry. The value of the orcldefaultsubscriber attribute is the DN of the default realm.
Locate the DN of the orclguest user entry.
Using Oracle Directory Manager, navigate to the cn=common,cn=products,cn=oraclecontext,default_realm_DN entry under the default realm DN. The value of the orclcommonusersearchbase attribute is the DN of the user search base.
Navigate to this DN. The orclguest user entry resides in the subtree under this DN—most likely one level under the user search base. Make note of the complete DN of this user.
Set the orclguest user's default profile group to OCS_PORTAL_USERS.
In the entry of the orclguest user, select All from View Properties in the DN of the orclguest user. Populate the orcldefaultprofilegroup attribute with the value cn=ocs_portal_users,cn=groups,default_realm_DN. Substitute default_realm_DN with the DN obtained in step a.
Add orclguest to the OCS_PORTAL_USERS group.
Using Oracle Directory Manager, navigate to the cn=ocs_portal_users,cn=groups,default_realm_DN entry. Add the orclguest DN obtained in step b to the uniquemember attribute. Do not remove any existing values of the attribute. Make note of the DN of the ocs_portal_users entry.
|
Note: When you create a new user, the Oracle Collaboration Suite Home page is not set by default. |
|
See Also: "Troubleshooting Oracle Collaboration Suite Web Client Configuration" for information on how to set the Oracle Collaboration Suite Home page |
To upgrade Oracle Email on the Oracle9iAS Infrastructure:
Make Access Control List (ACL) changes that allow e-mail administrators to modify e-mail attributes of base users.
Run oidadmin and connect as cn=orcladmin.
Go to the entry cn=Common,cn=Products,cn=OracleContext.
Get the value of attribute orclsubscribersearchbase from the common container.
Back up the emailaci.ldif file in the $ORACLE_HOME/oes/bin directory and re-create it with the following text:
|
Note: The line beginning withorclaci: and ending with (write) should be on one line. |
dn: %SUBSCRIBER_SEARCHBASE% changetype: modify add: orclaci orclaci: access to attr=(mail) by group="cn=EmailAdminsGroup, cn=EMailServerContainer,cn=Products,cn=OracleContext"(write)
Substitute %SUBSCRIBER_SEARCHBASE% in the script emailaci.ldif with the value for orclsubscribersearchbase retrieved in step c.
Load emailaci.ldif:
ldapmodify -v -a -Dcn=orcladmin -w orcladmin_password -h ldap_host -p ldap_port -f emailaci.ldif
Index attribute targetdn. This allows the attribute to be searched, which is required by Oracle Email.
Log in to the computer that has the Oracle9iAS Infrastructure Oracle Internet Directory.
Shut down the Oracle Internet Directory server.
Run catalog.sh for the targetdn:
$ORACLE_HOME/ldap/bin/catalog.sh -connect infrastructure_connectstr -add -attr targetdn
Where:
infrastructure_connectstr is the connect string for the Oracle9i Application Server Infrastructure database
Restart the Oracle Internet Directory server.
The Oracle9iAS Wireless schema in the Oracle Collaboration Suite Metadata Repository is automatically upgraded during installation of the Oracle Collaboration Suite Release 2 (9.0.4.1) middle tier against the existing metadata repository. You do not have to perform any additional upgrade steps on the Oracle Collaboration Suite Infrastructure.
Both the Oracle Email and Oracle Files information stores from Oracle Collaboration Suite Release 1 (9.0.3) must be upgraded to Oracle9i 9.2.0.3.
To update the information storage database to Oracle9i 9.2.0.3, download the patch 2761332 for the Oracle9i database server from OracleMetaLink at:
http://metalink.oracle.com/
If you are upgrading the Oracle Collaboration Suite Information Store, you need to confirm that the Catalog for the LDAP PL/SQL API has been loaded in this database.
To confirm the presence or absence of the Catalog, run the following SQL*Plus command as the SYS user on the database tier:
DESC DBMS_LDAP
If no such package exists, run the catldap.sql script that is present in $ORACLE_HOME/rdbms/admin as the SYS user on the database tier. This creates the catalog in the database.
|
Caution: Make sure that you runcatldap.sql in the Oracle home of the database; do not run the script from the middle tier or infrastructure Oracle homes. |
This section describes how to upgrade the Oracle Collaboration Suite middle tier from Release 1 (9.0.3) to Release 2 (9.0.4.1).
This section contains these topics:
|
Important: To enable multiple language support, you must follow the procedures in "Enabling Multiple Language Support in Oracle Collaboration Suite Release 2 (9.0.4.1)" before performing the upgrade tasks in this section. |
Before upgrading the middle tier, you must install the Oracle Collaboration Suite Release 2 (9.0.4.1) middle tier into a different $ORACLE_HOME on the same computer as the Release 1 (9.0.3) middle tier, as follows:
Shut down all Release 1 (9.0.3) processes.
Follow the middle tier installation instructions in "Installing the Oracle Collaboration Suite Middle Tier", with the following exception:
When installing Oracle Collaboration Suite Release 2 (9.0.4.1), deselect the Oracle Files checkbox in the Oracle Universal Installer, so that the Oracle Files configuration assistant is not launched automatically.
If the Oracle Files configuration assistant does launch, click Cancel to exit.
|
Notes:
|
|
See Also: "oraInventory Directory and Installation Session Log Files" for the litigation of theoraInst.loc file. |
This section lists the pre-upgrade tasks that you must perform before beginning the upgrade process.
This section contains these topics:
Before upgrading Oracle Calendar, you must perform the following on the Oracle Collaboration Suite Release 2 (9.0.4.1) system:
From $ORACLE_HOME/ocal/upgrade, run ocalPreUpg.sh as root. This will change the ownership of your Oracle Calendar 5.x installation.
Log back on as the user who installed Oracle Collaboration Suite and continue with the next pre-upgrade task.
|
Notes:
|
Before upgrading Oracle Email, you must perform the following tasks:
Apply patch 2868153 to the Oracle Collaboration Suite Release 1 (9.0.3) $ORACLE_HOME to upgrade the existing permissions on shared folders to a format that is required by Release 2 (9.0.4.1).
If you are planning on running multiple middle tiers that include installations of both Oracle Collaboration Suite Release 1 (9.0.3) and Oracle Collaboration Suite Release 2 (9.0.4.1), then you must apply patch 2979341 to the Oracle Collaboration Suite Release 1 (9.0.3) installations. This is necessary in order for the Oracle Collaboration Suite Release 1 (9.0.3) installations to access shared folders created by Oracle Collaboration Suite Release 2 (9.0.4.1) clients.
The Oracle Collaboration Suite upgrade assistant creates additional datafiles in the same directory as the datafile for the SYSTEM tablespace, which by default is the $ORACLE_HOME/dbs directory, and you therefore must ensure that there is sufficient space (85 MB) on the computer to accommodate the new datafiles.
The names of the new tablespaces, datafiles, and their initial sizes are as follows:
ESLMMR tablespace: eslmmr.dbf, 50 MB
ESNEWS tablespace: esnews.dbf, 10 MB
ESTEMP tablespace: estemp.dbf, 5 MB
ESORATEXT tablespace: esoratext.dbf, 20 MB
Before upgrading Oracle Ultra Search, you must perform the following tasks:
Log in to the Oracle Collaboration Suite Release 1 (9.0.3) Oracle Ultra Search administration tool to stop and disable all crawler synchronization schedules in every Oracle Ultra Search instance. You can enable all crawler synchronization schedules after upgrading to Oracle Collaboration Suite Release 2 (9.0.4.1).
Use the Oracle Net configuration assistant to set up the network service name for the Oracle Collaboration Suite infrastructure database.
|
See Also: Oracle9i Net Services Administor's Guide for details on using the Oracle Net configuration assistant |
In case of any failure during the upgrade, back up all the files in the database host $ORACLE_HOME/ultrasearch directory
Before upgrading Oracle Voicemail & Fax, you must perform the following tasks:
Shut down the advanced queue message waiting indicator (AQMWI) processes on the Oracle Collaboration Suite Release 1 (9.0.3) middle tier.
In case of any failure during the upgrade, back up the following trees in Oracle Internet Directory:
cn=midtier_hostname, cn=computers, cn=oraclecontext cn=telephony_server_host_name, cn=computers, cn=oraclecontext cn=umontainer,cn=products,cn=oraclecontext
Back up the Oracle Collaboration Suite Release 1 (9.0.3) targets.xml file located in the $ORACLE_HOME/sysman/emd/ directory.
On the Windows 2000 system, stop all running Oracle Voicemail & Fax Release 1 (9.0.3) processes. Also, delete all existing Oracle Voicemail & Fax Release 1 (9.0.3), including rmid, rmiregistry, and all services that begin with UM.
On the Windows 2000 system, remove the Oracle Voicemail & Fax container part from the sc_vsto.cfg file and restart the CT server.
|
See Also: "Adding an Additional Information Storage Database to Oracle Collaboration Suite" for information about configuring thesc_vsto.cfg file |
If you are upgrading multiple Oracle Collaboration Suite Wireless middle tiers, you must perform the following steps before starting the Oracle Collaboration Suite Upgrade Assistant:
Stop all Oracle Collaboration Suite Release 1 (9.0.3) Wireless middle tiers in the farm, including any Oracle9iAS middle tiers that are configured to run Oracle9iAS Wireless.
|
Caution: Ensure that you have a backup of the Oracle Collaboration Suite Release 1 (9.0.3) Wireless schema in the infrastructure before you perform the installation of the first Oracle Collaboration Suite Release 2 (9.0.4.1) Wireless middle tier, because that schema is upgraded during the installation of the first Oracle Collaboration Suite Release 2 (9.0.4.1) Wireless middle tier. |
Select the first Oracle Collaboration Suite Release 1 (9.0.3) Wireless middle tier to be upgraded.
Install the first Oracle Collaboration Suite Release 2 (9.0.4.1) Wireless middle tier on the same computer as the Oracle Collaboration Suite Release 1 (9.0.3) Wireless identified in the previous step.
The Oracle Collaboration Suite upgrade assistant is a command-line tool that automates the process of upgrading Oracle Collaboration Suite Release 1 (9.0.3) to Oracle Collaboration Suite Release 2 (9.0.4.1). During the upgrade process, you choose which Oracle Collaboration Suite components you want to upgrade. The Oracle Collaboration Suite upgrade assistant then runs separate plug-ins for each component you are upgrading to complete the upgrade process.
The Oracle Collaboration Suite upgrade assistant is located in the following directory:
$ORACLE_HOME/upgrade
The upgrade directory contains log and lib directories, and three primary files that are used in the upgrade process: ocsua.xml, ocsua.properties, and ocsua.sh. Each of these files is described later in this section.
The log directory contains log files generated during the upgrade process. The lib directory contains .jar files that are required by the Oracle Collaboration Suite Upgrade Assistant framework.
This section contains these topics:
The ocsua.xml file lists the component plug-ins along with variables that require user input. The Oracle Collaboration Suite Upgrade Assistant framework reads this file in order to read the plug-ins that perform the individual component upgrades. Do not modify this file.
The ocsua.properties files contains optional properties that are used by the Oracle Collaboration Suite Upgrade Assistant framework. If a property does not exist in the file, then the upgrade process uses the default values in the Java classes that are required by the Oracle Collaboration Suite Upgrade Assistant framework. The contents of the ocsua.properties are as follows:
# # Global properties # # These properties apply to all components of Upgrade Assistant. # # Default global log level is NOTIFICATION log.level=NOTIFICATION # # Utilities component # # Default log level for CopyFile class is NOTIFICATION CopyFile.log.level=NOTICATION # # Component plug-in specific properties # # For log level, the property name is plugin-name as a prefix # with ".log.level". Plug-ins can define any names for # other properties as long as they are prefixed with the # plug-in name # # Example: setting Ultra Search plug-in log level to TRACE to overide default # log level of NOTIFICATION #UltraSearch.log.level=TRACE
|
Notes:
|
The Oracle Collaboration Suite upgrade assistant automatically performs the following steps:
Verifies the existing and version number of the source Oracle Collaboration Suite directory that is being upgraded
Identifies the plug-ins to executed, based on the components you select to upgrade
Identifies the configuration files to update in the Oracle Collaboration Suite Release 1 (9.0.3) source directory for each component that is being upgraded
Displays a prompt for the values of common and plug-in specific variables for the components that are being upgraded
Table 3-2 lists information you will need to provide to the Oracle Collaboration Suite upgrade assistant for Oracle Files.
Table 3-2 Required Oracle Files Information for Oracle Collaboration Suite Upgrade Assistant
| Information | Description |
|---|---|
| Host | The database host where the existing Oracle Collaboration Suite Release 1 (9.0.3) Oracle Files schema resides |
| Port | The database listener port |
| SID | The database service name |
Table 3-3 lists information you will need to provide to the Oracle Collaboration Suite upgrade assistant for Oracle Files if your existing Oracle Collaboration Suite Release 1 (9.0.3) Oracle Files schema is integrated with Oracle Workflow.
|
Note: The schema upgrade process should be performed only for the first middle tier, not for any additional middle tiers. |
Table 3-3 Required Oracle Files Information for Oracle Collaboration Suite Upgrade Assistant if Oracle Files is Integrated with Oracle Workflow
| Information | Description |
|---|---|
| Oracle Files Schema | The name of the Oracle Files schema to integrate with the Oracle Workflow schema |
| Oracle Files Schema Password | The password for the Oracle Files schema |
| Oracle Workflow Schema | The name of the Oracle Workflow schema that is integrated with Oracle Files schema |
| Oracle Workflow Schema Password | The password for the Oracle Workflow schema |
If an error occurs while upgrading an Oracle Collaboration Suite Release 1 (9.0.3) Oracle Files schema, check the following log file for more information:
$ORACLE_HOME/upgrade/log/FilesUpgrade.log
Table 3-4 lists information you will need to provide to the Oracle Collaboration Suite upgrade assistant for Oracle Ultra Search.
Displays a summary of files that need to be upgraded for each component
Displays a list of pre-upgrade tasks that need to be performed, along with any warnings
To run the Oracle Collaboration Suite upgrade assistant, perform the following steps on the Oracle Collaboration Suite Release 2 (9.0.4.1) middle tier:
Change directory to $ORACLE_HOME/upgrade.
Execute the ocsua.sh script to start the Oracle Collaboration Suite upgrade assistant and begin the upgrade process. The usage of the ocsua.sh file is as follows:
bash-2.05$ ocsua.sh -help
ocsua -sourcehome sourcehome [-config input XML] [-all]
Upgrade configuration files to the Oracle Collaboration Suite
Release 2 (9.0.4.1)
Oracle home: -sourcehome $ORACLE_HOME for Oracle Collaboration Suite
Release 1 (9.0.3)
-config Input XML file that lists all the plug-ins
[-all] Run all the component plug-ins without prompt
The first time you perform an upgrade by executing the ocsua.sh file, the upgrade process automatically upgrades the Oracle9iAS components that are required by Oracle Collaboration Suite, including Oracle9iAS Portal, Oracle9iAS Web Cache, and Oracle Enterprise Manager.
ocsua.sh Script Example
Example 3-1 shows the log transcript of a sample upgrade session. It shows both input and output.
Example 3-1 ocsua.sh Script
bash-2.05$ ocsua.sh -sourcehome /home/ias903
Validating Oracle homes
-------------------
These are the components that can be upgraded
1. Oracle9iAS Portal
2. Oracle Ultra Search
3. Oracle9iAS Wireless
4. Oracle Calendar Server
5. Oracle Calendar Application System
6. Oracle Email
7. Oracle Email Store
8. Oracle Voicemail & Fax
9. Oracle Files
Enter component numbers and/or ranges(example:1-3,5)[all]:
--------------------------------------------------------------
Validating component plug-ins
-------------------
Examining "Oracle9iAS Portal"
Upgrade items found:
Oracle_Collaboration_Suite_Release_1_ORACLE_HOME/assistants/opca/ptlasst.csh
-------------------
Examining "Oracle Ultra Search"
Upgrade items found:
Oracle_Collaboration_Suite_Release_1_ORACLE_HOME/j2ee/OC4J_Portal/config
/data-sources.xml
-------------------
Examining "Oracle9iAS Wireless"
Upgrade items found:
Oracle_Collaboration_Suite_Release_1_ORACLE_HOME/wireless/server/classes/oracle
/panama/marconi/marconi.config
Oracle9iAS Wireless Repository
-------------------
Examining "Oracle Calendar Server"
Upgrade items found:
Oracle Calendar Server configuration files
Oracle Calendar Server database files
Oracle Calendar Server Oracle Internet Directory entries
Oracle Calendar Server administrator administration files
-------------------
Examining "Oracle Calendar Application System"
Upgrade items found:
Oracle Calendar applications configuration file
Oracle Calendar Web Client files
-------------------
Examining "Oracle Email"
Upgrade items found:
Oracle Email Oracle Internet Directory entries
Webmail configuration
listener.ora
oc4j.properties
-------------------
Examining "Oracle Email Store"
Upgrade items found:
Oracle Email Store
-------------------
Examining "Oracle Voicemail & Fax"
Upgrade items found:
Oracle Voicemail & Fax Oracle Internet Directory product tree
Oracle Voicemail & Fax mid-tier Oracle Internet Directory entry
-------------------
Examining "Oracle Files"
Upgrade items found:
Oracle Files Schema
--------------------------------------------------------------
Validate pre-upgrade requirements:
The destination Oracle home has not been modified since it was installed.
The source and destination instances of Oracle Collaboration Suite are not
running.
The Enterprise Manager Web site is not running.
The source Oracle home is based on Oracle9iAS 9.0.2.0.1 version with interim
patches.
[Oracle Ultra Search] A tnsnames.ora file has been created in the destination
Oracle home and contains an entry for the Oracle9iAS Metadata Repository
containing the Oracle Ultra Search schema.
[Oracle Calendar Server] The ocalPreUpg.sh script has been run in the
destination Oracle home.
Have you verified all pre-upgrade requirements?[No]Y
--------------------------------------------------------------
Specify the TNS connect string for the Oracle9iAS Metadata Repository used by
Oracle Ultra Search, as well as passwords for the following users:
TNS Connect: TNS_connect_string
SYS Password: password
WKSYS Password: password
-------------------
Specify connection information (host:port:SID) and associated passwords
for the Oracle Email Store to be upgraded:
Oracle Email Store Connect: host_name:port_number:SID
SYS Password: password
ESMail Password: password
CTXSYS Password: password
-------------------
Specify connection information for the Oracle Files Store to be upgraded:
Host: database_host_name
Port: port_number
SID: service_name
-------------------
Specify the Oracle Files schema and password in the Oracle Files Store to be
upgraded:
Oracle Files Schema: IFSSYS
Oracle Files Schema Password: password
-------------------
If Oracle Workflow was integrated with Oracle Files in the source installation,
specify the Oracle Workflow schema and password. If Oracle Workflow was not
integrated with Oracle Files, leave both fields blank:
Oracle Workflow Schema: OWF_MGR
Oracle Workflow Schema Password: password
--------------------------------------------------------------
Upgrading "Oracle Portal"
Executing the script
Oracle_Collaboration_Suite_Release_1_ORACLE_HOME/assistants/opca/ptlasst.csh to
upgrade Oracle Portal
Script terminated with exit value 0
Upgrade finished with status: Success.
-------------------
Upgrading "Oracle Ultra Search"
Upgrading the metadata schema (this will take approximately 5 to 10 minutes)
The schema upgrade log file is XXXXX
Finished upgrading metadata schema
Getting JDBC connection
Loading Java stored packages (this will take approximately about 3 to 5 minutes)
Finished loading Java stored packages
Creating the file materialization table
Upgrading database files (this will take approximately about 15 to 30 seconds)
Processing XXXXX
Finished upgrading database files
Dropping the file materialization table
Upgrading mid-tier configuration files...
Processing XXXXX
Finished upgrading mid-tier configuration files
Upgrade finished with status: Success.
-------------------
Upgrading "Oracle9iAS Wireless"
Copying Oracle9iAS Wireless customization files.
Upgrading Oracle9iAS Wireless repository.
Upgrade finished with status: Success.
-------------------
Upgrading "Oracle Calendar Server"
Upgrading configuration files.
Upgrading database files.....
Upgrading Oracle Internet Directory entries...
Upgrading administration files.
Upgrade finished with status: Success.
--------------------
Upgrading "Oracle Calendar application system"
Upgrading configuration files
Upgrading Web Client files
Upgrade finished with status: Success.
-------------------
Upgrading "Oracle Email"
Upgrading Oracle Internet Directory entries...
Upgrading configuration files\205
Upgrading Oracle Webmail configuration files\205
Upgrading listener.ora...
Upgrading oc4j.properties...
Upgrade finished with status: Success.
-------------------
Upgrading "Oracle Email Store"
Upgrading database content. (this will take approximately 20 minutes)
Upgrade finished with status: Success.
-------------------
Upgrading "Oracle Voicemail & Fax"
Upgrading product tree in Oracle Internet Directory.
Upgrading process tree in Oracle Internet Directory.
Upgrade finished with status: Success.
-------------------
Upgrading "Oracle Files"
Upgrading the Oracle Files schema (this will take roughly approximately 15 to
20 minutes)
Upgrade finished with status: Success.
--------------------------------------------------------------
>>>>>>>>>>>>>>> The upgrade completed successfully <<<<<<<<<<<<<<<<<<
You must now complete the following post-upgrade tasks:
[Oracle Files] Run the following script manually to complete the Oracle Files
upgrade:
Oracle_Collaboration_Suite_Release_1_ORACLE_HOME/ifs/files/bin/ifsca
[Oracle9iAS Web Cache] The following files may need to be upgraded manually if
they were customized in the old Oracle home:
Oracle_Collaboration_Suite_Release_2_ORACLE_HOME/XXX
Oracle_Collaboration_Suite_Release_2_ORACLE_HOME/XXX
[Oracle Enterprise Manager] The Oracle_Collaboration_Suite_Release_2_ORACLE_
HOME/sysman/emd/targets.xml file may
contain duplicate target entries from both the old Oracle home and the new
Oracle home. If you want to remove the old targets, edit this file.
--------------------------------------------------------------
Log files containing details of the upgrade process can be found in the
following location:
Oracle_Collaboration_Suite_Release_2_ORACLE_HOME/upgrade/log
A transcript of this upgrade session can be found at:
Oracle_Collaboration_Suite_Release_2_ORACLE_HOME/log/ocsua.log
This section contains these topics:
Coexistence can be useful for a large organization that is upgrading its current installation of Oracle Calendar to Release 2 (9.0.4.1). The ability to have nodes and servers of different versions connected and running at the same time can help reduce the down time required to achieve the upgrade.
|
Note: Coexistence between Oracle Calendar server 5.5 and Oracle Calendar server 9.0.4 is viewed as a migration step towards having a uniform (same version) network of calendar servers. It is not recommended that a mix of the two versions be sustained for a long period of time or permanently. |
This section contains the following topics:
Oracle Calendar Server Parameters
Coexistence will only work after the following parameters are added to $ORACLE_HOME/ocal/misc/unison.ini on the 9.0.4 calendar server.
Section: [ENG]
Parameter: coexist_cwsbasicauth
Value: TRUE
Section: [ACE_PLUGINS_SERVER]
Parameter: cs-standard_coexistence
Value: TRUE
|
Important: As a security precaution, you must remove the preceding parameters from |
The following parameters will be reset to the default values listed here. If you used different values in your Oracle Calendar server 5.x installation, reset them to your desired values after completing the upgrade.
Parameter: resourcemailmap
Value: "O"
Parameter: usermailmap
Value: "O"
Parameter: usersmcprefmap
Value: "OU3"
Parameter: usermobiletypemap
Value: "N"
Parameter: usermobilemap
Value: "R"
Parameter: itemuidmap
Value: "P"
Coexistence Limitations
There are limitations in having two servers of different versions coexist.
Web services 9.0.4 will only work when all connected servers are upgraded to version 9.0.4
Event calendars are not supported in coexistence scenarios
Passwords longer than 15 characters are not supported by the 5.5 calendar server or pre-9.0.4 Oracle Calendar clients. Consequently, users with passwords longer than 15 characters will not be able to log in to older clients.
Do not use 9.0.4 utilities to administer a 5.x Oracle Calendar server. The only exception to this is when moving users; the moveuser utility must be from the latest server version (9.0.4), even if moving a user between two nodes that are both on old server nodes (5.x).
Do not use 5.x utilities to administer a 9.0.4 Oracle Calendar server.
If you need to create a node network, the nodes.ini and the use of uninode commands must be done on the most recent version (9.0.4) of the server within the network.
Coexistence may cause odd error messages on an old Oracle Calendar server (5.x). This is due to the fact that the old server may not understand the features introduced by the new server.
Mapping parameters have been added to the 9.0.4 server unison.ini for coexistence and upgrades. 5.x servers map O for EMAIL and P for UID. However, 9.0.4 servers do not need this mapping anymore. Parameters added to a 9.0.4 server do not affect it.
The new parameters include:
[ENG] usermailmap = O itemuidmap = P resourcemailmap = O usersmscprefmap = OU3 usermobiletypemap = N usermobilemap = R
Unidbfix -c may report "Minor inconsistencies" on an Oracle Calendar 9.0.4 server when events are created by an Oracle Calendar 9.0.4 user using Oracle Connector for Outlook 9.0.4 and accepted or declined by an Oracle Calendar 5.4 user using the Windows Native client 9.0.4. These inconsistencies do not impact the integrity of the database.
Users of previous versions of Oracle Calendar will not generate e-mail messages when using resource scheduling
Attachment names may change to Mime-Encoded-attachment.txt when using a mix of Oracle Calendar 9.0.4 and 5.4 users with Oracle Connector for Outlook. The attachments will still be readable.
Oracle Calendar desktop clients for Macintosh (V5.2.3) users may not be able to download offline files while connecting to a 9.0.4 standalone installation
The current versions of Oracle Calendar clients work with Oracle Calendar server 9.0.4, including:
Oracle Calendar desktop client for Windows 6.0.5
Oracle Calendar desktop client for Macintosh version 5.2.3
Oracle Calendar desktop client for Linux/Solaris version 5.0.2
Oracle Connector for Outlook version 3.3 and later
It is best to use these client versions; if you are using an older client, please upgrade before proceeding with testing. The latest versions of the clients are available at:
http://metalink.oracle.com
The Oracle Calendar portlet of Oracle Collaboration Suite Web Client Release 1 (9.0.3) is not compatible with Oracle Calendar Release 2 (9.0.4.1). To avoid this problem, upgrade both components to Release 2 (9.0.4.1), as described in "Installing the Oracle Collaboration Suite Middle Tier".
If you have already upgraded Oracle Calendar but not the Oracle Collaboration Suite Web Client, see "Upgrading the Oracle Collaboration Suite Web Client".
Oracle Calendar Application System Upgrades
The upgrade assistant only migrates the following keys. Unless otherwise mentioned, they are migrated to ocwc.conf. Your installation will still work, but you may need to make changes to your parameters to get the look and feel you want. For information on editing parameters, see the Oracle Calendar Reference Manual.
[system] connection [servers] (All keys migrated to "connection" section of ocas.conf. If the old installation was a masternode, 'mnode' will be the only entry.) [ACE_PLUGINS_CLIENT] (All keys into ocas.conf) [admin] sso_user_env_key [modules] hide_eventcal hide_global hide_taskview hide_managegroups hide_suggesttime hide_show_unconfirmed hide_updateall enable_designate hide_viewpub [file_attachment] download_enable upload_enable [taskview] quickCreateStartTime quickCreateEndTime showQCCompletion [calendar_view] default_view default_dayview_mode default_weekview_mode hide_dayview_toggle hide_weekview_toggle pdv_notes_top_task_bottom default_color_mgt_by [cookies] domain [sched] showicalvcal (becomes same key in "modules" section in ocwc.conf).
The Oracle Email information storage database is upgraded when you run the Oracle Collaboration Suite upgrade assistant, as explained in "Running the Oracle Collaboration Suite Upgrade Assistant".
Additionally, perform the following steps to install required files and libraries on the Release 2 (9.0.4.1) information storage database:
Copy the umbackend.tar file from the $ORACLE_HOME/oes directory on the application server to the $ORACLE_HOME DIRECTORY on the information storage database.
Untar umbackend.tar file:
tar xvf umbackend.tar
Run the following commands to start the Oracle Universal Installer:
cd backend/Disk1
./runInstaller
Follow the screen prompts to complete the Oracle Email back-end installation.
Perform the following after the Oracle Collaboration Suite upgrade assistant finishes:
Restart the Oracle Files configuration assistant by executing ifsca from the following location:
$ORACLE_HOME/ifs/files/bin
On the Domain Operation screen, select Set up this computer to use an existing Oracle Files domain.
On the Schema Name screen, select the upgraded Oracle Files schema.
Click Next and follow the remaining Oracle Files configuration assistant screens.
|
See Also: "Setting Up a Computer to Use an Existing Domain" for more information about these screens |
On the Summary screen, click Configure.
A progress window appears. If an error occurs, check the following log file for more information:
$ORACLE_HOME/ifs/files/log/FilesConfig.log
When the process is complete, a message informs you that the configuration was successful. Click OK to close the message. Oracle Files and the Oracle Enterprise Manager Web Site are integrated automatically.
|
Note: You must run theifsca script on all middle tiers. |
If the Oracle Files schema that you are upgrading has been integrated with Oracle Workflow, follow the post-configuration instructions in the following sections:
|
Note: You do not have to follow the steps in "Configuring Net Service Names" unless you want to change the existing Oracle Workflow configuration parameters. |
The following sections describe the recovery steps for common errors:
Error upgrading middle tier configuration files
Check that the data-sources.xml configuration file is available in the following Oracle Collaboration Suite Release 1 (9.0.3) directory:
$ORACLE_HOME/j2ee/OC4J_Portal/config
Re-run the Oracle Ultra Search upgrade plug-in after you confirm the availability of the data-sources.xml file.
Failed to upgrade database file: <file_name>
Confirm that you have write permission to the $ORACLE_HOME/ultrasearch directory in the database file system. Then re-run the Oracle Ultra Search upgrade plug-in.
Error upgrading metadata schema
See the schema upgrade log file for error details. Fix the problem, and then re-run the Oracle Ultra Search upgrade plug-in.
Error loading Java stored packages and upgrading database files
Check that the file $ORACLE_HOME/ultrasearch/lib/ultrasearch_db.jar is in place. Then re-run the Oracle Ultra Search upgrade plug-in.
Oracle9iAS ships with Oracle9iAS Web Agent Packages (OWA packages) version 9.0.4.0.0. The PL/SQL applications accessed through OHS mod_plsql use the OWA packages, and must be manually upgraded.
You must complete this post-upgrade procedure if one of the following conditions is true:
You have Oracle9iAS Portal that uses an Oracle database
You have Oracle9iASInfrastructure that uses an Oracle database
You have an Oracle database that has custom PL/SQL procedures accessed through OHS mod_plsql
If one of the preceding conditions is true, then complete the following procedure:
Navigate to the directory where the owaload.sql file is located:
$ORACLE_HOME/Apache/modplsql/owa
Use SQL*Plus to log on to the Oracle database as the SYS user.
Enter the following command at the SQL prompt:
SQL> @owaload.sql log_file
where log_file is any temporary filename that will contain the output from the command to load OWA packages.
Scan the log file for any errors.
Manually recompile any invalidated packages; typically by running the $OH/rdbms/admin/utlrp.sql script as the SYS user.
Installing the OWA packages invalidates all dependent objects. These packages automatically recompile on first access, but Oracle recommends that you complete the manual recompile after the re-installation.
|
Note: You can check the existing version of the OWA packages by running the following query:select owa_util.get_version from dual |
The owaload.sql script checks the existing version of the OWA packages in the database. If one of the following conditions is true, then the script installs a new OWA package version:
No OWA packages exists
Older OWA packages are detected
If one of the preceding conditions does not exist, then your database already has the latest OWA packages or a later version installed; in which case the script does nothing.
The outcome of the owaload.sql script check is reported in the log file.
Upgrading Oracle Voicemail & Fax is not done through the Oracle Collaboration Suite upgrade assistant.
To upgrade Oracle Voicemail & Fax:
Install Oracle Voicemail & Fax Release 2 (9.0.4.1) on the Windows 2000 telephony server.
|
Note: If you installed CT Media 2.1 or 2.1.1 for Oracle Voicemail & Fax Release 1 (9.0.3), you must download the latest version of Timed withNTLMAuthentication.dll into the Program Files\Dialogic\CT Media\Client directory before you install Oracle Voicemail & Fax. |
Execute the following command to upgrade Oracle Voicemail & Fax:
%ORACLE_HOME%\um\scripts\UpgradeTelephonyServerfromV1.bat host_name 903_ORACLE_HOME 9041_ORACLE_HOME
Upgrading Oracle9iAS Wireless involves two tasks. First, runtime customization classes and configuration files must be copied into the new $ORACLE_HOME. Second, existing processes and their configurations must be moved to the new middle tier.
To upgrade Oracle9iAS Wireless:
Stop all Oracle9iAS Wireless Release 1 (9.0.3) middle tiers in the farms, including any Oracle9iAS middle tiers that are configured to run Oracle9iAS Wireless.
Select the first Oracle9iAS Wireless Release 1 (9.0.3) middle tier for upgrade.
Install the first Oracle9iAS Wireless Release 2 (9.0.4.1) middle tier on the same computer as the Oracle9iAS Wireless middle tier identified in step 2. During installation, the Oracle9iAS Wireless configuration assistant upgrades the Oracle9iAS Wireless schema in the Oracle9iAS Metadata Repository (see "Oracle9iAS Wireless Upgrade Items").
The Oracle Collaboration Suite upgrade assistant:
Copies runtime customization classes (such as listener hooks and customized folder renderers) as well as suite-level configuration files from $ORACLE_HOME_1 to $ORACLE_HOME_2 (See "Oracle9iAS Wireless Upgrade Items").
Copies the process configuration information for the Oracle9iAS Wireless standalone processes from the Oracle9iAS Wireless Release 1 (9.0.3) middle tier to the Oracle9iAS Wireless Release 2 (9.0.4.1) middle tier, and configures the Release 2 (9.0.4.1) middle tier accordingly.
At this time, all Oracle9iAS Wireless Release 2 (9.0.4.1) middle tiers can be restarted to reduce downtime.
The configuration information for the Oracle9iAS Wireless standalone processes is stored in the Oracle9iAS Wireless schema in the Oracle9iAS Metadata Repository. During upgrade from Release 1 (9.0.3) to Release 2 (9.0.4.1), the Oracle Collaboration Suite upgrade assistant copies the process configuration information from the Release 1 (9.0.3) middle tier to the Release 2 (9.0.4.1) middle tier by creating additional entries in the Oracle9iAS Wireless schema.
In the Oracle9iAS Wireless schema upgrade during the first middle tier installation, the Oracle9iAS Wireless configuration assistant pre-populates default standalone processes for each process type. When the Oracle9iAS Wireless upgrade assistant copies Release 1 (9.0.3) process information to a Release 2 (9.0.4.1) middle tier, it deletes the redundant process (if one is found in the Release 1 (9.0.3) middle tier). In addition, the Oracle9iAS Wireless upgrade assistant ensures that each process has a unique process name.
Oracle9iAS Wireless Upgrade Items
The following files are changed in the first phase of the Oracle9iAS Wireless upgrade process:
ORACLE_HOME_2/wireless/server/classes/*.class
ORACLE_HOME_2/wireless/server/classes/*.properties
ORACLE_HOME_2/wireless/server/classes/marconi.config
The Web client can be selected to be installed and configured using the Oracle Universal Installer during installation of the Oracle Collaboration Suite middle tier.
However, the Web client configuration assistant does not function properly in an upgrade scenario. This section describes how to invoke the Web client configuration assistant from the command line.
Before invoking the Web client configuration assistant, manually ensure that the Oracle9iAS Portal middle tier has been installed or upgraded, and configured.
This section contains the following topics:
Skip Configuring the Component URL if the host name and port number for the applications were provided during the Web client installation through Oracle Universal Installer.
webclient.properties FileWhen you upgrade from Oracle Collaboration Suite Release 1 (9.0.3) to Oracle Collaboration Suite Release 2 (9.0.4.1), you install the new Oracle Collaboration Suite middle tier in a new Oracle home. The new installation temporarily changes the port number specifications for various applications in certain files, such as the httpd.conf file, and the Web client configuration assistant then resets the specifications back to their original values.
However, the Web client configuration assistant does not reset the port number values in the webclient.properties file for the following components:
Oracle Calendar
Oracle Email
Oracle Files
Oracle Web Conferencing
Oracle9iAS Wireless and Voice
You must therefore manually reset the port numbers in the webclient.properties file, located in the located in the version_2_ORACLE_HOME/webclient/classes/oracle/collabsuite/webclient/resources directory, by entering the correct port numbers in the URL associated with each of the following entry points:
mail.help.urlfiles.help.urlcalendar.help.urlimeeting.help.urlsearch.help.urlwireless.help.urlmailcalendarfilessearchwirelessportalimeetingmail.providerfiles.providersearch.providerwireless.providerwebclient.providerimeeting.providercalendar.provider
This section explains how to configure a component URL, such as Oracle Email, Oracle Files, and Oracle Calendar. You configure the component URL by modifying the webclient.properties file.
The webclient.properties file contains three URL for each Oracle Collaboration Suite component:
Help page URL
Application entry point
Portlet provider URL
Open the webclient.properties file located in the $ORACLE_HOME/webclient/classes/oracle /collabsuite/webclient/resources directory.
In the webclient.properties file, set the entry point URL for each configured component.
Replace the token for the host name and the port number in all three URL for each component to be configured.
If you are not upgrading Oracle Calendar to Release 2 (9.0.4.1), perform the following steps to make Oracle Calendar Release 1 (9.0.3) available as a portlet:
Open the webclient.properties file from the $ORACLE_HOME/webclient/classes/oracle/collabsuite/webclient/resources directory on the Oracle Collaboration Suite Release 2 (9.0.4.1) middle tier.
Locate the following statement:
calendar=http://%CALENDAR_HOST%:%CALENDAR_PORT%/ocas-bin/ocas.fcgi?sub=web
Change it to:
calendar=http://%CALENDAR_HOST%:%CALENDAR_PORT%/fcgi-bin/owc/lexacal.fcgi?go=login
Locate the following statement:
calendar.provider=http://%WEBCLIENT_HOST%:%WEBCLIENT_PORT%/webclient-calendar/servlet/soaprouter
Change it to:
calendar.provider= http://%WIRELESS_HOST%:%WIRELESS_PORT%/marconi/servlet/soaprouter
Enter the following command:
$ORACLE_HOME/webclient/bin/webclient_installer.sh Oradcle9iAS_Portal_user_name Oradcle9iAS_Portal_user_password -complete
If you know the Oracle9iAS Portal schema name, password, and connect string information, you can invoke the configuration assistant, as follows:
$ORACLE_HOME/webclient/bin/webclient_installer.sh Oracle9iAS_Portal_user_name Oracle9iAS_Portal_user_password -complete -s schema -p password -c connect_string
Where:
schema: The Oracle database account for Oracle9iAS Portal
password: The Oracle9iAS Portal account password
connect_string: The connect string to the database instance where the Oracle9iAS Portal repository is installed; specified as host_name:port:SID
After you successfully upgrade to Oracle Collaboration Suite Release 2 (9.0.4.1), you can delete any instances of Release 1 (9.0.3).
Perform the following steps prior to deleting Release 1 (9.0.3) targets from the targets.xml file:
Make a copy of the targets.xml file before making any changes.
Ensure that the targets.xml file contains the following header:
<Targets> <Target TYPE="host" NAME="hostname.acme.com" VERSION="1.0"> </Targets>
Remove all Release 1 (9.0.3) targets from the targets.xml file located in the $ORACLE_HOME/sysman/emd directory in the active Enterprise Manager Daemon.
Execute the following command from the Oracle Collaboration Suite Release 2 (9.0.4.1) $ORACLE_HOME:
cd $ORACLE_HOME/dcm/bin dcmctl destroyInstance -i Release_1_instance_name
|
Note: Use the following command to list all instances by name to help identify the instances to be removed:dcmctl listInstances |
This section provides a high level outline on how to upgrade from an Oracle Calendar standalone installation with iPlanet Directory Server, to Oracle Collaboration Suite which uses Oracle Internet Directory. There are two possible upgrade scenarios.
Upgrading with Coexistence—Use this procedure if Oracle Calendar is not the only application that uses iPlanet Directory Server. In this case you keep iPlanet Directory Server and synchronize the data in both directories.
Upgrading Without Coexistence—Use this procedure if Oracle Calendar is the only application that uses iPlanet Directory Server. In this case you do not keep the iPlanet Directory Server.
This scenario assumes that you need to keep and manage iPlanet Directory Server along with the Oracle Internet Directory server. The Oracle Directory Integration Platform (DIP), a feature of Oracle Internet Directory, is used to keep the user data in both directories synchronized. A detailed procedure is available on OracleMetaLink
The Document ID is 268947.1.
Some General Notes and Assumptions
Before you begin this procedure take note of the following assumptions and limitations regarding this procedure.
You currently have Oracle Calendar standalone release 2 (9.0.4.2) and iPlanet Directory Server version 5.x installed and running.
The synchronization will be one-way only (from iPlanet Directory Server to Oracle Internet Directory).
Once the migration is completed, you can only add new users through iPlanet Directory Server.
Step 1 Install Oracle Collaboration Suite
Install Oracle Collaboration Suite release 2(9.0.4.2) and ensure that it is running.
Step 2 Migrate the Directory Entries from iPlanet Directory Server to Oracle Internet Directory
The directory entries must be exported from iPlanet Directory Server to an LDAP Data Interchange Format (LDIF) file, modified, then imported to Oracle Internet Directory. The modifications include removing proprietary data and operational attributes, and adding Oracle Internet Directory object classes.
Also, if you have made any modifications to the base schema of iPlanet Directory Server, you may also need to make the same modifications to Oracle Internet Directory. This depends on whether the attributes added to the base schema are also being imported into Oracle Internet Directory.
Step 3 Configure the Synchronization Service Between Oracle Internet Directory and iPlanet Directory Server
The Oracle Directory Integration Platform (DIP) provides the synchronization service between Oracle Internet Directory and iPlanet Directory Server. The synchronization is done through a user account and configuring the synchronization service involves, among other things, setting the mapping rules and creating an integration profile.
Step 4 Migrate the Calendar Database
Migrating the calendar database involves moving calendar nodes from the Oracle Calendar standalone installation to the Oracle Collaboration Suite installation then reconfiguring the node network to recognize this change.
This scenario assumes that once the upgrade is complete the user accounts will be managed through Oracle Internet Directory. A detailed procedure is available on Oracle Metalink
The Document ID is 268948.1.
|
Note: This procedure assumes that you have already upgraded the current Oracle Calendar standalone installation to Oracle Calendar standalone release 2 (9.0.4.2). |
Step 1 Install Oracle Collaboration Suite
When you install Oracle Collaboration Suite, use the same node network configuration (nodes and node IDs) as your current Oracle Calendar standalone installation.
Step 2 Migrate the Directory Entries from iPlanet Directory Server to Oracle Internet Directory
The directory entries must be exported from iPlanet Directory Server to an LDIF file, modified, then imported to Oracle Internet Directory. The modifications include removing proprietary data and operational attributes, and adding Oracle Internet Directory object classes.
Also, if you have made any modifications to the base schema of iPlanet Directory Server, you may also need to make the same modifications to Oracle Internet Directory. This depends on whether the attributes added to the base schema are also being imported into Oracle Internet Directory.
Step 3 Migrate the Calendar Database
Migrating the calendar database involves moving calendar nodes from the Oracle Calendar standalone installation to the Oracle Collaboration Suite installation then reconfiguring the node network to recognize this change.
This section outlines how to upgrade from Oracle Calendar standalone internal to Oracle Collaboration Suite. A detailed procedure is available on Oracle Metalink
The Document ID is 268949.1.
Step 1 Install Oracle Collaboration Suite
When you install Oracle Collaboration Suite, use the same node network configuration (nodes and node IDs) as your current Oracle Calendar standalone installation.
Step 2 Migrate the User and Resource Entries to Oracle Internet Directory
The user and resource entries must be exported to an LDAP Data Interchange Format (LDIF) file, modified, then imported to Oracle Internet Directory. The modifications include adding Oracle Internet Directory object classes to the entries.
Step 3 Reconfigure the .ini Files
Update the .ini files on the Oracle Collaboration Suite installation so that they match the settings in the Oracle Calendar standalone installation.
Step 4 Migrate the Calendar Database
Migrating the calendar database involves moving calendar nodes from the Oracle Calendar standalone installation to the Oracle Collaboration Suite installation then reconfiguring the node network to recognize this change.
Perform the following if you are installing the Oracle Collaboration Suite, Release 2 middle tier against a non Oracle Collaboration Suite infrastructure, such as Oracle 9iAS infrastructure 9.0.2.0.1, or Oracle9iAS infrastructure 9.0.2.0.0 upgraded to Oracle9iAS infrastructure 9.0.2.3.0.
Upgrade Oracle9iAS infrastructure 9.0.2.0.1 or Oracle9iAS infrastructure 9.0.2.0.0 to Oracle9iAS infrastructure 9.0.2.3.0.
Apply the Oracle9iAS infrastructure 9.0.2.3 patch 3038037 to the infrastructure.
|
Note: The patch 3038037 README contains instructions for applying the Oracle9i 9.0.1.4 database server patch 2517300. You must apply patch 2517300 before patch 3038037. Both of these patches are available at:http://metalink.oracle.com |
Copy the files listed in the following table from the CDROM_ROOT/tools /upgrade directory on the Oracle9iAS infrastructure installation CD-ROM for Release 2 (9.0.4.1) to the specified target directory in the infrastructure Oracle home directory that you are upgrading:
Table 3-5 Upgrade Files and Target Directories
| File | Target Directory |
|---|---|
modDirectiveMS.xsd |
%ORACLE_HOME%\dcm\config\plugins\apache |
opca.jar |
%ORACLE_HOME%\sysman\webapps\emd\WEB-INF\lib |
portalSMI.jar |
%ORACLE_HOME%\sysman\webapps\emd\WEB-INF\lib |
repository.jar |
%ORACLE_HOME%\jlib |
ApacheModuleFastCGI.dll |
%ORACLE_HOME%\Apache\Apache\modules |
ApacheModuleOSSO.dll |
%ORACLE_HOME%\Apache\Apache\modules |
FastCGI.dll |
%ORACLE_HOME%\Apache\fastcgi |
FastCGI.lib |
%ORACLE_HOME%\Apache\fastcgi |
fcgi.jar |
%ORACLE_HOME%\Apache\fastcgi |
Create an orclguest user using Oracle Delegated Administration Services.
|
Note: You must have sufficient privilege to create new users in the default subscriber. |
Log in to Oracle Delegated Administration Services as a user with privilege to create users.
Select the Directory tab.
In the Search Results section, click Create.
Depending on the configuration, the Create User page prompts for different values. The User Name value in this case should be orclguest. The rest of the values should be filled in, accordingly. Ensure that all of the required fields are filled in.
Click Submit.
|
Note: Ensure that there is no middle tier installed against this infrastructure. |
Install the Oracle Collaboration Suite information storage database.
|
Note: While registering the information storage database, point to the Oracle Internet Directory of the infrastructure upgraded to 9.0.2.3 in Step 1. |
Install the Oracle Collaboration Suite, Release 2 middle tier.
When installing the Oracle Collaboration Suite Release 2 middle tier against the upgraded Oracle9iAS infrastructure, the Oracle9iAS Wireless configuration assistant will fail during the configuration phase.
Perform the following steps to avoid this failure:
Complete the installation without configuring Oracle9iAS Wireless
Download patch 3133419 and run the Oracle9iAS Wireless configuration assistant tool as instructed in the patch.
Apply the Oracle9iAS Portal patch 2758529 on the middle tier machine. The patch can be downloaded from: http://metalink.oracle.com/
Recompile all of the invalid objects.
Re-run the Web Client installer from the command line:
$ORACLE_HOME/webclient/bin/webclient_installer.sh OID_Administrator password -complete
Complete the Oracle Collaboration Suite, Release 2 middle tier configuration steps.
