| Oracle® Collaboration Suite Installation Guide 10g Release 1 (10.1.1) for Microsoft Windows Part Number B14484-01 |
|
|
View PDF |
| Oracle® Collaboration Suite Installation Guide 10g Release 1 (10.1.1) for Microsoft Windows Part Number B14484-01 |
|
|
View PDF |
Beta Draft
This chapter contains the following sections:
The order for the installation of Oracle Collaboration Suite Single Cluster Architecture is as follows:
Install Oracle Cluster Ready Services. This is a prerequisite for the installation of Oracle Collaboration Suite Database in an Oracle Real Application Clusters (Oracle RAC) database.
Apply the Oracle Cluster Ready Services 10.1.0.4.2 patch set for your platform. patch set (10.1.0.4.2) for HP-UX DVD.
Install Oracle Collaboration Suite Database on Oracle RAC.
Configure load balancers for the Identity Management tier appropriately.
Install Identity Management on high availability nodes. The virtual server name of the load balancer must be specified in the Specify LDAP Virtual Host and Ports and the Specify HTTP Load Balancer Host and Ports screens during installation.
Run OCSdbSchemaReg.shOCSdbSchemaReg.bat script on a database node. This script registers the database with Oracle Internet Directory and runs the component Configuration Assistants that create schema objects for each Oracle Collaboration Suite component.
Install Oracle Calendar Server in Cold Failover Cluster Configuration. It must use a virtual host name, such as vhost.mydomain.com. Install the oraInventory directory and ORACLE_HOME on a shared device that can be mounted to the other node for a cold failover.
Install Oracle Collaboration Suite Applications (without Oracle Calendar Server).
Configure the first instance of Oracle Collaboration Suite Applications with a load balancer.
Install the subsequent instance of Oracle Collaboration Suite Applications.
Configure the load balancer to work with the subsequent instance of Oracle Collaboration Suite Applications.
This section contains the following topics:
Section 11.2.1, "Installing and Applying the Patch to Oracle Cluster Ready Services"
Section 11.2.3, "Configuring Load Balancers for Identity Management"
Section 11.2.4, "Installing Identity Management on High Availability Nodes"
Section 11.2.9, "Installing Subsequent Instance of Oracle Collaboration Suite Applications"
This section explains the installation steps for Oracle Cluster Ready Services. It also explains the steps involved in applying the patch to Oracle Cluster Ready Services.
Perform the steps listed in Table 11-1 to install Oracle Cluster Ready Services.
For Installation steps for Cluster Ready Services, refer to the Oracle Real Application Clusters Installation and Configuration Guide at
http://otn.oracle.com/pls/db10g/portal.portal_demo3?selected=16
Install the Oracle Cluster Ready Services software from the Oracle Collaboration Suite Supplemental DVD.
Table 11-1 Installing Oracle Cluster Ready Services
| Step | Screen | Action |
|---|---|---|
| 1. | None | Log in as the oracle user and set the ORACLE_BASE environment variable to specify the Oracle base directory that you created previously. For example:
\u01\app\oracle |
| 2. | None | Set the ORACLE_HOME environment variable to specify the CRS home directory that you created previously. For example:
\u01\crs\oracle\product\10.1.0\crs_1 |
| 3. | None | Run setup.exe from the top-level directory of the Oracle Cluster Ready Services Release 1 CD-ROM or the crs directory on the DVD-ROM. These are separate CD-ROMs and DVD-ROMs that contain the Cluster Ready Services software. |
| 4. | Welcome page | Click Next. |
| 5. | Specify Inventory Directory and Credentials
(Advanced installation only) |
This screen appears only if this is the first installation of any Oracle product on this computer.
Enter the full path for the inventory directory: Enter a full path to a directory for the installer files. Enter a directory that is different from the Oracle home directory for the product files. Example: Click OK. |
| 6. | Specify File Locations
(Advanced installation only) |
Enter the full path of the Source directory in the Path field for Source, if required.
Name: Enter a name to identify this Oracle home. The name cannot contain spaces, and has a maximum length of 16 characters. Example: Destination Path: Enter the full path to the destination directory. This is the Oracle home. If the directory does not exist, the installer creates it. To create the directory beforehand, create it as the Example: Click Next. |
| 7. | Language Selection
(Advanced installation only) |
Select the required language from the Available Languages list and add it to the Selected Languages list.
Click Next. |
| 8. | Cluster Configuration
(Advanced installation only) |
Cluster Name: Specify the cluster name.
Specify the host name under Public Node Name. Similarly, specify the private name under Private Node Name. These names will be used to interconnect the node names within the cluster. Note: The private name cannot be the same as the public name. However, the private name can be an IP address. Click Next. |
| 9. | Specify Network Interface Usage
(Advanced installation only) |
Select the interface name, subnet, and interface type for the node in the cluster from the respective drop-down list.
The interface that you mark private will only be used for Oracle RAC internode traffic. Note: If there is more than one subnet associated with an interface, then specify the subnet that you want to associate with the interface type. |
| 10. | Oracle Cluster Registry
(Advanced installation only) |
Specify OCR Location: Specify the shared raw device or the cluster file system file that will be visible to all nodes of the cluster.
Note: At least 100 MB of disk space is required for the OCR. Click Next. |
| 11. | Voting Disk
(Advanced installation only) |
Enter voting disk file name: Specify the raw device or the cluster file system file for voting disk that will be visible to all nodes of the cluster.
Click Next. Note: At least 20 MB of disk space is required for the OCR. |
| 12. | Summary | Verify your selections and click Install. |
| 13. | Install Progress | This screen displays the progress of the installation. |
| 14. | Configuration Assistants | This screen shows the progress of the configuration assistants. Configuration assistants configure components. |
| 15. | End of Installation | Click Exit to quit the installer. |
After installing Oracle Cluster Ready Services, you must apply Oracle Cluster Ready Services 10.1.0.4.2 patch set. The Oracle Cluster Ready Services 10.1.0.4.2 patch set for your platform is located on the Oracle Database 10patch set (10.1.0.4.2) for Solaris Operating System (SPARC) DVD. The Oracle Cluster Ready Services 10.1.0.4.2 patch set for your platform is located on the Oracle Database 10patch set (10.1.0.4.2) for Linux x86 DVD. The Oracle Cluster Ready Services 10.1.0.2 patch set for your platform is located on the Oracle Database 10 patch set (10.1.0.4.2) for HP-UX DVD. Oracle recommends you apply the 10.1.0.5 RDBMS patchset when it becomes available.
The steps to do so are listed in Table 11-2.
Table 11-2 Applying the Oracle Cluster Ready Services 10.1.0.4.2 Patch Set
| Step | Screen | Action |
|---|---|---|
| 1. | Welcome | Click Next. |
| 2. | Specify File Locations | Enter the full path of the Source directory in the Path field for Source, if required.
Destination Path: Enter the full path to the destination directory. This is the Oracle home. Both source and destination will be same as that provided during the installation of Oracle Cluster Ready Services. |
| 3. | Selected Nodes | Verify the nodes listed in the Node Names list and click Next. |
| 4. | Summary | Verify your selections and click Install. |
| 5. | End of Installation | Click Exit to quit the installer. |
To install Oracle Collaboration Suite Database on clustered hardware, follow the steps listed in Section 11.2.1.
If you plan to use an existing ASM instance and you want to use a new ASM disk group then create the ASM disk group prior to running the Oracle Collaboration Suite database installation. (See the Database Administration Guide for ASM administration details)
If you plan to use ASM instances for the Oracle Collaboration Suite database, then consider these recommendations:
If you plan to use ASM with Oracle Database instances from multiple database homes on the same node, then you should run the ASM instance from an Oracle home that is different from the database homes.
The ASM home should be installed on every cluster node. This prevents the accidental removal of ASM instances that are in use by databases from other homes during the deinstallation of a database Oracle home.
If you choose to not have the ASM ORACLE_HOME separate, then the Oracle Collaboration Suite database installation creates the ASM instance for you.
To install Oracle Collaboration Suite Database on Oracle RAC, follow the steps listed in Table 11-3.
Note:
If you are installing the Oracle Collaboration Suite Database separately and not against the Oracle Collaboration Suite Infrastructure, then you must not register the Oracle RAC database with Oracle Internet Directory during the database install because it will not be registered correctly.Table 11-3 Installing Oracle Collaboration Suite Database
| Step | Screen | Action |
|---|---|---|
| 1. | Welcome | Click Next. |
| 2. | Specify File Locations | Enter a name and path for the new Oracle home.
This new Oracle home will be the destination Oracle home for your Oracle Collaboration Suite Database. Click Next. |
| 3. | Specify Hardware Cluster Installation Mode | Select Cluster Installation and the nodes where you want to install the Oracle software. The local node will always be selected.
Click Next. |
| 4. | Select a Product to Install | Select Oracle Collaboration Suite Infrastructure 10.1.1.0.2.
Click Next. |
| 5. | Select Installation Type | Select Collaboration Suite Database.
Click Next. |
| 6. | Product-specific Prerequisite Checks | Make sure all the checks complete successfully.
Click Next. |
| 7. | Database Creation | Select Yes for Do you want to create a new database at this time?
Click Next. |
| 8. | Information Storage Registration | Select No for Do you want to register the information store at this time?
Click Next. |
| 9. | Specify Database Identification | Enter the global database name and the SID that you want to use for this install in the Global Database Name and SID fields.
Click Next. |
| 10. | Specify Database Management Option | Select Use Grid Control for Database Management or Use Database Control for Database Management.
Click Next. |
| 11. | Specify Database File Storage Option | Select Automated Storage Management (ASM).
Note: This example uses ASM. You can select any storage type based on the requirement. Click Next. |
| 12. | Specify Backup and Recovery Options | Select Do not enable Automated Backups. Oracle recommends that you disable automated backup. Note that if you enable automated backup, then this option will only back up the Oracle Collaboration Suite Database and not any other Oracle Collaboration Suite files.
Click Next. |
| 13. | Specify Database Schema Passwords | Enter password for each accounts or use the same password for all the accounts.
Click Next. |
| 14. | Summary | Make sure all of the settings and choices are correct for your installation.
Click Install. |
| 15. | Install Progress | This screen displays the progress of the installation. |
| 16. | The Configuration Assistants | This screen shows the progress of the configuration assistants. Configuration assistants configure components. |
| 17. | End of Installation | Click Exit to quit the installer. |
The postinstallation tasks involve troubleshooting the installation errors.
You must configure the SQLNET.EXPIRE_TIME parameter in the ORACLE_BASE\ORACLE_HOME\network\admin\sqlnet.ora file on the application infrastructure database. For the OracleAS Single Sign-On server, the parameter must be updated on each database host. The parameter should be set to a value less than the TCP timeout setting on the load balancer SSO virtual server.
To configure the time-out value on the computers specified, the steps are as follows:
Open the file ORACLE_BASE\ORACLE_HOME\network\admin\sqlnet.ora file file.
Set the SQLNET.EXPIRE_TIME parameter to a value lower than the TCP session time-out value for the load balancing router and firewall.
Restart the listener by issuing these commands in ORACLE_HOME\bin:
lsnrctl stop lsnrctl start
This section explains the implementation of load balancing for Identity Management in a high availability environment.
This section discusses the prerequisites for the installation of Identity Management on high availability nodes.
A load balancer should be configured to detect service down on a node and automatically stop traffic to that node. Also, the load balancer is recommended to be in a fault tolerant mode. This section provides instructions for configuring a load balancer for Identity Management.
To configure a load balancer for OracleAS Cluster (Identity Management), perform the following steps:
Verify that the load balancer virtual server name you select does not contain the physical host names of the nodes in the Identity Management.
When the installer copies files to different nodes in the Identity Management, it replaces the current host name in the files with the host name of the target node. Ensure that the load balancer's virtual server name does not contain the host names of the nodes in the cluster, or the installer might change the virtual server name of the load balancer as well.
For example, if you are installing on nodes named rac-1 and rac-2, be sure that the load balancer virtual server name does not contain "rac-1" or "rac-2". When the installer is installing files to rac-2, it searches for the string "rac-1" in the files and replaces it with "rac-2". If the load balancer's virtual server name happens to be LB-rac-1x, the installer sees the string "rac-1" in the name and replaces it with "rac-2", thus mangling the virtual server name to LB-rac-2x.
Configure your load balancer with virtual server names and associated ports as follows:
Configure a virtual server name for LDAP connections. For this virtual server, you must configure one port for SSL connections and the other for non-SSL connections.
Configure a virtual server name for HTTP connections. For this virtual server, you must configure one port for SSL connections and the other for non-SSL connections.
Configure your LDAP server to direct response to the first node initially. This procedure applies only to the LDAP virtual server configured on the load balancer. Note that this procedure applies only to the LDAP virtual server configured on your load balancer. This does not apply to the HTTP virtual server configured on the load balancer.
The installer will prompt you for the virtual server names and port numbers.
After you complete installation on a node, then you can add that node to the virtual server. For example, if you have three nodes, then perform the following steps:
Configure the LDAP virtual server to direct requests to node 1 only.
Install Identity Management components on node 1.
Install Identity Management components on node 2.
Add node 2 to the LDAP virtual server.
Install Identity Management components on node 3.
Add node 3 to the LDAP virtual server.
Set up cookie persistence for HTTP traffic on the load balancer. Specifically, set up cookie persistence for URIs starting with /oiddas/. This is the URI for Oracle Delegated Administration Services. If your load balancer does not allow you to set cookie persistence at the URI level, then set the cookie persistence for all HTTP traffic. In either case, set the cookie to expire when the browser session expires. Refer to your load balancer documentation for details.
To configure the load balancer for automatic monitoring of the Oracle Internet Directory and OracleAS Single Sign-On, Oracle Delegated Administration Services, set up monitors for the following:
LDAP port
LDAP SSL port
HTTP or HTTPS listen port (depending on the deployment type)
Oracle recommends that these monitors use the respective protocols to monitor the services. That is LDAP for the LDAP port, LDAP over SSL for the LDAP SSL port, and HTTP/HTTPS for the web server port. If the load balancer does not offer one or all of these monitors, consult the load balancer documentation for details on the best method to set up the load balancer.
This section describes how to install Identity Management on high availability nodes. This section does not show the use of a staticports.ini file to specify port numbers explicitly to the installer. To use this option refer to Section 2.4.4.
To install the first instance of Identity Management, follow the steps listed in Table 11-4.
Table 11-4 Installing the First Instance of Identity Management
| Step | Screen | Action |
|---|---|---|
| 1. | Welcome | Click Next. |
| 2. | Specify File Locations | Enter a name and path for the new Oracle home.This new Oracle home will be the destination Oracle home for your Identity Management. Click Next. |
| 3. | Specify Hardware Cluster Installation Mode (optional) | Select Local Installation.This screen will appear only if you are installing Identity Management on a cluster. Click Next. |
| 4. | Select a Product to Install | Select Oracle Collaboration Suite Infrastructure 10.1.1.0.2.
Click Next. |
| 5. | Select Installation Type | Select Identity Management.
Click Next. |
| 6. | Product-specific Prerequisite Checks | Make sure all the checks complete successfully.
Click Next. |
| 7. | Select Configuration Options | Select Oracle Internet Directory.Select OracleAS Single Sign-On.Select OracleAS Delegated Administration Services.Select OracleAS Directory Integration and Provisioning.Do not select OracleAS Certificate Authority (OCA).Select High Availability and Replication.
Click Next. |
| 8. | Specify Repository | Username: Enter the username to use to log in to the Oracle Collaboration Suite Database. The user must have DBA privileges.
Password: Enter the user password. Hostname and Port: Enter the names of all the nodes where the Oracle Collaboration Suite Database is running and the port numbers.Use the format: Host1.domain.com:port1^Host2.domain.com:port2^… Service Name: Enter the service name of the database. Note that the service name must include the database domain name. Click Next. |
| 9. | Select High Availability or Replication Option | Select OracleAS Cluster (Identity Management).
Click Next. |
| 10. | Specify New Oracle Application Server Cluster Name | Specify a cluster name you want to create for the OracleAS Cluster (Identity Management) in the New Oracle Application Server Cluster Name field.
Click Next. |
| 11. | Specify Namespace in Internet Directory | Enter a new namespace for Oracle Internet Directory or select the Suggested Namespace:
dc=us,dc=oracle,dc=com Click Next. |
| 12. | Specify LDAP Virtual Host and Ports | Hostname: Enter the fully qualified virtual server name of the LDAP virtual server configured on your load balancer.
SSL Port: Enter the SSL port number for Oracle Internet Directory. Non-SSL Port: Enter the port number for Oracle Internet Directory. Click Next. |
| 13. | Specify HTTP Load Balancer Host and Ports | HTTP Listener: Port: Enter the port number that you want Oracle HTTP Server to listen on.
Enable SSL: Select this option to configure Oracle HTTP Server for SSL on this port. HTTP Load Balancer: Hostname: Enter the name of the HTTP virtual server configured on your load balancer. HTTP Load Balancer: Port: Enter the port of the HTTP virtual server. Enable SSL: Select this option if this port is for SSL communications only. Click Next. |
| 14. | Specify Port Configuration Options | Select Automatic Port Selection or Manual and enter the port numbers for.
Click Next. Note: The Automatic option only uses ports in the range 7777-7877 for Oracle HTTP Server and 4443-4543 for Oracle HTTP Server with SSL. If you need to set the port numbers as 80 for Oracle HTTP Server and 443 for Oracle HTTP Server with SSL, then you must select the Manually Specify Ports option. |
| 15. | Guest Account Password | Enter the password for the orclguest account.
Click Next. |
| 16. | Specify Instance Name and ias_admin Password |
Instance Name: Enter a name for this Identity Management instance.
|
| 17. | Summary | Verify your selection and click Install. |
| 18. | The Configuration Assistant | This screen shows the progress of the configuration assistants. Configuration assistants configure components. |
| 19. | End of Installation | Click Exit to quit the installer. |
The Oracle Collaboration Suite Database must be registered in the Oracle Internet Directory for Oracle Collaboration Suite to work correctly. Additionally, the database schemas for each Oracle Collaboration Suite Applications component must be created in the Oracle Collaboration Suite Database. The ORACLE_HOME/install/OCSdbSchemaReg.shORACLE_HOME\install\OCSdbSchemaReg.bat script accomplishes both of these tasks. This script must only be run on a single database node.
The OCSdbSchemaReg.shOCSdbSchemaReg.bat script is located in ORACLE_HOME\install directory on the Oracle Collaboration Suite Database nodes.
Copy ORACLE_HOME\install\OCSdbSchemaReg.ini.sample to ORACLE_HOME\install\OCSdbSchemaReg.ini.
Modify the ORACLE_HOME\install\OCSdbSchemaReg.ini script with the appropriate values.
Run OCSdbSchemaReg.bat from ORACLE_HOME\install directory in Oracle RAC mode by entering multiple hosts in the $hostList option of the OCSdbSchemaReg.ini file from one of the Oracle Collaboration Suite Database machine.
Run the following script.
OCSdbSchemaReg.bat –f OCSdbSchemaReg.ini
This section explains the installation and postinstallation tasks for Identity Management. It contains the following topics:
Before installing Oracle Calendar Server in a Cold Failover Cluster, perform the following procedures:
For a Cold Failover Cluster, vendor clusterware is not required. If vendor clusterware is used then the failover process can be automated through the vendor clusterware mechanisms. If vendor clusterware is not used then the failover process can be scripted or manually executed. On Linux systems Oracle Cluster Ready Services (CRS) and vendor clusterware cannot coexist.
Each node in a Cold Failover Clusters configuration is associated with its own physical IP address. In addition, the active node in the cluster is associated with a virtual host name and virtual IP address. This enables clients to access the Cold Failover Clusters using the virtual host name.
Virtual host names and virtual IP addresses are any valid host name and IP address in the context of the subnet containing the hardware cluster.
Note:
Map the virtual host name and virtual IP address only to the active node. Do not map the virtual host name and IP address to both active and secondary nodes at the same time. When you failover, only then do you map the virtual host name and IP address to the secondary node, which is now the active node.The following example configures a virtual host name called calvhost.mydomain.com, with a virtual IP of 138.1.12.191:
Ensure that you have Administrator privileges.
Determine the public network interface.
# ipconfig /all
Typically, the interface name is Local Area Connection, Local Area Connection2, and so on. Local Area Connection is the public network interface. It is not a loopback interface and not a private interface.
Add the virtual IP to the Local Area Connection network interface.
# netsh interface ip add address name="Local Area Connection" addr="138.1.12.191" mask="255.255.0.0"
Local Area Connection and the IP address are values specific to this example. Replace them with values appropriate for your cluster.
Check that new interface was added:
# ipconfig /all
The virtual IP appears in the Local Area Connection entry. During installation, when you enter "calvhost.mydomain.com" as the virtual host name in the Specify Virtual Hostname screen, the installer checks that "calvhost.mydomain.com" is a valid interface.
On Failover If the active node fails, then the secondary node takes over. If you do not have a clusterware agent to map the virtual IP from the failed node to the secondary node, then must do it manually. You must remove the virtual IP mapping from the failed node, and map it to the secondary node.
On the failed node, if possible, become superuser and remove the virtual IP.
If the failed node fails completely (that is, it does not start), you can skip this step and go to Step 2. If the node fails partially (for example, disk or memory problems), and the node is still pingable, you must perform this step as an Administrator.
# netsh interface ip delete address name="Local Area Connection" addr=" 138.1.12.191"
Local Area Connection and the IP address are values specific to this example. Replace them with values appropriate for your cluster.
On the secondary node, add the virtual IP to the ge0 network interface.
# netsh interface ip add address name="Local Area Connection" addr="138.1.12.191" mask="255.255.0.0"
Local Area Connection and the IP address are values specific to this example. Replace them with values appropriate for your cluster.
On the secondary node, check that the new interface was added:
# ipconfig /all
Although the hardware cluster has shared storage, you must create a file system on this shared storage such that both nodes of the Cold Failover Clusters can mount this file system. You will use this file system for the following directories:
Oracle home directory for the Infrastructure
The oraInventory directory
If you are running a volume manager on the cluster to manage the shared storage, refer to the volume manager documentation for steps to create a volume. Once a volume is created, you can create the file system on that volume.
If you do not have a volume manager, you can create a file system on the shared disk directly. Ensure that the hardware vendor supports this, that the file system can be mounted from either node of the Cold Failover Clusters, and that the file system is repairable from either node if a node fails.
To check that the file system can be mounted from either node, do the following steps:
Set up and mount the file system from node 1.
Unmount the file system from node 1.
Mount the file system from node 2 using the same mount point that you used in Step 1.
Unmount it from node 2, and mount it on node 1, because you will be running the installer from node 1.
Note:
Only one node of the Cold Failover Clusters should mount the file system at any given time. File system configuration files on all nodes of the cluster should not include an entry for the automatic mount of the file system upon a node restart or execution of a global mount command.Before installing Oracle Calendar in a Cold Failover Clusters configuration, make sure that the virtual IP address and host name is enabled on the install node.
To install Oracle Calendar in a Cold Failover Clusters configuration, follow the steps listed in Table 11-5.
Table 11-5 Installing Oracle Calendar Server in Cold Failover Cluster Configuration
| Step | Screen | Action |
|---|---|---|
| 1. | None | Start the installer. |
| 2. | Welcome | Click Next. |
| 3. | Specify Inventory Directory and Credentials
(Advanced installation only) |
This screen appears only if this is the first installation of any Oracle product on this computer.
Enter the full path for the inventory directory: Enter a full path to a directory for the installer files. Enter a directory that is different from the Oracle home directory for the product files. Example: Click OK. |
| 4. | Specify File Locations
(Advanced installation only) |
Enter the full path of the Source directory in the Path field for Source, if required.
Name: Enter a name to identify this Oracle home. The name cannot contain spaces, and has a maximum length of 16 characters. Example: Destination Path: Enter the full path to the destination directory. This is the Oracle home. If the directory does not exist, the installer creates it. To create the directory beforehand, create it as the Example: Click Next. |
| 5. | Specify Hardware Cluster Installation Mode
(Advanced installation only) |
This screen appears only if the computer is part of a hardware cluster.
When you are installing Oracle Collaboration Suite Applications, select Local Installation because hardware cluster is not supported for Oracle Collaboration Suite Applications. Click Next. |
| 6. | Select a Product to Install
(Advanced installation only) |
Select Oracle Collaboration Suite Applications 10.1.2.
If you need to install additional languages, click Product Languages. Click Next. |
| 7. | Product-specific Prerequisite Checks
(Advanced installation only) |
The installer verifies requirements such as memory, disk space, and operating system version. If any check fails, make the required changes and click Retry.
Click Next. |
| 8. | Select Components to Configure
(Advanced installation only) |
Select Oracle Calendar Server.
Note: You can also configure any component after installation. Click Next. |
| 9. | Register with Oracle Internet Directory
(Advanced installation only) |
Host: Enter the LDAP virtual server name.
Port: Enter the non-SSL port number for the LDAP virtual server name. Use SSL to connect to Oracle Internet Directory: Select this option if you want Oracle Collaboration Suite components to use only SSL to connect to Oracle Internet Directory. Click Next. |
| 10. | Specify UserName and Password for Oracle Internet Directory
(Advanced installation only) |
Username: Enter the user name to use to log in to Oracle Internet Directory.
Password: Enter the user password. Click Next. Note: Use |
| 11. | OracleAS Metadata Repository
(Advanced installation only) |
Select the Oracle Collaboration Suite Database from the list.
Click Next. |
| 12. | Select Database Components
(Advanced installation only) |
Component Name: Oracle Calendar Server
Database Name: Name of the Oracle Collaboration Suite Database. Click Next. Note: If multiple instances of Oracle Collaboration Suite Databases are available in Oracle Internet Directory, then you must click on the Database Name column and then select the correct database for each component from the drop-down list. However, when you click Next to go to the next screen, the selection might not be retained. To ensure that the selection is retained, you must click the Database Name column again after selecting the required database for each component. |
| 13. | Specify Port Configuration Options
(Advanced installation only) |
Select Automatic Port Selection or Manual and enter the port numbers for.
Click Next. Note: If you manually configure the ports, then you must specify the port values for each port. Note: The Automatic option only uses ports in the range 7777-7877 for Oracle HTTP Server and 4443-4543 for Oracle HTTP Server with SSL. If you need to set the port numbers as 80 for Oracle HTTP Server and 443 for Oracle HTTP Server with SSL, then you must select the Manually Specify Ports option. |
| 14. | Specify Administrative Password and Instance Name
(Advanced installation only) |
Instance Name: Enter a name for this Calendar Server instance.
Administrative Password: Set the password for the administrative user. This is the administrative user for the Calendar Server instance. Confirm Password: Confirm the password. Click Next. Note: If multiple instances of Oracle Collaboration Suite Databases are available in Oracle Internet Directory, then you must click on the Database Name column and then select the correct database for each component from the drop-down list. However, when you click Next to go to the next screen, the selection might not be retained. To ensure that the selection is retained, you must click the Database Name column again after selecting the required database for each component. |
| 15. | Oracle Calendar Server Host Alias
(Advanced installation only) |
Host or Alias: Enter the virtual host name for the Calendar Server instance.
Click Next. Note: Oracle recommends that you use alias in place of host name if later you want to move the calendar server instance or change the host name. Specify the host name if an alias is not configured. |
| 16. | Summary | Verify your selections and click Install. |
| 17. | Install Progress | This screen displays the progress of the installation. |
| 18. | Configuration Assistants | This screen shows the progress of the configuration assistants. Configuration assistants configure components. |
| 19. | End of Installation | Click Exit to quit the installer. |
The postinstallation tasks involve troubleshooting the installation errors and performing manual postinstallation steps.
You might have to perform the postinstallation steps to solve the following problems:
Oracle Calendar Server installation does not accept virtual host name. This is a network problem. To resolve this error, exit and restart the installer.
You must also perform the following additional postinstallation steps:
In ORACLE_HOME\ocal\misc\unison.ini file, add dir_connectmodel = ondemand entry under the [DAS] section.
Restart Oracle Calendar Server.
ORACLE_HOME\opmn\bin\opmnctl restartproc ias-component=CalendarServer
Webcache by default uses the local host in its $ORACLE_HOME/webcache/webcache.xml configuration file. To avoid having to manually change the webcache.xml file hostname in the event of a Calendar Server failover, you can create a local hostname alias for the Oracle Collaboration Suite Calendar Server nodes. Creating this host name alias is a one-time requirement. You accomplish this by adding a line to the /etc/hosts file on each Calendar Server CFC node.
For example, if the nodes are called node1 and node2, and you want the alias to be called cfcwebcache, then you would follow these steps so that no post failover manual steps are required for getting webcache to startup correctly.
In the /etc/hosts file on node1, add the alias to the existing local host line:
139.185.141.98 node1.mycompany.com node1 loghost cfcwebcache.mycompany.com
In the /etc/hosts file on node2, add the alias to the existing local host line:
139.185.141.99 node2.mycompany.com node2 loghost cfcwebcache.mycompany.com
Update the CACHE NAME and HOSTNAME fields in $ORACLE_HOME/webcache/webcache.xml to use the alias cfcwebcache.mycompany.com. For example:
<CACHE NAME="cfcwebcache.mycompany.com-WebCache" ORACLEHOME="/cal/server" HOSTNAME="cfcwebcache. mycompany.com"VOTES="1" CAPACITY="30" WCDEBUGON="NO">
Restart webcache.
opmnctl restartproc process-type=WebCache
In the $ORACLE_HOME/Apache/Apache/conf/httpd.conf file, update it to use the Calendar Server virtual hostname as follows. For this example the Calendar Server virtual hostname is calvhost.mycompany.com.
Change the ServerName line.
ServerName calvhost.mycompany.com
Change the Server Status section.
<Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from localhost calvhost.mycompany.com calvhost
</Location>
Restart the HTTP Server.
opmnctl restartproc process-type=HTTP_Server
This section describes the installation of the first instance of Oracle Collaboration Suite Applications without Oracle Calendar Server.
To install first instance of Oracle Collaboration Suite Applications, follow the steps listed in Table 11-6.
Table 11-6 Installing the First Instance of Oracle Collaboration Suite Applications
| Step | Screen | Action |
|---|---|---|
| 1. | Welcome | Click Next. |
| 2. | Specify File Locations | Enter a name and path for the new Oracle home. This new Oracle home will be the destination Oracle home for your Oracle Collaboration Suite Applications.
Click Next. |
| 3. | Select a Product to Install | Select Oracle Collaboration Suite Applications 10.1.1.0.2.
Click Next. |
| 4. | Product-specific Prerequisite Checks | Make sure all the checks complete successfully.
Click Next. |
| 5. | Select Components to Configure | Select Oracle Mail.Select Oracle Mobile Collaboration.Select Oracle Content Services.Do not select Oracle Calendar Server.Select Oracle Calendar Web Client.Select Oracle Real-Time Collaboration.Select Oracle Collaboration Suite Search.Select Oracle Collaboration Suite Web Access.Select Oracle Collaborative Portlets.Select Oracle Workspaces.Select Oracle Discussions.
Click Next. |
| 6. | Register with Oracle Internet Directory | Host: Enter the LDAP virtual server name.
Port: Enter the non-SSL port number for the LDAP virtual server name. Click Next. |
| 7. | Specify UserName and Password for Oracle Internet Directory | Username: Enter the username to log in to Oracle Internet Directory. You must log in as the Oracle Internet Directory superuser (cn=orcladmin).
Password: Enter the password for the username. Click Next. |
| 8. | OracleAS Metadata Repository | Select Oracle Collaboration Suite Database from the list.
Click Next. |
| 9. | Select Database Components | Component Name: Oracle Mail, Oracle Discussions, Oracle Search, Oracle Real-Time Collaboration, Oracle Collaboration Suite Search, Oracle Workspaces, Oracle Content Services, Oracle Collaboration Suite Web Access
Database Name: Name of the Oracle Collaboration Suite Database. Click Next. |
| 10. | Specify Port Configuration Options | Select Automatic Port Selection or Manual and enter the port numbers for.
Click Next. Note: The Automatic option only uses ports in the range 7777-7877 for Oracle HTTP Server and 4443-4543 for Oracle HTTP Server with SSL. If you need to set the port numbers as 80 for Oracle HTTP Server and 443 for Oracle HTTP Server with SSL, then you must select the Manually Specify Ports option. |
| 11. | Specify Administrative Password and Instance Name | Instance Name: Enter a name for this Oracle Collaboration Suite Applications instance.
Administrative Password: Set the password for the administrative user. This is the administrative user for the Oracle Collaboration Suite Applications instance. Click Next. |
| 12. | Specify Oracle Mail Domain Information | Mail Domain: Enter the domain that you want to use for Oracle Mail server.
Click Next. |
| 13. | Summary | Verify your selection and click Install. |
| 14 | The Configuration Assistants | This screen shows the progress of the configuration assistants. |
| 15. | End of Installation | Click Exit to quit the installer. |
Postinstallation Steps
For Oracle Mail, start the UM listener (listener_es) on the Oracle Collaboration Suite Applications tier as the super user if the port that you are using is a privileged port (<1024). Get the user ID and group ID of the owner of the Oracle Collaboration Suite Applications.
Start the UM listener as root after setting ORACLE_HOME, LD_LIBRARY_PATH and PATH environment variables.
# *$ORACLE_HOME\bin\tnslsnr listener_es –user *\userid\* -group *\group_id\* &***
You can configure two or more Oracle Collaboration Suite Applications instances in a highly-available deployment by placing a load balancer in front of them. The load balancer publishes a single address for Oracle Collaboration Suite Applications while providing a redundant set of application servers that actually service requests. The load balancer can be configured to detect when one of the Oracle Collaboration Suite Applications instances has failed and can then fail over requests to another instance.
Our configuration is as follows:
There are two Oracle Collaboration Suite Applications computers: ocs_apps1.mycompany.com and ocs_apps2.mycompany.com. Both application servers listen on non-SSL port 7777.
The Oracle Collaboration Suite Applications computers are configured to use the Single Sign-On server located at im_virtual.mycompany.com.
The effective host name of the Oracle Collaboration Suite Applications published to the user is http://apps_virtual.mycompany.com. A load balancer is configured to listen at this address, on port 80. It has been configured to load balance and fail over user requests between ocs_apps1.mycompany.com and ocs_apps2.mycompany.com.
The Single Sign-On server and Directory server are located at im_virtual.mycompany.com.
The Oracle Collaboration Suite Database (including Identity Management metadata) is located at ocs_store1.mycompany.com and ocs_store2.mycompany.com (2-node Oracle RAC).
Perform the following steps to configure the first Oracle Collaboration Suite Applications tier with a load balancer:
Configure the Parallel Page Engine Loop-Back with the Load Balancer
Enable Monitoring of the Front-End Host and Port Settings of the Load Balancer for OracleAS Portal
To set up the load balancer to work with the installation of first instance of Applications tier, ensure that the following is configured (the port names and numbers should match your $ORACLE_HOME/install/portlist.ini file):
A virtual server name (apps_virtual.mycompany.com) that listens for requests on port 80 (HTTP) and balances them to the Oracle HTTP Server port from the portlist.ini file. For this example, the Oracle Collaboration Suite 10g Applications tier HTTP Server is running on ocs_apps1.mycompany.com on port 7777.
A virtual server name (apps_virtual.mycompany.com) that listens for requests on port 7777 (HTTP) and balances them to the Web Cache HTTP Listen port from the portlist.ini file. For this example, the Oracle Collaboration Suite 10g Applications tier the Webcache HTTP listener is running on ocs_apps1.mycompany.com on port 7777. Port 7777 on the load balancer receives the HTTP loop-back requests made by the Parallel Page Engine on ocs_apps1.mycompany.com. This 7777 port also receives requests from the Portal Metadata Repository for web providers design time messages. This configuration may require a Network Address Translation (NAT) rule in the load balancer in order for the loop-back request from the PPE to succeed.
A virtual server name (apps_virtual.mycompany.com) that listens for requests on port 9401 (Web Cache Invalidation Port) and balances them to the Web Cache on Oracle Collaboration Suite Applications tier on ocs_apps1.mycompany.com on port 9401 (Web Cache Invalidation Port). Port 9401 on the load balancer receives invalidation messages from the OracleAS Portal Repository when content that is cached in OracleAS Web Cache becomes stale. This configuration might require a NAT rule in the load balancer in order for the invalidation requests from the OracleAS Portal repository to succeed.
A virtual server name (apps_virtual.mycompany.com) that listens for requests on port 25 (SMTP) and balances them to the Oracle Collaboration Suite Applications tier's SMTP port on ocs_apps1.mycompany.com on port 25 (an SMTP listening port). This virtual server on port 25 (SMTP) should also have simple persistence. Simple Persistence returns a client to the same node to which it connected previously. Simple persistence tracks connections based only on the client IP address.
The virtual server name (apps_virtual.mycompany.com) listens for requests on port 143 (Oracle Mail IMAP4 port) and balances them to the Oracle Collaboration Suite Applications tier on ocs_apps1.mycompany.com on port 143 (Oracle Mail IMAP4 port).
Note:
apps_virtual.mycompany.com listens on 80 for external traffic, on port 7777 for Parallel Page Engine loop-back messages, and port 9401 for invalidation messages, and port 25 for SMTP traffic.For security reason, port 9401 and 7777 on the load balancer should not be visible to external users.
This step associates the components on which OracleAS Portal depends with load balancer virtual server name and port: apps_virtual.mycompany.com:80 as follows:
Access the Oracle Enterprise Manager – Oracle Collaboration Suite Control console.
Click the link for the ocs_apps1.mycompany.com installation.
Click the HTTP Server link.
Click the Administration link.
Click Advanced Server Properties.
Open the httpd.conf file.
Perform the following steps:
Add LoadModule certheaders_module directive.
LoadModule certheaders_module libexec/mod_certheaders.so
The LoadModule directives (in particular, the LoadModule rewrite_module directive) must appear in the httpd.conf file at a location preceding the VirtualHost directives. The server must load all modules before it can execute the directives in the VirtualHost container. It is a good idea to create the VirtualHost directives at the end of the httpd.conf file.
Add the following lines to create a NameVirtualHost directive and a VirtualHost container for apps_virtual.mycompany.com and port 80. Port 7778 in the following example corresponds to the Oracle HTTP Server Listen port from the $ORACLE_HOME/install/portlist.ini file.
NameVirtualHost *:7778 <VirtualHost *:7778> ServerName apps_virtual.mycompany.com Port 80 ServerAdmin you@your.address RewriteEngine On RewriteOptions inherit </VirtualHost>
Create a second VirtualHost container for ocs_apps1.mycompany.com and port 7777. Port 7778 in the following example corresponds to the Oracle HTTP Server Listen port and port 7777 corresponds to the Web Cache HTTP Listen port from the $ORACLE_HOME/install/portlist.ini file.
<VirtualHost *:7778> ServerName ocs_apps1.mycompany.com Port 7777 ServerAdmin you@your.address RewriteEngine On RewriteOptions inherit </VirtualHost>
Save the httpd.conf file, and restart the Oracle HTTP Server when prompted.
In this step, you configure non-SSL loop-back communication between the load balancer and the Parallel Page Engine on ocs_apps1.mycompany.com.Before you start this configuration, ensure the following:
You are able to resolve apps_virtual.mycompany.com from ocs_apps1.mycompany.com such that it contacts the load balancer. To ensure you can resolve apps_virtual.mycompany.com, issue the following command from ocs_apps1.mycompany.com.
nslookup apps_virtual.mycompany.com
The IP address for the load balancer should be returned.
You are able to contact port 7777 on apps_virtual.mycompany.com from ocs_apps1.mycompany.com. Issue the following command on ocs_apps1.mycompany.com.
telnet apps_virtual.mycompany.com 7777
Verify that no connection failure message is returned.
To create the loop-back configuration, the steps are as follows:
Open the ORACLE_HOME\j2ee\OC4J_Portal\applications\portal\portal\WEB-INF\web.xml file.
Locate the Page servlet section.
Add the lines shown in bold.
<servlet>
<servlet-name>page</servlet-name>
<servlet-class>oracle.webdb.page.ParallelServlet</servlet-class>
<init-param>
<param-name>useScheme</param-name>
<param-value>http</param-value>
</init-param>
<init-param>
<param-name>usePort</param-name>
<param-value>7777</param-value>
</init-param>
</servlet>
Save the web.xml file.
Issue this command in ORACLE_HOME\dcm\bin to update the DCM repository.
dcmctl updateConfig
Issue these commands in ORACLE_HOME\opmn\bin to restart the OCS Applications instance.
opmnctl stopall opmnctl startall
The Portal Dependency Settings file iasconfig.xml must contain the correct host, port, and farm name to enable access to OracleAS Portal and perform OracleAS Web Cache invalidation. To edit the file to include this information, the steps are as follows:
Create a backup copy of the ORACLE_HOME\portal\conf\iasconfig.xml file.
Open the ORACLE_HOME\portal\conf\iasconfig.xml file and perform the following steps:
Change the existing code as follows:
<IASConfig XSDVersion="1.0"> <IASFarm Name="Farm1.apps_virtual.mycompany.com" Host="apps_virtual.mycompany.com"> <WebCacheComponent ListenPort="80" InvalidationPort="9401" InvalidationUsername="invalidator" InvalidationPassword="welcome1" SSLEnabled="false" AdminPort="9400"/> </IASFarm> <IASInstance Name="ocsapps1.ocs_apps1.mycompany.com" Host="ocs_apps1.mycompany.com"> <EMComponent ConsoleHTTPPort="1810" SSLEnabled="false"/> </IASInstance>* <IASInstance Name="iAS-1.im_virtual.mycompany.com" Host="im_virtual.mycompany.com"> <OIDComponent AdminPassword="@BVELB7NJSpZHTYxd0Jc/EubFeXQKqrc5aw==" AdminDN="cn=orcladmin" SSLEnabled="false" LDAPPort="389"/> </IASInstance> <PortalInstance DADLocation="/pls/portal" SchemaUsername="portal" SchemaPassword="@BWQsAbPplXWMMsuK2bq0Wf4gZCaq6ZUDUg==" ConnectString="cn=imdb,cn=oraclecontext"> <WebCacheDependency ContainerType="IASFarm" Name="Farm1.apps_virtual.mycompany.com"/> <OIDDependency ContainerType="IASInstance" Name="iAS-1.im_virtual.mycompany.com"/> <EMDependency ContainerType="IASInstance" Name="ocsapps.ocs_apps1.mycompany.com"/> </PortalInstance> </IASConfi
Save the iasconfig.xml file.
Encrypt any plain text passwords in the iasconfig.xml configuration file by setting the ORACLE_HOME environment variable, if necessary, and issuing the following command from ORACLE_HOME\portal\conf:
ptlconfig –encrypt
In this step, you register the OracleAS Portal URLs using the load balancer virtual server name and port instead of the OracleAS Web Cache host name and port. Follow the steps in this section to use the OracleAS Portal Configuration Assistant to register the URLs.
Ensure that the ORACLE_HOME environment variable is set.
Register the URLs using the Portal Dependency Settings tool, which is available in %ORACLE_HOME%/portal/conf:
ptlconfig –dad dadname –wc –site
In the previous syntax, dadname is the name of the OracleAS Portal Database Access Descriptor that is specified in the iasconfig.xml file under the PortalInstance DADLocation entry. For example, in the iasconfig.xml file, the location of this descriptor is specified as:
PortalInstance DADLocation="/pls/portal"
As a result, you can register the URLs using the Portal Dependency Settings tool as follows:
ptlconfig -dad portal -wc -site
Note:
Older versions ofmod_plsql were mounted on a virtual path with a prefix of /pls. This restriction has been removed in newer versions, but the restriction is still imposed by the PL/SQL applications.To prevent access to Oracle Enterprise Manager 10g from the outside, the link provided by OracleAS Portal must be changed back to point to the internal server. To do this, issue the following command in %ORACLE_HOME%/portal/conf:
ptlconfig –dad dadname –em
In the previous syntax, dadname is the name of the OracleAS Portal Database Access Descriptor that is specified in the iasconfig.xml file under the PortalInstance DADLocation entry.
You must configure a site definition, site alias, and a site-to-server mapping to make OracleAS Web Cache function correctly with the load balancer.
Use the Web Cache Manager, the graphical user interface provided for editing the configuration stored in the webcache.xml file.
Access the Web Cache Administrator at: http://ocs_apps1.mycompany.com:9400/webcacheadmin. The Web Cache Administrator password dialog box appears.
Enter the OracleAS Web Cache administrator password. For the user name, enter ias_admin or administrator, and enter the OracleAS Web Cache administrator password.
Note:
At installation time, the OracleAS Web Cache administrator password is set to the same password as theias_admin password. The OracleAS Web Cache administrator password must be identical for all cache cluster members.Click the Site Definitions link in the Origin Servers, Sites and Load Balancing section. The Site Definitions window opens.
Click Add Site.
Enter the following information (leave other fields blank):
Host name: apps_virtual.mycompany.com
Port: 80
Client-side Certificate: Not requiredDefault Site: Yes
Create Alias from Site Name with or without www: No
Click Submit.
Select the radio button for the site for which the alias will be added (apps_virtual.mycompany.com)
Click Add Alias. The Add Alias for Site window opens.
Enter apps_virtual.mycompany.com for the host name and 7777 for the port. (7777 is the value for the usePort parameter in the web.xml file in the Parallel Page Engine configuration).
Click Submit. The alias is added. An alias is needed in the configuration because Portal sends invalidation messages with the value of the HOST attribute in the invalidation message the same as the site name (in this case, apps_virtual.mycompany.com:80), but OracleAS Web Cache caches the portal content keyed on a host:port combination such as apps_virtual.mycompany.com:7777; thus, the invalidation is not executed. Therefore, it is necessary to define an alias, so that OracleAS Web Cache manages the content caching so that it recognizes apps_virtual.mycompany.com:80 and apps_virtual.mycompany.com:7777 as one and the same, and thereby correctly invalidating OracleAS Portal content, although the content is keyed on a different host:port combination than the site name.Click Add Alias. A window with host name and port fields opens.
Enter apps_virtual.mycompany.com for the host name and 80 for the port.
Click Submit. The alias is added.
Note:
An alias for port 80 is needed because the HOST header sent by the browser will beapps_virtual.mycompany.com (without a port number appended to it). Since OracleAS Web Cache is listening on the HTTP port, it will assume that the port number is 80 and use this to determine the site-to-server mapping, and for any cache key creation.Click Apply Changes.
Click the Site-to-Server Mapping link in the Origin Servers, Sites, and Load Balancing section. The Site-to-Server Mapping page appears, in which you map the site and site alias to an origin server.
Select the first mapping in the table and click Insert Above. The Edit/Add Site-to-Server Mapping page appears.
Select the Select From Site Definitions option.
Select apps_virtual.mycompany.com.
Select ocs_apps1.mycompany.com in the Select Application Web Servers section.
Click Submit.
Remove unused mappings or entries containing the wild card character *. At this stage, the Site-to-Server Mapping table should look as follows:
Click Apply Changes.
Click Restart.
The steps for reregistering mod_osso are as follows:
Set the ORACLE_HOME environment variable to the current Oracle home.
Execute the SSO registration script ORACLE_HOME\sso\bin\ssoreg.
ORACLE_HOME\sso\bin\ssoreg.bat \ site_name ocsapps.apps_virtual.mycompany.com \ mod_osso_url http://apps_virtual.mycompany.com \ config_mod_osso TRUE \ oracle_home_path ORACLE_HOME \ config_file ORACLE_HOME\pache\Apache\conf\osso\osso.conf \ admin_info cn=orcladmin \ virtualhost
A partner application, ocsapps.apps_virtual.mycompany.com, is created.
Log on to the OracleAS Single Sign-On Administration page as the Administrator, and use the Administer Partner Applications page to delete the entry for the partner application Oracle Portal (portal) that is still using the physical hostname ocs_apps1.mycompany.com in the Home, Success and Logout URL. ocsapp1.ocs_apps1.mydomain.com is already deleted as part of the reregistration process.
When an object is changed in the database, the application metadata repository database sends an invalidation message to Web Cache to invalidate that object if it exists in the cache. Since the target configuration has two instances of OracleAS Web Cache, the invalidation message must be load balanced across both OracleAS Web Cache instances. This is an example of component level load balancing.
Before you proceed with this verification, ensure that messages can be sent from the computer hosting the database to the load balancer. To do this, issue the following command from ocs_store1.mycompany.com and ocs_store2.mycompany.com:
telnet apps_virtual.mycompany.com 9401
Verify that no connection failure message is returned.
The steps to enable monitoring of the host at the front end of the load balancer and port settings for OracleAS Portal are as follows:
Open the ORACLE_HOME\sysman\emd\targets.xml file.
Locate the OracleAS Portal targets, for example, TYPE="oracle_portal".
Edit the PortalListeningHostPort property so that it points to the load balancer. For example: <Property NAME="PortalListeningHostPort" VALUE="http://apps_virtual.mycompany.com:80"/>
Save and close targets.xml file.
Reload the targets.xml file in the OracleAS Control Console by issuing this command in ORACLE_HOME\bin:
emctl reload
Configure the URLs of the current OracleAS Wireless Instance on each Oracle Collaboration Suite Applications tier. Configuring Oracle Collaboration Suite Mobile Collaboration enables you to define the instance URLs for an application server, or direct an application server to use the URLs defined for the entire OracleAS Wireless site.The steps are as follows:
Access the Oracle Enterprise Manager – Oracle Collaboration Suite Control console.
Click the link for the ocs_apps1.mycompany.com installation.
Click the Wireless link under System Components.
Click the Instance URLs link under Instance Configuration.
Modify the Wireless Instance URLs to point to the load balancer's virtual server name (http://apps_virtual.mycompany.com:80/ptg/rm). Please note that if port 80 is used then it should be explicitly included in the URL as shown.
Repeat the preceding steps for each Oracle Collaboration Suite Applications tier.
Perform the following steps to enable the Oracle Calendar administrator to work through the load balancer virtual server of the Oracle Collaboration Suite Applications tier:
Add the following lines to the end of the $ORACLE_HOME\Apache\Apache\conf\httpd.conf file on each Applications Oracle home:
Execute the $ORACLE_HOME\dcm\bin\dcmctl updateconfig command so that changes are processed. This will enable Oracle Calendar administrator.
Note:
Refer to Section 2.1.1, "Considerations for Real-Time Collaboration".For Real-Time Collaboration, set GlobalWebHost and GlobalWebPort properties to integrate with a load balancer.
A load balancer provides a single published address to the client browser, while distributing requests to multiple Oracle Real-Time Collaboration core component Application tiers that serve the request. It acts as a global Web host for all of the requests.
If you add a load balancer, set the following parameters:
GlobalWebHost is the name of the global Web host.
For example, multiple Application tiers could be placed behind a load balancer (ocs_apps1.mycompany.com, ocs_apps2.mycompany.com), but the Web host name you want to have appear in the URL used to join a conference is apps_virtual.mycompany.com.
Note:
After you set this property, the only way you can unset it is to use the –pvaluenull true option with the SetProperty command. For example, to set the global Web host to apps_virtual.mycompany.com, run the following command:
ORACLE_HOME\imeeting\bin\rtcctl rtcctl> setProperty –system true –pname GlobalWebHost –pvalue "apps_virtual.mycompany.com"
GlobalWebPort is the HTTP port of the global Web host.
For example, to reset the global Web host to listen on port 80 for HTTP requests run the following command:
ORACLE_HOME\imeeting\bin\rtcctl rtcctl> setProperty –system true –pname GlobalWebPort –pvalue 80
SmtpHost is the name of the SMTP host. To set the smtp host to apps_virtual.mycompany.com, run the following command:
Because the SMTP default port is 25, there is no need to set the SMTP port.
Restart Oracle Collaboration Suite Applications using the following commands:
ORACLE_HOME\opmn\bin\opmnctl stopall ORACLE_HOME\opmn\bin\opmnctl startall
You can update the Oracle Collaboration Suite registry entries in Oracle Internet Directory by using the Oracle Directory Manager as follows:
Start the Oracle Directory Manager.
ORACLE_HOME\bin\oidadmin
When you start Oracle Directory Manager, it will prompt you for connection information. Enter the following information to connect to your Oracle Internet Directory, typically hosted in the Oracle Collaboration Suite Database on your Oracle Collaboration Suite Infrastructure:
Host: <infrahost.yourdomain.com> Port: 389 Username: cn=orcladmin Password: <password>
Port 389 is the default port used by Oracle Internet Directory. If you are using a different port, then enter the correct Oracle Internet Directory port.
If you have configured your Oracle Internet Directory to be accessed using SSL, select the SSL Enabled check box. Otherwise, leave it blank.
Select Login to log in to the Oracle Internet Directory. When the connection is successful, the Oracle Internet Directory management screen is displayed.
To access the Service Registry, drill down in to the Oracle Internet Directory by selecting the following items in the System Objects pane:
Select Entry Management.
Select cn=OracleContext.
Select cn=Services.
The System Objects pane displays a list of the Oracle Collaboration Suite Applications which that entries in the Service Registry. The Properties tab displays the properties of the cn=Services object.
To display URIs stored by each component in the Service Registry, select the component in the System Objects pane. Most components will contain a cn=VirtualServices object. This object contains one or more URIs used by other applications and OracleAS Portal to access that application. Applications store URIs in one or more child objects of the cn=VirtualServices object.
Note:
Oracle Universal Installer seeds the Oracle Internet Directory with objects for every Oracle Collaboration Suite Applications during installation, even if you do not configure and deploy every application. These unconfigured application entries will not contain child objects of theircn=VirtualServices objects. The child objects, and the URIs they store, are created in the Service Registry by each component's Configuration Assistant when it first runs.After you verify your configuration, update Oracle Collaboration Suite Service Registry entries in Oracle Internet Directory to use the load balancer virtual host name as follows:
Oracle Calendar Client
dn: cn=OCAS_xxxxx,cn=VirtualServices,cn=Calendar,cn=Services,cn=OracleContext labeleduri;syncserversecureurl labeleduri:syncserverurl labeleduri;webbaseurl labeleduri;webserviceurl
Oracle Calendar Administration
dn: cn=OCAD_xxxxx,cn=VirtualServices,cn=Calendar,cn=Services,cn=OracleContext labeleduri;adminurl
Oracle Collaborative Workspaces
dn:cn=<DBNAME>,cn=VirtualServices,cn=CollaborativeWorkspaces,cn=Services, cn=OracleContext labeleduri;adminurl labeleduri;webbaseurl labeleduri:webui
Oracle Mail
dn: cn=emailadmin,cn=VirtualServices,cn=Email,cn=Services,cn=OracleContext labeleduri;adminurl dn: cn=imap,cn=VirtualServices,cn=Email,cn=Services,cn=OracleContext labeleduri dn: cn=smtp,cn=VirtualServices,cn=Email,cn=Services,cn=OracleContext labeleduri dn: cn=Webmail,cn=VirtualServices,cn=Email,cn=Services,cn=OracleContext labeleduri;peopleurl labeleduri;webbaseurl orclraparameter;webbaseurl dn: cn=webservice,cn=VirtualServices,cn=Email,cn=Services,cn=OracleContext labeleduri;webservices
Oracle Content Services
dn: cn=Content,cn=VirtualServices,cn=Files,cn=Services,cn=OracleContext labeleduri;adminurl labeleduri;s2swebserviceurl labeleduri;webdavurl labeleduri;webservicesurl
Oracle Collaboration Suite Client
dn:cn=IntegratedClient,cn=VirtualServices,cn=OCSClient,cn=Services, cn=OracleContext labeleduri;baseurl labeleduri;popuplibraryurl dn: cn=Search,cn=VirtualServices,cn=OCSClient,cn=Services,cn=OracleContext labeleduri;webbaseurl
OracleAS Portal
dn:cn=ReturnToPortalURL,cn=VirtualServices,cn=Portal,cn=Services, cn=OracleContext labeleduri;
Note:
In addition to changing the host name to use the load balancer virtual host name, the port should also match the listen port used in Step 1 in Section 11.2.8.1. In this example it was port 80 (the default port), which means the port specification can be removed. So, for example, the Oracle Internet Directorylabeleduri for the Portal ReturnToPortalURL should change from
http://ocs_apps1.mycompany.com:7778/portal/page?_dad=portal&_schema=PORTAL&_pageid=
to
http://apps_virtual.mycompany.com/portal/page?_dad=portal&_schema=PORTAL&_pageid=
Oracle Discussions
dn:cn=Discussions:<DBNAME>:<MailDomain>,cn=VirtualServices, cn=ThreadedDiscusssions,cn=Services,cn=OracleContext labeleduri;adminurl labeleduri;rss labeleduri;webbaseurl labeleduri;webui
Oracle Mobile Collaboration
dn: cn=WIRELESS1,cn=VirtualServices,cn=Wireless,cn=Services,cn=OracleContext labeleduri;adminurl labeleduri;calendarnotificationlistenerurl labeleduri;mobilesetupurl labeleduri;presencewebserviceurl
When you have finished editing the properties of an object, select Apply to save the new values in Oracle Internet Directory. If you decide to reject the changes you have made, select Revert to reset the displayed attributes to those currently stored in the Oracle Internet Directory.
Restart Oracle Calendar server so that the changes that you made in the previous step are enabled.
Using opmnctl or Oracle Enterprise Manager 10g, restart the Oracle Collaboration Suite Infrastructure and all Oracle Collaboration Suite Applications tiers, to clear caches that may still be storing the old URIs and to load the new URIs you have entered.
Restart Oracle Collaboration Suite Applications using the following commands:
ORACLE_HOME\opmn\bin\opmnctl stopall ORACLE_HOME\opmn\bin\opmnctl startall
There is no need to restart the Oracle Collaboration Suite Database.
This configuration is necessary if you want the Ultrasearch Crawler to be able to run on any Oracle Collaboration Suite Database Real Application Clusters instance in the cluster and is dependent on shared storage being allocated as instructed in the section, 9.2.2.4.3. For this instruction set the example will use /shared/ultrasearch/log as the shared storage location.
Log on to the Ultrasearch administration page using the URL http://apps_virtual.mycompany.com/ultrasearch/admin/index.jsp. The username and password should be wksys.
Select the Ultrasearch instance, WK_INST in the Select instance to manage drop down list.
Click Apply. This should show Instance WK_INST in the upper left.
Select the Crawler tab.
Set the Cache Directory field, Cache Directory Location (Absolute Path) to /shared/ultrasearch/log.
Set the Crawler Logging field, Crawler Log File Directory to /shared/ultrasearch/log.
Verify that the Database Connect String is set to the proper Real Application Clusters connect string format and if it is not set, then modify it. The proper format is as follows:
(DESCRIPTION=(ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=<RAC Virtual Host 1>)(PORT=1521)) (ADDRESS=(PROTOCOL=TCP)(HOST=<RAC Virtual Host 2>)(PORT=1521)) (LOAD_BALANCE=yes))(CONNECT_DATA=(SERVICE_NAME=<RAC database service name>)))
Click Apply.
All Ultrasearch cache files and log files should be in the shared location, /shared/ultrasearch/log.
The steps to test the configuration are as follows:
Access OracleAS Web Cache and Oracle HTTP Server through the load balancer with the following URL:
http://apps_virtual.mycompany.com
Test the connection to the Oracle Collaboration Suite Database through the load balancer, by accessing the following URL:
http://apps_virtual.mycompany.com/pls/portal/htp.p?cbuf=test
The response should be test. If this succeeds, then the Oracle Collaboration Suite Applications tier can connect to the Oracle Collaboration Suite Database. If this test fails, then examine the Oracle HTTP Server ORACLE_HOME\Apache\Apache\logs\error_log file to determine the cause.
Test the OracleAS Portal using following URL (ensure that you can log in):
http://apps_virtual.mycompany.com/pls/portal
Verify that content is being cached in OracleAS Web Cache on ocs_apps1.mycompany.com, using Web Cache Administrator. Under Monitoring, click Popular Requests. Select Cached from the Filtered Objects drop-down list, and click Update.
If you accessed OracleAS Portal, portal content will appear. If there is no portal content, open another browser and log on to OracleAS Portal. Return to the Popular Requests page, and click Update to refresh the page content.
This section describes the installation of the subsequent instance of Oracle Collaboration Suite Applications without Oracle Calendar Server and postinstallation tasks.
To install the subsequent instance of Oracle Collaboration Suite Applications, follow the steps listed in Table 11-8.
Table 11-8 Installing the Subsequent Instance of Oracle Collaboration Suite Applications
| Step | Screen | Action |
|---|---|---|
| 1. | Welcome | Click Next. |
| 2. | Specify File Locations | Enter a name and path for the new Oracle home. This new Oracle home will be the destination Oracle home for your Oracle Collaboration Suite Applications.
Click Next. |
| 3. | Select a Product to Install | Select Oracle Collaboration Suite Applications 10.1.1.0.2.
Click Next. |
| 4. | Product-specific Prerequisite Checks | Make sure all the checks complete successfully.
Click Next. |
| 5. | Select Components to Configure | Select Oracle Mail.Select Oracle Mobile Collaboration.Select Oracle Content Services.Do not select Oracle Calendar Server.Select Oracle Calendar Web Client.Select Oracle Real-Time Collaboration.Select Oracle Collaboration Suite Search.Select Oracle Collaboration Suite Web Access.Do not select Oracle Collaborative Portlets.Select Oracle Workspaces.Select Oracle Discussions.
Click Next. |
| 6. | Register with Oracle Internet Directory | Host: Enter the LDAP virtual server name.
Port: Enter the non-SSL port number for the LDAP virtual server name. Click Next. |
| 7. | Specify UserName and Password for Oracle Internet Directory | Username: Enter the username to log in to Oracle Internet Directory. You must log in as the Oracle Internet Directory superuser (cn=orcladmin).
Password: Enter the password for the username. Click Next. |
| 8. | OracleAS Metadata Repository | Select Oracle Collaboration Suite Database from the list.
Click Next. |
| Error: The installation has detected that Oracle Collaborative Portlets has already been configured in the Metadata Repository you have selected. Oracle Collaborative Portlets will be unselected for this configuration.
This screen will appear only if you selected Oracle Collaborative Portlets from the Select Components to Configure screen. Click Yes. |
||
| 9. | Select Database Components | Component Name: Oracle Mail, Oracle Discussions, Oracle Search, Oracle Real-Time Collaboration, Oracle Collaboration Suite Search, Oracle Workspaces, Oracle Content Services, Oracle Collaboration Suite Web Access
Database Name: Name of the Oracle Collaboration Suite Database. Click Next. |
| 10. | Specify Port Configuration Options | Select Automatic Port Selection or Manual and enter the port numbers for.
Click Next. Note: The Automatic option only uses ports in the range 7777-7877 for Oracle HTTP Server and 4443-4543 for Oracle HTTP Server with SSL. If you need to set the port numbers as 80 for Oracle HTTP Server and 443 for Oracle HTTP Server with SSL, then you must select the Manually Specify Ports option. |
| 11. | Specify Administrative Password and Instance Name | Instance Name: Enter a name for this Oracle Collaboration Suite Applications instance.
Administrative Password: Set the password for the administrative user. This is the administrative user for the Oracle Collaboration Suite Applications instance. Click Next. |
| 12. | Specify Oracle Mail Domain Information | Local Domain: Select it from the list.
Select the same domain as in the first Oracle Collaboration Suite Applications installation. Click Next. |
| 13. | Summary | Verify your selection and click Install. |
| 14 | The Configuration Assistants | This screen shows the progress of the configuration assistants. |
| 15. | End of Installation | Click Exit to quit the installer. |
The postinstallation tasks involve troubleshooting the installation errors and performing manual postinstallation steps.
You might have to perform the postinstallation steps to solve the following problems:
Oracle Calendar Home Page cannot be accessed through orclguest account. To resolve this error, the steps are as follows:
Stop all fast CGI (FCGI) processes using Oracle OCAS Control (ocasctl). When Oracle Collaboration Suite Application tier is started or stopped using OPMN control (opmnctl), OCAS is not started or stopped because OCAS is not integrated with OPMN.
ORACLE_HOME\ocas\bin\ocasctl -stopall
Start the FCGI processes.
ORACLE_HOME\ocas\bin\ocasctl –start –t ochecklet –p 8020 –n 1 ORACLE_HOME\ocasctl –start –t ocas –p 8010 –n 5
The default ports are 8010 and 8020. The valid range is 8010-8020.
Verify the status of the FCGI processes:
ORACLE_HOME\ocas\bin\ocasctl –status
When you log on to Portal as a newly created user, the Oracle Calendar portlet shows "Service temporarily unable due to maintenance message".
Click the Oracle Calendar link and go to the Oracle Calendar view page.
Click the Return to Portal link and the portlet should show up correctly.
When accessing workspaces, user cannot be found in LDAP directory. To resolve this error, run the following command:
$ORACLE_HOME\opmn\bin\opmnctl restartproc process-type=OC4J_OCSClient
You must also perform the following additional postinstallation steps for Oracle Mail and Oracle Mobile Collaboration:
For Oracle mail, the steps are as follows:
Get the user ID and group ID of the owner of the Oracle Collaboration Suite Applications.
Start LISTENER_ES as root, if the port that you are using is a privileged port (< 1024).. Make sure ORACLE_HOME, LD_LIBRARY_PATH and PATH environment variables are set correctly.
ORACLE_HOME\bin\tnslsnr listener_es –user <userid> -group <group_id> &
Oracle Mail has a feature designed to avoid Denial of Service (DoS) attacks and if it repeatedly receives requests from the same IP, then it will block all incoming requests. This is a problem when requests are all coming from the same IP, the load balancer in the case of Oracle Collaboration Suite high availability installation. To avoid this, it is necessary to increase the Maximum Flood count setting as follows.
In Enterprise Manager under Mail Application, perform the following steps for both the instances of the Applications tier:
Navigate to IMAP Server Default Settings, Rules and Routing Control Parameters.
Change Spam Maximum Flood Count from 40 to 40000.
To enable Oracle Mobile Collaboration Calendar notifications, the steps are as follows:
Log in to Enterprise Manager. Go to System Components, Wireless, Site Administration.
Expand Component Configuration section and click XMS Configuration.
Under XMS Center, ensure that Enable XMSC is checked.
Go to System Components, Wireless, Notification eng xxxx. Click Enable/Disable link and make sure Notification engine is enabled.
Restart the wireless component.
To configure Calendar Oracle Mobile Data Sync to Use Shared Storage Location, the steps are as follows:
Setup Shared Storage Configuration for Links Database.
Follow the Instructions in the Oracle Calendar Administration Guide in "Configuring the Links Database" in Oracle Calendar Administrator's Guide.
You can configure two or more Oracle Collaboration Suite Applications instances in a highly-available deployment by placing a load balancer in front of them. The load balancer publishes a single address for Oracle Collaboration Suite Applications while providing a redundant set of application servers that actually service requests. The load balancer can be configured to detect when one of the Oracle Collaboration Suite Applications instances has failed and can then fail over requests to another instance.
The details of the configuration are as follows:
There are two Oracle Collaboration Suite Applications computers: ocs_apps1.mycompany.com and ocs_apps2.mycompany.com. Both application servers listen on non-SSL port 7777.
The Oracle Collaboration Suite Applications computers are configured to use the Single Sign-On server located at im_virtual.mycompany.com.
The effective host name of the Oracle Collaboration Suite Applications published to the user is apps_virtual.mycompany.com. A load balancer is configured to listen at this address, on port 80. It has been configured to load balance and fail over user requests between ocs_apps1.mycompany.com and ocs_apps2.mycompany.com.
The Single Sign-On server and Directory server are located at im_virtual.mycompany.com.
The Oracle Collaboration Suite Database (including Identity Management metadata) is located at ocs_store1.mycompany.com and ocs_store2.mycompany.com (2-node Oracle RAC).
The postinstallation steps are follows:
Configure the Parallel Page Engine Loop-Back with the Load Balancer
Enable Monitoring of the Front-End Host and Port Settings of the Load Balancer for OracleAS Portal
The first task is to configure OracleAS Portal, using the Oracle Enterprise Manager 10g Collaboration Suites Control Console. Follow these steps to configure OracleAS Portal, beginning on the Oracle Collaboration Suite page:
Click Configure Component. The Select Component page appears.
Select portal from the list.
Click Continue. The configuration process may take 10 to 20 minutes to complete.
Before you continue with the OracleAS Portal application server configuration, ensure that the following is configured:
You are able to resolve apps_virtual.mycompany.com from ocs_apps2.mycompany.com, such that it contacts the load balancer. To ensure you can resolve apps_virtual.mycompany.com by running the following command:
nslookup apps_virtual.mycompany.com
The IP address for the virtual server name should be returned.
You are able to contact port 7777 on apps_virtual.mycompany.com from ocs_apps2.mycompany.com. Run the following command on ocs_app2.mycompany.com:
telnet apps_virtual.mycompany.com 7777
Verify that no connection failure message is returned.
This step associates the components on which OracleAS Portal depends with load balancer virtual server name and port: apps_virtual.mycompany.com:80. The steps to configure the Oracle HTTP Server with the Load Balancer are as follows:
Access the Oracle Enterprise Manager – Oracle Collaboration Suite Control console.
Click the link for the ocs_apps2.mycompany.com installation.
Click the HTTP Server link.
Click the Administration link.
Click Advanced Server Properties.
Open the httpd.conf file.
Perform the following steps:
Add LoadModule certheaders_module directive.
LoadModule certheaders_module libexec\mod_certheaders.so
Note:
The LoadModule directives (in particular, the LoadModule rewrite_module directive) must appear in thehttpd.conf file at a location preceding the VirtualHost directives. The server must load all modules before it can execute the directives in the VirtualHost container. It is a good idea to create the VirtualHost directives at the end of the httpd.conf file.Add the following lines to create a NameVirtualHost directive and a VirtualHost container for apps_virtual.mycompany.com and port 80.
NameVirtualHost *:7778 <VirtualHost *:7778> ServerName apps_virtual.mycompany.com Port 80 ServerAdmin you@your.address RewriteEngine On RewriteOptions inherit </VirtualHost>
Create a second VirtualHost container for ocs_apps2.mycompany.com and port 7777.
<VirtualHost *:7778> ServerName ocs_apps2.mycompany.com Port 7777 ServerAdmin you@your.address RewriteEngine On RewriteOptions inherit </VirtualHost>
Save the httpd.conf file, and restart the Oracle HTTP Server when prompted.
Copy the dads.conf file from ocs_apps1.mycompany.com to ORACLE_HOME\Apache\modplsql\conf directory of ocs_apps2.mycompany.com.
In this step, you configure non-SSL loop-back communication between the load balancer and the Parallel Page Engine on ocs_apps1.mycompany.com and ocs_apps2.mycompany.com. If the OracleAS Web Cache on ocs_app1.mycompany.com is down, the Parallel Page Engine can loop back to the OracleAS Web Cache on ocs_apps2.mycompany.com through the load balancer to reach mod_plsql.
The steps to create the loop-back configuration are as follows:
Open the ORACLE_HOME\j2ee\OC4J_Portal\applications\portal\portal\WEB-INF\web.xml file.
Locate the Page servlet section.
Add the lines shown in bold.
<servlet>
<servlet-name>page</servlet-name>
<servlet-class>oracle.webdb.page.ParallelServlet</servlet-class>
<init-param>
<param-name>useScheme</param-name>
<param-value>http</param-value>
</init-param>
<init-param>
<param-name>usePort</param-name>
<param-value>7777</param-value>
</init-param>
</servlet>
Save the web.xml file.
Save the manual configuration changes in the DCM repository by running the following command on ocs_apps2.mycompany.com in ORACLE_HOME\dcm\bin:
dcmctl updateConfig
Restart all components on ocs_apps2.mycompany.com by running the following command in ORACLE_HOME\opmn\bin:
opmnctl stopall opmnctl startall
The Portal Dependency Settings file iasconfig.xml must contain the correct host, port, and farm name to enable access to OracleAS Portal and perform OracleAS Web Cache invalidation. Follow the steps to edit the file to include this information:
Create a backup copy of the ORACLE_HOME\portal\conf\iasconfig.xml file.
Copy the iasconfig.xml file in ocs_apps1.mycompany.com to ORACLE_HOME\portal\conf of ocs_apps2.mycompany.com.
Overwrite the file on ocs_apps2.mycompany.com when prompted.
The steps for reregistering mod_osso are:
Back up the ORACLE_HOME\Apache\Apache\conf\osso\osso.conf file on ocs_apps2.mycompany.com. For example:
cp $ORACLE_HOME/Apache/Apache/conf/osso/osso.conf $ORACLE_HOME/Apache/Apache/conf/osso/osso.conf.orig
Use the FTP binary mode to copy the $ORACLE_HOME/Apache/Apache/conf/osso/osso.conf%ORACLE_HOME%\Apache\Apache\conf\osso\conf\osso\osso.conf file of ocs_apps1.mycompany.com to %ORACLE_HOME%\Apache\Apache\conf\osso\osso.conf on ocs_apps2.mycompany.com.
Synchronize the DCM repository with the file by FTP using the following command:
ORACLE_HOME\Apache\Apache\bin\ssotransfer ORACLE_HOME\Apache\Apache\conf\osso\osso.conf
Note:
This does not create any new partner applications. It enables the partner applicationocsapps.apps_virtual.mycompany.com for ocs_apps1.mycompany.com and ocs_apps2.mycompany.com.Restart the components on ocs_apps2.mycompany.com by running the commands in ORACLE_HOME\opmn\bin of ocs_apps2.mycompany.com:
opmnctl stopall opmnctl startall
Log in to the OracleAS Single Sign-On Administration page as the Administrator, and use the Administer Partner Applications page to delete the entry for the partner application ocsapp1.ocs_apps2.mycompany.com.
To cluster the OracleAS Web Cache instances, you will perform the configuration steps on ocs_apps1.mycompany.com and propagate them to ocs_apps2.mycompany.com.
From the Oracle Enterprise Manager Collaboration Suite Control Console, you can access the Web Cache Manager, the graphical user interface provided for editing the configuration stored in the webcache.xml file. Start the Oracle Collaboration Suite Applications instance on ocs_apps1.mycompany.com, then follow the steps to access the Web Cache Manager from the System Components page.
Access the Web Cache Administrator at the following URL:
http://ocs_apps1.mycompany.com:9400/webcacheadmin
The Web Cache Administrator password dialog box appears.
For the user name, enter ias_admin or administrator, and enter the OracleAS Web cache administrator password.
Note:
At installation time, the OracleAS Web Cache administrator password is set to the same password as the ias_admin password. The OracleAS Web Cache administrator password must be identical for all cache cluster members.The Web Cache Manager page appears.
Click Clustering in the Properties section. The Clustering page appears.
In the Cluster Members table, click Add. The Add Cache to Cluster page appears.
Enter the following information for ocs_apps2.mycompany.com:
ocs_apps2.mycompany.comocs_apps2.mycompany.com-WebcacheClick Submit.
Click the Origin Server link in the Origin Servers, Sites, and Load Balancing section. The Origin Server page appears.
Click Add under the Application Web Servers table.
Enter the following information:
ocs_apps2.mycompany.com7778ENABLE1005/10HTTPClick Submit.
Click the Site-to-Server Mapping link in the Origin Servers, Sites and Load Balancing section. The Site-to-Server Mapping page appears.
Select the mapping for the Load Balancer site (apps_virtual.mycompany.com) from the table and click Edit Selected. The Edit/Add Site-to-Server mapping page appears.In the Select Application Web Servers section, select an application Web server specified in the Origin Servers page for ocs_apps2.mycompany.com (ocs_apps1.mycompany.com is already mapped). Click Submit.
Verify that each Applications tier also has a site-to-server mapping from the Web Cache HTTP Listen port to the Oracle HTTP Server Listen port. If there are any missing, then add them. At this stage of the install the Webcache Site-to-Server Mapping table should look as follows:
Table 11-9 Webcache Site to Server Mapping Table
| Site | Origin Server | |||||||
|---|---|---|---|---|---|---|---|---|
| Select | Priority | Host Name | Port | URL Path Prefix | ESI Content Policy | Host Name | Port | Proxy |
| 1 | ocs_apps.mycompany.com | 80 | Unrestricted | ocs_apps1.mycompany.com
ocs_apps2.mycompany.com |
7778
7778 |
No
No |
||
| 2 | ocs_apps1.mycompany.com | 7777 | Unrestricted | ocs_apps1.mycompany.com | 7778 | No | ||
| 3 | ocs_apps2.mycompany.com | 7777 | Unrestricted | ocs_apps2.mycompany.com | 7778 | No |
Click Apply Changes.
In the Cache Operations page, click Propagate. The changes are propagated to ocs_apps2.mycompany.com.
Click Restart. OracleAS Web Cache is restarted on ocs_apps1.mycompany.com and ocs_apps2.mycompany.com. OracleAS Web Cache on ocs_apps1.mycompany.com begins to balance requests to the Oracle HTTP Server and OC4J_Portal instances on ocs_apps2.mycompany.com.
The steps are as follows:
Open the ORACLE_HOME\sysman\emd\targets.xml file.
Locate the OracleAS Portal targets, for example, TYPE="oracle_portal".
Edit the PortalListeningHostPort property so that it points to the load balancer. For example:
<Property NAME="PortalListeningHostPort" VALUE="http://apps_virtual.mycompany.com:80"/>
Save and close targets.xml file.
Reload the targets.xml file in the Oracle Collaboration Suite Control Console by running the following command in ORACLE_HOME\bin:
emctl reload
The session binding feature in OracleAS Web Cache is used to bind user sessions to a given origin server to maintain state for a period of time. Enabling session binding forces all the user requests to go to a give OracleAS Portal middle-tier, resulting in a better cache hit ratio for the portal cache. For this reason, session binding is required although almost all components running in a given OracleAS Portal middle tier are stateless.
To enable session binding in OracleAS Web Cache, the steps on ocs_apps1.mycompany.com or ocs_apps2.mycompany.com are as follows:
Access the Web cache Administrator at the following URL:
http://ocs_apps1.mycompany.com:9400
The Web Cache Administrator password dialog box appears.
Enter the OracleAS Web Cache administrator password.
Note:
At installation time, the OracleAS Web Cache administrator password is set to the same password as theias_admin password. The OracleAS Web Cache administrator password must be identical for all cache cluster members.The Web Cache Manager page appears.
Click the Session Binding link in the Origin Servers, Sites, and Load Balancing section. The Session Binding page appears.
Select the Load Balancing Router site, apps_virtual.mycompany.com:80 from the table and click Edit Selected. The Edit Session Binding window opens.
Select Any Set-Cookie from the Please select a session list.
Select Cookie-based from the Please select a session binding mechanism list.
Click Submit.
Click Apply Changes.
On the Cache Options page, click Propagate.The changes are propagated to the OracleAS Web Cache instance on the other computer.
Click Restart. OracleAS Web Cache is restarted on ocs_apps1.mycompany.com and ocs_apps2.mycompany.com.
Configure Collaborative Portlets from Oracle Enterprise Manager 10g Application Server Control Console. The Configure Component button appears above the System Components table if you have installed, but not configured, some components.
To configure Collaborative Portlets, perform the following steps:
On the Oracle Collaboration Suite home page, click Configure Component.
Select Collaborative Portlets from the drop-down list on the Select Component page, and click Continue.
Enter the following values:
apps_virtual.mycompany.comORACLE_HOME\install\portlist.ini – 9401Click Continue. The configuration process may take 10-15 minutes to complete.
Restart the components on ocs_apps2.mycompany.com by running the following commands in ORACLE_HOME\opmn\bin of ocs_apps2.mycompany.com:
opmnctl stopall opmnctl startall
Configure the URLs of the current OracleAS Wireless Instance on each Oracle Collaboration Suite Applications tier. Configuring Oracle Collaboration Suite Mobile Collaboration enables you to define the instance URLs for an application server, or direct an application server to use the URLs defined for the entire OracleAS Wireless site.The steps are as follows:
Access the Oracle Enterprise Manager – Oracle Collaboration Suite Control console.
Click the link for the ocs_apps1.mycompany.com installation.
Click the Wireless link under System Components.
Click the Instance URLs link under Instance Configuration.
Modify the Wireless Instance URLs to point to the load balancer's virtual server name (http://apps_virtual.mycompany.com:80/ptg/rm). Please note that if port 80 is used then it should be explicitly included in the URL as shown.
Repeat the preceding steps for each Oracle Collaboration Suite Applications tier.
Perform the following steps to set up the Oracle Calendar administrator to work through the load balancer:
Add the following lines to the end of $ORACLE_HOME\Apache\Apache\conf\httpd.conf file on the Calendar Server Oracle home:
# Include the Oracle configuration file for Calendar Server include "<full ORACLE_HOME path>/ocad/conf/ocad.conf"
Execute the $ORACLE_HOME\dcm\bin\dcmctl updateconfig command so that changes are processed. This will enable Oracle Calendar administrator.
To configure Calendar Oracle Mobile Data Sync to Use Shared Storage Location, the steps are as follows:
Setup Shared Storage Configuration for Links Database.
Follow the Instructions in the Calendar Administration Guide at "Configuring the Links Database" in Chapter 3 in Oracle Calendar Administrator's Guide.
A problem with the digest login module prevents Oracle Collaboration Suite deployment scenarios using multiple Applications tiers accessed using a load balancer virtual server from working properly. The digest login module issue only occurs in Oracle Collaboration Suite service-to-service operations, when one Oracle Collaboration Suite Application performs a service request against another Oracle Collaboration Suite Application.
This includes deployment scenarios described in Configuring the First Oracle Collaboration Suite Applications Tier with a Load Balancer and Installing Subsequent Instance of Oracle Collaboration Suite Applications.
In this type of installation, multiple Java Virtual Machines (JVMs) are used because Oracle Collaboration Suite Applications tier access may be routed to any one of the Applications tiers by the load balancer. If you are using the service-to-service features of Oracle Collaboration Suite Applications in a multiple Oracle Collaboration Suite Applications tier deployment (these features enable integration between different Oracle Collaboration Suite applications) then you may see errors like the following in a component's application log:
$ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/ocsprovs/OC4J_Portal_default _island_1/application.log , caused by: [SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported response content type "text/html", must be: "text/xml". Response was: <HTML><HEAD><TITLE>401 Unauthorized</TITLE></HEAD><BODY><H1>401 Unauthorized</H1></BODY></HTML>
These problems occur with several applications, including various Oracle Collaboration Suite Portal portlets, Oracle Workspaces integration with Oracle Content Services, and Oracle Collaboration Suite Search. Applications tier access will fail intermittently for these services.
To solve this problem, you must set up a new load balancer virtual server, modify the Oracle Internet Directory Service Registry to use the new virtual server, and then restart the Applications tier, as described in the following steps.
Set Up the Load Balancer
The steps are as follows:
Create a new virtual server in the load balancer, such as ocs_apps_s2s.mycompany.com:80.
Map the virtual server, ocs_apps_s2s.mycompany.com:80, to a node pool that consists the following elements:
n1:port
n2:port
port is the Oracle HTTP Server Listener port. If you have not changed it since installation, then the port is listed in the following path:
$ORACLE_HOME/install/portlist.ini
Set Insert Active Cookie persistence for this node pool.
Modify the Oracle Internet Directory Service Registry
Modify the Oracle Internet Directory Service Registry to use the new virtual server (ocs_apps_s2s.mycompany.com:80). You can modify the entries using Oracle Directory Manager (oidadmin).
Start Oracle Directory Manager and log in to the Oracle Internet Directory.
See Also:
For detailed instructions on using Oracle Directory Manager to modify the Oracle Internet Directory Service Registry, see "Using Oracle Directory Manager to Edit the Oracle Internet Directory Service Registry" in Chapter 7 of Oracle Calendar Administrator's Guide.Navigate to Entry Management , OracleContext, Services and then modify the following entries.
For Calendar, the steps are as follows:
Navigate to
cn=OCAS_xxxxx,cn=VirtualServices,cn=Calendar,cn=Services,cn=OracleContext
Select labeleduri;webserviceurl.
Set it to the following URL:
http://ocs_apps_s2s.mycompany.com/ocws-bin/ocas.fcgi
For Email, the steps are as follows:
Navigate to
cn=webservice,cn=VirtualServices,cn=Email,cn=Services,cn=OracleContext
Select labeleduri;webservice.
Set it to the following URL:
http://ocs_apps_s2s.mycompany.com/oes/ws
For Content Services, the steps are as follows:
Navigate to
cn=Content,cn=VirtualServices,cn=Files,cn=Services,cn=OracleContext
Select labeleduri;s2sauthenticationurl.
Set it to the following URL:
http://ocs_apps_s2s.mycompany.com/content/s2s
Select labeleduri;webservicesurl.
Set it to the following URL:
http://ocs_apps_s2s.mycompany.com/content/ws
Select labeleduri;webdavurl.
Set it to the following URL:
http://ocs_apps_s2s.mycompany.com/content/dav
On one of the Applications tier Enterprise Manager Collaboration Suite Control Console, set IFS.DOMAIN.APPLICATION.ApplicationHost in Oracle Collaboration Suite Control, Content, Domain Properties to the following URL:
http://ocs_apps_s2s.mycompany.com/content/ws
For Real-Time Collaboration, the steps are as follows:
Navigate to
cn=RTC,cn=VirtualServices,cn=RTC,cn=Services,cn=OracleContext
Select labeleduri;integrationserviceurl.
Set it to the following URL:
http://ocs_apps_s2s.mycompany.com/imtapp/OracleRTCService
For Mobile or Wireless, the steps are as follows:
Navigate to
cn=WIRELESS1,cn=VirtualServices,cn=Wireless,cn=Services,cn=OracleContext
Select labeleduri:presencewebserviceurl.
Set it to the following URL:
http://ocs_apps_s2s.mycompany.com/presence/webservices
After you perform all these steps, restart the Applications tiers.
To ensure that it is working as it should, perform the following tests:
Ensure that all components on ocs_apps2.mycompany.com are running.
Run the following command fromORACLE_HOME\opmn\bin to query the status of the components:
opmnctl status
If necessary, run the following command in ORACLE_HOME\opmn\bin:
opmnctl startall
Stop all components on ocs_apps1.mycompany.com by running the following command in ORACLE_HOME\opmn\bin:
opmnctl stopall
Access OracleAS Web Cache and Oracle HTTP Server through the load balancer with the following URL:
http://apps_virtual.mycompany.com
Test the connection to the Oracle Collaboration Suite Database through the load balancer, by accessing the following URL:
http://apps_virtual.mycompany.com/pls/portal/htp.p?cbuf=test
The response should be test. If this succeeds, then the Oracle Collaboration Suite Applications tier can connect to the Oracle Collaboration Suite Database. If this test fails, then examine the ORACLE_HOME\Apache\Apache\logs\error_log file of Oracle HTTP Server to determine the cause.
Test the OracleAS Portal using following URL (ensure that you can log in):
http://apps_virtual.mycompany.com/pls/portal
Verify that content is being cached in OracleAS Web Cache on ocs_apps1.mycompany.com, using Web Cache Administrator. Under Monitoring, click Popular Requests. Select Cached from the Filtered Objects drop-down list, and click Update.
If you accessed OracleAS Portal, portal content will appear. If there is no portal content, open another browser and log in to OracleAS Portal. Return to the Popular Requests page, and click Update to refresh the page content.
Repeat steps 3 through 6, by ensuring that all components on ocs_apps1.mycompany.com are running, and all components on ocs_apps2.mycompany.com are stopped and vice versa.
