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.

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.

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.

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:

Login to Fusion Middleware Control.

Expand WebLogic Domain in the Target Navigation Pane.

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

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:

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