Skip Headers
Oracle® Fusion Middleware Administrator's Guide
11g Release 1 (11.1.1)

Part Number E10105-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

4 Starting and Stopping Oracle Fusion Middleware

This chapter describes procedures for starting and stopping Oracle Fusion Middleware.

It contains the following topics:

4.1 Overview of Starting and Stopping Procedures

Oracle Fusion Middleware is a flexible product that you can start and stop in different ways, depending on your requirements. In most situations, you can use Fusion Middleware Control, Oracle WebLogic Server Administration Console, or the WLST or OPMN commands to start or stop Oracle Fusion Middleware components.

These tools are completely compatible and, in most cases, can be used interchangeably. For example, you can start a J2EE component using WLST and stop it using Fusion Middleware Control.

Note:

For information about starting and stopping servers for IBM Websphere, see "Starting and Stopping Servers on IBM WebSphere" in the Oracle Fusion Middleware Third-Party Application Server Guide.

4.2 Starting and Stopping Oracle WebLogic Server Instances

You can start Oracle WebLogic Server Administration Servers using the WLST command line. You can start and stop Managed Servers using scripts, the WLST command line, the WebLogic Server Administration Console, or Fusion Middleware Control. The following sections describe how to start and stop WebLogic Servers using the WLST command line, Fusion Middleware Control, or both:

4.2.1 Starting and Stopping Administration Servers

You can start and stop Oracle WebLogic Server Administration Servers using the WLST command line or a script. When you start or stop the Administration Server, you also start or stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.

For example, to start an Administration Server, use the following script:

MW_HOME/user_projects/domains/domain_name/bin/startWebLogic.sh
         -Dweblogic.management.username=weblogic
         -Dweblogic.management.password=password
         -Dweblogic.system.StoreBootIdentity=true

To stop an Administration Server, use the following script:

MW_HOME/user_projects/domains/domain_name/bin/stopWeblogic.sh 
       username password [admin_url]

4.2.2 Starting and Stopping Managed Servers

You can start and stop Managed Servers using Fusion Middleware Control or WLST commands and scripts, as described in the following topics:

4.2.2.1 Starting and Stopping Managed Servers Using Fusion Middleware Control

Fusion Middleware Control and the Oracle WebLogic Server Administration Console use Node Manager to start Managed Servers. If you are starting a Managed Server that does not contain Oracle Fusion Middleware products other than Oracle WebLogic Server, you can start the servers using the procedure in this section.

However, if the Managed Server contains other Oracle Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter, or Oracle JRF, you must first configure Node Manager, as described in Section 4.2.4.

To start or stop a WebLogic Server Managed Server using Fusion Middleware Control:

  1. From the navigation pane, expand the farm, then WebLogic Domain, and then the domain.

  2. Select the Managed Server.

  3. From the WebLogic Server menu, choose Control, then Start Up or Shut Down.

Alternatively, you can right-click the server, then choose Control, then Start Up or Shut Down.

4.2.2.2 Starting and Stopping Managed Servers Using WLST

You can use a script or WLST to start and stop a WebLogic Server Managed Server.

For example, to start a WebLogic Server Managed Server, use the following script:

(UNIX) MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh
           managed_server_name admin_url 
(Windows) MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd
           managed_server_name admin_url

When prompted, enter your user name and password.

To stop a WebLogic Server Managed Server, use the following script:

(UNIX) MW_HOME/user_projects/domains/domain_name/bin/stopManagedWebLogic.sh
            managed_server_name admin_url username password 
(Windows) MW_HOME\user_projects\domains\domain_name\bin\stopManagedWebLogic.cmd 
            managed_server_name admin_url username password

4.2.3 Enabling Servers to Start Without Supplying Credentials

You can enable the Administration Server and Managed Servers to start without prompting you for the administrator username and password.

  1. For the Administration Server, create a boot.properties file:

    1. Create the following directory:

      MW_HOME/user_
      projects/domains/domain_name/servers/AdminServer/security
      
    2. Use a text editor to create a file called boot.properties in the security directory created in the previous step, and enter the following lines in the file:

      username=adminuser
      password=password
      
  2. For each Managed Server:

    1. Create the following directory:

      MW_HOME/user_
      projects/domains/domain_name/servers/server_name/security
      
    2. Copy the boot.properties file you created for the Administration Server to the security directory you created in the previous step.

  3. Restart the Administration Server and Managed Servers, as described in Section 4.2.1 and Section 4.2.2.

Note:

When you start the Administration Server or Managed Server, the username and password entries in the file are encrypted.

For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible in order for the entries to be encrypted.

See Also:

"Boot Identity Files" in the Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server for more information

4.2.4 Configuring Node Manager to Start Managed Servers

