3.3 Starting, Stopping, and Restarting Content Server

There are several methods for starting, stopping, and restarting Oracle Content Server. Which method you choose depends on your requirements, your authorization, and the task you want to complete. For example, when certain configuration changes are made to Content Server, such as when components are enabled or disabled, Content Server must be restarted. Available methods include:

  • Oracle WebLogic Server Administration Console

  • Oracle WebLogic Scripting Tool (WLST) commands

  • Oracle Enterprise Manager Fusion Middleware Control

Note:

In earlier releases, the Admin Server could be directly used to start, stop, and restart Content Server. This functionality has been replaced in 11g Release 1 (11.1.1), although other functions are still managed with the Admin Server.

Procedures are described in these topics:

3.3.1 Starting Content Server

Content Server is initially started during the process of installing and deploying the instance. At other times you may want to start a Content Server instance. For example, you would start an instance after it has been stopped when changing a Content Server configuration setting.

3.3.1.1 Starting Content Server with Oracle WebLogic Server

The Oracle WebLogic Server Administration Console is available to Content Server administrators because these users must have administrative privileges to manage Content Server. The Node Manager must be configured and running in order to start Content Server.

To start Content Server with the Oracle WebLogic Server Administration Console:

  1. On the Administration Console Domain Structure navigation bar, select Environment, then Servers.

  2. On the Conversion tab for the Summary of Servers section, click the name of the Oracle UCM server for Oracle Content Server.

  3. In the Settings for server_name section, click the Control tab.

  4. In the Server Status area, click Start.

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

3.3.1.2 Starting Content Server with Oracle WebLogic Scripting Tool Commands

The Oracle WebLogic Scripting Tool (WLST) provides a quick method for using command lines to execute actions.

To start Content Server with Oracle WLST commands:

Run the command to start the Oracle WebLogic Server Administration Console, then the command to start Oracle UCM (in this example, named UCM_server1):

MW_HOME../domain_name/bin/startWeblogic.sh
MW_HOME../domain_name/bin/startManagedWeblogic.sh UCM_server1

For more information, see Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

3.3.1.3 Starting Content Server with Fusion MIddleware Control

Oracle Enterprise Manager Fusion Middleware Control can be used by administrators to manage multiple domains, including Oracle WebLogic Server running Content Server. This method of starting a Content Server also provides access to information about the Oracle UCM domain in which Content Server is deployed.

To start Content Server with Fusion Middleware Control:

  1. In the Fusion Middleware Control interface navigation tree, expand the appropriate domain name (for example, UCM_ucm_domain).

  2. Expand Content Management, then Universal Content Management, then Content Server.

  3. Select the Oracle UCM Content Server name (for example, Oracle Content Server (UCM_server1)). The home page for your Oracle Content Server instance displays.

  4. From the UCM menu on the Oracle Content Server page, select Control, then Start. The Content Server is started.

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

3.3.2 Stopping Content Server

Content Server may be stopped for several reasons, including changing the configuration, such as enabling or disabling a server component.

3.3.2.1 Stopping Content Server with Oracle WebLogic Server

The Oracle WebLogic Server Administration Console is available to Content Server administrators because the users must have administrative privileges to manage Content Server. The Node Manager must be configured and running in order to stop Content Server.

To stop Content Server with the Oracle WebLogic Server Administration Console:

  1. On the Administration Console Domain Structure navigation bar, select Environment, then Servers.

  2. On the Conversion tab for the Summary of Servers section, click the name of the Oracle UCM server for Oracle Content Server.

  3. In the Settings for server_name section, click the Control tab.

  4. In the Server Status area, click Shutdown.

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

3.3.2.2 Stopping Content Server with Oracle WebLogic Scripting Tool Commands

The Oracle WebLogic Scripting Tool (WLST) provides a quick method for using command lines to execute actions.

To Stop Content Server with Oracle WLST commands:

Run the command to stop Oracle UCM (in this example, named UCM_server1), then, if necessary, run the command to stop the Oracle WebLogic Server Administration Console:

MW_HOME../domain_name/bin/stopManagedWeblogic.sh UCM_server1
MW_HOME../domain_name/bin/stopWeblogic.sh

For more information, see Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

3.3.2.3 Stopping Content Server with Fusion MIddleware Control

Oracle Enterprise Manager Fusion Middleware Control can be used by administrators to manage multiple domains, including Oracle WebLogic Server running Content Server. This method of stopping a Content Server also provides access to information about the Oracle UCM domain in which Content Server is deployed.

To stop Content Server with Fusion Middleware Control:

  1. In the navigation tree, expand the appropriate domain name (for example, UCM_ucm_domain).

  2. Expand Content Management, then Universal Content Management, then Content Server.

  3. Select the Content Server instance name (for example, Oracle Content Server (UCM_server1)). The home page for your Oracle Content Server instance displays.

  4. From the UCM menu on the Oracle Content Server page, select Control, then Shut Down.... The Oracle Content Server is shut down.

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

3.3.3 Restarting Content Server

Content Server may be restarted for several reasons, including changing the configuration, such as enabling or disabling a server component.

3.3.3.1 Restarting Content Server with Oracle WebLogic Server

The Oracle WebLogic Server Administration Console is available to Content Server administrators because the users must have administrative privileges to manage Content Server. The Node Manager must be configured and running in order to stop and start Content Server.

To restart Content Server with the Oracle WebLogic Server Administration Console:

  1. On the Administration Console Domain Structure navigation bar, select Environment, then Servers.

  2. On the Conversion tab for the Summary of Servers section, click the name of the Oracle UCM server for Oracle Content Server.

  3. In the Settings for server_name section, click the Control tab.

  4. In the Server Status area, click Shutdown.

  5. Confirm that Oracle Content Server has stopped, and then click Start.

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

3.3.3.2 Restarting Content Server with Oracle WebLogic Scripting Tool Commands

The Oracle WebLogic Scripting Tool (WLST) provides a quick method for using command lines to execute actions.

To Restart Content Server with Oracle WLST commands:

Run the command to stop Oracle UCM (in this example, named UCM_server1), the command to stop the Oracle WebLogic Server Administration Console, then the command to start the Oracle WebLogic Server Administration Console, then the command to start Oracle UCM:

MW_HOME../domain_name/bin/stopManagedWeblogic.sh UCM_server1
MW_HOME../domain_name/bin/stopWeblogic.sh
MW_HOME../domain_name/bin/startWeblogic.sh
MW_HOME../domain_name/bin/startManagedWeblogic.sh UCM_server1

For more information, see Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

3.3.3.3 Restarting Content Server with Fusion MIddleware Control

Oracle Enterprise Manager Fusion Middleware Control can be used by administrators to manage multiple domains, including Oracle WebLogic Server running Content Server. This method of stopping and starting a Content Server also provides access to information about the Oracle UCM domain in which Content Server is deployed.

To restart Content Server with Fusion Middleware Control:

  1. In the navigation tree, expand the appropriate domain name (for example, UCM_ucm_domain).

  2. Expand Content Management, then Universal Content Management, then Content Server.

  3. Select the Content Server instance name (for example, Oracle Content Server (UCM_server1)). The home page for your Oracle Content Server instance displays.

  4. From the UCM menu on the Oracle Content Server page, select Control, then Shut Down....

  5. Confirm that the Oracle Content Server instance is shut down.

  6. From the UCM menu on the Oracle Content Server page, select Control, then Start. The Oracle Content Server is started.

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.