| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter 11g Release 1 (11.1.1) Part Number E12405-10 |
|
|
View PDF |
| Oracle® Fusion Middleware Administrator's Guide for Oracle WebCenter 11g Release 1 (11.1.1) Part Number E12405-10 |
|
|
View PDF |
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 (Announcements, Discussions, Documents, Mail, Instant Messaging and Presence, Personal Events, Search, Wiki and Blog, Worklists) 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:
Section 8.2, "Starting and Stopping Managed Servers for WebCenter Application Deployments"
Section 8.4, "Starting and Stopping Custom WebCenter Applications"
You perform all start and stop operations from the Oracle WebLogic Server Administration Console too. .
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.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".
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.
To start Node Manager:
(First time only). Run the following script to set StartScriptEnabled=true in the nodemanager.properties file:
(UNIX) ORACLE_COMMON_HOME/common/bin/setNMProps.sh (Windows) ORACLE_COMMON_HOME\common\bin\setNMProps.cmd
To start the Node Manager:
Navigate to WL_HOME/server/bin.
From the command line, enter:
WL_HOME/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 the managed servers. Note that you need to run the setNMProps script only once.
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.
Note:
The only exceptions are portlet producer and external application registration which are both dynamic. New portlet producers and updates to existing producers are immediately available; there is no need to restart the WebCenter application or the managed server. Similarly for external application configuration.When you start or restart the managed server, all WebCenter applications deployed on the managed server start automatically (including WebCenter Spaces).
This section describes starting and stopping managed servers throughFusion Middleware Control. See also, "Starting and Stopping WebLogic Managed Servers Using the Command Line" in Oracle Fusion Middleware Administrator's Guide.
To start, stop, or restart a managed server through Fusion Middleware Control:
Login to Fusion Middleware Control and navigate to the home page for WebCenter Spaces or your custom WebCenter application as follows:
Navigate to the home page for this application's managed server:
For WebCenter Spaces - Find WebLogic Server (Related Components section), and then click the name of the managed server. For WebCenter Spaces, this is always WLS_Spaces.
For custom WebCenter applications - Find Deployed On (Summary section), and then click the name of the managed server.
The home page for the managed server displays (Figure 8-1).
If you know the name of the managed server where your application's is deployed, you can navigate directly to this page if you expand the parent WebLogic Domain in the Target Navigation Pane.
From the WebLogic Server menu:
To start the managed server, choose Control > Start Up.
To stop the managed server, choose Control > Shut Down.
Alternatively, right-click the name of the managed server in the Target Navigation Pane to access menu options for the managed server.
It's easy to start, restart, and shut down WebCenter Spaces from Fusion Middleware Control:
Alternatively, use WLST:
Note:
You can also start WebCenter Spaces through Oracle WebLogic Server Administration Console.Starting WebCenter Spaces makes the application available to its users; stopping it makes it unavailable.
To start WebCenter Spaces through Fusion Middleware Control:
In Fusion Middleware Control, navigate to the home page for WebCenter Spaces.
See Section 6.2, "Navigating to the Home Page for WebCenter Spaces".
From the main WebCenter menu, choose WebCenter >Control > Start Up.
Alternatively, right-click WebCenter Spaces (WLS_Spaces) in the Target Navigation Pane to access this menu option.
A progress message displays.
Click Close.
Note how the application status changes to Up (Green arrow).
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.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."
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 (WLS_Spaces) remains available.
To stop a WebCenter Spaces application through Fusion Middleware Control:
In Fusion Middleware Control, navigate to the home page for WebCenter Spaces.
See Section 6.2, "Navigating to the Home Page for WebCenter Spaces".
From the main menu, choose WebCenter >Control > Shut Down.
Alternatively, right-click WebCenter Spaces (WLS_Spaces)in the Target Navigation Pane to access this menu option.
Click OK to continue.
A progress message displays.
Click Close.
Note how the status changes to Down (Red arrow).
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.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."
It's easy to start and shut down custom WebCenter applications from Fusion Middleware Control:
Starting Custom WebCenter Applications Using Fusion Middleware Control
Stopping Custom WebCenter Applications Using Fusion Middleware Control
Alternatively, use WLST:
Starting a custom WebCenter application makes it available to its users; stopping it makes it unavailable.
When you stop a custom WebCenter application, the managed server on which it is deployed remains available.
To start a custom WebCenter application through Fusion Middleware Control:
In Fusion Middleware Control, navigate to the home page for the custom WebCenter application.
See Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications".
From the Application Deployment menu, choose Application Deployment >Control > Start Up.
Alternatively, right-click the name of the custom WebCenter application in the Target Navigation Pane to access this menu option.
A progress message displays.
Click Close.
Note how the application status changes to Up (Green arrow).
Use the WLST command startApplication to start a custom WebCenter 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.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."
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.
Note:
You can also stop WebCenter Spaces through Oracle WebLogic Server Administration Console.To stop a custom WebCenter application:
In Fusion Middleware Control, navigate to the home page for the custom WebCenter application.
See Section 6.3, "Navigating to the Home Page for Custom WebCenter Applications".
From the main menu, choose Application Deployment >Control > Shut Down.
Alternatively, right-click the name of the custom WebCenter application in the Target Navigation Pane to access this menu option.
Click OK to continue.
A progress message displays.
Click Close.
Note how the status changes to Down (Red arrow).
Use the WLST command stopApplication to stop a custom WebCenter 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.12.3.1, "Running Oracle WebLogic Scripting Tool (WLST) Commands."
|
 Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
