Skip Headers

Oracle® Collaboration Suite Certified Configuration Deployment and Cloning Guide
Release 9.0.4.1 for Linux x86
Part No. B12145-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous Next  

3 Installation and Configuration Using the Gold Image on a Two-Tier System

This chapter describes how to install and configure an Oracle Collaboration Suite Certified Configuration (Oracle Collaboration Suite CC) from the gold image on a two-tier system.

Oracle Collaboration Suite components are pre-installed and pre-configured in the gold image. Using the gold image when deploying Oracle Collaboration Suite takes less time than using product CDs.


Note:

If you want to deploy Infostores on Oracle9i Real Application Clusters Certified Configuration (Real Application Clusters CC), see Chapter 5, " Installation and Configuration From the Product CD-ROMs on a Two-Tier System" for instructions. You cannot use the gold image to deploy Oracle Collaboration Suite CC on Real Application Clusters CC.

This chapter contains the following sections:

Access to the Gold Image

When you perform the first gold image installation, the system needs to be clean with no previous Oracle homes configured or Oracle processes running.

Before installing using the gold image, you must make the gold image stage area accessible on your system. The gold image stage area can be mounted from a remote machine using nfs, or copied onto the local machine and extracted in the location described below.

Oracle Collaboration Suite CC expects the gold image stage area to be made available in the /stage/ocs904 directory. If you want to put the gold image in another directory, you must set the CC_STAGE_AREA environment variable to that location, as follows:

# CC_STAGE_AREA=/mystage/gold
# export CC_STAGE_AREA

Creating a Stage Area Using Oracle Collaboration Suite CC Gold Image CDs

For a two-tier deployment, if you are creating a stage area using Oracle Collaboration Suite CC gold image CDs, copy the files from all the CDs into the stage directory. Ensure you have about 20 GB of free disk space in the stage directory. Run following commands:

# cat OCS9041_CC_TwoTier_a* > ocs9041cc_twotier_images.tar
# rm OCS9041_CC_TwoTier_a*
# tar xvf ocs9041cc_twotier_images.tar

For a single-tier deployment, if you are creating a stage area using Oracle Collaboration Suite CC gold image CDs, copy the files from all the CDs into the stage directory. Ensure you have about 12 GB of free disk space in the stage directory. Run following commands:

# cat OCS9041_CC_Single_Tier_a* > ocs9041cc_singletier_images.tar
# rm OCS9041_CC_Single_Tier_a*
# tar xvf ocs9041cc_singletier_images.tar

Overview of a Two-Tier Deployment

A two-tier deployment involves deploying the following components:


On the database-tier:

On the middle-tier:

Installing Database-Tier Components

Install database-tier components using the following:

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

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

    # cd /<stage area/Disk0
    
    
  3. Run the install.sh script with the following options:

    # ./install.sh -goldimage -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=infradb,infoemail,infofiles,infortc,calendar
    
    

This installs Infrastructure database, Email Infostore, Files Infostore, Real-Time Collaboration Infostore, and Calendar Server in their respective Oracle homes if the respective partitions are present.

If you want to install Infostores on the database-tier as a single database, run the install.sh script with the folloing options:

# ./install.sh -goldimage -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=infradb,infoall,calendar

Example 3-1 Deriving $ORACLE_BASE and User ID of the Installation Owner on the Database-Tier

For example, if the customer ID is ‘orcl’ and the instance type is ‘p’, then:

  • Infrastructure database will be installed in the /porcls/oracle directory and owned by user orporcls

  • Email Infostore will be installed in the /porclu/oracle directory and owned by user orporclu

  • Files Infostore will be installed in the /porclf/oracle directory and owned by user orporclf

  • Real-Time Collaboration Infostore will be installed in the /porclr/oracle directory and owned by user orporclr

  • Calendar Server will be installed in the /porclc/collab directory and owned by user iaporclc

  • Single Infostore (where all component Infostores are on a single database) will be installed in the /porcla/oracle directory and owned by user orporcla


Note:

The Infostore database installed using the gold image contains schema for all the OCS components (Email, Files, Real-Time Collaboration), but only the schema of the configured components will be used.

Installing Mid-Tier Components

Install mid-tier components using the following:

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

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

    # cd /<stage area/Disk0
    
    
  3. Run the install.sh script with the following options:

    # ./install.sh -goldimage -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=inframt,ocsmt
    
    

This installs Infrastructure mid-tier and Oracle Collaboration Suite middle-tier in their respective Oracle homes.

