| Oracle® Collaboration Suite Readme Release 2 Patch Set 1 (9.0.4.2.1) for Windows Part Number B14386-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Readme Release 2 Patch Set 1 (9.0.4.2.1) for Windows Part Number B14386-02 |
|
|
View PDF |
This chapter contains postinstallation instructions for the various components of Oracle Collaboration Suite.
This chapter includes the following topics:
Section 3.1, "Oracle Calendar Server Postinstallation Tasks"
Section 3.2, "Oracle Calendar Application System Postinstallation Tasks"
Section 3.3, "Oracle Calendar Administrator Postinstallation Tasks"
Section 3.6, "Oracle Voicemail and Fax Postinstallation Tasks"
Section 3.7, "Oracle Web Conferencing Postinstallation Tasks"
This section includes the following topics:
Section 3.1.1, "Manually Updating category.ini and categorytype.ini for Oracle Calendar"
Section 3.1.2, "Setting Up HTTPS with mod_osso on the Middle Tier"
If you modified category.ini before applying the patch
It is possible that before you installed the Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.1), you were using a customized version of the category.ini file with your Oracle Calendar server. For example, you may have modified category.ini to include specific resource names for your organization. In this case, the patch set installation program detects that the category.ini was customized, and does not overwrite it. However, if you want to take advantage of the patch set's increased support for languages, make the following manual changes:
Back up your current category.ini file by renaming it (for example, to category.ini.bak).
Make a copy of the newly installed category.ini.sbs file and name it category.ini. This new category.ini file contains support for the new languages.
Duplicate any custom changes made to the original category.ini file in the new category.ini file.
The file categorytpe.ini does not get overwritten during the installation of the patch. To manually update this file, copy categorytype.ini.sbs to categorytype.ini.
If you did not modify category.ini before applying the patch
The files category.ini and categorytype.ini are not overwritten during the installation of the patch. Follow these steps to manually update these files.
Copy category.ini.sbs to category.ini.
Copy categorytype.ini.sbs to categorytype.ini.
Oracle Calendar Administrator uses HTTPS with mod_osso on the middle tier. Other single sign-on applications may require this, as well. If HTTPS with mod_osso is configured on your existing installation, applying the patch set leaves this intact.
If, however, HTTPS with mod_osso is not configured on your existing installation, applying the patch set does not rectify this. To configure HTTPS with mod_osso manually, follow the steps described in "Manually Setting Up HTTPS with mod_osso on the Middle Tier" in Chapter 6 of the Oracle Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1.1).
|
See Also: The technical note "How do I set up Oracle9iAS Portal (9.0.2) to use HTTPS (SSL)," available on the Oracle9iAS Portal Web site athttp://portalcenter.oracle.com |
This section covers the following Oracle Calendar application system postinstallation topics:
Section 3.2.1, "Enabling Support for New Languages in Oracle Calendar"
Section 3.2.2, "Reducing Page Size and Enabling Support for New Attachment Types in Oracle Calendar"
Section 3.2.4, "Increasing the Size of the Favorites List in the Oracle Calendar Web Client"
Section 3.2.5, "Properly Shutting Down the Oracle Calendar Application Processes"
Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.1) provides new language translations for Hungarian, Russian, Czech, and Romanian.
Enable the new language translations in Oracle Calendar, as follows:
Stop the Oracle HTTP Server.
Edit the %ORACLE_HOME%\ocas\conf\ocas.conf file, as follows:
[languages] czech=cs romanian=ro russian=ru hungarian=hu [sortalgorithm] czech=czech romanian=Romanian russian=Generic_M hungarian=Hungarian
Start the Oracle HTTP Server.
Follow the steps described in Section 5.1, "Enabling New Language Translations (Optional)" to enable the languages in Oracle Collaboration Suite.
This release of Oracle Calendar includes a fix for reducing the size of pages displayed in the Oracle Calendar Web client, as well as support for new default attachment types.
Apply the page size fix and enable the attachment support as follows:
Stop the Oracle HTTP Server.
Edit the %ORACLE_HOME%\ocas\conf\ocwc.conf file as follows:
Add the following line to the [url_prefix] section:
javascript_prefix = "/ocas/ocwc/%ocwc_language%/javascript/"
Add the following lines to the [download_extension] section:
.zip = application/zip .bmp = image/bmp .png = image/png
Add the following new section at the end of the file:
[javascript] # extension of JavaScript file. extension = ".ojs"
Start Oracle HTTP Server.
The procedures in this section describe how to configure Oracle9iAS Portal on a different middle tier than Oracle HTTP Server, and how to enable SSL requests from the Oracle Calendar portlet.
This section includes the following topics:
Configuring Oracle9iAS Portal on a Different Middle Tier
If Oracle9iAS Portal is running on a different middle tier than Oracle HTTP Server, copy the newly installed Calendar.jsp and calendarlet.zip files onto the Oracle9iAS Portal middle tier to resolve the time zone issue described in Section 1.6.1, "Configuring Time Zone Behavior for the Oracle Calendar Portlet". The two files to be copied are located in the following directories:
%ORACLE_HOME%\j2ee\OC4J_Portal\applications\webclient-calendar\webclient-calendar-web\portlets\Calendar.jsp %ORACLE_HOME%\j2ee\OC4J_Portal\applications\webclient-calendar\webclient-calendar-web\WEB-INF\lib\calendarlet.zip
Enabling SSL Requests from the Oracle Calendar Portlet
The following steps describe how to enable SSL requests from the Oracle Calendar portlet.
|
Note: This procedure is only necessary if you did not previously enable SSL requests on the portlet in your 9.0.4.1.1 installation. |
Include the following .jar files in the Oracle9iAS Containers for J2EE instance CLASSPATH.
%ORACLE_HOME%\jlib\javax-ssl-1_1.jar %ORACLE_HOME%\jlib\jssl-1_1.jar
For example, you could include the.jar files in
%ORACLE_HOME%\j2ee\OC4J_Portal\config\application.xml
with the following lines.
<library path="%ORACLE_HOME%\jlib\javax-ssl-1_1.jar"/> <library path="%ORACLE_HOME%\jlib\jssl-1_1.jar"/>
Modify the following file to use HTTPS rather than HTTP when accessing Oracle Calendar Web services.
%ORACLE_HOME%\webclient\classes\oracle\collabsuite\webclient\resources\webclient.properties
For example, change the following line
calendar=http://host_name:port/ocas-bin/ocas.fcgi?sub=web
to
calendar=https://host_name:SSL_port/ocas-bin/ocas.fcgi?sub=web
Update Calendar.jsp to support SSL requests. In a typical installation, Calendar.jsp is found in the following directory:
%ORACLE_HOME%\j2ee\C4J_Portal\applications\webclient-calendar\webclient-calendar-web\portlets
Enable SSL requests before the portlet's main routine, as follows:
System.setProperty("javax.net.ssl.KeyStore",
"Oracle_Wallet_Client_Certificate_Path");
System.setProperty("javax.net.ssl.KeyStorePassword", "Oracle_Wallet_
Password");
Restart Oracle9iAS Portal.
The javax.net.ssl.KeyStore property points to the Oracle wallet Web service client certificate. Since all requests are local to the same middle tier, Oracle Web Cache wallet is used.
If Oracle9iAS Portal and the Oracle Calendar Web services are running on the same middle tier, they can use the Oracle Web Cache wallet.
The Oracle Calendar Web client Favorites list can now include more than 15 agendas, provided you configure this in the ocwc.conf and unison.ini files. Depending on the number you need, modify the files using values in Table 3-2. Restart the Calendar server and Oracle HTTP Server for your changes to take effect.
It is important to use the following shutdown procedure when shutting down the Oracle Calendar Application Processes.
In ocas.conf, add the following to the end of the [system] section:
# This value will allow OCAS to determine the PID# of the Apache application that spawned it. This# is used under Windows only. The value must be# a relative path from ocas.fcgi to the Apache log path.# default: ../../Apache/Apache/logshttpdPidPath=../../Apache/Apache/logsVerify that the httpdPidPath is referencing the log directory of the Apache server that is running ocas.fcgi and ochecklet.fcgi. This must be a relative path from ocas.fcgi to the actual directory. For typical installations use the default value.
Restart the Oracle HTTP Server for the change to take effect.
On standalone installations of Oracle Calendar Administrator, you need to set the PATH environment variable to include the %ORACLE_HOME%\ocal\lib and %ORACLE_HOME%\lib directories. You can do this through the Windows Control Panel, by configuring your webserver to include these directories during startup, or you can edit the SetEnv PATH statement in the %ORACLE_HOME%\ocad\config\ocad.conf file.
The Oracle Universal Installer checks the listener.ora file for NNTP entries during installation of the patch set. These entries may be missing before applying the patch set. If the Oracle Universal Installer does not find any NNTP entries, it automatically adds them. In order to have the listener.ora changes take effect, the listener on middle tier must be stopped and restarted.
Stopping the Email Listener
To stop the email listener:
Click Services.
In the list of local services, locate the service ending with listener_es.
Right-click the listener name and choose Stop.
To stop the email listener manually, enter:
%ORACLE_HOME%\bin\lsnrctl stop listener_es
Starting the Email Listener
To start the email listener:
Click Services.
In the list of local services, locate the service ending with listener_es.
If the service is not running, right click the listener name and choose Start.
To start the email listener manually, enter:
%ORACLE_HOME%\bin\lsnrctl start listener_es
|
See Also: Chapter 1, "Listener Control Utility" in the Oracle9i Net Services Reference Guide |
Communicating with LDAP Over Secure SSL Connections
In installations where the mail protocol servers are configured to communicate with LDAP over secure SSL connections, the protocol servers log in to LDAP two times—once over the standard LDAP port in order to obtain the port address on which the LDAP server is listening for SSL connections; then a second time over the SSL port. This patch set corrects this behavior. Following the application of this patch set, the protocol servers configured to communicate with LDAP securely will pick up the LDAP SSL port address from a local file and connect directly.
If your installation is configured for mail protocol servers to communicate with LDAP over secure SSL connections, edit the oesadmin.properties file located in the %ORACLE_HOME%\oes\admin directory on each middle tier, adding the following two lines:
oracle.mail.ldap.connectssl=boolean oracle.mail.ldap.sslport=port_number
Replace boolean with either true or false (case insensitive). Setting true ensures the value read for sslport is used to connect to LDAP. A setting of false uses the standard non-SSL port.
port_number specifies the TCP/IP port address on which the Oracle Internet Directory (infrastructure installation) is listening for secure SSL traffic.
In order to have the LDAP SSL changes to take effect, you must restart mail protocol servers. Please refer to the Email administration guide to get information on restarting mail protocol servers.
This section describes the following Oracle Files postinstallation tasks:
|
See Also: "Using Oracle Files with an Upgraded Oracle Database 10g" if you intend to upgrade your existing Oracle Files information storage database to Oracle Database 10g or "Using Oracle Files with a New Oracle 10g Database" if you have a new Oracle Files installation and want to use Oracle Database 10g for your information storage database. Refer to Section 4.3, "Using Oracle Collaboration Suite with Oracle Application Server 10g Identity Management and Oracle Database 10g" if you plan to configure Oracle Files with Oracle Database 10g and Oracle Identity Management 10g. |
Redeploying Oracle9iAS Containers for J2EE
To redeploy Oracle9iAS Containers for J2EE, follow these steps on each middle tier that runs an Oracle Files HTTP node and on which you have installed the patch set:
Stop the Oracle Files HTTP nodes. From the Oracle9iAS Home Page on the Oracle Enterprise Manager Web site, select OC4J_iFS_files.
Click Stop. On the Warning page, click Yes to stop the OC4J instance.
Undeploy the OC4J_iFS_files instance by entering the following command as one continuous line:
%ORACLE_HOME%\dcm\bin\dcmctl undeployApplication -a files -co OC4J_iFS_ files -d -v
Deploy the OC4J_iFS_files instance by entering the following command as one continuous line:
%ORACLE_HOME%\dcm\bin\dcmctl deployApplication -f %ORACLE_HOME%\ifs\files \lib\files.ear -a files -co OC4J_iFS_files -d -v
Starting Oracle Files Processes
To start Oracle Files processes, including the Oracle Files domain, regular nodes, and HTTP nodes, follow these steps for each Oracle Files middle tier:
Using a Web browser, access Oracle Enterprise Manager at http://host_name:port, where host_name is the name of the Oracle Files middle tier computer. The port is typically 1810.
Enter the authentication information in the pop-up window. The user name is typically ias_admin.
Click the name of the application server instance where Oracle Files is running. The Oracle9iAS Home Page appears.
Click the Oracle Files domain link. The domain appears in the following format:
iFS_db_host_name:port:db_service_name:files_schema
Click Start Local Components.
Click OK.
If there is an Oracle Files HTTP node on this middle tier, follow these additional steps:
Return to the Oracle9iAS Home Page and select OC4J_iFS_files.
Click Start.
Loading the Oracle Files Help and the Oracle FileSync Executable
Load the Oracle Files help and the Oracle FileSync executable, as follows (you only need to do this once for each Oracle Files domain):
Execute the following commands:
cd %ORACLE_HOME%\ifs\files\bin ifsuploadfiles
When prompted, provide the following values:
Oracle Files schema password
Oracle Files system user password
The Oracle Files system user resides in the Oracle Files schema. This user is not the database user system. You entered the password for the Oracle Files system user during Oracle Files configuration.
Oracle Files site_admin password
Oracle Files domain name, in the format:
ifs://db_host:listener_port:db_service_name:files_schema_name
|
Note: To find out the Oracle Files domain name, execute the following command from%ORACLE_HOME%\ifs\files\bin:
ifsctl status -n |
To ensure the files were uploaded successfully, check the ifsuploadfiles.log file in the %ORACLE_HOME%\ifs\files\log directory.
Oracle Workflow Postinstallation Steps
Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.1) provides Czech, Hungarian, Romanian, and Russian language support. The following table lists the codes for these languages:
To enable additional languages in the Oracle Workflow schema, add the language codes to the ifswfsetup.properties file (located at %ORACLE_HOME%\ifs\files\settings) and run the Oracle Workflow configuration assistant. The Oracle Workflow configuration assistant executable, ifswfsetup.bat, is located in the following directory:
%ORACLE_HOME%\ifs\files\bin\
|
Note: Before integrating Oracle Workflow with the Oracle Files schema, you must download and install fromhttp://metalink.oracle.com the patch found under bug 3525423. |
|
See Also: Oracle Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1.1) for complete instructions about runningifswfsetup, enabling languages for Oracle Workflow, and applying critical Oracle Workflow patches. |
This post installation task is required if you plan to install Oracle Voicemail & Fax after applying the 9.0.4.2.1 patch set to Oracle Email. Changes in the Oracle Internet Directory after applying the 9.0.4.2.1 patch set to Oracle Email cause an error to occur when executing the Voicemail & Fax Backend Configuration Tool. The following workaround must be applied after running the Voicemail & Fax Backend Configuration Tool (%ORACLE_HOME%\um\uminfra\uminfra_install.bat).
Update the middletier.ldif file in %ORACLE_HOME%\um\scripts by performing a global replacement. For example, if ORACLE_HOME is C:\test1, perform global replace cn=C:\test1 with cn=test1.
Re-run the script that loads the ldif file.
%ORACLE_HOME%\um\scripts\ldap_ias.bat %ORACLE_HOME% 1
This section describes the following Oracle Web Conferencing postinstallation tasks:
After installing the patch set, you must reimport any root certificates and restart all Oracle Web Conferencing components that were shut down during the preinstallation steps in Section 1.9.1, "Shut Down Oracle Real-Time Collaboration Services", as follows:
Reimport root certificates that you backed up as described in Section 1.9, "Oracle Web Conferencing Preinstallation Requirements" into the %ORACLE_HOME%\imeeting\conf\certdb.txt file.
If any Oracle Real-Time Collaboration servers are running, stop them as follows:
%ORACLE_HOME%\imeeting\bin\imtctl stop
If the Oracle Real-Time Collaboration OC4J instance is running, stop it as follows:
%ORACLE_HOME%\dcm\bin\dcmctl stop -co OC4J_imeeting -t 360 -v
Start the Oracle Real-Time Collaboration OC4J instance, as follows:
%ORACLE_HOME%\dcm\bin\dcmctl start -co OC4J_imeeting -t 360 -v
Start all Oracle Real-Time Collaboration servers, including document and voice conversion servers, as follows:
%ORACLE_HOME%\imeeting\bin\imtctl start
This information in this section only applies to deployments in which the Web Conferencing middle tier and the Portal middle tier reside in different domains. The Portal middle tier, which hosts the Web Conferencing portlet, assumes that the Web Conferencing middle tier resides in the same domain. As a result, users deploying the Web Conferencing middle tier and the Portal middle tier in different domains cannot use the Web Conferencing middle tier to start or join conferences. To correct this issue, set the imtgDomain property to the domain name of the Web Conferencing middle tier as follows:
Find imtgp.properties in the following location (all one line):
In imtgp.properties, set the property imtgDomain to the domain name of the Web Conferencing middle tier.
Restart the Portal middle tier as follows:
%ORACLE_HOME%\opmn\bin\opmnctl restartproc gid=OC4J_Portal
Get instance-specific configuration information from the original portal.properties file (that you made a copy of in Section 1.10, "Oracle9iAS Wireless Preinstallation Requirements"), and apply it to the new portal.properties and portal_*.properties files. The instance-specific configuration keys are:
marconi.account.voiceaccess.number.value marconi.account.wirelessaccess.url.value marconi.account.askaccess.sms.value marconi.account.askaccess.email.value
Restart OC4J_Wireless, all Messaging Server instances, and the PIM Notification Dispatcher process that you shut down in Section 1.10, "Oracle9iAS Wireless Preinstallation Requirements".
If the Oracle Collaboration Suite Patchset was installed on an Oracle Collaboration Suite 9.0.4.1.1 midtier configured against a non Oracle Collaboration Suite Infrastructure, the following scripts need to be run from the Collaboration Suite Midtier Oracle home using a SQL*Plus session against the wireless schema in the Infrastructure Metadata Repository:
$ORACLE_HOME/wireless/sql/trans_clean.sql%ORACLE_HOME\wireless\sql\trans_clean.sql %ORACLE_HOME\wireless\sql\trans_setup.sql %ORACLE_HOME\wireless\sql\up9022-9023.sql %ORACLE_HOME\wireless\sql\up9028-9032.sql %ORACLE_HOME\wireless\sql\recomp_obj.sql
