| Oracle® Beehive Administrator's Guide Release 1 (1.5) Part Number E14836-04 |
|
|
View PDF |
| Oracle® Beehive Administrator's Guide Release 1 (1.5) Part Number E14836-04 |
|
|
View PDF |
This module describes how to start and stop Oracle Beehive, managed components, and processes using the beectl command-line utility. It contains the following sections:
The following topics are covered in this section:
Oracle Beehive is a flexible product that you can start and stop in different ways, depending on your requirements. You can start, stop, or restart an Oracle Beehive managed component, or the entire deployment.
The Oracle Database must be running to start Oracle Beehive successfully. If the Oracle Database instance is not running, start it before using the instructions in this section.
The Oracle Install Wizard will attempt to start Oracle Beehive when it completes installation. Occasionally, you will need to stop, start, or restart various managed components of the system or the entire deployment.
Note:
The Oracle Install Wizard will attempt to start Oracle Beehive after installation only when the "Install and Configure" option is selected during installation.To perform the administration tasks described in this section, you must be logged into the system as the user that installed Oracle Beehive. The beectl utility can be invoked every time you run a command, or you can use it in shell mode. This section explains different methods of invoking the beectl shell mode, and includes the following topic:
Note:
The
beectl shell expires if inactive for more than 30 minutes.beectl Commands in Shell Mode Without AuthenticationTo use the beectl shell, run the beectl command-line utility with no commands or options from the Oracle Beehive $ORACLE_HOME/beehive/bin directory. After running the command, the following beectl prompt will appear on the command-line:
beectl>
Once this prompt appears on the command-line, there is no need to specify beectl before a command.
beectl Command-Line UtilityThis section describes how to stop, start, and restart Oracle Beehive using the beectl command-line utility. The instructions in this section assume that the beectl shell is being used.
See Also:
For more information about thebeectl commands used in this section, see "Oracle Beehive Command-Line Utility" in Module 2 of the Oracle Beehive Administrator's Reference Guide.To start all Oracle Beehive managed components using the beectl command-line utility, use the start command with the --all option.
The following example illustrates the command with the --all option, as well as the resulting output:
beectl> start --all
Starting all the beehive components ...
Successfully started all the beehive components.
Operation completed in <time>.
To stop all Oracle Beehive managed components using the beectl command-line utility, use the stop command with the --all option.
The following example illustrates the command with the --all option, as well as the resulting output:
beectl> stop --all
Stopping all the beehive components ...
Successfully stopped all the beehive components.
Operation completed in <time>.
To restart all Oracle Beehive managed components using the beectl command-line utility, use the restart command with the --all option.
The following example illustrates the command with the --all option, as well as the resulting output:
beectl> restart --all Stopping all the beehive components ... Successfully stopped all the beehive components. Operation completed in <time>. Starting all the beehive components ... Successfully started all the beehive components. Operation completed in <time>.
beectl Command-Line UtilityThis section describes how to stop, start, and restart Oracle Beehive managed components individually using the beectl command-line utility. The instructions in this section assume that the beectl shell is being used.
See Also:
For more information about thebeectl commands used in this section, see "Oracle Beehive Command-Line Utility" in Module 2 of the Oracle Beehive Administrator's Reference Guide.Use the following instructions to determine the component identifier of a specific Oracle Beehive managed component using the beectl command-line utility:
Determine the component identifiers of all managed components by running the status command:
beectl> status --------------------------------------------+----------------+--------------- Component identifier | Component type | Status --------------------------------------------+----------------+--------------- BTI_redirector_instance1.host.domain.com | Bti | RUNNING --------------------------------------------+----------------+--------------- BEECLIENT_instance1.host.domain.com | ManagedOc4j | RUNNING --------------------------------------------+----------------+--------------- BEEAPP_instance1.host.domain.com | ManagedOc4j | RUNNING --------------------------------------------+----------------+--------------- BEEMGMT_instance1.host.domain.com | ManagedOc4j | RUNNING --------------------------------------------+----------------+--------------- BEECORE_instance1.host.domain.com | ManagedOc4j | RUNNING --------------------------------------------+----------------+--------------- oc4j_soa_instance1.host.domain.com | ManagedOc4j | RUNNING --------------------------------------------+----------------+--------------- ohs_instance1.host.domain.com | HttpServer | RUNNING --------------------------------------------+----------------+---------------
The component identifier is a string of characters, including the fully qualified host name preceded by a descriptive prefix. For a list of services included in each managed component, see "Managed Component Services".
Take note of the managed component identifier.
For example, from the output returned by the status command in step 1, we can determine that the component identifier of the Oracle Beehive Applications is: BEEAPP_instance1.host.domain.com.
Note:
Component identifiers differ from one deployment to another.Table 2-1 describes the services that are associated with different managed components. Stopping, starting, or restarting a managed component will affect all of the associated services listed in the Oracle Beehive Services column of Table 2-1.
Table 2-1 Managed Component Services
| Managed Component Prefix | Oracle Beehive Services |
|---|---|
|
Oracle Container for Java Service Oriented Architecture |
|
|
Discussions Service Device Management Service E-mail Service Event Services Fax Service FTP Service Instant Message Services Message Delivery Service Mobile Data Sync Service Mobile Device Management Service Mobile Mail Service Mobile Push Service Notification Service Platform Service Platform Web Service Presence Service Records Management Service Search Service Time Management Service Voice Message Service WebDAV Service Workflow Service XMPP Service |
|
|
Alarm Service Audit Service Authentication Services Policy Service Resource Directory Service Time Zone Service User Directory Service Workspace Service |
|
Use the following instructions to start a specific Oracle Beehive managed component using the beectl command-line utility:
Determine the component identifier of the managed component to start. For more information about obtaining the component identifier, see "Determining the Managed Component Identifier".
Start a specific Oracle Beehive managed component using the beectl command-line utility, use the start command with the --component option and argument.
The following example illustrates the command and option, including the component identifier noted from the output in Step 2 of "Determining the Managed Component Identifier":
beectl> start --component BEEAPP_instance1.host.domain.com
Starting beehive component "BEEAPP_instance1.host.domain.com" ...Successfully started beehive component "BEEAPP_instance1.host.domain.com".Operation completed in <time>.
Note:
To start more than one managed component, specify the --component option multiple times: once before each argument. For example:start --component <componentID1> --component <componentID2>... --component <componentIDn>Use the following instructions to stop a specific Oracle Beehive managed component using the beectl command-line utility:
Determine the ID of the managed component to stop. For more information about obtaining the component identifier, see "Determining the Managed Component Identifier".
Stop a specific Oracle Beehive managed component using the beectl command-line utility, use the stop command with the --component option and argument.
The following example illustrates the command and option, including the component identifier noted from the output in Step 2 of "Determining the Managed Component Identifier":
beectl> stop --component BEEAPP_instance1.host.domain.com
Stopping beehive component "BEEAPP_instance1.host.domain.com" ...
Successfully stopped beehive component "BEEAPP_instance1.host.domain.com".
Operation completed in <time>.
1 of 1 component(s) stopped successfully.
Note:
To stop more than one managed component, specify the --component option multiple times: once before each argument. For example:stop --component <componentID1> --component <componentID2>... --component <componenIDn>Use the following instructions to restart a specific Oracle Beehive managed component using the beectl command-line utility:
Determine the ID of the managed component to restart. For more information about obtaining the component identifier, see "Determining the Managed Component Identifier".
Restart a specific Oracle Beehive managed component using the beectl command-line utility, use the restart command with the --component option and argument.
The following example illustrates the command and option, including the component identifier, as it appears in the output within Step 1 of "Determining the Managed Component Identifier":
beectl> restart --component BEEAPP_instance1.host.domain.com Stopping beehive component "BEEAPP_instance1.host.domain.com" ... Successfully stopped beehive component "BEEAPP_instance1.host.domain.com". Operation completed in <time>. Starting beehive component "BEEAPP_instance1.host.domain.com" ... Successfully started beehive component "BEEAPP_instance1.host.domain.com". Operation completed in <time>. 1 of 1 component(s) restarted successfully.
Note:
To restart more than one managed component, specify the --component option multiple times: once before each argument. For example:restart --component <componentID1> --component <componentID2>... --component <componentIDn>Oracle Beekeeper is installed as a separate, stand-alone OC4J process. To start or stop Oracle Beekeeper, you start or stop the OC4J component, by using the opmnctl utility.
Ensure your environment is set with the following variables. Adjust the variables to match the install path and version numbers appropriate to your particular installation:
export ORACLE_BASE=/home/oracle/oracle/product export ORACLE_HOME=$ORACLE_BASE/1.5.1.0.0/beekeeper_1 export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/opmn/bin
To start Oracle Beekeeper, perform the following steps:
From the command line on the machine where Oracle Beekeeper is installed, start opmnctl:
> opmnctl start opmnctl: opmn started.
Check the status of the OC4J process:
> opmnctl status
You should see output similar to the following:
Processes in Instance: BeehiveControl ---------------+--------------+-----+--------- ias-component | process-type | pid | status ---------------+--------------+-----+--------- bkpr | bkpr | N/A | Down
Start Oracle Beekeeper
Using Oracle Beekeeper 1.5.1.0 or later:
> opmnctl startproc process-type=BEEKEEPER opmnctl: starting opmn managed processes...
Using Oracle Beekeeper 1.4.3 or earlier:
> opmnctl startproc process-type=bkpr opmnctl: starting opmn managed processes...
To stop Oracle Beekeeper, perform the following steps:
From the command line on the machine where Oracle Beekeeper is installed, run the following command:
In Oracle Beekeeper 1.5.1.0 or later:
> opmnctl stopproc process-type=BEEKEEPER opmnctl: stopping opmn managed processes...
In Oracle Beekeeper 1.4.3 or earlier:
> opmnctl stopproc process-type=bkpr opmnctl: stopping opmn managed processes...
If you want to, you can also stop opmnctl:
> opmnctl stopall opmnctl: stopping opmn and all managed processes...
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|