Example 3-2 Deriving $ORACLE_BASE and User ID of the Installation Owner on the Middle-Tier

For example, if the customer ID is ‘orcl’ and the instance type is ‘p’, then:

  • Infrastructure mid-tier (oidsso) will be installed in the /porcls/idm directory and owned by user iaporclu

  • Oracle Collaboration Suite middle-tier will be installed in the /porclu/collab directory and owned by user iaporclu

Configuring Components on the Database-Tier and Middle-Tier


Note:

You must configure the components in the following order.
  1. Infrastructure database on the database-tier

  2. Infrastructure mid-tier on the middle-tier

  3. Apply patch ARU 4693083 for bug number 3119475 on both the Infrastructure database Oracle home and Infrastructure mid-tier Oracle home. For both Oracle homes, run the patch_server.sh only.

  4. Email Infostore on the database-tier (if you are deploying Email)

  5. Files Infostore on the database-tier (if you are deploying Files)

  6. Real-Time Collaboration Infostore on the database-tier (if you are deploying Real-Time Collaboration)

  7. Calendar Server on the database-tier (if you are deploying Calendar)

  8. Oracle Collaboration Suite mid-tier components on the middle-tier


This section details configuring the Oracle homes of different components on the database-tier. Table 3-1, "Oracle Home Locations" lists the location of the Oracle home for each component.

Table 3-1 Oracle Home Locations

Oracle Home Server Tier Location
Infrastructure database Database-tier /XYYYYs/oracle/product/infra_902
Infrastructure mid-tier Middle-tier /XYYYYs/idm/product/infra_902
Email Infostore Database-tier /XYYYYu/oracle/product/920
Files Infostore Database-tier /XYYYYf/oracle/product/920
Real-Time Collaboration Infostore Database-tier /XYYYYr/oracle/product/920
Calendar Server Database-tier /XYYYYc/collab/product/ocsmt_904
Oracle Collaboration Suite mid-tier Middle-tier /XYYYYu/collab/product/ocsmt_904

Configure components on the database-tier using the following

  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. Set the DISPLAY variable to the valid X server.

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

    • Using interactive mode

    • Using an input file

Configuring Components Using Interactive Mode

Use the corresponding commands from Table 3-2, "Configuration Commands For Interactive Mode" to configure components using interactive mode:

Table 3-2 Configuration Commands For Interactive Mode

Component Server Tier Configuration Command
Infrastructure database Database-tier # ./config.sh -prodver=904 -infra dbonly
Infrastructure mid-tier Middle-tier # ./config.sh -prodver=904 -infra oidsso
Email Infostore Database-tier # ./config.sh -prodver=904 -infostore email
Files Infostore Database-tier # ./config.sh -prodver=904 -infostore files
Real-Time Collaboration Infostore Database-tier # ./config.sh -prodver=904 -infostore rtc
Single Infostore for Email, Files, and Real-Time Collaboration Database-tier # ./config.sh -prodver=904 -infostore all
Calendar Server Database-tier # ./config.sh -prodver=904 -ocsmt caldb
Oracle Collaboration Suite mid-tier components (Email, Files, Real-Time Collaboration, Calendar Webclient, Ultra Search, Wireless, and Portal) Middle-tier # ./config.sh -prodver=904 -ocsmt mtall
Oracle Collaboration Suite mid-tier components (Email only) Middle-tier # ./config.sh -prodver=904 -ocsmt email
Oracle Collaboration Suite mid-tier components (Files only) Middle-tier # ./config.sh -prodver=904 -ocsmt files
Oracle Collaboration Suite mid-tier components (Real-Time Collaboration only) Middle-tier # ./config.sh -prodver=904 -ocsmt rtc
Oracle Collaboration Suite mid-tier components (Calendar only) Middle-tier # ./config.sh -prodver=904 -ocsmt calweb

Configuring Components Using An Input File

Use the following procedure to configure components 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 using the corresponding commands from Table 3-2, "Configuration Commands For Interactive Mode" and appending the following to the command:

    -propfile <propfile name>
    

    Example 3-3 Configuration Command for Input File

    For example, to configure Infrastructure database using an input file, use the following command:

    # ./config.sh -prodver=904 -infra dbonly -propfile <propfile name>
    
    
  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 component will be configured and will be brought up at the end of configuration.


Important:

You must perform the steps in Chapter 6, " Post-Configuration " to complete the deployment.