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

Part Number E12405-15
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

8 Starting and Stopping WebCenter Applications

Most WebCenter application configuration changes that you make, through Fusion Middleware Control or using WLST, are not dynamic; you must restart the managed server on which the application is deployed for your changes to take effect. For example, when you add or modify connection details for WebCenter services such as Announcements, Discussions, Documents, Mail, and so on, you must restart the application's managed server.

There are several exceptions; portlet producer and external application registration is dynamic. Any new portlet producers and external applications that you register are immediately available in your WebCenter application and any changes that you make to existing connections take effect immediately too.

This chapter includes the following sections:

You perform all start and stop operations from the Oracle WebLogic Server Administration Console too. See also "Starting and Stopping Servers" in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.

Note:

Node Manager must be running before you can start and stop administration servers, managed servers, and WebCenter applications through Fusion Middleware Control or Oracle WebLogic Server Administration Console.

Audience

The content of this chapter is intended for Fusion Middleware administrators (users granted the Admin or Operator role through the Oracle WebLogic Server Administration Console). See also, Section 1.8, "Understanding Administrative Operations, Roles, and Tools".

8.1 Starting Node Manager

Node Manager must be running before you can start and stop administration servers, managed servers, and WebCenter applications through Fusion Middleware Control or Oracle WebLogic Server Administration Console. Node Manager starts after installation, so you only need to restart Node Manager if someone specifically shuts it down.

For information on how to start Node Manager with startNodeManager.sh, see "Using Node Manager" in the Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.

8.2 Starting and Stopping Managed Servers for WebCenter Application Deployments

Most WebCenter configuration changes that you make, through Fusion Middleware Control or using WLST, are not dynamic; you must restart the managed server on which the application is deployed for your changes to take effect.

When you start or restart a managed server, all applications deployed on the managed server start automatically, see also Table 8-1.

Table 8-1 Oracle WebCenter Managed Servers and Applications

Managed Server Application(s)

WC_Spaces

webcenter (WebCenter Spaces)

webcenter-help (WebCenter Spaces Online Help)

WC_Portlet

portalTools (OmniPortlet and Web Clipping)

wsrp-tools (WSRP Tools)

pagelet-producer (Pagelet Producer)

WC_Collaboration

owc_discussions (WebCenter Discussions Server)

WC_Utilities

analytics-collector (WebCenter Analytics)

activitygraph-engines (WebCenter Activity Graph)

wcps-services (WebCenter Personalization Services)

WC_CustomPortal

<your_webcenter_portal_application_name>


Note:

This section describes how to start and stop WebCenter managed servers listed in Table 8-1. To start and stop managed servers for other components, refer to:

While a specific order in which to start managed servers is not mandated, if you must start multiple managed servers, it is good practice to start the managed server on which WebCenter Spaces or your WebCenter Portal application is deployed last.

To start, stop, or restart a WebCenter managed server through Fusion Middleware Control:

  1. Login to Fusion Middleware Control.

  2. Expand WebLogic Domain in the Target Navigation Pane.

  3. Expand wc_domain, and select the managed server you want to start or stop.

    The home page for the managed server displays (Figure 8-2).

    Figure 8-1 Managed Server Home Page

    Managed Server Home Page
  4. From the WebLogic Server menu:

    • To start the managed server, choose Control > Start Up.

    • To stop the managed server, choose Control > Shut Down.

    Figure 8-2 Managed Server Start Up or Shut Down

    Managed Server Home Page

    Alternatively, right-click the name of the managed server in the Target Navigation Pane to access menu options for the managed server.

To start and stop WebCenter managed servers using command line tools, see "Starting and Stopping WebLogic Managed Servers Using the Command Line" in Oracle Fusion Middleware Administrator's Guide.

8.3 Starting and Stopping WebCenter Spaces

It's easy to start, restart, and shut down WebCenter Spaces from Fusion Middleware Control:

Alternatively, use WLST:

You can also start WebCenter Spaces through Oracle WebLogic Server Administration Console.

Note:

Application configuration changes require you to restart the WC_Spaces managed server on which WebCenter Space is deployed. For details, see Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments".

8.3.1 Starting WebCenter Spaces Using Fusion Middleware Control

Starting WebCenter Spaces makes the application available to its users; stopping it makes it unavailable.