If a Managed Server contains other Oracle Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter, or Oracle JRF, the Managed Servers environment must be configured to set the correct classpath and parameters. This environment information is provided through the start scripts, such as startWebLogic and setDomainEnv, which are located in the domain directory.

If the Managed Servers are started by Node Manager (as is the case when the servers are started by the Oracle WebLogic Server Administration Console or Fusion Middleware Control), Node Manager must be instructed to use these start scripts so that the server environments are correctly configured. Specifically, Node Manager must be started with the property StartScriptEnabled=true.

There are several ways to ensure that Node Manager starts with this property enabled. As a convenience, Oracle Fusion Middleware provides the following script, which adds the property StartScriptEnabled=true to the nodemanager.properties file:

(UNIX) ORACLE_COMMON_HOME/common/bin/setNMProps.sh.
(Windows) ORACLE_COMMON_HOME\common\bin\setNMProps.cmd

For example, on Linux, execute the setNMProps script and start Node Manager:

ORACLE_COMMON_HOME/common/bin/setNMProps.sh
MW_HOME/wlserver_n/server/bin/startNodeManager.sh

When you start Node Manager, it reads the nodemanager.properties file with the StartScriptEnabled=true property, and uses the start scripts when it subsequently starts Managed Servers. Note that you need to run the setNMProps script only once.

See Also:

"Using Node Manager" in the Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server for other methods of configuring and starting Node Manager

4.3 Starting and Stopping Components

You can start and stop components using the command line, the WebLogic Server Administration Console, or Fusion Middleware Control, depending upon the component. The following topics describe how to start and stop components using Fusion Middleware Control and the command line:

4.3.1 Starting and Stopping Components Using Fusion Middleware Control

To start or stop a component:

  1. From the navigation pane, expand the farm, then navigate to the component.

  2. Select the component, such as SoaInfra.

  3. From the dynamic target menu, choose Control, then Start Up or Shut Down.

Note:

If OPMN is not started, you cannot start system components such as Oracle HTTP Server or Oracle Internet Directory using Fusion Middleware Control. To start OPMN, use the following command:
opmnctl start

4.3.2 Starting and Stopping Components Using the Command Line

If a component is a Java component, you use WLST commands to start and stop the component. If a component is a system component, you use opmnctl commands to start and stop the components.

  • To start and stop Java components, use the WLST startApplication and stopApplication commands:

    startApplication(appName, [options])
    stopApplication(appName, [options])
    

    For example, to start Oracle Directory Integration Platform, use the following command:

    startApplication("DIP")
    
  • To start and stop system components, use the opmnctl command-line tool. It is located in the following directory:

    (UNIX) ORACLE_HOME/opmn/bin
    (Windows) ORACLE_HOME\opmn\bin
    

    To start or stop OPMN and all system processes, such as Oracle HTTP Server:

    opmnctl startall
    opmnctl stopall
    

    To start, stop, or restart a component using opmnctl:

    opmnctl startproc ias-component=component_name
    opmnctl stopproc ias-component=component_name
    opmnctl restartproc ias-component=component_name
    

    For example, to start Oracle HTTP Server, ohs1:

    opmnctl startproc ias-component=ohs1
    

    To start, stop, or restart the subprocess of a component:

    opmnctl stopproc process-type=process
    opmnctl startproc process-type=process
    opmnctl restartproc process-type=process
    

4.4 Starting and Stopping Fusion Middleware Control

If Fusion Middleware Control is configured for a domain, it is automatically started or stopped when you start or stop an Oracle WebLogic Server Administration Server, as described in Section 4.2.1.

4.5 Starting and Stopping Oracle Management Agent

Oracle Management Agent is designed specifically for monitoring particular Oracle Fusion Middleware components.

To start Oracle Management Agent, use the following command:

opmnctl startproc ias-component=EMAGENT

To stop Oracle Management Agent, use the following command:

opmnctl stopproc ias-component=EMAGENT

4.6 Starting and Stopping Applications

You can start and stop applications using Fusion Middleware Control, the WebLogic Server Administration Console, or the WLST command line. The following topics describe how to start and stop applications using Fusion Middleware Control and the command line:

4.6.1 Starting and Stopping Java EE Applications Using Fusion Middleware Control

To start or stop a Java EE application using Fusion Middleware Control:

  1. From the navigation pane, expand Application Deployments.

  2. Select the application.

  3. From the Application Deployment menu, choose Control, then Start Up or Shut Down.

To start or stop a SOA Composite application using Fusion Middleware Control:

  1. From the navigation pane, expand the farm, then SOA, and then soa-infra.

  2. Select the application.

  3. On the SOA Composite page, click Start Up or Shut Down.

4.6.2 Starting and Stopping Java EE Applications Using WLST

To start or stop a Java EE application with the WLST command line, use the following commands:

startApplication(appName, [options])
stopApplication(appName, [options])

