| Oracle® Collaboration Suite Administrator's Guide 10g Release 1 (10.1.1) for Windows or UNIX Part Number B14476-03 |
|
|
View PDF |
| Oracle® Collaboration Suite Administrator's Guide 10g Release 1 (10.1.1) for Windows or UNIX Part Number B14476-03 |
|
|
View PDF |
This chapter describes how to start and stop Oracle Collaboration Suite components; Infrastructure tier instances; Applications tier instances; Oracle Collaboration Suite Databases; and various Oracle Collaboration Suite components; using Oracle Enterprise Manager 10g and command-line tools.
You can start, stop, or restart any component. Some components may be hard-restarted, meaning, the service is completely stopped and then restarted. Other components may be soft-restarted, meaning the service is re-initialized, but not completely stopped, and users will not experience a service interruption.
Oracle Collaboration Suite is a flexible product that you can start and stop in different ways, depending on your requirements. This chapter contains the following sections:
Overview of Starting and Stopping Oracle Collaboration Suite
This section outlines the recommended order of operations for starting and stopping the entire Oracle Collaboration Suite deployment. Follow the procedures in this section when starting an entire deployment after a reboot, or when you would like to stop your entire instance, for example, in preparation for shutting down your system.
Starting and Stopping Oracle Collaboration Suite Tiers
Oracle Collaboration Suite deployments include Oracle Collaboration Suite Infrastructure tiers and Oracle Collaboration Suite Applications tiers. Follow these instructions for starting and stopping Oracle Collaboration Suite tiers.
Starting and Stopping Oracle Collaboration Suite DatabaseInstances
Follow the procedures in this section when starting and stopping Oracle Collaboration Suite Database instances. Although the Oracle Collaboration Suite Database is often hosted as part of an Infrastructure tier, you start and stop it using separate commands.
Starting and Stopping Individual Components
Use the procedures in this section to start or stop individual components without shutting down the entire Applications tier.
Enabling and Disabling Components
This section describes how to disable components (prevent them from starting when you start a Applications tier instance) and enable components (allow them to start when you start a Applications tier instance).
Starting and Stopping: Special Topics
This section describes some exceptions to the general procedures for starting and stopping, including starting and stopping the Log Loader, procedures to use in High Availability environments, and resolving errors that may occur.
The Oracle Universal Installer will attempt to start Oracle Collaboration Suite when it completes installation. From time to time you will need to stop and restart various components of the system, or the entire deployment. If you are starting Oracle Collaboration Suite 'cold' (such as after rebooting a server) you should follow these instructions carefully to avoid problems.
In general, you should start Oracle Collaboration Suite in the following order:
First start the Collaboration Suite Infrastructure. The Infrastructure includes all instances of Enterprise Manager, Oracle Internet Directory, Identity Management, and the Collaboration Suite Database, hosted on Infrastructure tiers.
If you have a distributed Infrastructure installation, start all of the Infrastructure tiers.
In some deployment scenarios, the Collaboration Suite Database (including application data and the OracleAS Metadata Repository) is installed along with the Infrastructure. In this case, the database will start automatically when you start the Infrastructure, if you use the automatic script.
In other deployment scenarios, the Collaboration Suite Database is hosted separately. You may even have multiple Oracle Collaboration Suite Databases. Or, you may choose to start individual components manually. In these scenarios, you may start the Infrastructure and the Oracle Collaboration Suite Databases in any order. If you start the Infrastructure first, you can use Enterprise Manager to start all Collaboration Suite Databases.
Note:
If you have upgraded from a previous version of Oracle Collaboration Suite, your Infrastructure will host an instance of the OracleAS Metadata Repository, while the Collaboration Suite Database (formally known as the Infostore) is in a separate Oracle Home. In fresh installations of Oracle Collaboration Suite 10g Release 1 (10.1.1), the OracleAS Metadata Repository may be integrated with the Collaboration Suite Database.Second, start Applications tiers. Applications tier components include all the HTTP server and all OC4J applications. If you have configured Oracle Calendar on an Applications tier, you must also start the Oracle Calendar Application System (OCAS) control processes. If you have configured Oracle Mail on an Applications tier, you must also start the Oracle Mail Listener. You may not be able to successfully start Applications tier components unless all Infrastructure tiers and all Oracle Collaboration Suite Database instances are running.
In general, you should stop Oracle Collaboration Suite in the following order:
Stop all Applications tiers. To avoid data loss or corruption, never stop the Infrastructure or Collaboration Suite Database while any application is running.
Stop Infrastructure instances and Oracle Collaboration Suite Database instances.
The Infrastructure includes all instances of Enterprise Manager, Oracle Internet Directory, Identity Management, and may include the Oracle Collaboration Suite Database.
In many deployments, you will need to issue separate commands to stop the database, and to stop Infrastructure tiers.
You may stop the Infrastructure and the databases in any order. If you stop the databases first, you can use Oracle Enterprise Manager 10g to stop all Collaboration Suite Databases.
Scripted Starting and Stopping
Oracle has provided a sample Oracle Collaboration Suite control script (ocsctl_sample) to make starting up and shutting down your Infrastructure and Applications tiers easier. In the following sections, the procedure and syntax for using the script is provided.
Note:
The
ocsctl_sample script is a sample. It has not been extensively tested with all possible deployment scenarios. You should instead use it as a template for the creation of your own, customized startup and shutdown script. Oracle cannot guarantee that the ocsctl_sample script will properly start up or shut down any specific deployment.While the script is running, it prints the name of processes on the console as and when they are started or stopped with the status as successful or failed. If all the processes are started or stopped successfully it prints "Infrastructure/Applications tier processes started successfully." Otherwise, it prints the list of processes that failed to start or stop.
Before running the script, make sure that ORACLE_HOME and ORACLE_SID have been set to the proper values. For example, if you want to start or stop the Infrastructure processes, you should set the ORACLE_HOME to the location of Infrastructure installation, and the ORACLE_SID to the name of the Oracle Collaboration Suite Database.
Oracle Collaboration Suite is composed of two tiers; the Infrastructure tier, and the Applications tier (referred to as the 'middle tier' in previous releases of Oracle Collaboration Suite). Infrastructure tiers are comprised of the following five processes:
OracleAS Metadata Repository Net listener
One or more Oracle Collaboration Suite Databases
Oracle Enterprise Manager 10g Application Server Control Console
Oracle Enterprise Manager 10g Database Control
Oracle Process Manager and Notification Server (OPMN) and all managed processes
Similarly, Applications tiers are comprised of the following four processes:
Enterprise Manager Application Server Control Console for Oracle Collaboration Suite (Oracle Collaboration Suite Control)
Oracle Process Manager and Notification Server (OPMN) and all managed processes, including all Oracle Collaboration Suite applications
Oracle Mail listener
Oracle Calendar Application System (OCAS) control processes
This section provides procedures for starting and stopping the various tiers of an Oracle Collaboration Suite deployment, tier-by-tier. A deployment can consist of multiple Infrastructure and Applications tier instances distributed across one or more hosts.
These instances are dependent on each other and it is important to start and stop them in the proper order. For an overview of the correct order for starting and stopping an entire Oracle Collaboration Suite deployment, see "Overview of Starting and Stopping Oracle Collaboration Suite"
This section describes how to start and stop Oracle Collaboration Suite tiers. It contains the following topics:
This section describes how to start all processes in an Infrastructure. You can follow this procedure after you have rebooted your host, or any other time you would like to start up your entire Infrastructure.
This procedure applies to all Infrastructure types:
Identity Management and Oracle Collaboration Suite Database (which includes the OracleAS Metadata Repository and application data)
Distributed Infrastructure deployments, with the Oracle Collaboration Suite Database hosted separately
Starting an Infrastructure Tier Manually
To perform a manual (unscripted) start of the Infrastructure:
Set the ORACLE_HOME environment variable to the Infrastructure Oracle home.
Set the ORACLE_SID environment variable to the Oracle Collaboration Suite Database SID (default is ocsdb).
Start the Net Listener:
ORACLE_HOME/bin/lsnrctl start
Start the Oracle Collaboration Suite Database:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> startup
SQL> quit
Note:
If you have a distributed Infrastructure (you are hosting one or more Oracle Collaboration Suite Databases on separate computers or Oracle Homes), you can skip this step. Be sure to start the Oracle Collaboration Suite Database before you start any Applications tier instances.See Also:
For many more flexible ways to start the Oracle Collaboration Suite Database, see "Starting and Stopping Oracle Collaboration Suite DatabaseInstances"Start Infrastructure services:
ORACLE_HOME/opmn/bin/opmnctl startall
This command starts OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and Oracle Internet Directory.
Start the Enterprise Manager Application Server Control Console for Oracle Collaboration Suite:
ORACLE_HOME/bin/emctl start iasconsole
Starting an Infrastructure Tier Using the Sample Script
To start the Infrastructure using the sample script:
Set the ORACLE_HOME environment variable to the Infrastructure Oracle Home
Set the ORACLE_SID environment variable to the Oracle Collaboration Suite Database SID (default is ocsdb).
Run the Oracle Collaboration Suite control script:
On UNIX/Linux:
ORACLE_HOME/bin/ocsctl_sample -start infra
On Windows:
ORACLE_HOME\bin\ocsctl_sample -start infra
This command starts the five processes of the Infrastructure. If the Oracle Collaboration Suite Database is installed on the Infrastructure, it will also be started. If you have a distributed Infrastructure (you are hosting the Oracle Collaboration Suite Database on a separate machine), you must start the Oracle Collaboration Suite Database separately. Be sure to start the Oracle Collaboration Suite Database before you start any Applications tiers.
Note:
Theocsctl_sample script is a sample. It has not been extensively tested with all possible deployment scenarios. You should instead use it as a template for the creation of your own, customized startup and shutdown script. Oracle cannot guarantee that the ocsctl_sample script will properly start up or shut down any specific deployment.You can use Oracle Enterprise Manager Grid Control 10g (Grid Control) to administer your infrastructure, including starting it up and shutting it down. Grid Control is a separate Oracle product that combines a GUI console, agents, common services, and tools to provide an integrated and comprehensive systems management platform for managing Oracle products. Grid Control enables you to start the Infrastructure using a GUI interface, rather than command line operations.
See Also:
Oracle Enterprise Manager Grid Control Installation and Basic Configuration
Oracle Enterprise Manager Managing Oracle Collaboration Suite
This section describes how to stop all processes in an Infrastructure instance. You can follow this procedure when you are preparing to shut down your host, or any other time you would like to stop an Infrastructure tier.
Note:
To avoid possible data loss or corruption, you should stop all Applications tiers before stopping any Infrastructure tiers.This procedure applies to all Infrastructure types:
Identity Management and Oracle Collaboration Suite Database (which includes the OracleAS Metadata Repository and application data)
Distributed Infrastructure deployments, with the Oracle Collaboration Suite Database hosted separately
Stopping an Infrastructure Tier Manually
To perform a manual (unscripted) shutdown of an Infrastructure instance:
Set the ORACLE_HOME environment variable to the Infrastructure Oracle home.
Set the ORACLE_SID environment variable is set to the Oracle Collaboration Suite Database SID (default is asdb).
Stop the Enterprise Manager Application Server Control Console for Oracle Collaboration Suite:
ORACLE_HOME/bin/emctl stop iasconsole
Stop components:
ORACLE_HOME/opmn/bin/opmnctl stopall
This command stops OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and Oracle Internet Directory.
Stop the Oracle Collaboration Suite Database instance:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> shutdown
SQL> quit
Note:
If you have a distributed Infrastructure (you are hosting the Oracle Collaboration Suite Database on a separate machine), you can skip this step. The Oracle Collaboration Suite Database will continue to run without the Infrastructure, until you shut it down manually.See Also:
For many more flexible ways to stop the Oracle Collaboration Suite Database, see "Starting and Stopping Oracle Collaboration Suite DatabaseInstances"Stop the Net Listener:
ORACLE_HOME/bin/lsnrctl stop
Stopping an Infrastructure Tier Using the Sample Script
To stop the Infrastructure using the sample script:
Set the ORACLE_HOME environment variable to the Infrastructure Oracle Home
Set the ORACLE_SID environment variable to the Oracle Collaboration Suite Database SID (default is ocsdb).
Run the Oracle Collaboration Suite control script:
On UNIX/Linux:
ORACLE_HOME/bin/ocsctl_sample -stop infra
On Windows:
ORACLE_HOME\bin\ocsctl_sample -stop infra
This command stops the five processes of the Infrastructure in the reverse order they were started. If the Oracle Collaboration Suite Database is installed on the Infrastructure, it will also be stopped. If you have a distributed Infrastructure (you are hosting the Oracle Collaboration Suite Database on a separate machine), you must stop the Oracle Collaboration Suite Database separately.
Note:
Theocsctl_sample script is a sample. It has not been extensively tested with all possible deployment scenarios. You should instead use it as a template for the creation of your own, customized startup and shutdown script. Oracle cannot guarantee that the ocsctl_sample script will properly start up or shut down any specific deployment.This section describes how to start all processes in a Applications tier instance. You can follow this procedure after you have rebooted your host, or any other time you would like to start up an Applications tier.
Starting an Applications Tier Manually
To start an Applications tier instance manually (unscripted):
Make sure that you have started the Infrastructure. If you have a distributed Infrastructure (the Oracle Collaboration Suite Database is hosted on a different computer) make sure you have also started the Oracle Collaboration Suite Database.
Set the ORACLE_HOME environment variable to the Applications tier Oracle home.
Start the Enterprise Manager Application Server Control Console for Oracle Collaboration Suite:
On UNIX/Linux:
ORACLE_HOME/bin/emctl start iasconsole
On Windows:
ORACLE_HOME\bin\emctl start iasconsole
Start the Oracle Mail listener:
On UNIX/Linux:
Log in as root, if the listener is configured to run on a privileged port (such as port 25), and then run the following command:
ORACLE_HOME/bin/tnslsnr listener_es -user <user_id> -group <group_id>
On Windows:
ORACLE_HOME\bin\tnslsnr start listener_es -user <user_id> -group <group_id>
where <user_id> and <group_id> are the numeric user and group ID numbers.
Note:
This command is not expected to return. On UNIX, you can add '&' to the end if you want to run it in the background.Start components:
On UNIX/Linux:
ORACLE_HOME/opmn/bin/opmnctl startall
On Windows:
ORACLE_HOME\opmn\bin\opmnctl startall
This command starts configured Applications tier applications, including OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, Web Cache, Oracle Calendar Server, Oracle Mail, Oracle Content Services, Oracle RTC, Oracle Voicemail & Fax, Oracle Mobile Collaboration, Portal, Collaborative Workspaces, Oracle Web Access, and Collaboration Suite Search.
The Oracle Calendar Application System (OCAS) control processes is running as an external fast CGI process, and therefore is not managed with HTTP Server. Further, because OCAS is not integrated with OPMN, when an Applications tier is started or stopped using opmnctl, OCAS is not started or stopped.
If this Applications tier hosts an instance of Oracle Calendar, you must start the Oracle Calendar Application System (OCAS) control processes separately:
On UNIX/Linux:
ORACLE_HOME/ocas/bin/ocasctl -start -t ochecklet ORACLE_HOME/ocas/bin/ocasctl -start
On Windows:
ORACLE_HOME\ocas\bin\ocasctl -start -t ochecklet ORACLE_HOME\ocas\bin\ocasctl -start
Ports 8010 and 8020 are the default ports used by OCAS. The valid range is 8010-8020.
Starting an Applications Tier Using the Sample Script
To start an Applications tier instance using the sample script:
Make sure that you have started the Infrastructure. If you have a distributed Infrastructure (the Oracle Collaboration Suite Database is hosted on a different computer) make sure you have also started the Oracle Collaboration Suite Database.
Set the ORACLE_HOME environment variable to the Applications tier Oracle home.
Run the Oracle Collaboration Suite sample control script:
On UNIX/Linux:
ORACLE_HOME/bin/ocsctl_sample -start apps
On Windows:
ORACLE_HOME\bin\ocsctl_sample -start apps
Note:
The Oracle Collaboration Suite sample control script starts the Oracle Mail listener, if you have configured Oracle Mail on this Applications tier. The Oracle Mail listener is configured to use port 25, a privileged port, by default. On UNIX platforms, superuser permissions are required to run processes on privileged ports. Therefore, if your Applications tier is hosting Oracle Mail, using a privileged port, on a UNIX platform,ocsctl_sample will prompt you to enter the root password.The ocsctl_sample script starts all configured Applications tier applications, including OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, Web Cache, Oracle Calendar Server, Oracle Calendar Application System, Oracle Mail, Oracle Content Services, Oracle RTC, Oracle Voicemail & Fax, Oracle Mobile Collaboration, Portal, Collaborative Workspaces, Oracle Web Access, and Collaboration Suite Search. The script also starts the Enterprise Manager Application Server Control Console for Oracle Collaboration Suite, and the Oracle Mail listener.
Note:
Theocsctl_sample script is a sample. It has not been extensively tested with all possible deployment scenarios. You should instead use it as a template for the creation of your own, customized startup and shutdown script. Oracle cannot guarantee that the ocsctl_sample script will properly start up or shut down any specific deployment.You can use Oracle Enterprise Manager Grid Control 10g (Grid Control) to administer your Applications tiers, including starting and stopping components. Grid Control is a separate Oracle product that combines a GUI console, agents, common services, and tools to provide an integrated and comprehensive systems management platform for managing Oracle products. Grid Control enables you to start your Applications tiers using a GUI interface, rather than command line operations.
See Also:
Oracle Enterprise Manager Grid Control Installation and Basic Configuration
Oracle Enterprise Manager Managing Oracle Collaboration Suite
This section describes how to stop all processes in an Applications tier instance. You can follow this procedure when you are preparing to shut down your host, or any other time you would like to stop an Applications tier.
Stopping an Applications Tier Manually
To stop an Applications tier instance manually (unscripted):
Set the ORACLE_HOME environment variable to the Applications tier Oracle home.
The Oracle Calendar Application System (OCAS) control processes is running as an external fast CGI process, and therefore is not managed with HTTP Server. Further, because OCAS is not integrated with OPMN, when an Applications tier is started or stopped using opmnctl, OCAS is not started or stopped.
If this Applications tier hosts an instance of Oracle Calendar, you must stop the Oracle Calendar Application System (OCAS) control processes separately:
On UNIX/Linux:
ORACLE_HOME/ocas/bin/ocasctl -stopall
On Windows:
ORACLE_HOME\ocas\bin\ocasctl -stopall
Stop components:
On UNIX/Linux:
ORACLE_HOME/opmn/bin/opmnctl stopall
On Windows:
ORACLE_HOME\opmn\bin\opmnctl stopall
This command stops all configured Applications tier applications, including OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, Web Cache, Oracle Calendar, Oracle Mail, Oracle Content Services, Oracle RTC, Oracle Voicemail & Fax, Oracle Mobile Collaboration, Portal, Collaborative Workspaces, Oracle Web Access, and Collaboration Suite Search.
On Applications tiers hosting an instance of Oracle Mail, stop the Oracle Mail listener:
On UNIX/Linux:
ORACLE_HOME/bin/lsnrctl stop listener_es -user <user_id> -group <group_id>
On Windows:
ORACLE_HOME\bin\lsnrctl stop listener_es -user <user_id> -group <group_id>
Stop the Enterprise Manager Application Server Control Console for Oracle Collaboration Suite:
ORACLE_HOME/bin/emctl stop iasconsole
Stopping an Applications Tier Using the Sample Script
To stop an Applications tier instance using the sample script:
Set the ORACLE_HOME environment variable to the Applications tier Oracle home.
Run the Oracle Collaboration Suite sample control script:
On UNIX/Linux:
ORACLE_HOME/bin/ocsctl_sample -stop apps
On Windows:
ORACLE_HOME\bin\ocsctl_sample -stop apps
This script stops all configured Applications tier applications, including OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, Web Cache, Oracle Calendar Server, Oracle Calendar Application System, Oracle Mail, Oracle Content Services, Oracle RTC, Oracle Voicemail & Fax, Oracle Mobile Collaboration, Portal, Collaborative Workspaces, Oracle Web Access, and Collaboration Suite Search.
Stop the Enterprise Manager Application Server Control Console for Oracle Collaboration Suite:
ORACLE_HOME/bin/emctl stop iasconsole
Note:
Theocsctl_sample script is a sample. It has not been extensively tested with all possible deployment scenarios. You should instead use it as a template for the creation of your own, customized startup and shutdown script. Oracle cannot guarantee that the ocsctl_sample script will properly start up or shut down any specific deployment.Many typical Oracle Collaboration Suite configurations include a single instance of the Collaboration Suite Database, installed on the Infrastructure tier. In these scenarios, the Collaboration Suite Database will start up and shut down automatically, when you start up or shut down the Infrastructure using the sample script. The most simple method for starting the Collaboration Suite Database manually is also listed in the instructions for manually starting the Infrastructure.
See Also:
To start the Infrastructure and Collaboration Suite Database automatically, follow the instructions provided in "Starting the Infrastructure Tier".
To stop the Infrastructure and Collaboration Suite Database automatically, follow the instructions provided in "Stopping the Infrastructure Tier".
In other deployment scenarios, you may be hosting the Collaboration Suite Database on a separate computer or Oracle home, or you may have multiple instances of the Collaboration Suite Database. If you upgraded from a previous version of Oracle Collaboration Suite to Oracle Collaboration Suite 10g Release 1 (10.1.1), your OracleAS Metadata Repository may be in a separate database from the Collaboration Suite Database. In these scenarios, you will have to start and stop your database instances directly.
All of the options for starting and stopping the Collaboration Suite Database directly are described in Chapter 6, "Managing Oracle Collaboration Suite Databases".
When you start up an Applications tier instance using Oracle Collaboration Suite Control, the sample ocsctl_sample script, or the Grid Control Console, all of the Oracle Collaboration Suite applications (and other Applications tier components) hosted on that tier are automatically started. When you stop an Applications tier using those methods, all of the Oracle Collaboration Suite applications (and other components) are stopped.
From time to time, you may wish to stop and start specific applications or components, rather than the entire tier. For example, you may wish to stop Oracle Real-Time Collaboration in order to perform maintenance, but you do not wish to also stop the Oracle Mail processes hosted on the same Applications tier.
You can use the following tools to start, stop, restart, and view the status of Oracle Collaboration Suite applications and components:
Oracle Collaboration Suite Control Console—a Web-based tool
opmnctl—a command-line tool
Grid Control Console—a Web-based tool (for Oracle Voice Mail & Fax only)
These tools are completely compatible—they use OPMN as their underlying technology for managing processes—and can be used interchangeably. For example, you can start a component using opmnctl and stop it using the Oracle Collaboration Suite Control.
Although the tools can be used interchangeably, they offer different features. The opmnctl command allows you to start and stop sub-processes within components, as well as the entire component. For example, you can start and stop the Web Cache component, or you can start and stop only the Web Cache Admin sub-process. Oracle Collaboration Suite Control allows you to view components that cannot be started or stopped, but whose status depends on other components. For example, it displays the status of the Oracle Workspaces application, whose status depends on the OC4J_OCSClient component. In addition to its other functions, the Grid Control Console provides a view of Oracle Voicemail & Fax similar to that of Oracle Collaboration Suite Control for other Oracle Collaboration Suite applications.
This section contains the following topics:
Starting and Stopping Using the Oracle Collaboration Suite Control
Starting and Stopping Oracle Real-Time Collaboration Components
You can start, stop, restart, and view status of components on the Oracle Collaboration Suite home page:
Navigate to the Oracle Collaboration Suite home page for any Applications tier using the Oracle Collaboration Suite Control Console. Scroll to the System Components section.
Select the checkboxes in the Select column for the components you want to start, stop, or restart.
Click the Start, Stop, or Restart button on the top right of the System Components section.
Each component may be started and stopped using the controls on this page. The Oracle Collaboration Suite Database and the Infrastructure must be running before you can start any component.
For more information about using the Oracle Collaboration Suite Control Console, see "Using Oracle Collaboration Suite Control Console".
Generally, you should use the Oracle Process Manager and Notification Server control for starting and stopping Applications tier components and processes of Oracle Collaboration Suite.
To start, stop, or restart any component:
ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=component ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=component ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=component
To start, stop, or restart the sub-process of a component:
ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=component process-type=process ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=component process-type=process ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=component process-type=process
To view the status of components and processes:
ORACLE_HOME/opmn/bin/opmnctl status
To learn more about using opmnctl, refer to Oracle Process Manager and Notification Server Administrator's Guide.
The Oracle Calendar Server can also be started and stopped manually with command line utilities. There are two sets of commands. One set of command line utilities will start and stop the Oracle Calendar Server, and the other set will start and stop the Oracle Calendar application system. Using the command line utilities specific to the Oracle Calendar application system will affect the Oracle Calendar Web Client, Oracle Calendar Web Services, and the Oracle Calendar Sync Server.
To check the status of the Oracle Calendar Server before stopping or starting the server, use the unistatus command line utility:
$ORACLE_HOME/ocal/bin/unistatus
Running this utility will provide a summary of the state of the Oracle Calendar Server, indicating which daemons are currently up and running. Moreover, the utility will return a summary of the general status of the Calendar Server, in the form of:
The Calendar Server is up
or
The Calendar Server is down
To check the status of the Oracle Calendar application system, use the ocasctl command line utility:
$ORACLE_HOME/ocas/bin/ocasctl -status
To start the Oracle Calendar Server, use the opmnctl command line utility:
opmnctl startproc ias-component=CalendarServer
To start the Oracle Calendar application system, use the ocasctl command line utility, with the options specified below:
ORACLE_HOME/ocas/bin/ocasctl -start -t ochecklet ORACLE_HOME/ocas/bin/ocasctl -start
Note:
Ports 8010 and 8020 are default port numbers forocas and ochecklet. The valid range is 8010 through 8020To stop the Oracle Calendar Server, use the opmnctl command line utility:
opmnctl stopproc ias-component=CalendarServer
Running this utility will terminate all existing Oracle Calendar Server connections by stopping all of the Calendar Server daemons -- unless otherwise specified by utility exception options.
To stop the Oracle Calendar application system, use the ocasctl command line utility:
$ORACLE_HOME/ocas/bin/ocasctl -stopall
See Also:
Oracle Calendar Reference Manual, Calendar Server Utilities,Oracle Calendar Administrator's Guide, Introduction to Calendar Administration
The Oracle Content Services software runs as a set of Applications tier processes, called Oracle Content Services nodes. Oracle Content Services nodes are processes that manage one or more services and servers, such as the Oracle Content Services FTP server. An Oracle Content Services domain is a logical grouping of Oracle Content Services nodes and an Oracle database instance that contains the Oracle Content Services data.
There are two types of nodes: regular nodes, and HTTP nodes. Oracle Content Services HTTP nodes run as part of an OC4J process. You cannot have more than two HTTP nodes on a single Applications tier: one to support the Oracle Content Services application, and one to support the Oracle Records Management application. The OC4J instance for the Oracle Content Services application is OC4J_Content, while the OC4J instance for the Oracle Records Management application is OC4J_RM.
You can start and stop Oracle Content Services node processes using the Application Server Control for Collaboration Suite, or using the opmnctl command-line tool.
You can choose to start and stop local Oracle Content Servicess processes on a single Applications tier, or you can start and stop processes across multiple Applications tiers. You can also start and stop Oracle Content Services sub-processes, such as protocol servers or agents.
For more information about starting and stopping Oracle Content Services processes, see Chapter 5, "Managing Oracle Content Services Processes" in Oracle Content Services Administrator's Guide.
See the following sections for information about how to start and stop Oracle Content Services node processes on a single Applications tier:
You can start all Oracle Content Services node processes across multiple Applications tiers from the Oracle Content Services Home page in the Application Server Control for Collaboration Suite, or you can use opmnctl.
To start and stop all Oracle Content Services node processes using the Application Server Control for Collaboration Suite:
From the Collaboration Suite Home page, click the name of the Oracle Content Services domain (typically Content).
Perform one of the following actions from the Oracle Content Services Home page:
Click Start Domain to start node processes across all Oracle Content Services Applications tiers.
Click Stop Domain to stop all node processes across all Oracle Content Services Applications tiers.
Click Restart Domain to restart node processes across all Oracle Content Services Applications tiers. Only those node processes that are running are affected; processes that are not running will not be started.
To start, stop, or restart all Oracle Content Services node processes across multiple Applications tiers using opmnctl, use the @farm option, as follows:
opmnctl @farm startproc ias-component=Content opmnctl @farm stopproc ias-component=Content opmnctl @farm restartproc ias-component=Content
You can find the opmnctl command-line tool in ORACLE_HOME/opmn/bin.
Note:
If you have multiple Oracle Content Services domains registered in Oracle Internet Directory, you must specify which domain to start or stop. The first Oracle Content Services domain to be registered is typically identified as "Content," while the second domain to be registered is identified as "Content_2," and so on. You should specify the appropriate domain display name inopmnctl commands. For example:
opmnctl @farm startproc ias_component=Content_2
Use the Application Server Control for Collaboration Suite to start or stop Oracle Content Services protocol servers or agents. For more information, see "Starting, Stopping, Suspending, and Resuming Servers" in Oracle Content Services Administrator's Guide.
You can start and stop Oracle Discussions by starting and stopping the OC4J_OCSClient process.
The OC4J_OCSClient process includes:
Oracle Discussions
Oracle Web Access Client client
Oracle Collaboration Suite Search
Oracle WebMail
Oracle Voicemail & Fax administration pages
The Oracle Collaboration Suite Welcome pages
Oracle Workspaces
You can start and stop the OC4J_OCSClient process using Oracle Collaboration Suite Control. See "Starting and Stopping Using the Oracle Collaboration Suite Control".
You can start and stop the OC4J_OCSClient process from the command line by using opmnctl.
ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OC4J process-type=OC4J_OCSClient ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J process-type=OC4J_OCSClient ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=OC4J process-type=OC4J_OCSClient
The Oracle Mail server resides on the Oracle Collaboration Suite application tier. Starting, stopping, or restarting the Oracle Mail server starts or stops all of the Oracle Mail processes, including Housekeeper, IMAP, NNTP, POP, list server, SMTP, and virus scrubber.
An administrator can prevent individual processes from starting by disabling them.
See Also:
"Starting, Stopping, Restarting, or Refreshing All Server Processes" in Chapter 3 of Oracle Mail Administrator's Guide for more information about starting and stopping individual Oracle Mail processesTo start, stop, or restart the Oracle Mail server:
Open a Web browser and enter the following URL:
http://host_name:port_number/emd/console
Enter an administrator user ID, such as ias_admin, and password.
Click the name of the Oracle Collaboration Suite application tier in the Name column.
Select E-mail Application.
Click Start, Stop, Restart, or Reload.
E-mail service will be temporarily interrupted after clicking Restart, and will completely stop or resume after clicking Stop or Start.
Because Oracle Mobile Collaboration is configured on top of Oracle Application Server Wireless, its running status depends upon that of OracleAS Wireless; Oracle Mobile Collaboration runs only if OracleAS Wireless runs. Stopping OracleAS Wireless also stops Oracle Mobile Collaboration.
The Mobile Collaboration Home page displays the running status of the Mobile Collaboration Server (up, down, or unavailable) and a link to the OracleAS Wireless System Manager. Clicking the Wireless link enables you to access the Home page of the OracleAS System Manager, a tool that enables you to manage and configure the OracleAS Wireless server. Using the Start All and Stop All buttons on the Home page, you can start or stop the entire OracleAS Wireless instance, which includes the Web-based processes and the standalone processes. The Web-based processes, which are the OracleAS Containers for Java (J2EE) applications that run in the OracleAS Wireless instance, are started or stopped using the Start OC4J Instance and StopOC4J Instance buttons. You can only start or stop these processes as a group; they cannot be started or stopped individually. The standalone processes, which include the processes for such components as the Messaging Server, Notification Engine, and the Notification Event Collector, can be started or stopped individually.
You can start and stop the OC4J_Wireless process from the command line by using opmnctl as well:
ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OC4J process-type=OC4J_Wireless ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J process-type=Wireless ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=OC4J process-type=OC4J_Wireless
See "Starting and Stopping Using opmnctl".
For more information on starting and stopping OracleAS Wireless and the OracleAS Wireless processes, see Oracle Application Server Wireless Administrator's Guide.
In addition to the other utilities described in this chapter, if you need to start or stop the Oracle Real-Time Collaboration components, you can do so using the rtcctl utility on each Applications tier where Oracle Real-Time Collaboration components have been installed.
To check the status of Oracle Real-Time Collaboration components on this tier, use the rtcctl getState command:
$ORACLE_HOME/imeeting/bin/rtcctl getState
To start this Oracle Real-Time Collaboration instance, enter the following command:
$ORACLE_HOME/imeeting/bin/rtcctl start
The Document Conversion or Voice Conversion Servers, used to support conversion of documents for document sharing and streaming voice during conferences, are installed on Windows systems. The syntax of the command to start these instances is:
%ORACLE_HOME%\imeeting\bin\rtcctl start
You can stop any Oracle Real-Time Collaboration instance by using the stop command. On UNIX systems:
$ORACLE_HOME/imeeting/bin/rtcctl stop
On Windows systems:
%ORACLE_HOME%\imeeting\bin\rtcctl stop
See Also:
Chapter 4, "rtcctl Command-line utility for Oracle Real-Time Collaboration," in Oracle Real-Time Collaboration Administrator's Guide for details about rtcctl and about how to start and stop individual components in an Oracle Real-Time Collaboration instance.It is also possible to stop specific instance processes by choosing Conference Details and then Diagnostics from the Web Conference reports available under the Monitor tab. See "Monitoring Current Conferences" in Chapter 5 of Oracle Real-Time Collaboration Administrator's Guide for more details.
You can start and stop Oracle Collaboration Suite Search by starting and stopping the OC4J_OCSClient process.
The OC4J_OCSClient process includes:
Oracle Discussions
Oracle Web Access Client client
Oracle Collaboration Suite Search
Oracle WebMail
Oracle Voicemail & Fax administration pages
The Oracle Collaboration Suite Welcome pages
Oracle Workspaces
You can start and stop the OC4J_OCSClient process using Oracle Collaboration Suite Control. See "Starting and Stopping Using the Oracle Collaboration Suite Control".
You can start and stop the OC4J_OCSClient process from the command line by using opmnctl.
ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OC4J process-type=OC4J_OCSClient ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J process-type=OC4J_OCSClient ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=OC4J process-type=OC4J_OCSClient
In addition to starting and stopping Oracle Voicemail & Fax using opmnctl or Oracle Collaboration Suite Control, you can also use Oracle Enterprise Manager Grid Control 10g to manage the Oracle Voicemail & Fax processes. From Grid Control, you can manage the Voicemail & Fax group and any of its subcomponents. Navigate to any Home page, Performance page, or Administration page of the Voicemail & Fax group or any of its subcomponents. From wherever you are in the hierarchy, you can stop, start, restart, or reload any component at that level or any subcomponent below it. For more information on starting and stopping Oracle Voicemail & Fax, see "Managing the Oracle Voicemail & Fax Components" in Chapter 6 in Oracle Voicemail & Fax Administrator's Guide.
You can start and stop Oracle Workspaces by starting and stopping the OC4J_OCSClient process.
The OC4J_OCSClient process includes:
Oracle Discussions
Oracle Web Access Client client
Oracle Collaboration Suite Search
Oracle WebMail
Oracle Voicemail & Fax administration pages
The Oracle Collaboration Suite Welcome pages
Oracle Workspaces
You can start and stop the OC4J_OCSClient process using Oracle Collaboration Suite Control. See "Starting and Stopping Using the Oracle Collaboration Suite Control".
You can start and stop the OC4J_OCSClient process from the command line by using opmnctl.
ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=OC4J process-type=OC4J_OCSClient ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J process-type=OC4J_OCSClient ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=OC4J process-type=OC4J_OCSClient
When you disable a component, you prevent it from starting when you start the tier, and you remove it from the list of System Components displayed on the Oracle Collaboration Suite home page.
When you enable a component, you allow it to start when you start the tier, and it appears in the list of System Components displayed on the Oracle Collaboration Suite home page.
You can enable and disable components using Oracle Collaboration Suite Control. On the Oracle Collaboration Suite home page, click Enable/Disable Components. You can select which components to enable or disable. Notice that components that are dependent on each other are grouped, and are all enabled or disabled together.
This section contains the following special topics about starting and stopping Oracle Application Server:
Using opmnctl Instead of Other Command-Line Tools to Start and Stop
Shutting Down Oracle Collaboration Suite Database with the IMMEDIATE Option
In previous versions of Oracle Collaboration Suite, which were based on Oracle9i Application Server Release 2 (9.0.2 and 9.0.3), dcmctl was the recommended command-line tool for starting and stopping Oracle HTTP Server, OC4J, and OPMN. Other command-line tools, such as webcachectl, were used to start the rest of the components.
In Oracle Collaboration Suite 10g Release 1 (10.1.1), you should use opmnctl to start all components in your instance, with the exception of the following:
OracleAS Certificate Authority—use ocactl to start and stop. See the Oracle Application Server Certificate Authority Administrator's Guide for details.
Oracle Collaboration Suite Database—use SQL*Plus to start and stop. See "Starting the Infrastructure Tier", and "Stopping the Infrastructure Tier", for details.
The Net Listener—use lsnrctl to start and stop. See "Starting the Infrastructure Tier", and "Stopping the Infrastructure Tier", for details.
The Enterprise Manager Application Server Control Console for Oracle Collaboration Suite—use emctl to start and stop. See "Starting an Applications Tier", and "Stopping an Applications Tier", for details.
Oracle Calendar Application System (OCAS) control processes—use ocasctl to start and stop. See "Starting an Applications Tier", and "Stopping an Applications Tier", for details.
The Oracle Mail listener—use tnslsnr to start and stop. See "Starting an Applications Tier", and "Stopping an Applications Tier", for details.
The method for starting and stopping Oracle Application Server Log Loader is different from other components.
Log Loader is not started when you issue the opmnctl startall command or when you perform a Start All operation in the Oracle Collaboration Suite Control. You can start Log Loader in the following ways:
Using the following command:
ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=LogLoader
By clicking the Start button on the Log Loader page in the Oracle Collaboration Suite Control.
Log Loader is not stopped when you issue a Stop All operation in the Oracle Collaboration Suite Control. You can stop Log Loader in the following ways:
Using the following command:
ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=LogLoader
By clicking the Stop button on the Log Loader pager in the Oracle Collaboration Suite Control.
Refer to Refer to "Using Oracle Collaboration Suite Log Loader" for detailed information on using the Oracle Application Server Log Loader.
For complete instructions on starting and stopping in High Availability environments, see "Starting and Stopping Oracle Collaboration Suite in a High-Availability Environment"
If you find that the Oracle Collaboration Suite Database instance is taking a long time to shut down, you can use the following command to force an immediate shutdown:
SQL> shutdown immediate
Immediate database shutdown proceeds with the following conditions:
No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued.
Any uncommitted transactions are rolled back. (If long uncommitted transactions exist, this method of shutdown might not complete quickly, despite its name.)
The immediate shutdown does not wait for users currently connected to the database to disconnect. The Oracle Collaboration Suite Database implicitly rolls back active transactions and disconnects all connected users.
The next startup of the database will not require any instance recovery procedures.
