5 Installation and Configuration From the Product CD-ROMs on a Two-Tier System

Preconfiguration Validations

Set the DISPLAY environment variable to a valid X Server, and tune the kernel parameters as specified in Chapter 2, " Deployment Requirements". Otherwise, the preconfiguration validation will fail.

Configuring Components on the Database-Tier and Middle-Tier

Table 5-1, "Installation Commands for Components" lists the location of the Oracle home for each component:

1. Log in as the root user on the database-tier.

2. Set up your environment by sourcing the /etc/ora_cc_env file using the following commands:

   # . /etc/ora_cc_env
   # cd $ORACLE_CC_ROOT/ocs
   
   

3. Run the config.sh script in one of the following ways:

   • Using interactive mode

   • Using an input file

Installing Infostores on the Database-Tier in a Single Database

(Use this section only if you want to install Infostores on the database-tier in a single database.)

Install Infostores on the database-tier using the following steps:

1. Log in as the root user on the database-tier.

2. Change directories to the stage area using the following command:

   # cd /<stage area/Disk0
   
   

3. Run the install.sh script using the corresponding commands from Table 5-4, "Installation Commands for Infostores":

   Table 5-4 Installation Commands for Infostores

   Component	Command
   Email Infostore	# ./install.sh -productcd -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=infoemail
   Files Infostore	# ./install.sh -productcd -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=infofiles
   Real-Time Collaboration Infostore	# ./install.sh -productcd -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=infortc
   Single Infostore for Email, Files, and Real-Time Collaboration	# ./install.sh -productcd -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=infoall

   
   

Configuring Infostores on the Database-Tier in a Single Database

Use the following sections to configure the Infostore Oracle homes on the database-tier.

Installing and Configuring Infostores on Real Application Clusters CC

(Use this section only if you want to install Infostores on Real Application Clusters CC.)

Configure Infostores on Real Application Clusters CC with the following steps:

1. When you install and configure Infostores on Real Application Clusters CC, you can install and configure one instance of Real Application Clusters CC on one of the following:

   • the same system where the Infrastructure database is installed

   • a separate system

   If you choose to install and configure Real Application Clusters CC on a separate system, then you must install Utility Pack on at least one system of Real Application Clusters CC. Use the following instructions to install Utility Pack on one node of Real Application Clusters CC:

   1. Log in as the root user.

   2. Mount the gold image export area as described in Chapter 1, "Installation and Configuration Using the Gold Image on a Two-Tier System".

   3. Change directory to the stage area.

   4. Run the install.sh script as follows:

      # ./install.sh -ccutilpack
      
      

2. Install and configure Real Application Clusters CC on the database-tier and all applicable systems. (Follow the instructions in Oracle9i Real Application Clusters Installation and Configuration Guide Release 2 (9.2.0.3) for Linux Intel to install Real Application Clusters CC.)

   Ensure that the domain name is set properly on all the systems of Real Application Clusters CC before installation. The dnsdomainname command should return the proper domain name.

3. Change the default sys, system, and ctxsys user passwords to configure the Oracle Collaboration Suite mid-tier components. Valid passwords for Oracle Collaboration Suite mid-tier components must be at least five characters and contains one number.

4. Proceed to one of the following sections depending on whether you are configuring Email, Files, or Email and Files Infostore.

Preconfiguration Steps for Email Infostore on Real Application Clusters CC

(Use this section only if you are deploying Email Infostore on Real Application Clusters CC.)

Install the umbackend.tar file on the database-tier of all Real Application Clusters CC nodes. The umbackend.tar file is located in the <Collaboration Suite mid-tier Oracle home>/oes directory.

1. Use ftp to transfer the file to the <Real Application Clusters Oracle home>/um directory on each node.

   If the /etc/oraInst.loc file points to an Oracle home other than the RAC Oracle home, rename the file to /etc/oraInst.bak before proceeding to the next step.

2. Untar the file and run the runInstaller.sh script.

3. Run sqlplus as the sys user, and connect to the RAC node as the sysdba user to complete the preconfiguration steps for Email Infostore on Real Application Clusters CC.

   SQL> $ORACLE_HOME/oes/install/sql/install_infra.sql
   

Preconfiguration Steps for Files Infostore on Real Application Clusters CC

(Use this section only if you are deploying Files Infostore on Real Application Clusters CC.)

Ensure that only one instance is running before you configure Files Infostore on Real Application Clusters CC by performing the following:

1. Log in to the database-tier.

2. Change directories to the Real Application Clusters CC Oracle home bin directory.

3. When configuring Files Infostore on Real Application Clusters CC, ensure that only one instance is running on Real Application Clusters. You must shut down all other instance. Use the following instructions to turn off all nodes but one on the Real Application Clusters CC:

   1. Log in as the user who owns the Real Application Clusters CC Oracle home.

   2. Set the environment using the .profile script:

      $ . $HOME/.profile.oradb
      
      

   3. Run the following commands to stop the database instance and other Real Application Clusters CC processes:

      $ /admin/dbcc/3.1.0/ref_config/localdbora stop
      $ /admin/dbcc/3.1.0/ref_config/oracm_gsd stop
      

Configuring Oracle Collaboration Suite Mid-Tier Components Using Interactive Mode

To configure the Oracle Collaboration Suite mid-tier components, use the following commands depending on the components you need to configure:

