In this module you learn how to start up the components of
Oracle Collaboration Suite including Infrastructure, Information store, and
Middle-Tier applications.
There is a sequence of tasks for starting and stopping the
Oracle Collaboration Suite components. You can start and stop Oracle Application
Server in different ways based on your requirements. There are a number of tools
available that you can use to start, stop, restart and view the status of components:
The dcmctl
command: This command allows you to start and stop an entire component as
well as the subprocesses within the components. For example, you can start
and stop Web Cache, or you can start and stop only the Web Cache Admin subprocess.
Oracle
Enterprise Manager: Use to view components that you cannot start or
stop, but whose status depends on other components. For example, it displays
the status of the Single Sign-On component, whose status depends on the
HTTP Server.
EM and dcmctl
are completely compatible, they use OPMN as their underlying component to manage
processes, and can be used interchangeably. For example, you can start a component
using opmnctl and stop it using
EM.
This module shows how to manage and start the Oracle Collaboration
Suite components and processes—Infrastructure, Middle-Tier Instance, and
applications—using the command-line.
Because of the dependencies between Oracle Collaboration Suite
components and subcomponents, start the Oracle Collaboration Suite components
in the sequence listed below:
This module includes an example of starting the following
types of components:
Database
Instance: Listener and Database
Oracle
Collaboration Suite Infrastructure: Components such as DCM, Oracle HTTP
Server, OC4J instances, and OID, and Application Server Control
Information
Store (Email and Files): Listener and Database
Oracle
Calendar
Oracle
Collaboration Suite Mid-Tier Instance: Components such as J2EE and Web
Cache, Portal and Wireless, and Business Intelligence and Forms
Components
and Processes: Components such as Oracle Collaboration Suite applications
except for Oracle Calendar
Starting up Oracle Collaboration Suite Infrastructure
After you reboot your host, or to start up your entire Infrastructure,
you must start all processes
in the Infrastructure. For this example, the Infrastructure host contains a
Metadata Repository and Identity Management.
1.
Open
a terminal window on the Infrastructure host as user oracle, and
set the environment variables for the Infrastructure (set ORACLE_HOME
environment variable to the Infrastructure Oracle home and set ORACLE_SID
environment variable to the Metadata Repository SID):
For
this example, ocs_inf_profile
is set as follows:
2.
Start
the Oracle Net listener using lsnrctl
start:
3.
Start
the Infrastructure Metadata Repository database.
sqlplus "
/ as sysdba"
startup
exit
4.
Start the Oracle Internet
Directory monitor process.
You will
need to start all processes in a middle-tier instance after you reboot your
host, or when you want to start up the entire instance. For this example, the
Middle-Tier instance uses the Infrastructure services (such as Identity Management
and a Metadata Repository) which have already been started in section one. To
startup the Oracle Collaboration Suite Middle-Tier applications, perform the
following steps:
1.
Open
a terminal window on the mid-tier host and set the environment variables
for the middle tier.
. ocs_mid_profile
2.
Start
the Email listener. First, determine the <user id#> and <group
id#> values for the oracle user:
id oracle
To
actually start the Email listener, log in as the root user, substituting
the user id# and group id# for the oracle
user (from the query issued above):
Verify
that the XServer virtual framebuffer has already been started.
ps -elf |
grep Xvfb
If
the XServer virtual framebuffer is not already started, then start it
for the correct web page rendering.
su root
cd /tmp
nohup /usr/X11R6/bin/Xvfb :11 -screen 0 1152x900x8 &
exit
4.
Start
the OPMN process. Note that for this example, you will only start the
OPMN process; each OPMN managed processes will be started individually.
$ORACLE_HOME/opmn/bin/opmnctl
start
Note: The $ORACLE_HOME/opmn/bin/opmnctl
startall can be used to start OPMN and all of the OPMN-managed
processes such as DCM, Oracle HTTP Server, OC4J instances and Web Cache.
5.
Start
the Oracle HTTP Server for the middle-tier applications.
$ORACLE_HOME/dcm/bin/dcmctl
start -v -ct ohs
6.
Start
the OC4J instances of Portal, Unified Messaging (Oracle E-mail), Wireless,
Oracle Files, and Oracle Web Conferencing.
$ORACLE_HOME/dcm/bin
dcmctl start -v -co OC4J_Portal
dcmctl start -v CO OC4J_UM
dcmctl start -v CO OC4J_Wireless
dcmctl start -v CO OC4J_iFS_files
dcmctl start -v CO OC4J_Portal
Bookmark
