4 Configuring Oracle WebCenter Portal Domain
After you have installed Oracle WebCenter Portal, 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:
- Creating the Database Schemas
Before you can configure an Oracle WebCenter Portal domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware. - Configuring the Domain
Use the Configuration Wizard to create and configure a domain. - 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. - Setting Up an External LDAP-Based Identity Store
Oracle WebCenter Content Server and Oracle WebCenter Portal's Discussion Server rely on external LDAP-based identity stores. Therefore, if your portals need to include documents, discussions, or announcements, you must install and configure an external LDAP-based identity store.
Creating the Database Schemas
Before you can configure an Oracle WebCenter Portal domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.
- Installing and Configuring a Certified Database
Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running. - Starting the Repository Creation Utility
Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed on your system. - Navigating the Repository Creation Utility Screens to Create Schemas
Enter required information in the RCU screens to create the database schemas.
Parent topic: Configuring Oracle WebCenter Portal Domain
Installing and Configuring a Certified Database
Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.
Note:
For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated
(ATP-D)
and Oracle Autonomous Transaction Processing-Shared
(ATP-S)), you must modify the wallet settings and set the
environment variables, and apply patches on ORACLE HOME
.
For more information, see Settings to connect to
Autonomous Transaction Processing Database and Applying Patches on ORACLE
HOME.
See Understanding Database Requirements for an Oracle Fusion Middleware Installation.
Parent topic: Creating the Database Schemas
Starting the Repository Creation Utility
Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed on your system.
To start the RCU:
Parent topic: Creating the Database Schemas
Navigating the Repository Creation Utility Screens to Create Schemas
Enter required information in the RCU screens to create the database schemas.
- Introducing the RCU
The Welcome screen is the first screen that appears when you start the RCU. - Selecting a Method of Schema Creation
Use the Create Repository screen to select a method to create and load component schemas into the database. - Providing Database Connection Details
On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database. - Specifying a Custom Prefix and Selecting Schemas
Specify a custom prefix and database schema to automatically select the Common Infrastructure Services and dependent schemas. - Specifying Schema Passwords
On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords. - Specifying Custom Variables
Specify the custom variables for the Oracle WebCenter Portal schema. - Completing Schema Creation
Navigate through the remaining RCU screens to complete schema creation.
Parent topic: Creating the Database Schemas
Introducing the RCU
The Welcome screen is the first screen that appears when you start the RCU.
Click Next.
Selecting a Method of Schema Creation
Use the Create Repository screen to select a method to create and load component schemas into the database.
-
If you have the necessary permissions and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have SYSDBA privileges.
-
If you do not have the necessary permissions or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option generates a SQL script that you can give to your database administrator. See About System Load and Product Load in Creating Schemas with the Repository Creation Utility.
-
If the DBA has already run the SQL script for System Load, select Perform Product Load.
Note:
For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you must create schemas as a
Normal
user, and though, you do not have full SYS or SYSDBA privileges on the database, you must select System Load and Product Load.
Providing Database Connection Details
On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.
Note:
If you are unsure of the database service name, you can obtain
it from the SERVICE_NAMES
parameter in the initialization
parameter file of the database. If the initialization parameter file does
not contain the SERVICE_NAMES
parameter, then the service
name is the same as the global database name, which is specified in the
DB_NAME
and DB_DOMAIN
parameters.
For an Oracle Autonomous Transaction Processing-Shared
(ATP-S) database, use
the database service name,
<databasename>_tpurgent
or
<databasename>_tp
, specified in
tnsnames.ora
. For service name details, see Database Service Names for
Autonomous Transaction Processing and Autonomous JSON Database in
Using Oracle Autonomous Database on Shared Exadata
Infrastructure.
To create schemas on an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you can specify the connection credentials using only the Connection String option. In this screen, a warning message is displayed. You can ignore the warning and continue with the schema creation. For more information, see SYS DBA Privileges Warning After Applying Patches.
To provide the database connection details:
- On the Database Connection Details screen, provide the database
connection details.
For example:
- Database Type: Oracle Database
- Connection String Format: Connection Parameters or Connection String
- Connection String: examplehost.exampledomain.com:1521:Orcl.exampledomain.com
- Host Name: examplehost.exampledomain.com
- Port: 1521
- Service Name: Orcl.exampledomain.com
- User Name: sys
- Password: ******
- Role: SYSDBA
For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), enter connect string in the following format:
jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>
In the connect string, you must pass
TNS_alias
as the database name found intnsnames.ora
, andTNS_ADMIN
property to the location of the wallet files,ojdbc.properties
, andtnsnames.ora
.Note:
For an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, you must use only one of the database service names,<databasename>_tpurgent
or<databasename>_tp
, specified intnsnames.ora
. For database service name details, see Database Service Names for Autonomous Transaction Processing and Autonomous JSON Database in Using Oracle Autonomous Database on Shared Exadata Infrastructure.Example connect string for Oracle Autonomous Transaction Processing-Dedicated (ATP-D) database::
jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/wallet_dbname/
Example connect string for Oracle Autonomous Transaction Processing-Shared (ATP-S) database:
jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/
- Click Next to proceed, then click OK in the dialog window that confirms a successful database connection.
Specifying a Custom Prefix and Selecting Schemas
Specify a custom prefix and database schema to automatically select the Common Infrastructure Services and dependent schemas.
Oracle WebCenter Portal relies on the MDS, STB, OPSS, IAU, IAU_APPEND, and IAU_VIEWER schemas. Depending on the Oracle WebCenter Portal components used, your Oracle WebCenter Portal installation may also require the following schemas: WEBCENTER, DISCUSSIONS, ACTIVITIES, and PORTLET.
-
MDS: WebCenter Portal uses the Oracle Metadata Services (MDS) repository to store its configuration data; it accesses the MDS repository as a JDBC data source within the Oracle WebLogic framework.
-
STB: This provides Common Infrastructure Services to Fusion Middleware products. This schema must exist for the Datasource Connection Defaults screen during domain configuration.
-
OPSS, IAU, IAU_APPEND, and IAU_VIEWER: These schemas are used to provide Platform Security Services.
-
WEBCENTER: There must be a distinct WEBCENTER schema for WebCenter Portal.
-
ACTIVITIES: Analytics can be used only by a single application within a domain, and there can only be one instance of this schema in any domain.
-
PORTLET: Many Portlet Producer applications can be deployed to a single Custom Services Producer managed server. Portlet Producer applications can share a single PORTLET schema.
Specifying Schema Passwords
On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords.
Note:
For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), the schema password must be minimum 12 characters, and must contain at least one uppercase, one lower case, and one number.
You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.
Click Next.
Specifying Custom Variables
Specify the custom variables for the Oracle WebCenter Portal schema.
Oracle WebCenter Portal has one custom variable, Analytics
. Changing the Value from the default of N to Y allows Oracle database partitioning to be used for this schema.
Note:
To enable partitioning for Analytics data, the database must have partitioning enabled.For an enterprise deployment, Oracle recommends partitioning of the Analytics data. This partitions the analytics data by month. In a partitioned environment, the recommended method for purging data is simply to drop the month-based partitions that are no longer required.
See Also:
-
Partitioning Oracle WebCenter Portal's Analytics Data in Administering Oracle Fusion Middleware
-
Custom Variables in Creating Schemas with the Repository Creation Utility
Completing Schema Creation
Navigate through the remaining RCU screens to complete schema creation.
On the Map Tablespaces screen, the Encrypt Tablespace check box appears only if you enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU.
To complete schema creation:Configuring the Domain
Use the Configuration Wizard to create and configure a domain.
For information on other methods to create domains, see Additional Tools for Creating, Extending, and Managing WebLogic Domains in Creating WebLogic Domains Using the Configuration Wizard.
- Starting the Configuration Wizard
Start the Configuration Wizard to begin configuring a domain. - Navigating the Configuration Wizard Screens to Create and Configure the Domain
Enter required information in the Configuration Wizard screens to create and configure the domain for the topology.
Parent topic: Configuring Oracle WebCenter Portal Domain
Starting the Configuration Wizard
Start the Configuration Wizard to begin configuring a domain.
To start the Configuration Wizard:
Parent topic: Configuring the Domain
Navigating the Configuration Wizard Screens to Create and Configure the Domain
Enter required information in the Configuration Wizard screens to create and configure the domain for the topology.
Note:
You can use this procedure to extend an existing domain. If your needs do not match the instructions in the procedure, be sure to make your selections accordingly, or see the supporting documentation for more details.
- Selecting the Domain Type and Domain Home Location
Use the Configuration Type screen to select a Domain home directory location, optimally outside the Oracle home directory. - Selecting the Configuration Templates for Oracle WebCenter Portal
Use the Templates screen to select the templates you require. - Configuring High Availability Options
Use this screen to configure service migration and persistence settings that affect high availability. This screen appears for the first time when you create a cluster that uses automatic service migration, persistent stores, or both, and all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply the selected HA options. - Selecting the Application Home Location
Use the Application Location screen to select the location to store applications associated with your domain, also known as the Application home directory. - Configuring the Administrator Account
Use the Administrator Account screen to specify the user name and password for the default WebLogic Administrator account for the domain. - Specifying the Domain Mode and JDK
Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK). - Specifying the Database Configuration Type
Use the Database Configuration type screen to specify details about the database and database schema. - Specifying JDBC Component Schema Information
Use the JDBC Component Schema screen to verify or specify details about the database schemas. - Testing the JDBC Connections
Use the JDBC Component Schema Test screen to test the data source connections. - Selecting Advanced Configuration
Use the Advanced Configuration screen to complete the domain configuration. - Configuring the Administration Server Listen Address
Use the Administration Server screen to select the IP address of the host. - Configuring Node Manager
Use the Node Manager screen to select the type of Node Manager you want to configure, along with the Node Manager credentials. - Configuring Managed Servers for Oracle WebCenter Portal
Use the Managed Servers screen to configure Managed Servers. - Configuring a Cluster for Oracle WebCenter Portal
Use the Clusters screen to create a new cluster. - Defining Server Templates
If you are creating dynamic clusters for a high availability setup, use the Server Templates screen to define one or more server templates for domain. - Configuring Dynamic Servers
If you are creating dynamic clusters for a high availability setup, use the Dynamic Servers screen to configure the dynamic servers. - Assigning Oracle WebCenter Portal Managed Servers to the Cluster
Use the Assign Servers to Clusters screen to assign managed servers to the new cluster - Configuring Coherence Clusters
Use the Coherence Clusters screen to configure the Coherence cluster. - Creating a New Oracle WebCenter Portal Machine
Use the Machines screen to create new machines in the domain. A machine is required so that Node Manager can start and stop servers. - Assigning Servers to Oracle WebCenter Portal Machines
Use the Assign Servers to Machines screen to assign the Administration Server and Managed Servers to the new machine you just created. - Virtual Targets
If you have a WebLogic Server Multitenant (MT) environment, you use the Virtual Targets screen to add or delete virtual targets. For this installation (not a WebLogic Server MT environment), you do not enter any values; just select Next. - Partitions
The Partitions screen is used to configure partitions for virtual targets in WebLogic Server Multitenant (MT) environments. Select Next without selecting any options. - Reviewing Your Configuration Specifications and Configuring the Domain
The Configuration Summary screen shows detailed configuration information for the domain you are about to create. - Writing Down Your Domain Home and Administration Server URL
The End of Configuration screen shows information about the domain you just configured.
Parent topic: Configuring the Domain
Selecting the Domain Type and Domain Home Location
Use the Configuration Type screen to select a Domain home directory location, optimally outside the Oracle home directory.
To specify the Domain type and Domain home directory:
- On the Configuration Type screen, select Create a new domain.
- In the Domain Location field, specify your Domain home directory.
For more details about this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
Selecting the Configuration Templates for Oracle WebCenter Portal
Use the Templates screen to select the templates you require.
On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following template:
-
Oracle WebCenter Portal - 12.2.1.4.0 [wcportal]
Selecting this template automatically selects the following as dependencies:
-
Oracle Enterprise Manager
-
Oracle WSM Policy Manager
-
Oracle JRF
-
WebLogic Coherence Cluster Extension
-
You can also select any of the Oracle WebCenter Portal products listed in the following table. You do not need to select all of these templates, and you can always run the configuration wizard again to add products to your domain later.
Table 4-1 Oracle WebCenter Portal Products Available for Configuration
Product | Dependencies |
---|---|
Oracle WebCenter Portlet Producers |
Oracle WSM Policy Manager Oracle JRF WebLogic Coherence Cluster Extension |
Oracle WebCenter Analytics Collector |
Oracle JRF WebLogic Coherence Cluster Extension |
Note:
If you plan to install WebCenter Content alongside WebCenter Portal, see Selecting the Configuration Templates for Oracle WebCenter Content in Installing and Configuring Oracle WebCenter Content for the domain extension templates you should choose to install WebCenter Content as well.
For more information about this screen, see Templates in Creating WebLogic Domains Using the Configuration Wizard.
Configuring High Availability Options
Use this screen to configure service migration and persistence settings that affect high availability. This screen appears for the first time when you create a cluster that uses automatic service migration, persistent stores, or both, and all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply the selected HA options.
Enable Automatic Service Migration
Select Enable Automatic Service Migration to enable pinned services to migrate automatically to a healthy Managed Server for failover. It configures migratable target definitions that are required for automatic service migration and the cluster leasing. Choose one of these cluster leasing options:
-
Database Leasing - Managed Servers use a table on a valid JDBC System Resource for leasing. Requires that the Automatic Migration data source have a valid JDBC System Resource. If you select this option, the Migration Basis is configured to Database and the Data Source for Automatic Migration is also automatically configured by the Configuration Wizard. If you have a high availability database, such as Oracle RAC, to manage leasing information, configure the database for server migration according to steps in High-availability Database Leasing.
-
Consensus Leasing - Managed Servers maintain leasing information in-memory. You use Node Manager to control Managed Servers in a cluster. (All servers that are migratable, or which could host a migratable target, must have a Node Manager associated with them.) If you select this option, the Migration Basis is configured to Consensus by the Configuration Wizard.
See Leasing for more information on leasing.
See Service Migration for more information on Automatic Service Migration.
JTA Transaction Log Persistence
-
Default Persistent Store - Configures the JTA Transaction Log store of the servers in the default file store.
-
JDBC TLog Store - Configures the JTA Transaction Log store of the servers in JDBC stores.
Oracle recommends that you select JDBC TLog Store. When you complete the configuration, you have a cluster where JDBC persistent stores are set up for Transaction logs.
JMS Service Persistence
A persistent JMS store is a physical repository for storing persistent message data and durable subscribers. It can be either a disk-based file store or a JDBC-accessible database. You can use a JMS file store for paging of messages to disk when memory is exhausted.
-
JMS File Store - Configures a component to use JMS File Stores. If you select this option, you can choose the File Store option in the Advanced Configuration Screen to change the settings, if required. In the File Stores screen, you can set file store names, directories, and synchronous write policies.
-
JMS JDBC Store - Configures a component to use JDBC stores for all its JMS servers. When you complete the configuration, you have a cluster and JDBC persistent stores are configured for the JMS servers.
Selecting the Application Home Location
Use the Application Location screen to select the location to store applications associated with your domain, also known as the Application home directory.
Oracle recommends that you locate your Application home in accordance with the directory structure in What Are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware, where the Application home is located outside the Oracle home directory. This directory structure helps avoid issues when you need to upgrade or re-install your software.
For more about the Application home directory, see About the Application Home Directory.
For more information about this screen, see Application Location in Creating WebLogic Domains Using the Configuration Wizard.
Configuring the Administrator Account
Use the Administrator Account screen to specify the user name and password for the default WebLogic Administrator account for the domain.
Oracle recommends that you make a note of the user name and password that you enter on this screen; you need these credentials later to boot and connect to the domain's Administration Server.
Specifying the Domain Mode and JDK
Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK).
On the Domain Mode and JDK screen:
-
Select Production in the Domain Mode field.
-
Select the Oracle HotSpot JDK in the JDK field.
Specifying the Database Configuration Type
Use the Database Configuration type screen to specify details about the database and database schema.
On the Database Configuration type screen, select RCU Data. This option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for schemas needed to configure the domain.
Note:
If you select Manual Configuration on this screen, you must manually fill in parameters for your schema on the next screen.
For an Autonomous Transaction Processing database, (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you must select only the RCU Data option.
After selecting RCU Data, specify details in the following fields:
Field | Description |
---|---|
DBMS/Service |
Enter the database DBMS name, or service name if you selected a service type driver. Example: |
Host Name |
Enter the name of the server hosting the database. Example:
|
Port |
Enter the port number on which the database listens. Example: |
Schema Owner Schema Password |
Enter the username and password for connecting to the database's Service Table schema. This is the schema username and password entered for the Service Table component on the Schema Passwords screen in the RCU (see Specifying Schema Passwords). The default username is
|
For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), specify the connection credentials using only the Connection URL String option, and enter the connect string in the following format:
jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path of the wallet
files, ojdbc.properties, and tnsnames.ora>
In the connect string, you must pass TNS_alias
as the
database name found in tnsnames.ora
, and TNS_ADMIN
property to the location of the wallet files, ojdbc.properties
, and
tnsnames.ora
.
Example connect string for Oracle Autonomous Transaction Processing-Dedicated (ATP-D) database:
jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/wallet_dbname/
Example connect string for Oracle Autonomous Transaction Processing-Shared (ATP-S) database:
jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/
Click Get RCU Configuration when you finish specifying the database connection information. The following output in the Connection Result Log indicates that the operation succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
For more information about the schema installed when the RCU is run, see About the Service Table Schema in Creating Schemas with the Repository Creation Utility.
See Database Configuration Type in Creating WebLogic Domains Using the Configuration Wizard .
Specifying JDBC Component Schema Information
Use the JDBC Component Schema screen to verify or specify details about the database schemas.
Verify that the values populated on the JDBC Component Schema screen are correct for all schemas. If you selected RCU Data on the previous screen, the schema table should already be populated appropriately.
For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), specify the connection credentials using only the Connection URL String option, and enter the connect string in the following format:
jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>
In the connect string, you must pass TNS_alias
as the
database service name found in tnsnames.ora
, and
TNS_ADMIN
property to the location of the wallet files,
ojdbc.properties
, and tnsnames.ora
.
Example connect string for Oracle Autonomous Transaction Processing-Dedicated (ATP-D) database:
jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/wallet_dbname/
Example connect string for Oracle Autonomous Transaction Processing-Shared (ATP-S) database:
jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/wallet_dbname/
For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:
See JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard for more details about this screen.
Testing the JDBC Connections
Use the JDBC Component Schema Test screen to test the data source connections.
A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
By default, the schema password for each schema component is the password you specified while creating your schemas. If you want different passwords for different schema components, manually edit them in the previous screen (JDBC Component Schema) by entering the password you want in the Schema Password column, against each row. After specifying the passwords, select the check box corresponding to the schemas that you changed the password in and test the connection again.
For more information about this screen, see JDBC Component Schema Test in Creating WebLogic Domains Using the Configuration Wizard.
Selecting Advanced Configuration
Use the Advanced Configuration screen to complete the domain configuration.
On the Advanced Configuration screen, select:
-
Administration Server
Required to properly configure the listen address of the Administration Server.
-
Node Manager
Required to configure Node Manager.
-
Topology
Required to configure the Oracle WebCenter Portal Managed Server.
Optionally, select other available options as required for your desired installation environment. The steps in this guide describe a standard installation topology, but you may choose to follow a different path. If your installation requirements extend to additional options outside the scope of this guide, you may be presented with additional screens to configure those options. For information about all Configuration Wizard screens, see Configuration Wizard Screens in Creating WebLogic Domains Using the Configuration Wizard.
Configuring the Administration Server Listen Address
Use the Administration Server screen to select the IP address of the host.
Select the drop-down list next to Listen Address and select the IP address of the host where the Administration Server will reside, or use the system name or DNS name that maps to a single IP address. Do not use All Local Addresses
.
Do not specify any server groups for the Administration Server.
Configuring Node Manager
Use the Node Manager screen to select the type of Node Manager you want to configure, along with the Node Manager credentials.
Select Per Domain Default Location as the Node Manager type, then specify Node Manager credentials.
For more information about this screen, see Node Manager in Creating WebLogic Domains Using the Configuration Wizard.
For more about Node Manager types, see Node Manager Overview in Administering Node Manager for Oracle WebLogic Server.
Configuring Managed Servers for Oracle WebCenter Portal
Use the Managed Servers screen to configure Managed Servers.
On the Managed Servers screen, new Managed Servers named WC_Collaboration
, WC_Portlet
, and WC_Portal
are automatically created by default.
These Managed Server names will be referenced throughout this document; if you choose different names be sure to replace them as needed.
To configure Managed Servers for Oracle WebCenter Portal:
Configuring multiple Managed Servers is one of the steps needed to configure the standard topology for high availability. For more information about the high availability standard topology, see Understanding the Fusion Middleware Standard HA Topology in High Availability Guide.
For more information about the next steps to prepare for high availability after your domain is configured, see Preparing Your Environment for High Availability.
For more information about this screen, see Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.
Configuring a Cluster for Oracle WebCenter Portal
Use the Clusters screen to create a new cluster.
On the Clusters screen:
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, see Considerations for Choosing Unicast or Multicast in Administering Clusters for Oracle WebLogic Server.
You can also create clusters using Fusion Middleware Control. In this case, you can configure cluster communication (unicast or multicast) when you create the new cluster. See Create and configure clusters in Oracle WebLogic Server Administration Console Online Help.
For more information about this screen, see Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Defining Server Templates
If you are creating dynamic clusters for a high availability setup, use the Server Templates screen to define one or more server templates for domain.
For steps to create a dynamic cluster for a high availability setup, see Using Dynamic Clusters in High Availability Guide.
Configuring Dynamic Servers
If you are creating dynamic clusters for a high availability setup, use the Dynamic Servers screen to configure the dynamic servers.
If you are not configuring a dynamic cluster, click Next to continue configuring the domain.
Note:
When you create dynamic clusters, keep in mind that after you assign the Machine Name Match Expression, you do not need to create machines for your dynamic cluster.To create a dynamic cluster for a high availability setup, see Using Dynamic Clusters in High Availability Guide.
Assigning Oracle WebCenter Portal Managed Servers to the Cluster
Use the Assign Servers to Clusters screen to assign managed servers to the new cluster
On the Assign Servers to Clusters screen:
For more information about options on this screen, see Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Configuring Coherence Clusters
Use the Coherence Clusters screen to configure the Coherence cluster.
Leave the default port number as the Coherence cluster listen port. After configuration, the Coherence cluster is automatically added to the domain.
Note:
Setting the unicast listen port to 0
creates an offset for the Managed Server port numbers. The offset is 5000
, meaning the maximum allowed value that you can assign to a Managed Server port number is 60535
, instead of 65535
.
See Table 5-2 for more information and next steps for configuring Coherence.
For Coherence licensing information, see Oracle Coherence Products in Licensing Information.
Creating a New Oracle WebCenter Portal Machine
Use the Machines screen to create new machines in the domain. A machine is required so that Node Manager can start and stop servers.
If you plan to create a high availability environment and know the list of machines your target topology requires, you can follow the instructions in this section to create all the machines at this time. For more about scale out steps, see Optional Scale Out Procedure in High Availability Guide.
Note:
If you are extending an existing domain, you can assign servers to any existing machine. It is not necessary to create a new machine unless your situation requires it.
For more information about this screen, see Machines in Creating WebLogic Domains Using the Configuration Wizard.
Assigning Servers to Oracle WebCenter Portal Machines
Use the Assign Servers to Machines screen to assign the Administration Server and Managed Servers to the new machine you just created.
On the Assign Servers to Machines screen:
For more information about this screen, see Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.
Virtual Targets
If you have a WebLogic Server Multitenant (MT) environment, you use the Virtual Targets screen to add or delete virtual targets. For this installation (not a WebLogic Server MT environment), you do not enter any values; just select Next.
For details about this screen, see Virtual Targets in Creating WebLogic Domains Using the Configuration Wizard.
Note:
WebLogic Server Multitenant virtual targets are deprecated in WebLogic Server 12.2.1.4.0 and will be removed in the next release.Partitions
The Partitions screen is used to configure partitions for virtual targets in WebLogic Server Multitenant (MT) environments. Select Next without selecting any options.
For details about options on this screen, see Partitions in Creating WebLogic Domains Using the Configuration Wizard.
Note:
WebLogic Server Multitenant domain partitions are deprecated in WebLogic Server 12.2.1.4.0 and will be removed in the next release.Reviewing Your Configuration Specifications and Configuring the Domain
The Configuration Summary screen shows detailed configuration information for the domain you are about to create.
Review each item on the screen and verify that the information is correct. To make any changes, go back to a screen by clicking the Back button or selecting the screen in the navigation pane. Domain creation does not start until you click Create.
For more details about options on this screen, see Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
Writing Down Your Domain Home and Administration Server URL
The End of Configuration screen shows information about the domain you just configured.
Make a note of the following items because you need them later:
-
Domain Location
-
Administration Server URL
You need the domain location to access scripts that start Node Manager and Administration Server, and you need the URL to access the Administration Server.
Click Finish to dismiss the Configuration Wizard.
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.
- Starting Node Manager
- Starting the Administration Server
- Starting the Oracle WebCenter Portal Managed Servers
Parent topic: Configuring Oracle WebCenter Portal Domain
Starting Node Manager
-
Change to the following directory:
-
(UNIX)
setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0_211
-
(Windows)
set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_211
-
-
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_211
-
(Windows)
set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_211
-
-
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
Starting the Oracle WebCenter Portal Managed Servers
To start the Managed Servers:
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 Oracle WebCenter Portal Domain
Setting Up an External LDAP-Based Identity Store
Oracle WebCenter Content Server and Oracle WebCenter Portal's Discussion Server rely on external LDAP-based identity stores. Therefore, if your portals need to include documents, discussions, or announcements, you must install and configure an external LDAP-based identity store.
If you configure an external LDAP-based identity store, then WebCenter Portal and all the back-end components configured for any Oracle WebCenter Portal tools and services must use the same external LDAP-based identity store. Table 4-2 describes whether additional configuration is required for any back-end component if a shared external LDAP-based identity store is used.
For information about installing and configuring back-end components for Oracle WebCenter Portal tools and services, see Preparing Back-End Components for WebCenter Portal Tools and Services.
Table 4-2 Configuring Back-End Components for a Shared External LDAP-Based Identity Store
Back-End Component | Built-In Support | Additional Configuration Requirement |
---|---|---|
Content Server |
Database |
Configure Content Server to use the same external LDAP-based identity store as Oracle WebCenter Portal. For information, see Reassociating the Identity Store with an External LDAP Server in Administering Oracle WebCenter Portal. |
Oracle SOA Suite (BPEL server) |
Embedded LDAP store |
Configure Oracle SOA Suite to use the same external LDAP-based identity store as Oracle WebCenter Portal. For information about:
|
Oracle WebCenter Portal can use libOVD
to allow multiple identity stores to be used with portals. Sites with multiple identity stores can use libOVD
to aggregate their user profile information. For information, see Aggregating Multiple Identity Store LDAP Servers Using libOVD in Administering Oracle WebCenter
Portal.
Parent topic: Configuring Oracle WebCenter Portal Domain