The application must be fully configured and available in the domain. The startApplication command returns a WLSTProgress object that you can access to check the status of the command. In the event of an error, the command returns a WLSTException. For more information about the WLSTProgress object, see "WLSTProgress Object" in the Oracle Fusion Middleware Oracle WebLogic Scripting Tool.

4.7 Starting and Stopping Your Oracle Fusion Middleware Environment

This section provides procedures for starting and stopping an Oracle Fusion Middleware environment. An environment can consist of an Oracle WebLogic Server domain, an Administration Server, multiple Managed Servers, Java components, system components, including Identity Management components, and a database used as a repository for metadata. The components may be dependent on each other. Therefore, it is important to start and stop them in the proper order.

You can follow these procedures when you need to completely shut down your Oracle Fusion Middleware environment. For example, when preparing to perform a complete backup of your environment, or apply a patch.

4.7.1 Starting an Oracle Fusion Middleware Environment

To start an Oracle Fusion Middleware environment:

  1. Start any database-based repository:

    1. Set the ORACLE_HOME environment variable to the Oracle home for the database.

    2. Set the ORACLE_SID environment variable to the SID for the database (default is orcl.)

    3. Start the Net Listener:

      ORACLE_HOME/bin/lsnrctl start
      
    4. Start the database instance:

      ORACLE_HOME/bin/sqlplus /nolog
      SQL> connect SYS as SYSDBA
      SQL> startup
      SQL> quit
      
  2. Start the Oracle WebLogic Server Administration Server as described in Section 4.2.1.

  3. If you have not already done so, configure Node Manager, as described in Section 4.2.4.

  4. Ensure the Node Manager is running. If the Node Manager is not running, start it by executing the following command:

    MW_HOME/user_projects/domains/DOMAIN_NAME/bin/startNodeManager.sh
    
  5. Start Oracle Identity Management system components:

    1. Set the ORACLE_HOME environment variable to the Oracle home and ORACLE_INSTANCE environment variables for the Identity Management components.

    2. Start OPMN and all system components:

      opmnctl startall
      
  6. Start the Oracle WebLogic Server Managed Servers as described in Section 4.2.2.2. Any applications deployed to the server are also started.

  7. Start OPMN and all other system components, such as Oracle HTTP Server.

    1. Set the ORACLE_HOME and ORACLE_INSTANCE environment variables to the Oracle home and Oracle instance for the system components.

    2. Start OPMN and all system components in that Oracle instance:

      opmnctl startall
      
  8. If your environment includes components that are targets monitored by Oracle Management Agent, start Oracle Management Agent, as described in Section 4.5.

4.7.2 Stopping an Oracle Fusion Middleware Environment

To stop an Oracle Fusion Middleware environment:

  1. Stop system components, such as Oracle HTTP Server. You can stop them in any order.

    1. Set the ORACLE_HOME and ORACLE_INSTANCE environment variables to the Oracle home and Oracle instance for the system components.

    2. Stop OPMN and all system components in that Oracle instance:

      opmnctl stopall
      
  2. If your environment includes components that are targets monitored by Oracle Management Agent, stop Oracle Management Agent, as described in Section 4.5.

  3. Stop the Oracle WebLogic Server Managed Servers, as described in Section 4.2. Any applications deployed to the server are also stopped.

  4. Stop Oracle Identity Management components:

    1. Set the ORACLE_HOME environment variable to the Oracle home for the Identity Management components.

    2. Stop OPMN and all system components:

      opmnctl stopall
      
  5. Stop the Administration Server as described in Section 4.2.1.

  6. If you want to stop the Node Manager, you can use the kill command:

    kill -9 PID
    
  7. Stop any database-based repository:

    1. Set the ORACLE_HOME environment variable to the Oracle home for the database.

    2. Set the ORACLE_SID environment variable to the SID for the database (default is orcl).

    3. Stop the database instance:

      ORACLE_HOME/bin/sqlplus /nolog
      SQL> connect SYS as SYSDBA
      SQL> shutdown
      SQL> quit
      
    4. Stop the Net Listener:

      ORACLE_HOME/bin/lsnrctl stop
      

4.8 Starting and Stopping: Special Topics

This section contains the following special topics about starting and stopping Oracle Fusion Middleware:

4.8.1 Starting and Stopping in High Availability Environments

There are special considerations and procedures for starting and stopping High Availability environments, such as:

4.8.2 Forcing a Shutdown of Oracle Database

If you find that the Oracle Database instance is taking a long time to shut down, you can use the following commands to force an immediate shutdown:

ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> SHUTDOWN IMMEDIATE;

An 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.)

  • Oracle does not wait for users currently connected to the database to disconnect. Oracle implicitly rolls back active transactions and disconnects all connected users.

The next startup of the database will not require any instance recovery procedures.

See Also:

Oracle Database Administrator's Guide in the Oracle Database 11g documentation library