|
Oracle® Collaboration Suite Certified Configuration Deployment and Cloning Guide
Release 9.0.4.1 for Linux x86 Part No. B12145-01 |
|
|
|
|
This chapter describes how to install and configure an Oracle Collaboration Suite Certified Configuration (Oracle Collaboration Suite CC) from the gold image on a single-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.
This chapter contains the following sections:
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
A single-tier deployment involves installing and configuring all the components on a single system. The following components are configured:
Infrastructure
Single Infostore for Email, Files, and Real-Time Collaboration
Oracle Collaboration Suite mid-tier components (Email, Files, Real-Time Collaboration, Calendar, Ultra Search, Wireless, and Portal)
Install components on the single-tier using the following:
Log in as the root user on the single-tier.
Change directories to the gold image stage area using the following command:
# cd /<stage area/Disk0
Run the install.sh script with the following options:
# ./install.sh -goldimage -custid=<4 letter customer id> -instancetype={t|d|p} -installtype=singletier
This installs Infrastructure, Email Infostore, Files Infostore, Real-Time Collaboration Infostore, and Oracle Collaboration Suite mid-tier components in their respective Oracle homes.
|
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. |
Configure components on the single-tier using the following:
Log in as the root user on the single-tier.
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
Set the DISPLAY variable to the valid X server.
Run the config.sh script in one of the following ways:
Using interactive mode
Using an input file
Use the corresponding commands from Table 4-1, "Configuration Commands For Interactive Mode on the Single-Tier" to configure components using interactive mode:
Table 4-1 Configuration Commands For Interactive Mode on the Single-Tier
| Component | Configuration Command |
|---|---|
| Infrastructure | # ./config.sh -prodver=904 -infra all
|
| Email Infostore | # ./config.sh -prodver=904 -infostore email
|
| Files Infostore | # ./config.sh -prodver=904 -infostore files
|
| Real-Time Collaboration Infostore | # ./config.sh -prodver=904 -infostore rtc
|
| Single Infostore for Email, files, and Real-Time Collaboration | # ./config.sh -prodver=904 -infostore all
|
| Oracle Collaboration Suite mid-tier components (Email, Files, Calendar, Ultra Search, Wireless, and Portal) | # ./config.sh -prodver=904 -ocsmt stall
|
| Oracle Collaboration Suite mid-tier components (Email only) | # ./config.sh -prodver=904 -ocsmt email
|
| Oracle Collaboration Suite mid-tier components (Files only) | # ./config.sh -prodver=904 -ocsmt files
|
| Oracle Collaboration Suite mid-tier components (Real-Time Collaboration only) | # ./config.sh -prodver=904 -ocsmt rtc
|
| Oracle Collaboration Suite mid-tier components (Calendar only) | # ./config.sh -prodver=904 -ocsmt calall
|
Use the following procedure to configure components with input parameters (except passwords) specified in the parameter file:
Copy the /admin/mwcc/ocs/904/config_inputfile.template file to another file, such as config_inputfile.
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.)
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.
Run the config.sh script using the corresponding commands from Table 4-1, "Configuration Commands For Interactive Mode on the Single-Tier" and appending the following to the command:
-propfile <propfile name>
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 components 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. |