Oracle® Collaboration Suite Readme Release 2 Patch Set 1 (9.0.4.2.0) for hp-ux PA-RISC (64-bit), Linux x86, and Solaris Operating Environment (SPARC 32-bit) Part Number B13767-02 |
|
|
View PDF |
This chapter contains information and 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.5, "Oracle Web Conferencing Postinstallation Tasks"
This section includes the following topics:
Section 3.1.1, "Manually Updating category.ini for Oracle Calendar"
Section 3.1.2, "Setting Up HTTPS with mod_osso on the Middle Tier"
It is possible that before you installed the Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0), 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 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.
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).
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"
Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) 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.
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.jar
files onto the Oracle9iAS Portal middle tier to resolve the time zone issue described in Section 1.4.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.jar 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 installation. |
Include the following .jar
files in the Oracle9iAS Containers for J2EE instance CLASSPATH
.
For example, you could include .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"/>
Ensure that libnjssl9.so
is in the directory specified in the LD_LIBRARY_PATH
environment variable.
For hp-ux PA-RISC (64-bit), ensure that libnjssl9.sl
is in the directory specified in the SHLIB_PATH
environment variable.
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/OC4J_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-1:
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 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.
Ensure that the ORACLE_HOME
environment variable is set to the $ORACLE_HOME
directory of the concerned middle tier. To stop the listener, execute the following command on the middle tier:
lsnrctl stop listener_es
Start the listener as root
. On the middle tier, at the operating system prompt, enter the following command line arguments:
tnslsnr listener_es [-user user] [-group group]
-user
user
is the numerical identification of the UNIX account that owns the Oracle software
-group
group
specifies the numerical identification of the UNIX group to which the Oracle owner belongs
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 into 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.
This section covers the following Oracle Files postinstallation tasks:
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:
Undeploy the OC4J_iFS_files
instance, as follows (the following command is one continuous line):
$ORACLE_HOME/dcm/bin/dcmctl undeployApplication -a files -co OC4J_iFS_ files -d -v
Deploy the OC4J_iFS_files
instance, as follows (the following command is 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_schemaClick 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 per 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
You must run ifswfsetup
if you want to
Integrate Oracle Files with Oracle Workflow
Enable additional languages in Oracle Workflow
See Also: Oracle Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1) for complete instructions about runningifswfsetup , enabling languages for Oracle Workflow, and applying critical Oracle Workflow patches |
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.7.1, "Shut Down Oracle Real-Time Collaboration Services", as follows:
Reimport root certificates that you backed up as described in Section 1.7, "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 -v -t 360
Start the Oracle Real-Time Collaboration OC4J instance, as follows:
$ORACLE_HOME/dcm/bin/dcmctl start -co OC4J_imeeting -v -t 360
Start all Oracle Real-Time Collaboration servers, as follows:
$ORACLE_HOME/imeeting/bin/imtctl start
Restart document and voice conversion servers located on Windows systems, as follows:
%ORACLE_HOME%\imeeting\bin\imtctl start
Get instance-specific configuration information from the original portal.properties
file (that you made a copy of in Section 1.8, "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.8, "Oracle9iAS Wireless Preinstallation Requirements".