• For all Oracle Collaboration Suite mid-tier components (Email, Files, Calendar, Ultra Search, Wireless, and Portal), run the following command:

  # ./config.sh -prodver=904 -ocsmt mtall
  
  

• For Email only, run the following command:

  # ./config.sh -prodver=904 -ocsmt email
  
  

• For Files only, run the following command:

  # ./config.sh -prodver=904 -ocsmt files
  
  

• For Real-Time Collaboration only, run the following command:

  # ./config.sh -prodver=904 -ocsmt rtc
  
  

• For Calendar only, run the following command:

  # ./config.sh -prodver=904 -ocsmt calweb
  
  

  The -ocsmt calweb option only configures Calendar middle-tier components

You can use more than one of the options in the same command. For example, if you want to configure Email and Files, run the following command:

# ./config.sh -prodver=904 -ocsmt email -ocsmt files

Configuring Oracle Collaboration Suite Mid-Tier Components Using An Input File

To configure the Oracle Collaboration Suite middle-tier components, use the following command to configure Oracle Collaboration Suite CC with input parameters (except passwords) specified in the parameter file:

1. Copy the /admin/mwcc/ocs/904/config_inputfile.template file to another file, such as config_inputfile.

2. Edit the config_inputfile file and specify the parameters needed for the specific configuration you need to carry out. (See Appendix A, " Input Parameters for config.sh" for descriptions of these parameters.)

3. Note that the passwords in the input file will not be honored because of security reasons. You will be prompted for passwords during interactive mode when you run the config.sh script.

4. Run the config.sh script with the appropriate options to configure Oracle Collaboration Suite CC. For example, to configure Email and Files, use the following command:

   # ./config.sh -prodver=904 -ocsmt email -ocsmt files -propfile  <propfile name>
   

   
   

   See Also: The parameters required for configuration can be supplied by an input file or by interactive mode. See Appendix A, " Input Parameters for config.sh" for usage notes for running the config.sh script.

   
   

5. If any parameter is missing or in error, the config.sh will print out an error message and will not continue with the configuration. The user can correct the error in the input file and re-run the configuration.

The Oracle Collaboration Suite mid-tier components will be configured and will be brought up at the end of configuration.

Additional Configuration Steps for Files on Real Application Clusters CC

(Use this section for Files Infostore on Real Application Clusters CC only.)

Use the following instructions to configure Real Application Clusters CC for Files Infostore on the middle-tier:

1. (TNS load balancing only) Log in to the Enterprise Management Web site to set the IFS.SERVICE.JDBC.DatabaseUrl property in the following format:

   jdbc:oracle:oci8:@<service name>
   
   

   where <service name> refers to the TNS entry in the tnsnames.ora file of the middle-tier Oracle home.

2. Change the entry in the tnsnames.ora file of the middle-tier Oracle home to contain the failover and load balance. For example:

   <service name> =
   (DESCRIPTION = (ADDRESS_LIST = (LOAD_BALANCE = YES) (FAILOVER = ON) 
   (ADDRESS = (PROTOCOL =TCP)(HOST = <fully qualified host name for rac node1>)(PORT = <port number>))
   (ADDRESS = (PROTOCOL =TCP)(HOST = <fully qualified host name for rac node2>)(PORT 	= <port number>))
   .
   .
   .
   (ADDRESS = (PROTOCOL =TCP)(HOST = <fully qualified host name for rac nodeN>)(PORT 	= <port number>))
   )
   (CONNECT_DATA = (SERVICE_NAME = <global_db_name>) (FAILOVER_MODE = (TYPE = SELECT)(METHOD = BASIC)(RETRIES = 20)(DELAY = 20))
   
   

3. On the middle-tier, edit the ifs/common/registry.xml file to add the following entry:

   <Instance>
     <DatabaseUrl>jdbc:oracle:oci8:@tnsentry</DatabaseUrl
     <Domain>ifs://DBHOME:1521:dbservice:ifssys</Domain>
     <DomainType>files</DomainType>
     <Registered>1018925008096</Registered>
     <LastStarted>1028329087966</LastStarted>
     <LastModified>1028330926700</LastModified>
     <Ports>
   </Instance>
   
   

4. Restart the database instance and other Real Applications Clusters CC processes on all the Real Application Clusters CC nodes using the following instructions:

   1. Log in as the user who owns the Oracle home for Real Application Clusters CC.

   2. Set the environment using the .profile script:

      $ . $HOME/.profile.oradb
      
      

   3. Run the following commands to restart the database instance and other Real Application Clusters CC processes:

      $ /admin/dbcc/3.1.0/ref_config/localdbora stop
      $ /admin/dbcc/3.1.0/ref_config/oracm_gsd stop
      $ /admin/dbcc/3.1.0/ref_config/oracm_gsd start
      $ /admin/dbcc/3.1.0/ref_config/localdbora start
      
      

5. Repeat step 4 for all nodes of the Real Application Clusters CC.

6. Log in to the middle-tier.

   1. Restart Files as the root user using the following commands:

      $ ifsctl stop
      $ ifsctl start
      
      

   2. Restart opmn as the owner of the Oracle home using the following commands:

      $ opmnctl stop
      $ opmnctl start
      
      

   3. Restart EMD as the owner of the Oracle home using the following commands:

      $ emctl stop
      $ emctl start