| Oracle Collaboration Suite Release Notes Release 2 (9.0.4) for hp-ux PA-RISC (64-bit) and Linux x86 Part Number B12029-02 |
|
|
View PDF |
| Oracle Collaboration Suite Release Notes Release 2 (9.0.4) for hp-ux PA-RISC (64-bit) and Linux x86 Part Number B12029-02 |
|
|
View PDF |
This chapter summarizes release note issues not specific to any one feature of Oracle Collaboration Suite.
The following sections are included in the chapter:
Run the Oracle Collaboration Suite Upgrade Assistant from the $ORACLE_HOME/upgrade directory after the installation. $ORACLE_HOME refers to the main installation directory where Oracle Collaboration Suite is installed. The following steps should be completed before running Oracle Collaboration Suite Upgrade Assistant:
/tools/upgrade/dms904.jar file from the Oracle Collaboration Suite Disk1 to the $ORACLE_HOME/upgrade/lib directory.$ORACLE_HOME/upgradeocsua.sh file.
$ cd $ORACLE_HOME/upgrade $ cp ocsua.sh ocsua.sh.bak
/tools/upgrade/ocsua.sh file from the Oracle Collaboration Suite Disk1 to the $ORACLE_HOME/upgrade directory.$ORACLE_HOME/upgrade/ocsua.sh file with the new file in the installation CD.$ORACLE_HOME/upgrade/ocsua.sh file is set to executable:
$ chmod +x $ORACLE_HOME/upgrade/ocsua.sh
$ORACLE_HOME/upgrade/ocsua.sh script to set the ORACLE_HOME and OUI_HOME environment variables.$ORACLE_HOME/upgrade/ocsua.sh.bak file:
ORACLE_HOME=/home/user/ocs
$ORACLE_HOME/oui.$ORACLE_HOME/upgrade/ocsua.sh.bak file:
OUI_HOME=/home/user/ocs/oui
$ORACLE_HOME/upgradeocsua.sh script.
The following section provides information on pre-installation tasks.
If you are installing on HP-UX, you must manually create some symbolic links before performing the installation. This is because of a HP-UX problem, Doc. ID. KBRC00003627.
To create the required links:
root user./usr/lib.# ln -s /usr/lib/libX11.3 libX11.sl # ln -s /usr/lib/libXIE.2 libXIE.sl # ln -s /usr/lib/libXext.3 libXext.sl # ln -s /usr/lib/libXhp11.3 libXhp11.sl # ln -s /usr/lib/libXi.3 libXi.sl # ln -s /usr/lib/libXm.4 libXm.sl # ln -s /usr/lib/libXp.2 libXp.sl # ln -s /usr/lib/libXt.3 libXt.sl # ln -s /usr/lib/libXtst.2 libXtst.sl
Oracle Collaboration Suite Upgrade Assistant is a command line tool that automates upgrading of OCS V1 to OCS V2. OCS Upgrade Assistant related files are located under $ORACLE_HOME/upgrade directory. Following is the directory structure for the upgrade assistant home:
$ORACLE_HOME/upgrade $ORACLE_HOME/upgrade/log $ORACLE_HOME/upgrade/lib
The home directory, $ORACLE_HOME/upgrade, contains mainly three files: ocsua.sh, ocsua.xml, and ocsua.properties. Details of content for these files are described in the sections that follow. The log directory contains log files produced during the upgrade process. The lib directory contains jar files for the framework.
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 to read the plug-ins that perform the individual component upgrades. Do not modify this file.
This file contains properties which may be set by users. All properties have default values. If a property does not exist, the default value set in the Java classes will be used. This file is optional. It does not have to exist for the Upgrade Assistant to run. Following is the content of this file:
# # 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
This is the file that user should execute to start the upgrade process. Following is the usage of this file:
bash-2.05$ ocsua.sh -help ocsua -sourcehome < sourcehome > [-config inputXML] [-all] Upgrade configuration files to a OCSv2 Oracle home: -sourcehome <Source OCSv1 Oracle home path> -config <Input XML file that lists all the plugins> [-all] <Run all the component plugins without prompt>
Upgrade assistant will let the user choose the components that have to be upgraded. First time the upgrade assistant is invoked to upgrade some or all OCS components, management plug-ins that are hidden from the user are automatically invoked. Management plug-ins take care of upgrading iAS components that the OCS components depend on including Portal, Apache, Enterprise Manager and Web Cache. During this process, if upgrading from an OCS V1 source home that is also active EMD home, active EMD home will be reset to be the new OCS V2 home. Upgrading from OCS V1 home that is not an active EMD will not cause the active EMD to be changed.
The following steps describe the overall flow of upgrade assistant:
The code sample that follows shows how the script is executed.
bash-2.05$ ocsua.sh -sourcehome /home/ias903 Validating Oracle homes ------------------- These are the components that can be upgraded 1. Oracle Ultra Search 2. Oracle Wireless & Voice 3. Oracle Calendar Server 4. Oracle Calendar application system 5. Oracle Email 6. Oracle Email Store 7. Oracle Voicemail & Fax 8. Oracle Files Enter component numbers and/or ranges(example:1-3,5)[all]: -------------------------------------------------------------- Validating component plug-ins ------------------- Examining "Oracle Ultra Search" Upgrade items found: /home/eujang/ias903/j2ee/OC4J_Portal/config/data-sources.xml ------------------- Examining "Oracle Wireless & Voice" Upgrade items found: /home/eujang/ias903/wireless/server/classes/oracle/panama/marconi/marconi.config Oracle 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:TNSConnect SYS Password: WKSYS Password: ------------------- Specify connection information (host:port:serviceName) and associated passwords for the Oracle Email Store to be upgraded: Oracle Email Store Connect:Email SYS Password: ESMail Password: CTXSYS Password: ------------------- Specify connection information for the Oracle Files Store to be upgraded: Host:Host Port:1234 SID:SID ------------------- Specify the Oracle Files schema and password in the Oracle Files Store to be upgraded: Oracle Files Schema:Files Oracle Files Schema 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: Oracle Workflow Schema Password: -------------------------------------------------------------- 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 "Oracle Wireless & Voice" Copying Oracle Wireless customization files. Upgrading 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: /home/eujang/ias903/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: /home/eujang/ias904/XXX /home/eujang/ias904/XXX [Oracle Enterprise Manager] The /home/eujang/ias904/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: /home/eujang/ias904/upgrade/log A transcript of this upgrade session can be found at: /home/eujang/ias904/upgrade/log/ocsua.log
After upgrading from Oracle Collaboration Suite, Release 1 to Oracle Collaboration Suite, Release 2, you must manually re-register the Oracle HTTP server with Single Sign-On server.
The single sign-on registration tool updates the mod_osso registration record in the osso.conf file to reflect SSL settings on the single sign-on server. The single sign-on registration tool generates this file whenever it is run.
To run the tool, execute the following command:
$ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar -oracle_home_path orclHomePath -host database_host_name -port database_port_number -sid database_SID -site_name sitename -success_url successurl -logout_url logouturl -cancel_url cancelurl -home_url homeurl [-admin_id adminid] [-admin_info admininfo] -config_mod_osso TRUE -u userid -sso_server_version v1.2
Where:
| See Also:
Chapter 7, "Component Configuration Dependencies," in the Oracle9i Application Server Administrator's Guide, for more information about when to run the single sign-on registration tool. |
The following sections describe issues affecting Oracle Collaboration Suite Web Client.
The following error is thrown when the Date portlet on Oracle Collaboration Suite home page is accessed:
Portlets not displayed, based on the severity
The portlet does show any error on the web page, but displays the default time zone instead of the user preferred time zone. The SecurityException error is logged in the opmn logs.
Workaround: Edit the jazn-data.xml file in the $ORACLE_HOME/config folder, and add the following XML text after the line containing the <jazn-policy> tag:
<grant> <grantee> <codesource> <url>file:ORACLE_HOME/webclient/lib/webclient_common.jar</url> </codesource> </grantee> <permissions> <permission> <class>oracle.ias.repository.schemaimpl.CheckRepositoryPermission</class> <name>connectAs</name> </permission> </permissions> </grant>
Portlets might not display properly in Oracle Collaboration Suite 9.0.4. To correct the problem, you need to delete the cached JSPs, increase the provider timeout, and restart opmn on the middle tier.
Correct the problem as follows:
opmn by running the following command:
$ORACLE_HOME/opmn/bin/opmnctl stopall
$ORACLE_HOME/j2ee/OC4J_Portal/application-deployments
_default.properties files in the folders specified in the list below:
executionKillTimeout=120 executionWarningTimeout=120
The _default.properties files are in the following directories:
$ORACLE_HOME/j2ee/OC4J_Portal/applications/webclient-common/webclient-common-web/WEB-INF/deployment/$ORACLE_HOME/j2ee/OC4J_Portal/applications/webclient-calendar/webclient-calendar-web/WEB-INF/deployment/$ORACLE_HOME/j2ee/OC4J_Portal/applications/webclient-imeeting/webclient-imeeting-web/WEB-INF/deployment/$ORACLE_HOME/j2ee/OC4J_Portal/applications/marconi/marconi-web/WEB-INF/deployment/$ORACLE_HOME/dcm/bin/dcmctl updateConfig
opmn:
$ORACLE_HOME/opmn/bin/opmnctl startall
Oracle has assigned bug number 3011905 to track this problem.
After installing the Oracle Files middle-tier, the Files domain is not started by default. Consequently, the Web Client configuration assistant is unable to contact the Files portlet during Web Client configuration, and the automatic registration of the Files portlet will fail.
There are two workarounds to this problem:
$ORACLE_HOME/webclient/classes/oracle/collabsuite/webclient/resources/webclient.properties file, and re-run the Web Client configuration assistant from the command line:
$ORACLE_HOME/webclient/bin/webclient_installer.sh
The Web Client uses Oracle UIX (User Interface XML) technology to generate Web pages. UIX dynamically generates many images (such as buttons and tabs) appearing throughout the UI. Due to limitations in Java 2 Standard Edition (J2SE) prior to version 1.4, UIX requires an X-Windows X server process to generate dynamic images on UNIX platforms.
To locate the X-Windows X server, the UIX runtime relies on the value of the DISPLAY environment variable. If the Web Client is running on a UNIX host, and some of the images in the UI appear broken or inconsistent, the problem may be that the value of the DISPLAY environment variable for the Web Client process is set incorrectly. (A common symptom of this problem is that instead of the rounded, beige, Oracle-style buttons, UI pages are rendered using native browser buttons.)To verify the value of the DISPLAY environment variable for the Web Client process, open the $ORACLE_HOME/opmn/conf/opmn.conf file in a text editor, and locate the entry for the instance called \OC4J_Portal\:
<oc4j maxRetry="3" instanceName="OC4J_Portal" gid="OC4J_Portal" numProcs="1"> <environment> <prop name="DISPLAY" value="your-host-name:0.0"/> </environment> </oc4j>
The value of the DISPLAY property should point to a running X-Windows X server.
In the Collaboration Suite welcome page (at http://<host>:<port>/), the link in the End-User Login portlet will only function on the host where Oracle Portal is configured; on other middle-tier hosts, the link will be broken.
You must edit the webclient.properties file because the Webmail online help file name has changed.
Edit the webclient.properties file, located in the
$ORACLE_HOME/webclient/classes/oracle/collabsuite/webclient/resources directory, by replacing:
mail.help.url = http://%MAIL_HOST%:%MAIL_PORT%/um/help/_MAIL_LOCALE_TOKEN_/ \ What_is_the_WebMail_Client_.htm
with:
mail.help.url = http://%MAIL_HOST%:%MAIL_PORT%/um/help/_MAIL_LOCALE_TOKEN_/ \ The_All_Messages_Subtab.htm
For every system and Oracle home directory where you have configured Oracle Email, every message store, and every system running Oracle Collaboration Suite Infrastructure, you must run the mandatory security patch script, mailsecuritypatch.sh. This script is in the "patches" directory of the Oracle Collaboration Suite Release 2 (9.0.4.0.0) CD 1. Ensure that your Oracle home directory is set before running the script. Instructions on how to apply the mailsecuritypatch.sh are available in the README.txt file in the same directory as the script.
While running the ocsua.sh script with the Oracle Email Store upgrade option, it prompts for the connect information to be entered in the form of host:port:serviceName. However, the script interprets the serviceName as the SID, which results in an upgrade failure.
Workaround: Enter the SID.
The Oracle Email upgrade plug-in does not work on the middle tier if the Oracle Collaboration Suite, release 1 and release 2 Oracle home directories are installed on the same host.
Workaround: Run the following scripts before invoking the ocsua.sh script:
$ORACLE_HOME/oes/bin/renameorahomeforumprocs.sh middletier_host v1_oraclehome v2_oraclehome$ORACLE_HOME/oes/bin/UpgradeUMOIDDataToV2.sh middletier_hostWhen using the Oracle Collaboration Suite, release 2 Upgrade Assistant to upgrade the Ultra Search component from Oracle Collaboration Suite release 1, the Ultra Search upgrade plug-in fails when establishing the database connection, and the upgrade does not proceed.
Perform the following steps to upgrade Ultra Search component from Oracle Collaboration Suite release 1 to Oracle Collaboration Suite release 2:
$ORACLE_HOME/ultrasearch/setup/ directory to the database-tier $ORACLE_HOME directory:
setupDB.sh file in the database tier $ORACLE_HOME directory.%oraclesid% with the database SID. Replace %port% with the database port number.setupDB.sh, located in the database tier $ORACLE_HOME directory. The system sets the current directory as $ORACLE_HOME and prompts for the database host name. If the default path to the jar executable or Java executable is not correct, then the system asks for the path to JDK. If you do not have JDK installed, then download the latest JDK, and run setupDB.sh again.$ORACLE_HOME/ultrasearch/admin directory, and log in to the database as SYSDBA. Then run the following:
SQL> @wkpatch.sql
data-sources.xml file from the Oracle Collaboration Suite, Release 1 middle tier $ORACLE_HOME/j2ee/OC4J_Portal/config directory to the Oracle Collaboration Suite, release 2 middle tier$ORACLE_HOME/j2ee/OC4J_Portal/config directory.The current release does not permit a photo of a single sign-on user to be uploaded. Oracle assigned bug number 2429849 to track this.
Step 4 in the Upgrading Infrastructure documentation instructs users to run the ocsGroup.sh script. However, because this script generates 2 log files that are stored in the directory from which the script is run, the directory must have write privileges or the script will fail.
Ensure that you copy the ocsGroup.sh and ocsGroup.dmp files into a directory with write permissions before you run the ocsGroup.sh script.
If the Create or Edit button of Resource Access Information in the Delegated Administration Service is clicked, previously filled columns are cleared. To correct this problem, enter user columns after setting user resource information. Oracle assigned bug number 2487223 to track this.
HTTPS must be set up with mod_osso on the middle tier. This section describes how to set up HTTPS with mod_osso on a default Oracle Collaboration Suite mid tier. This is necessary for using Oracle Calendar Administrator with HTTPS, but also works for any other SSO-protected application requiring HTTPS on the mid tier.
For the following sections, these conventions apply:
SSO_HOST is the host name of the Single Sign On ServerMIDTIER_HOST is the middle tier's host name or IP addressMIDTIER_HTTPS_PORT is the middle tier's HTTPS port, usually 4443
To verify the setup:
http port:
http://SSO_HOST:7777/pls/orasso
If your system does not meet both of these requirements, refer to your SSO and OHS documentation to correct the configuration.
$ dcmctl restart -ct ohs
To set up HTTPS with mod_osso:
ssl_osso.sh and add the following content to it:
#!/bin/sh # This script creates a osso\osso-conf file ($AS_HOST.AS_ PROTOCOL-osso.conf) # AS = Application server or midtier # Modify following variables before running AS_PROTOCOL=https AS_HOST=<MIDTIER_HOST> AS_PORT=<MIDTIER_HTTPS_PORT> SSO_HOST=<SSO_HOST> MODOSSO_FILE=${ORACLE_HOME}/Apache/Apache/conf/mod_osso.conf MODOSSO_HTTPSFILE=${ORACLE_HOME}/Apache/Apache/conf/mod_osso_ https.conf echo 'Registering mod_osso, please wait...' cp $MODOSSO_FILE $MODOSSO_HTTPSFILE # Note: make sure that your SSO server runs on port 1521. #If not, replace '-port 1521' with correct port number. $ORACLE_HOME/jdk/bin/java \ -jar $ORACLE_HOME/sso/lib/ossoreg.jar \ -host $SSO_HOST \ -port 1521 \ -sid iasdb \ -site_name $AS_HOST.$AS_PROTOCOL:$AS_PORT \ -oracle_home_path $ORACLE_HOME \ -success_url $AS_PROTOCOL://$AS_HOST:$AS_PORT/osso_login_success \ -logout_url $AS_PROTOCOL://$AS_HOST:$AS_PORT/osso_logout_success \ -cancel_url $AS_PROTOCOL://$AS_HOST:$AS_PORT/ \ -home_url $AS_PROTOCOL://$AS_HOST:$AS_PORT/ \ -config_mod_osso TRUE -u root -sso_server_version v1.2 \ -config_file $ORACLE_HOME/Apache/Apache/conf/osso/$AS_HOST.${AS_ PROTOCOL}-osso.conf cp $MODOSSO_HTTPSFILE $MODOSSO_FILE
ssl_osso.sh script that you created in the previous step:
$ sh ssl_osso.sh
LoadModule osso_module libexec/mod_osso.so within the following files:
mod_osso_https.conf file, replace the OssoConfigFile directive with the following:
OssoConfigFile conf/osso/MIDTIER_HOST.https-osso.conf
httpd.conf file, add the following directive directly after all of the LoadModule directives (immediately after fastcgi_module in a default setup):
LoadModule osso_module libexec/mod_osso.so
VirtualHost _default_:4444 directive, (or your HTTPS VirtualHost if the port is different) of httpd.conf, add the following line:
include conf/mod_osso_https.conf
opmnctl):
$ dcmctl stop -ct ohs $ dcmctl start -ct ohs
When you are running the root.sh script, you might receive an error that the $ORACLE_HOME/rdbms/filemap file could not be found. This error occurs because a file does not exist. You can ignore this error.
When browsing the documentation from the CD through Disk1/doc/index.html, the links for the following documents under the Resource Kit section are broken:
To correct this:
$ cp -R cd_mount_point/doc ./doc
$ cd ./doc/admin $ mv calendar Calendar $ mv files Files $ mv wireless Wireless
./doc/index.html file.The following resource kit documents are not available on the Oracle Collaboration Suite Product CD_ROM:
You can obtain these documents on the Oracle Technology Network:
http://otn.oracle.com/
This section describes documentation issues in the Oracle Collaboration Suite Installation and Configuration Guide:
The following tasks are no longer relevant:
This section applies only if you are not using the Oracle Collaboration Suite installed database.
The following steps are no longer applicable:
5. Click Next. The UMADMIN Password screen displays.
6. Enter and confirm the UMADMIN password. If a password is not entered, the default value "welcome" is stored in both Oracle Internet Directory and the database as the UMADMIN password.
