|
Oracle® Collaboration Suite Certified Configuration Deployment and Cloning Guide
Release 9.0.3.1 for Linux x86 Part No. B10635-04 |
|
|
|
|
Oracle® Collaboration Suite Certified Configuration Deployment and Cloning Guide
Release 9.0.3.1 for Linux x86 Part No. B10635-04 |
|
|
|
|
This chapter describes how to install and configure an Oracle Collaboration Suite Certified Configuration (Oracle Collaboration Suite CC) from the gold image.
Oracle Collaboration Suite components are pre-installed and pre-configured in the gold image. When you install and configure Oracle Collaboration Suite CC using the gold image, the installation and configuration time is significantly less than the installation and configuration time when using the product CDs. The pre-installed and pre-configured gold image saves you time when deploying Oracle Collaboration Suite.
Oracle Collaboration Suite CC is configured to support the following 9 languages: Brazilian Portuguese, French, German, Italian, Japanese, Korean, Simplified Chinese, Spanish, and Traditional Chinese. You can configure additional language support using the Product Configuration tool.
|
Note: If you want to deploy Infostores on Oracle9i Real Application Clusters Certified Configuration (Real Application Clusters CC), see Chapter 4, " Installation and Configuration From the Product CD-ROMs" 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:
In addition to the requirements detailed in Chapter 2, " Deployment Requirements", ensure you meet the following prerequisites before you install and configure Oracle Collaboration Suite CC.
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/ocs903 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
You will need the following information before installing and configuring Oracle Collaboration Suite CC:
4-letter customer ID
instance type (test, development, or production)
install type (singletier, midtier, or dbtier)
|
See Also: For details on all installation and configuration requirements, see Chapter 2, " Deployment Requirements". |
|
Note: You are asked to log in as theroot user to start installation, configuration, or cloning. However, internally, all the operations are done as a normal operating system user (not the root user) who owns or will own the Oracle software except when it is mandatory to perform operations as the root user.
After you complete the installation and configuration of Oracle Collaboration Suite CC, you must perform maintenance and management operations using a normal operating system user who is the owner of a particular Oracle home, unless otherwise required by the base product itself. |
A two-tier deployment involves deploying the following components:
Infrastructure database
Email Infostore (needed if you are deploying Email)
Files Infostore (needed if you are deploying Files)
Calendar Server (needed if you are deploying Calendar)
Infrastructure mid-tier - Oracle Internet Directory (OID) and Single Sign-On (SSO) server
Oracle Collaboration Suite middle-tier (Email, Files, Calendar, Ultra Search, Wireless, and Portal)
|
Note: You must first configure Infrastructure database on the database-tier, then Infrastructure mid-tier on the middle-tier before configuring other components. |
Install database-tier components using the following:
Log in as the root user on the database-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=dbtier
This installs Infrastructure database, Email Infostore, Files Infostore, and Calendar Server in their respective Oracle homes if the respective partitions are present.
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
Calendar Server will be installed in the /porclc/collab directory and owned by user iaporclc
Install mid-tier components using the following:
Log in as the root user on the middle-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=midtier
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
This section details configuring the Infrastructure database Oracle home on the database-tier in the /XYYYYs/oracle/product/infra_902 directory. Configure Infrastructure database on the database-tier using the following:
Log in as the root user on the database-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 following command to configure the Infrastructure database in interactive mode:
# ./config.sh -infra dbonly
Use the following procedure to configure the Infrastructure database with input parameters (except passwords) specified in parameter file:
Copy the $ORACLE_CC_ROOT/ocs/9.0.3/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 C, " 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 as follows:
# ./config.sh -infra dbonly -propfile <propfile name>
|
See Also: The parameters required for configuration can be supplied by an input file or by interactive mode. See Appendix B, " Usage Notes for config.sh " for usage notes for running theconfig.sh script.
|
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 Infrastructure database will be configured and will be brought up at the end of configuration.
Check the configuration log file located in the $ORACLE_CC_ROOT/ocs/9.0.3/logs/config directory for any errors.
To verify that the Infrastructure database is correctly installed and configured, log in to the system as the user who owns the Infrastructure database Oracle home. Source the profile and choose this Oracle home. Log in to the Infrastructure database as the SYS user. The login should be successful.
|
Note: You must have configured:
before you configure Infrastructure mid-tier on the middle-tier. |
This section details configuring the Infrastructure mid-tier Oracle home on the middle-tier in the /XYYYYs/idm/product/infra_902 directory. Configure Infrastructure mid-tier on the middle-tier using the following:
Log in as the root user on the middle-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 following command to configure Infrastructure mid-tier in interactive mode:
# ./config.sh -infra oidsso
Use the following command to configure Infrastructure middle-tier with input parameters (except passwords) specified in parameter file:
Copy the $ORACLE_CC_ROOT/ocs/9.0.3/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. The config_inputfile file contains descriptions and default values for each parameter. (See Appendix C, " 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 with the appropriate options to configure Oracle Collaboration Suite CC.
# ./config.sh -infra oidsso -propfile <propfile name>
|
See Also: The parameters required for configuration can be supplied by an input file or by interactive mode. See Appendix B, " Usage Notes for config.sh " for usage notes for running theconfig.sh script.
|
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 Infrastructure mid-tier will be configured and will be brought up at the end of configuration.
Check the configuration log file located in the $ORACLE_CC_ROOT/ocs/9.0.3/logs/config directory for any errors.
To verify that the Infrastructure mid-tier is correctly installed and configured, go to the following URL: http://<hostname>.<domainname>:7777/oiddas. Log in as the orcladmin user with the password as specified during configuration. The login should be successful.
|
Note: You must have configured:
before you configure the Email and Files Infostores on the database-tier. |
This section details configuring:
Email Infostore Oracle home in the /XYYYYu/oracle/product/920 directory
Files Infostore Oracle home in the /XYYYYf/oracle/product/920 directory
Configure Email and Files Infostore on the database-tier using the following:
Log in as the root user on the database-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 following command to configure both Email and Files Infostores in interactive mode:
# ./config.sh -infostore email -infostore files
Use the following command to only configure only Email Infostore in interactive mode:
# ./config.sh -infostore email
Use the following command to only configure only Files Infostore in interactive mode:
# ./config.sh -infostore files
Use the following command to configure both Email and Files Infostores with input parameters (except passwords) specified in parameter file:
Copy the $ORACLE_CC_ROOT/ocs/9.0.3/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 C, " 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 with the appropriate options to configure Oracle Collaboration Suite CC. For example, to configure Email and Files Infostores, use the following:
# ./config.sh -infostore email -infostore files -propfile <propfile name>
|
See Also: The parameters required for configuration can be supplied by an input file or by interactive mode. See Appendix B, " Usage Notes for config.sh " for usage notes for running theconfig.sh script.
|
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 Email and Files Infostores will be configured and will be brought up at the end of configuration.
Check the configuration log file located in the $ORACLE_CC_ROOT/ocs/9.0.3/logs/config directory for any errors.
To verify that the Email and Files Infostores are correctly installed and configured, log in to the system as the user who owns the Email and Files Infostores Oracle home. Source the profile and choose this Oracle home. Log in to the Email and Files Infostores as the SYS user. The login should be successful.
|
Note: You must have configured:
before you configure Calendar Server on the database-tier. |
This section details configuring Calendar Server Oracle home in the /XYYYYc/collab/product/ocsmt_903 directory.
Configure Calendar Server on the database-tier using the following:
Log in as the root user on the database-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 following command to configure Calendar Server in interactive mode:
# ./config.sh -ocsmt caldb
Use the following command to configure Calendar Server with input parameters (except passwords) specified in parameter file:
Copy the $ORACLE_CC_ROOT/ocs/9.0.3/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 C, " 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 with the appropriate options to configure Oracle Collaboration Suite CC.
# ./config.sh -ocsmt caldb -propfile <propfile name>
|
See Also: The parameters required for configuration can be supplied by an input file or by interactive mode. See Appendix B, " Usage Notes for config.sh " for usage notes for running theconfig.sh script.
|
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 Calendar Server will be configured and will be brought up at the end of configuration.
Check the configuration log file located in the $ORACLE_CC_ROOT/ocs/9.0.3/logs/config directory for any errors.
To verify that the Calendar Server is correctly installed and configured:
Log in as the owner of the Oracle home for Calendar Server.
Source the profile for this Oracle home by using the following command:
$ . ./profile_iascc_env
Change to the root user by using the following command:
$ su
Change directory to $ORACLE_HOME/calendarserver/bin:
# cd $ORACLE_HOME/calendarserver/bin
Run the unistatus tool as follows to check the status of Calendar Server:
# ./unistatus
|
Note: You must have configured:
before you configure Oracle Collaboration Suite mid-tier components on the middle-tier. |
This section details configuring Oracle Collaboration Suite mid-tier components Oracle home in the /XYYYYc/collab/product/ocsmt_903 directory.
|
Note: The letter ‘c’ in/XYYYYc should be replaced by the following letters for customer deployments:
|
Configure Oracle Collaboration Suite mid-tier components on the middle-tier by using the following steps:
Log in as the root user on the middle-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
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 -ocsmt email -ocsmt files -ocsmt calweb
For Email only, run the following command:
# ./config.sh -ocsmt email
For Files only, run the following command:
# ./config.sh -ocsmt files
For Calendar only, run the following command:
# ./config.sh -ocsmt calweb
The -ocsmt calweb option only configures Calendar mid-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 Infostores, run the following command:
# ./config.sh -ocsmt email -ocsmt files
To configure the Oracle Collaboration Suite mid-tier components, use the following command to configure Oracle Collaboration Suite CC with input parameters (except passwords) specified in parameter file:
Copy the $ORACLE_CC_ROOT/ocs/9.0.3/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 C, " 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 with the appropriate options to configure Oracle Collaboration Suite CC. For example, to configure Email and Files Infostore, use the following command:
# ./config.sh -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 B, " Usage Notes for config.sh " for usage notes for running theconfig.sh script.
|
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. Note that Ultra Search, Wireless, and Portal are also configured (except when doing a calweb configuration only.)
Check the configuration log file located in the $ORACLE_CC_ROOT/ocs/9.0.3/logs/config directory for any errors.
To verify that the Oracle Collaboration Suite middle-tier Email component is correctly installed and configured, go to the following URL: http://<hostname>.<domainname>:7778/um/traffic_cop. Log in as the initial Email user specified during configuration. The login should be successful.
To verify that the Oracle Collaboration Suite middle-tier Files component is correctly installed and configured. Set ORACLE_HOME to point to the Oracle Collaboration Suite mid-tier Oracle home and start up the Files process as the root user by going to $ORACLE_HOME/ifs/files/bin/ifsctl start. Also go to the following URL: http://<hostname>.<domainname>:7778/files/app/AdminLogin. Log in as site_admin with the password specified during configuration. The login should be successful.
To verify that the Oracle Collaboration Suite middle-tier Calendar component is correctly installed and configured, go to the following URL: http://<hostname>.<domainname>:7778. Click on the Calendar Administration link from this page. Log in with the SYSOP password specified during configuration. (Specify node ID as 1.) The login should be successful. Click on the Users link and create a Calendar user. (Note that this user must exist in OID.)
Also, go to the following URL http://<hostname>.<domainname>:7778/calendar. Log in as the Calendar user you created in the previous step.
To verify that the Oracle Collaboration Suite middle-tier Portal component is correctly installed and configured, go to the following URL: http://<hostname>.<domainname>:7778/pls/portal. Click on the Login link and log in as ‘portal’ with the password specified during configuration. The login should be successful.
A single-tier deployment involves installing and configuring all the components on a single node. The following components are configured:
Infrastructure
Email Infostore
Files Infostore
Oracle Collaboration Suite mid-tier components (Email, Files, 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, and Oracle Collaboration Suite mid-tier components in their respective Oracle homes.
Example 3-3 Deriving $ORACLE_BASE and User ID of the Installation Owner on the Single-Tier
For example, if the customer ID is ‘orcl’ and the instance type is ‘d’, then:
Infrastructure will be installed in the /dorcls/oracle directory and owned by user iadorcls
Email Infostore will be installed in the /dorclu/oracle directory and owned by user ordorclu
Files Infostore will be installed in the /dorclf/oracle directory and owned by user ordorclf
Oracle Collaboration Suite mid-tier components (Email, Files, and Calendar) will be installed in the /dorclu/collab directory and owned by user iadorclu
Configure Infrastructure 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 following command to configure Infrastructure in interactive mode:
# ./config.sh -infra all
Use the following command to configure Infrastructure with input parameters (except passwords) specified in parameter file:
Copy the $ORACLE_CC_ROOT/ocs/9.0.3/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 C, " 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 with the appropriate options to configure Oracle Collaboration Suite CC.
# ./config.sh -infra all -propfile <propfile name>
|
See Also: The parameters required for configuration can be supplied by an input file or by interactive mode. See Appendix B, " Usage Notes for config.sh " for usage notes for running theconfig.sh script.
|
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 Infrastructure will be configured and will be brought up at the end of configuration.
Check the configuration log file located in the $ORACLE_CC_ROOT/ocs/9.0.3/logs/config directory for any errors.
To verify that the Infrastructure is correctly installed and configured, go to the following URL: http://<hostname>.<domainname>:7777/oiddas. Log in as the orcladmin user with the password as specified during configuration. The login should be successful.
Configure Email and Files Infostores 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 following command to configure both Email and Files Infostores in interactive mode:
# ./config.sh -infostore email -infostore files
Use the following command to only configure Email Infostore in interactive mode:
# ./config.sh -infostore email
Use the following command to only configure Files Infostore in interactive mode:
# ./config.sh -infostore files
Use the following command to configure both Email and Files Infostores with input parameters (except passwords) specified in parameter file:
Copy the $ORACLE_CC_ROOT/ocs/9.0.3/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 C, " 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 with the appropriate options to configure Oracle Collaboration Suite CC. For example, to configure Email and Files Infostores, use the following command:
# ./config.sh -infostore email -infostore files -propfile <propfile name>
|
See Also: The parameters required for configuration can be supplied by an input file or by interactive mode. See Appendix B, " Usage Notes for config.sh " for usage notes for running theconfig.sh script.
|
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 Email and Files Infostores will be configured and will be brought up at the end of configuration.
Check the configuration log file located in the $ORACLE_CC_ROOT/ocs/9.0.3/logs/config directory for any errors.
To verify that the Email and Files Infostores are correctly installed and configured, log in to the system as the user who owns the Email and Files Infostores Oracle home. Source the profile and choose this Oracle home. Log in to the Email and Files Infostores as the SYS user. The login should be successful.
|
Note: The letter ‘c’ in/XYYYYc should be replaced by the following letters for customer deployments:
|
Configure Oracle Collaboration Suite mid-tier 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 one of the following commands depending on the components you need to configure:
For all mid-tier components (Email, Files, and Calendar, including Calendar Server), run the following command:
# ./config.sh -ocsmt all
For Email only, run the following command:
# ./config.sh -ocsmt email
For Files only, run the following command:
# ./config.sh -ocsmt files
For Calendar only, run the following command:
# ./config.sh -ocsmt calall
You can use more than one of the options in the same command. For example, if you want to configure Email and Files Infostores, run the following command:
# ./config.sh -ocsmt email -ocsmt files
Use the following command to configure Oracle Collaboration Suite mid-tier components with input parameters (except passwords) specified in parameter file:
Copy the $ORACLE_CC_ROOT/ocs/9.0.3/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 C, " 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 with the appropriate options to configure Oracle Collaboration Suite CC. For example, to configure all the mid-tier components, use the following command:
# ./config.sh -ocsmt all -propfile <propfile name>
|
See Also: The parameters required for configuration can be supplied by an input file or by interactive mode. See Appendix B, " Usage Notes for config.sh " for usage notes for running theconfig.sh script.
|
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.
Check the configuration log file located in the $ORACLE_CC_ROOT/ocs/9.0.3/logs/config directory for any errors.
To verify that the Oracle Collaboration Suite middle-tier Email component is correctly installed and configured, go to the following URL: http://<hostname>.<domainname>:7778/um/traffic_cop. Log in as the initial Email user specified during configuration. The login should be successful.
To verify that the Oracle Collaboration Suite middle-tier Files component is correctly installed and configured, start up the Files process as the root user by going to $ORACLE_HOME/ifs/files/bin/ifsctl start. Also go to the following URL: http://<hostname>.<domainname>:7778/files/app/AdminLogin. Log in as site_admin with the password specified during configuration. The login should be successful.
To verify that the Oracle Collaboration Suite middle-tier Calendar component is correctly installed and configured, go to the following URL: http://<hostname>.<domainname>:7778. Click on the Calendar Administration link from this page. Log in with the SYSOP password specified during configuration. (Specify node ID as 1.) The login should be successful. Click on the Users link and create a Calendar user. (Note that this user must exist in OID.)
Also, go to the following URL http://<hostname>.<domainname>:7778/calendar. Log in as the Calendar user you created in the previous step.
To verify that the Oracle Collaboration Suite middle-tier Portal component is correctly installed and configured, go to the following URL: http://<hostname>.<domainname>:7778/pls/portal. Click on the Login link and log in as ‘portal’ with the password specified during configuration. The login should be successful.
You must complete the following post-configuration tasks.
Use the following to perform post-configuration for Files.
The site_admin user password for Files can be modified by going through the Files admin login interface. The default password for this user from a gold image installation is welcome1.
Use the following to change the administrative user for Files:
Start the Files processes. (You must do this before you can log into the admin login interface.)
Using EM, start up the OC4J_iFS_files component and the Files local domain components.
Connect to http://<hostname.domain>:7778/files/app/AdminLogin and log in as site_admin/<current_pwd>.
Click the Preferences link on the top right corner of the browser.
Click the Password link on the left side of the browser.
Enter the old password, new password, and confirm the new password. Then click Apply.
You have changed the site_admin user password for the site.
You must modify the following credential managers for Files: SmallServiceConfiguration, MediumServiceConfiguration, and LargeServiceConfiguration. This procedure enables Files to connect to OID to retrieve authentication information.
Each time you run Oracle9iFS Credential Manager Configuration Assistant (ifscmca), you can only modify one existing Credential Manager. Use the following steps to run ifscmca. Run ifscmca three times, once for each credential manager.
Run Oracle9iFS Credential Manager Configuration Assistant. ($ORACLE_HOME/ifs/files/bin/ifscmca.)
The Welcome window opens.
Click Next.
The Login to Oracle9iFS window opens.
Enter the iFS schema name (ifssys) schema password, Files Infostore database host name, listener port number, and the database service name (TNS alias). Then, click Next.
The Existing Credential Managers window opens, listing the following existing Credential Managers: SmallServiceConfiguration, MediumServiceConfiguration, and LargeServiceConfiguration.
Select the entry OiD under the Configuration Manager, click Modify, then click Next.
The OiD Login window opens.
Ensure that the OiD host name, port number, and password entries are correct. Then, click Next.
The wizard connects before going on to the next screen to ensure that the information you entered is valid.
The Supported Functions window opens.
Click Next.
The Authentication Types window opens.
Click Next.
The Oracle9iFS Specific Passwords window opens.
Click Next.
The Subscribers window opens.
Click Next.
The Summary window opens.
Click Configure.
The configuration begins. A task completion window opens to inform you when the configuration is complete (typically within 30 minutes).
Repeat this procedure until all three Credential Managers are configured.
Oracle Files is configured to use ifssys as the schema name and welcome1 as the password. For enhanced security, use the following to change the ifssys schema password:
Use ifsctl to shut down Files, and use dcmctl stop -co OC4J_iFS_files to shut down OC4J_iFS_files.
Log into the Files Infostore as the system user and change the ifssys schema password. For example:
$ sqlplus system/<pwd>@torclf.us.oracle.com > alter user ifssys identified by <new_password>; > exit;
Log into OID using orcladmin as the oidadmin user and navigate to the following DN:
cn=OracleContext-> cn=Products-> cn=IFS-> orclApplicationCommonName=<files_infostore_host:1721:tns_service_name:ifssys>
Change the user password attribute at the bottom of the right hand pane. Enter the new password, then click Apply.
Edit the EM targets.xml file in the EMD_Oracle_Home/sysman/emd/target.xml directory.
Look for <Target TYPE="oracle_ifs"...
Change <Property NAME="SchemaPassword" VALUE="f7adf52b5a20c7bd" ENCRYPTED="TRUE"/> to <Property NAME="SchemaPassword" VALUE="<new pwd in plain text" ENCRYPTED="FALSE"/>
Restart EM.
You have changed the Files Infostore schema password. Use the new password when you next run ifsctl.
Use the following to enable Portal for Oracle Collaboration Suite components:
Log into the middle-tier node (in the case of a two-tier deployment) as the owner of the mid-tier Oracle home.
Source the profile for this Oracle home by using the following command:
$ . ./profile_iascc_env
On the Oracle Collaboration Suite mid-tier, navigate to the $ORACLE_HOME/wireless/server/classes/oracle/panama/marconi directory.
Edit the marconi.config file to replace token values in %APPLICATION_SERVER_HOST% and %APPLICATION_SERVER_PORT% with the server's host and port values for those applications that are configured. If an application is not configured, the link value should be kept to include %APPLICATION_SERVER_HOST% and %APPLICATION_SERVER_PORT% tokens.
For example, if you configure only the Email and Files Infostores, but not any other component on the middle-tier, where the host name is host1.mycompany.com, then the marconi.config file should look like this:
mail=http:// host1.mycompany.com:7778/um/traffic_copcalendar=http://%CALENDAR_SERVER_HOST%:%CALENDAR_SERVER_PORT%/fcgibin /owc/lexacal.fcgi?go=loginfiles=http:// host1.mycompany.com:7778/files/appsearch=http://host1.mycompany.com:7778/files/app/FederatedSearch wireless=http://%WIRELESS_SERVER_HOST%:%WIRELESS_SERVER_PORT%/ tools=http://otn.oracle.com
Go to the $ORACLE_HOME/bin directory and open the ocsinstall.sh file.
Verify the ORACLE_HOME value is set to the current $ORACLE_HOME value. If not, update with the current $ORACLE_HOME value.
From the $ORACLE_HOME/bin directory, run the following:
$ ./ocsinstall.sh orcladmin <iAS instance password
The iAS instance password is the password you used to create this middle-tier instance. This will import all the application portlets into Portal.
|
See Also: Refer to Oracle Collaboration Suite Administrator’s Guide Release 1 (9.0.3) for more information on creating Portal users and setting default Portal pages. |
If you used the gold image to deploy your Oracle Collaboration Suite CC, then use the following to remove old partner applications on the system. This fix is not required for the deployments installed and configured from the Product CD-ROMs.
Log into the Single Sign On (SSO) Server at:
http://<hostname:<port/pls/orasso
Click SSO Server Administration.
Click Administer Partner Applications.
In the Edit/Delete Partner Application section, delete the following old partner applications:
Oracle Portal (portal) cgoldc_ocscal.<hostname.<domainname cgolds_oidsso.<hostname.<domainname cgoldu_ocsmt.<hostname.<domainname wireless_deviceportal
If there are two application entries with the same name (for example, wireless_deviceportal), then use the following procedure to identify the old application:
Click on the Edit icon against the partner application.
Note the ID of the application in the Edit Partner Application page.
The application ID with the lesser value is the old partner application
You must perform these steps in the following sequence.
Use the following to refresh the ONS configuration for a two-tier deployment:
In the Infrastructure database Oracle home on the database-tier, update the ias.properties file in the $ORACLE_HOME/config directory with the proper host name values for the following entries:
SSOhost
OIDhost
Run the following command in the Infrastructure mid-tier Oracle home on the middle-tier system. This command updates the $ORACLE_HOME/opmn/conf/ons.conf file with the IP addresses of the database-tier and middle-tier systems.
$ $ORACLE_HOME/dcm/bin/dcmctl listinstances
Verify that the ons.conf file contains the IP addresses of the database-tier and middle-tier systems only.
Run the following command in the Infrastructure database Oracle home on the database-tier system. This command updates the $ORACLE_HOME/opmn/conf/ons.conf file with the IP addresses of the database-tier and middle-tier systems.
$ $ORACLE_HOME/dcm/bin/dcmctl listinstances
Verify that the ons.conf file contains the IP addresses of the database-tier and middle-tier systems only.
Run the following command in the Calendar Server Oracle home on the database-tier system. This command updates the $ORACLE_HOME/opmn/conf/ons.conf file with the IP addresses of the database-tier and middle-tier systems only.
$ $ORACLE_HOME/dcm/bin/dcmctl listinstances
Verify that the ons.conf file contains the IP addresses of the database-tier and middle-tier systems only.
You must now stop and start services in all Oracle homes. See "Restart Oracle Collaboration Suite" for details.
Use the following to refresh the ONS configuration for a single-tier deployment:
Run the following command in the Infrastructure Oracle home.This command updates the $ORACLE_HOME/opmn/conf/ons.conf file with the IP addresses of the current system.
$ $ORACLE_HOME/dcm/bin/dcmctl listinstances
Verify that the ons.conf file contains the IP addresses of the current system.
You must now stop and start services in all Oracle homes. See "Restart Oracle Collaboration Suite" for details.
If you installed Oracle Collaboration Suite CC from gold image, then the running OPMN processes may contain outdated information. You must restart Oracle Collaboration Suite services to ensure the information in the OPMN processes is up to date. See "Starting and Stopping Oracle Collaboration Suite Components" on page 5-2 for details on how to start or stop services in a specific Oracle home. You must restart the services in the following order:
Stop and start Oracle Collaboration Suite in the following sequence:
Stop the Oracle Collaboration Suite mid-tier components Oracle home on the middle-tier
Stop the Calendar Server Oracle home on the database-tier (if you have deployed Calendar)
Stop the Infrastructure mid-tier Oracle home on the middle-tier (OID/SSO)
Start the Infrastructure mid-tier Oracle home on the middle-tier (OID/SSO)
Start the Calendar Server Oracle home on the database-tier (if you have deployed Calendar)
Start the Oracle Collaboration Suite mid-tier components Oracle home on the middle-tier
Stop and start Oracle Collaboration Suite in the following sequence:
Stop the Oracle Collaboration Suite mid-tier components Oracle home
Stop the Infrastructure Oracle home
Start the Infrastructure Oracle home
Start the Oracle Collaboration Suite mid-tier components Oracle home
Refer to Appendix D, " Troubleshooting" for handling failures during configuration. If the failure requires you to reinstall the software, follow instructions in Appendix E, " Deinstalling" to remove your existing installation.
|
 Copyright © 1999, 2003 Oracle Corporation All rights reserved |
|