To start WebCenter Spaces through Fusion Middleware Control:

  1. In Fusion Middleware Control, navigate to the home page for WebCenter Spaces.

    See Section 6.2, "Navigating to the Home Page for WebCenter Spaces".

  2. From the main WebCenter menu, choose WebCenter >Control > Start Up.

    Alternatively, right-click WC_Spaces in the Target Navigation Pane to access this menu option.

    A progress message displays.

  3. Click Close.

Note how the application status changes to Up (Green arrow).

8.3.2 Starting WebCenter Spaces Using WLST

Use the WLST command startApplication to start WebCenter Spaces. For command syntax and detailed examples, see "startApplication" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For WebCenter Spaces, the appName argument is always webcenter.

For information on how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

8.3.3 Stopping WebCenter Spaces Using Fusion Middleware Control

When you stop WebCenter Spaces no one can use it. Stopping an application does not remove its source files from the server; you can later restart a stopped application to make it available again.

When you stop WebCenter Spaces, the managed server on which WebCenter Spaces is deployed (WC_Spaces) remains available.

To stop a WebCenter Spaces application through Fusion Middleware Control:

  1. In Fusion Middleware Control, navigate to the home page for WebCenter Spaces.

    See Section 6.2, "Navigating to the Home Page for WebCenter Spaces".

  2. From the main menu, choose WebCenter >Control > Shut Down.

    Alternatively, right-click WC_Spaces in the Target Navigation Pane to access this menu option.

  3. Click OK to continue.

    A progress message displays.

  4. Click Close.

Note how the status changes to Down (Red arrow).

8.3.4 Stopping WebCenter Spaces Using WLST

Use the WLST command stopApplication to stop WebCenter Spaces. For command syntax and detailed examples, see "stopApplication" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For WebCenter Spaces, the appName argument is always webcenter.

For information on how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

8.4 Starting and Stopping WebCenter Portal Applications

It's easy to start and shut down WebCenter Portal applications from Fusion Middleware Control:

Alternatively, use WLST:

You can also start WebCenter Portal applications through Oracle WebLogic Server Administration Console.

Note:

Application configuration changes require you to restart the managed server on which WebCenter Portal application is deployed. For details, see Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments".

8.4.1 Starting WebCenter Portal Applications Using Fusion Middleware Control

Starting a WebCenter Portal application makes it available to its users; stopping it makes it unavailable.

When you stop a WebCenter Portal application, the managed server on which it is deployed remains available.

To start a WebCenter Portal application through Fusion Middleware Control:

  1. In Fusion Middleware Control, navigate to the home page for the WebCenter Portal application.

    See Section 6.3, "Navigating to the Home Page for WebCenter Portal Applications".

  2. From the Application Deployment menu, choose Application Deployment >Control > Start Up.

    Alternatively, right-click the name of the WebCenter Portal application in the Target Navigation Pane to access this menu option.

    A progress message displays.

  3. Click Close.

Note how the application status changes to Up (Green arrow).

8.4.2 Starting WebCenter Portal Applications Using WLST

Use the WLST command startApplication to start a WebCenter Portal application. For command syntax and detailed examples, see "startApplication" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."

8.4.3 Stopping WebCenter Portal Applications Using Fusion Middleware Control

When you stop a WebCenter Portal application no one can use it. Stopping an application does not remove its source files from the server; you can later restart a stopped application to make it available again.

Note:

You can also stop WebCenter Spaces through Oracle WebLogic Server Administration Console.

To stop a WebCenter Portal application:

  1. In Fusion Middleware Control, navigate to the home page for the WebCenter Portal application.

    See Section 6.3, "Navigating to the Home Page for WebCenter Portal Applications".

  2. From the main menu, choose Application Deployment >Control > Shut Down.

    Alternatively, right-click the name of the WebCenter Portal application in the Target Navigation Pane to access this menu option.

  3. Click OK to continue.

    A progress message displays.

  4. Click Close.

Note how the status changes to Down (Red arrow).

8.4.4 Stopping WebCenter Portal Applications Using WLST

Use the WLST command stopApplication to stop a WebCenter Portal application. For command syntax and detailed examples, see "stopApplication" in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

For information on how to run WLST commands, see Section 1.13.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."