| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for AIX-Based Systems Part Number B12204-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for AIX-Based Systems Part Number B12204-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).
This chapter contains these topics:
Upgrading CorporateTime Server 5.4 to Oracle Collaboration Suite
Upgrading from Oracle Calendar Standalone External to Oracle Collaboration Suite
Upgrading from Oracle Calendar Standalone Internal to Oracle Collaboration Suite
CorporateTime Server 5.4, internal or external, can be upgraded to Oracle Collaboration Suite Release 2 (9.0.4.1). While this is a supported upgrade path, the process involves manual steps.
To upgrade CorporateTime Server 5.4 to Oracle Collaboration Suite:
Upgrade CorporateTime Server 5.4 to Release 2 (9.0.4.1) of Oracle Calendar, standalone, as described in "Server Upgrade".
Install the Oracle Collaboration Suite infrastructure and middle tier as described in Chapter 6, "Installing Oracle Collaboration Suite".
Migrate the user information to the Oracle Internet Directory component of your new Oracle Collaboration Suite infrastructure.
Import your CorporateTime Calendar attributes, including the ctCalXitem ID, into the Oracle Internet Directory component of your new Oracle Collaboration Suite infrastructure.
Copy the Oracle Calendar database files, upgraded in step 1, over to the Oracle Calendar component of your new Oracle Collaboration Suite installation.
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 Oracle Metalink
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-1 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.
