4 Configuring WebCenter Sites Domain
After you have installed WebCenter Sites, you can configure the domain, which you can also extend for high availability.
Refer to the following sections to create the database schemas, configure a WebLogic domain, and verify the configuration:
- Starting the Servers
After configuration is complete, start Node Manager, then the WebLogic Administration Server and Managed Servers. - Verifying the Configuration
After completing all configuration steps, you can perform additional steps to verify that your domain is properly configured.
Parent topic: Installing and Configuring Oracle WebCenter Sites
Starting the Servers
After configuration is complete, start Node Manager, then the WebLogic Administration Server and Managed Servers.
For more information on additional tools you can use to manage your domain, see Overview of Oracle Fusion Middleware Administration Tools in Administering Oracle Fusion Middleware.
Parent topic: Configuring WebCenter Sites Domain
Starting Node Manager
-
Change to the following directory:
-
(UNIX)
setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0_131
-
(Windows)
set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_131
-
-
Enter the following command:
-
(UNIX) Using
nohup
andnm.out
as an example output file:nohup ./startNodeManager.sh >
LOG_DIR
/nm.out&where
LOG_DIR
is the location of directory in which you want to store the log files. -
(Windows)
startNodeManager.cmd
Note:
On Windows operating systems, Oracle recommends that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.
See Running Node Manager as a Startup Service in Administering Node Manager for Oracle WebLogic Server.
-
Parent topic: Starting the Servers
Starting the Administration Server
-
Change to the following directory:
-
(UNIX)
setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0_131
-
(Windows)
set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_131
-
-
Enter the following command:
-
(UNIX)
./startWebLogic.sh
-
(Windows)
startWebLogic.cmd
-
If you selected Production Mode on the Domain Mode and JDK screen when you created the domain, you see a prompt for the Administrator user login credentials as the Administrator Account screen provides.
For more information about starting the Administration Server, see Starting and Stopping Administration Server in Administering Oracle Fusion Middleware.
In production mode, you can create a boot identity file to bypass the need to provide a user name and password when starting the Administration Server. See Creating a Boot Identity File for an Administration Server in Administering Server Startup and Shutdown for Oracle WebLogic Server.
You can verify that the Administration Server is up and running by accessing the Administration Server Console. The URL is provided on the End of Configuration screen (http://administration_server_host:administration_server_port/console
). The default Administration Server port number is 7001
.
Note:
Make sure that the database hosting your product schemas is up and running and accessible by the Administration Server.
For more information about how to use the Administration Console, see Getting Started Using Oracle WebLogic Server Administration Console in Administering Oracle Fusion Middleware.
Parent topic: Starting the Servers
Verifying the Configuration
After completing all configuration steps, you can perform additional steps to verify that your domain is properly configured.
To verify that the domain is configured properly, see Performing Additional Domain Configuration Tasks.
Parent topic: Configuring WebCenter Sites Domain