|
Oracle® Collaboration Suite Certified Configuration Deployment and Cloning Guide
Release 9.0.4.1 for Linux x86 Part No. B12145-01 |
|
|
|
|
Oracle® Collaboration Suite Certified Configuration Deployment and Cloning Guide
Release 9.0.4.1 for Linux x86 Part No. B12145-01 |
|
|
|
|
This chapter describes service administration tasks for Oracle Collaboration Suite Certified Configuration (Oracle Collaboration Suite CC).
This chapter contains the following sections:
Configuring Additional Oracle Collaboration Suite Middle-Tier Components
Sequence for Starting and Stopping Oracle Collaboration Suite Components
You can configure additional Oracle Collaboration Suite middle-tier components after you have initially configured Oracle Collaboration Suite middle-tier components on the middle-tier. For example, if you had initially installed and configured Email, then you later decide to install and configure Files (assuming that the Files Infostore has already been set up), you can run the following command to configure Files:
$ config.sh -ocsmt files
Use the following command to configure additional Oracle Collaboration Suite middle-tier components:
$ config.sh -ocsmt <new component
The following are restrictions for adding Oracle Collaboration Suite middle-tier components:
The config.sh script only allows configuration of new components. The script does not allow reconfiguration of existing components.
The calweb and calall options are mutually exclusive. For example, when calall is configured, you cannot configure using calweb.
The config.sh script prompts you with default values for the values shared among the different components. You cannot change these default values.
At the end of configuration, the CC_INVENTORY will be updated. The new component will be started.
If you have configured one or more Oracle Collaboration Suite middle-tier component on the middle-tier, you can choose to disable the components at any time. Use the following instructions depending on whether you want to disable or re-enable Oracle Collaboration Suite middle-tier components.
To disable Oracle Collaboration Suite middle-tier components, use the following:
Log in as the root user.
Change directories to the <ORACLE_CC_PRODTOP> directory.
Run the following command:
# ./disable_component.sh
A list of available Oracle homes displays.
Select the Oracle home you want.
A list of active components displays.
Select one or more of the components that you want to disable.
When the disable_component.sh script has completed, the CC_INVENTORY active component list will be updated. The newly disabled component or components will be stopped.
To enable Oracle Collaboration Suite middle-tier components, use the following:
Log in as the root user.
Change directories to the <ORACLE_CC_PRODTOP> directory.
Run the following command:
# ./enable_component.sh
A list of available Oracle homes displays.
Select the Oracle home you want.
A list of inactive components displays.
Select one or more of the components that you want to enable.
When the enable_component.sh script has completed, the CC_INVENTORY active component list will be updated. The newly enabled component or components will be started.
The following are sequences for starting and stopping Oracle Collaboration Suite Components on two-tier and single-tier deployments.
Start two-tier components in the following sequence:
Infrastructure database on the database-tier
Email, Files, and Real-Time Collaboration Infostores on the database-tier
Infrastructure mid-tier on the middle-tier
Calendar Server on the database-tier
Oracle Collaboration Suite middle-tier components on the middle-tier
Stop two-tier components in the following sequence:
Oracle Collaboration Suite middle-tier components on the middle-tier
Calendar Server on the database-tier
Infrastructure mid-tier on the middle-tier
Email, Files and Real-Time Collaboration Infostores on the database-tier
Infrastructure database on the database-tier
To start all Oracle Collaboration Suite services in an Oracle home, run the following commands as the owner of that Oracle home:
$. /etc/ora_cc_env $ /admin/mwcc/ocs/904/etc/rc.oracle/startocs.sh ORACLE_HOME
where the variable ORACLE_HOME is the full path of the Oracle home in which you want to start the Oracle Collaboration Suite services. This starts all the configured and enabled services in the Oracle home, except the Oracle Files domain controller.
To start the Oracle Files domain controller, run the following as the root user:
# $ORACLE_HOME/ifs/files/bin/ifsctl start
where the variable ORACLE_HOME is the full path of the Oracle Collaboration Suite middle-tier Oracle home in which Oracle Files is configured.
To stop all Oracle Collaboration Suite services in an Oracle home, run the following commands as the owner of that Oracle home:
$ . /etc/ora_cc_env $ /admin/mwcc/ocs/904/etc/rc.oracle/stopocs.sh ORACLE_HOME
where the variable ORACLE_HOME is the full path of the Oracle home in which you want to stop the Oracle Collaboration Suite services. This stops all the configured and enabled services in the Oracle home, except the Oracle Files domain controller and OEM.
To stop the Oracle Files domain controller, run the following as the root user:
# $ORACLE_HOME/ifs/files/bin/ifsctl stop
where the variable ORACLE_HOME is the full path of the Oracle Collaboration Suite middle-tier Oracle home in which Oracle Files is configured.
To stop OEM, run the following command:
$ $ORACLE_HOME/bin/emctl stop
Table 12-1, "Components Started on Oracle9iAS Infrastructure" shows the components that start in the corresponding Oracle home for a split infrastructure setup.
Table 12-1 Components Started on Oracle9iAS Infrastructure
| Component | Metadata Database | OID and SSO only | Complete Infrastructure |
|---|---|---|---|
| Net Listener | Yes | No | Yes |
| Metadata Database | Yes | No | Yes |
| Directory Server (OID) | No | Yes | Yes |
| OHS (for SSO) | No | Yes | Yes |
| OC4J DAS Instance | No | Yes | Yes |
If you want to start or stop other individual components, then refer to Oracle Collaboration Suite documentation for details.
|
 Copyright © 1999, 2003 Oracle Corporation All rights reserved |
|