upload and stage directories for the new Managed Servers.Parent topic: Configuring the Enterprise Deployment
As you perform the tasks in this chapter, you will be referencing the following directory variables, which are defined in File System and Directory Variables Used in This Guide.
ORACLE_HOME
ASERVER_HOME
APPLICATION_HOME
DEPLOY_HOME
OHS_CONFIG_DIR
JAVA_HOME
In addition, you'll be referencing the following virtual IP (VIP) addresses and host names defined in Physical and Virtual IP Addresses Required by the Enterprise Topology:
ADMINVHN
WCPHOST1
WCPHOST2
DBHOST1
DBHOST2
SCAN Address for the Oracle RAC Database (DB-SCAN.examle.com)
The following sections describe how to install the software for an enterprise deployment.
To start the installation program:
When the installation program appears, you are ready to begin the installation.
The installation program displays a series of screens, in the order listed in the following table.
If you need additional help with any of the installation screens, click the screen name.
| Screen | Description |
|---|---|
|
This screen introduces you to the product installer. |
|
|
Use this screen to automatically search My Oracle Support for available patches or automatically search a local directory for patches that you’ve already downloaded for your organization. |
|
|
Use this screen to specify the location of your Oracle home directory. For more information about Oracle Fusion Middleware directory structure, see "Selecting Directories for Installation and Configuration" in Planning an Installation of Oracle Fusion Middleware. |
|
|
Use this screen to select the type of installation and consequently, the products and feature sets you want to install. Select WebCenter Portal. Notes:
|
|
|
This screen verifies that your system meets the minimum necessary requirements. If there are any warning or error messages, you can refer to one of the following documents in the Roadmap for Verifying Your System Environment section in Planning Your Oracle Fusion Middleware Infrastructure Installation. |
|
|
If you already have an Oracle Support account, use this screen to indicate how you would like to receive security updates. If you do not have one and are sure you want to skip this step, clear the check box and verify your selection in the follow-up dialog box. |
|
|
Use this screen to verify the installation options you selected. Click Install to begin the installation. |
|
|
This screen allows you to see the progress of the installation. Click Next when the progress bar reaches 100% complete. |
|
|
Review the information on this screen, then click Finish to dismiss the installer. |
If you have followed the EDG shared storage recommendations, there is a separate shared storage volume for product installations on WCPHOST2, and you must also install the software on WCPHOST2. For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.
Before you can configure an Oracle WebCenter Portal domain, you must install the required schemas on a certified database for use with this release of Oracle Fusion Middleware.
The following topics describe how to install the required schemas.
To start the Repository Creation Utility (RCU):
Schema creation involves the following tasks.
Click Next.
If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have the necessary privileges.
If you do not have the necessary permission or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option will generate a SQL script, which can be provided to your database administrator. See "Understanding System Load and Product Load" in Creating Schemas with the Repository Creation Utility.
Provide the database connection details for RCU to connect to your database.
In the Host Name field, enter the SCAN address of the Oracle RAC Database.
Enter the DBMS/Service details.
Enter the Schema Owner and Schema Password details.
Click Next to proceed, then click OK on the dialog window confirming that connection to the database was successful.
Select Select existing prefix, and then select the prefix you used when you created the initial domain in Creating the Initial Infrastructure Domain for an Enterprise Deployment.
From the list of schemas, select WebCenter Portal . This will automatically select the required WebCenter Portal schemas. In addition, the following dependent schemas have already been installed with the Infrastructure and are grayed out:
Metadata Services
Audit Services
Audit Services Append
Audit Services Viewer
Oracle Platform Security Services
User Messaging Service
The custom prefix is used to logically group these schemas together for use in this domain only; you must create a unique set of schemas for each domain as schema sharing across domains is not supported.
Tip:
For more information about custom prefixes, see "Understanding Custom Prefixes" in Creating Schemas with the Repository Creation Utility.
For more information about how to organize your schemas in a multi-domain environment, see "Planning Your Schema Creation" in Creating Schemas with the Repository Creation Utility.
Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.
Specify how you want to set the schema passwords on your database, then specify and confirm your passwords.
Tip:
You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.
For an enterprise deployment, Oracle recommends that you enter “Y” to enable partitioning of the Analytics data.
This feature 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.
For information about partitioning analytics data, see "Partitioning Oracle WebCenter Portal's Analytics Data" in the Oracle Fusion Middleware Administrator's Guide.
On the Map Tablespaces screen, review the information, and then click Next to accept the default values.
Click OK in the confirmation dialog box.
Navigate through the remainder of the RCU screens to complete schema creation. When you reach the Completion Summary screen, click Close to dismiss RCU.
To verify that the schemas were created successfully, and to verify the database connection details, use SQL*Plus or another utility to connect to the database, using the WCPINFRA schema name and the password you provided.
For example:
./sqlplus
SQL*Plus: Release 11.2.0.4.0 Production on Fri Nov 1 08:44:18 2013
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Enter user-name: FMW1221_WEBCENTER
Enter password: wcpinfra_password
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
Extending the domain involves the following:
Follow the instructions in this section to update and configure the domain for the topology.
Note:
If your needs do not match the instructions given in the procedure, be sure to make your selections accordingly, or refer to the supporting documentation for additional details.
Domain configuration includes the following tasks.
On the Configuration Type screen, select Update an existing domain.
In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the Administration Server domain home you created in Creating the Initial Infrastructure Domain for an Enterprise Deployment.
For more information about the directory location variables, see File System and Directory Variables Used in This Guide
Tip:
More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
On the Templates screen, make sure Update Domain Using Product Templates is selected, then select the following templates:
Oracle WebCenter Portal – 12.2.1.1.0 [wcportal]
Oracle WebCenter Pagelet Producer – 12.2.1.1.0 [wcportal]
Oracle WebCenter Portlet Producers - 12.2.1.1.0 [wcportal]
Oracle WebCenter Discussion Server - 12.2.1.1.0 [wcportal]
Oracle WebCenter Analytics Collector - 12.2.1.1.0 [wcportal]
In addition, the following additional templates should already be selected, because they were used to create the initial domain in Creating the Initial Infrastructure Domain for an Enterprise Deployment:
Oracle Enterprise Manager - 12.2.1.1.0 [em]
Oracle WSM Policy Manager - 12.2.1.0 [oracle_common]
Oracle JRF - 12.2.1.1.0 [oracle_common]
WebLogic Coherence Cluster Extension - 12.2.1.1.0 [wlserver]
Tip:
More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.
On the Database Configuration Type screen, select RCU Data.
All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain.
Verify and ensure that credentials in all the fields are the same that you have provided while configuring Oracle Fusion Middleware Infrastructure.
Click Get RCU Configuration after you finish verifying 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.
Tip:
For more information about the RCU Data option, see "Understanding the Service Table Schema" in Creating Schemas with the Repository Creation Utility.
For more information about the other options on this screen, see "Datasource Defaults" in Creating WebLogic Domains Using the Configuration Wizard.
On the JDBC Component Schema screen, select all the WebCenter Portal schemas in the table.
When you select the schemas, the fields on the page are activated and the database connection fields are populated automatically.
Click Convert to GridLink and click Next.
On the GridLink Oracle RAC Component Schema screen, provide the information required to connect to the RAC database and component schemas, as shown in the following table.
| Element | Description and Recommended Value |
|---|---|
|
SCAN, Host Name, and Port |
Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, |
|
ONS Host and Port |
In the ONS Host field, enter the SCAN address for the Oracle RAC database. In the Port field, enter the ONS Remote port (typically, |
|
Enable Fan |
Select the Enable Fan check box to receive and process FAN events, |
Use the JDBC Component Schema Test screen to test the data source connections you have just configured.
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.
Tip:
For more information about the other options on this screen, see "Test Component Schema" in Creating WebLogic Domains Using the Configuration Wizard
To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:
Topology
Deployments and Services
On the Managed Servers screen, new Managed Servers for Oracle WebCenter Portal, Portlets, and Collaboration appear in the list of servers along with the other Managed Servers that were created earlier. These servers are created automatically by the Oracle WebCenter Portal configuration template you selected earlier in the Configuration Wizard session.
Perform the following tasks to modify the default Managed Servers and create a second Managed Server for each server type:
Select WC_Portal and rename it to WC_Portal1.
Select Clone to create another managed server. Rename the new server to WC_Portal2.
Repeat the above two steps to edit and create WC_Portlet1, WC_Portlet2, WC_Collaboration1 and WC_Collaboration2.
Tip:
More information about the options on the Managed Server screen can be found in Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.
| Server Name | Listen Address | Listen Port | Enable SSL | SSL Listen Port | Server Groups |
|---|---|---|---|---|---|
|
WLS_WSM1 |
WCPHOST1 |
7010 |
No |
Disabled |
WSMPM-MAN-SVR JRF-MAN-SVR WSM-CACHE-SVR |
|
WLS_WSM2 |
WCPHOST2 |
7010 |
No |
Disabled |
WSMPM-MAN-SVR JRF-MAN-SVR WSM-CACHE-SVR |
|
WC_Portal1 |
WCPHOST1 |
9001 |
No |
Disabled |
WebCenter Portal Managed Server WebCenter Portal Analytics Managed Server |
|
WC_Portal2 |
WCPHOST2 |
9001 |
No |
Disabled |
WebCenter Portal Managed Server WebCenter Portal Analytics Managed Server |
|
WC_Portlet1 |
WCPHOST1 |
9002 |
No |
Disabled |
WebCenter Portal Pagelet Producer Managed Server WebCenter Portal Portlet Producer Managed Server |
|
WC_Portlet2 |
WCPHOST2 |
9002 |
No |
Disabled |
WebCenter Portal Pagelet Producer Managed Server WebCenter Portal Portlet Producer Managed Server |
|
WC_Collaboration1 |
WCPHOST1 |
9003 |
No |
Disabled |
WebCenter Portal Discussions Managed Server |
|
WC_Collaboration2 |
WCPHOST2 |
9003 |
No |
Disabled |
WebCenter Portal Discussions Managed Server |
In the Configure Clusters screen, add three new clusters:
Portal_Cluster
Portlet_Cluster
Collab_Cluster
For all three clusters, leave the default values for Cluster Address, Frontend Host, and Port.
Note:
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, refer to "Considerations for Choosing Unicast or Multicast" in Administering Clusters for Oracle WebLogic Server.
Tip:
More information about the options on this screen can be found in Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Use the Assign Servers to Clusters screen to assign Managed Servers to their respective cluster:
In the Clusters pane, select the cluster to which you want to assign the servers; in this case, Portal_Cluster.
In the Servers pane, assign WC_Portal1 to Portal_Cluster by doing one of the following:
Click once on WC_Portal1 Managed Server to select it, then click on the right arrow to move it beneath the selected cluster in the Clusters pane.
Double-click on WC_Portal1 to move it beneath the selected cluster in the clusters pane.
Repeat to assign WC_Portal2 to Portal_Cluster.
Repeat steps 1-3 to assign WC_Portlet1 and WC_Portlet2 to Portlet_Cluster.
Repeat steps 1-3 to assign WC_Collaboration1 and WC_Collaboration2 to Collaboration_Cluster.
Tip:
More information about the options on this screen can be found in Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.
Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the port number value at 9991, as it was defined during the initial Infrastructure domain creation.
Note:
For Coherence licensing information, refer to "Oracle Coherence" in Oracle Fusion Middleware Licensing Information.
Under the Unix Machine tab, verify the names of the machines you created when creating the initial Infrastructure domain.
Click Next to proceed.
Use the Assign Servers to Machines screen to assign the Managed Servers you just created to the corresponding machines in the domain.
Assign WC_Portal1, WC_Portlet1, WC_Collaboration1 to WCPHOST1.
Assign WC_Portal2, WC_Portlet2, WC_Collaboration2 to WCPHOST2.
Tip:
More information about the options on this screen can be found in Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.
Click Next to proceed to the next screen.
Click Next to proceed to the next screen.
With the Oracle Web Services Manager Policy Manager deployed to a separate cluster, the default targeting of the WSM-PM application to the Portal, Collaboration, and Portlet clusters can be removed.
For each of the Portal_Cluster, Collaboration_Cluster, and Portlet_Cluster in the Targets panel:
Select the wsm-pm application entry within the Application folder and click the left arrow button to remove it from the targets list.
With the Oracle Web Services Manager Policy Manager deployed to a separate cluster, the default targeting of the WSM-PM service resources to the Portal, Collaboration, and Portlet clusters can be removed.
For each of the Portal_Cluster, Collaboration_Cluster, and Portlet_Cluster in the Targets panel:
Select and remove the following two resources from the targets list:
mds-owsm
WSM Startup Class
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.
You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.
Domain creation will not begin until you click Update.
Tip:
More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
The Configuration Success screen will show the following items about the domain you just configured:
Domain Location
Administration Server URL
You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.
Click Finish to dismiss the configuration wizard.
Start the Administration Server to ensure the changes you have made to the domain have been applied.
After configuring the domain and unpacking it to the Managed Server domain directories on all the hosts, verify and update the upload and stage directories for the new Managed Servers.
This step is necessary to avoid potential issues when performing remote deployments and for deployments that require the stage mode.
To update these directory paths for all the Managed Servers in the Managed Server domain home directory:
Log in to the Oracle WebLogic Server Administration Console.
In the left navigation tree, expand Domain, and then Environment.
Click Lock & Edit.
Click Servers.
For each new Managed Server in the Managed Server domain home directory:
Click the name of the Managed Server.
Click the Configuration tab, and then click the Deployment tab.
Verify that the Staging Directory Name is set to the following:
MSERVER_HOME/servers/server_name/stage
Replace MSERVER_HOME with the directory path for the MSERVER_HOME directory; replace server_name with the name of the Server you are editing.
Update the Upload Directory Name to the following value:
ASERVER_HOME/servers/AdminServer/upload
Replace ASERVER_HOME with the directory path for the ASERVER_HOME directory.
Click Save.
Return to the Summary of Servers screen.
When you have modified these values for each Managed Server, click Activate Changes.
Now that you have extended the domain, restarted the Administration Server, and propagated the domain to the other hosts, you can start the newly configured Oracle WebCenter Portal servers.
This process involves three tasks:
Before you validate the Oracle WebCenter Portal configuration on WC_Portal1 Managed Server, grant the WebCenter Portal administrator role to the WCPAdministrators LDAP group.
To perform this task, refer to Configuring Roles for Administration of Oracle WebCenter Portal Products.
This section describes how to grant WebCenter Portal's Administrator role to a user account other than the default weblogic account.
After you have validated the successful configuration and startup of the Managed Servers on WCPHOST1, you can then start and validate the new Managed Servers on WCPHOST2, using the procedure in Starting and Validating the WC_Portal1, WC_Portlet1, WC_Collaboration1 Managed Servers.
For the validation URL, enter the following in your Web browser and log in using the enterprise deployment administration user (weblogic_wcp):
http://WCPHOST2:9001/webcenter/
Out-of-the box, analytics collectors are configured to communicate with the local WebCenter Portal application in a 1-1 relationship (the collectors listen on localhost). No additional analytics collector configuration is required.
However, you must configure the WebCenter Portal applications to send event messages to localhost:
Note:
Clustered analytics collectors are not supported for collecting WebCenter Portal events.To connect the WebCenter Portal application to the analytics collector:
This section describes the procedure to configure REST APIs.
These credential entries should already be configured as part of the domain extension for WebCenter Portal.
To confirm the seed entries in the credential store that enable the REST security tokens to function properly, execute these WLST commands:
Note:
If the credential maps already exist, JPS-01007 exceptions messages will be returned. This confirms the configuration.The WebCenter Portal Content Manager component and task flows utilize the WebCenter Content remote UI (RUI) APIs to provide content integration capabilities. While these libraries are directly included with the Portal installation, specific MBean configuration settings need to be modified for fail-safe runtime within a High Availability architecture.
Modify and validate the following attributes for the ADFConfig:WccAdfConfiguration and ADFConfig:ADFcConfig application-defined MBeans on the portal application:
ADFConfig:ADFcConfig:
AdfScopeHaSupport
ADFConfig:WccAdfConfiguration:
ClusterCompatible
TemporayDirectory
The upload temporary directory specified must be configured to a common directory location on a shared disk volume across all portal nodes when the portal is clustered in a High Availability environment.
The following sections describe how to configure the Oracle HTTP Server instances so they route requests for both public and internal URLs to the proper clusters in the enterprise topology.
To configure the Oracle HTTP Server instances in the Web tier so they route requests correctly to the Oracle WebCenter Portal clusters, use the following procedure to create an additional Oracle HTTP Server configuration file that creates and defines the parameters of the wcp.example.com virtual server.
This procedure assumes you performed the Oracle HTTP Server configuration tasks described in Configuring Oracle HTTP Server to Route Requests to the Application Tier.
To create the virtual host configuration file so requests are routed properly:
Before you can validate that requests are routed correctly through the Oracle HTTP Server instances, you must set the WebLogic Plug-In Enabled parameter for the clusters you just configured.
To validate the configuration of the Oracle HTTP Server virtual hosts and to verify that the hardware load balancer can route public service requests through the Oracle HTTP Server instances to the application tier:
To configure the Oracle HTTP Server instances in the Web tier so they route requests correctly to the internal Oracle WebCenter services, use the following procedure to edit existing wcpinternal_vh.conf file.
This procedure assumes you performed the Oracle HTTP Server configuration tasks described in Configuring Oracle HTTP Server to Route Requests to the Application Tier.
To edit the virtual host configuration file so requests are routed properly:
To validate the configuration of the Oracle HTTP Server virtual hosts and to verify that the hardware load balancer can route internal service requests through the Oracle HTTP Server instances to the application tier:
This section describes how to configure external tools and services for WebCenter Portal applications using Fusion Middleware Control or WLST commands. For most external services, you must set up a connection between the WebCenter Portal application and the backend server.
After installing Oracle WebCenter Portal, you must attach the default Oracle Web Services Manager (OWSM) security policy to the following:
WebCenter Portal application (webcenter)
Discussions application (owc_discussions)
WebCenter Services Portlet Producer (services-producer)
WSRP Tools Producer (wsrp-tools)
These steps are required because security policies for these Web service end points are not configured out-of-the-box.
If you want to provide discussions or announcements in WebCenter Portal, you must connect the application to a discussions server. To configure a connection for the WebCenter Portal Enterprise Deployment, the following values are required:
Discussions Server URL: http://wcpinternal.example.com/owc_discussions
Discussions Admin User: WebCenter Portal Admin user name from LDAP (for example, weblogic_wcp)
Discussions Admin Password: WebCenter Portal Admin user password
Authenticated User Web Service Policy URI: WSS 1.0 SAML Token Client Policy
You can connect to a discussions server using Fusion Middleware Control or WLST commands.
For more information, see "Managing Announcements and Discussions" in Administering Oracle WebCenter Portal.
Several out-of-the-box portlet producers can be registered with the WebCenter Portal application. In the WebCenter Portal Enterprise Deployment, the required producer URLs are as follows:
WSRP Producer URL: http://wcpinternal.example.com/wsrp-tools/portlets/wsrp2?WSDL
WebClipping Producer URL: http://wcpinternal.example.com/portalTools/webClipping/providers
OmniPortlet Producer URL: http://wcpinternal.example.com/portalTools/omniPortlet/providers
You can register portlet producers using Fusion Middleware Control or WLST commands.
For details on how to register portlet producers using Fusion Middleware Control, see "Managing Portlet Producers" in Administering Oracle WebCenter Portal.
If you want to expose WSRP and Oracle JPDK portlets and OpenSocial gadgets as pagelets in WebCenter Portal, you must register the pagelet producer. In the WebCenter Portal Enterprise Deployment, the required pagelet producer URL is:
http://wcpinternal.example.com/pagelets
You can register the pagelet producer using Fusion Middleware Control or WLST commands.
To register Pagelet Producer using Fusion Middleware Control:
Log in to Fusion Middleware Control as weblogic_wcp, and navigate to the WebCenter Portal home page.
Note:
When administering WebCenter resources in the Enterprise Manager Fusion Middleware Control, it is recommended to use the WebCenter-specific administrative user created in the remote LDAP authenticator (for example, weblogic_wcp). For more information, see Configuring Roles for Administration of an Enterprise Deployment.
For more information, see “Navigating to the Home page for WebCenter Portal” in Administering Oracle WebCenter Portal .
From the WebCenter Portal menu, select Register Producer.
Enter connection details for Pagelet Producer, as shown in the following table.
| Field | Description |
|---|---|
|
Connection Name |
A unique name to identify this Pagelet Producer instance within the application. The name must be unique across all WebCenter Portal connection types. The name specified here appears in Composer under the UI Components > Pagelet Producers folder (by default). |
|
Producer Type |
Select Pagelet Producer. |
|
Server URL |
The URL to Pagelet Producer. The URL must include a fully-qualified domain name. Use the following syntax:
For example:
If pagelets contain secure data, the registered URL must use the
The context root can be changed from /pagelets/ if necessary; for details, see “Redeploying Pagelet Producer to a Different Context” in Administering Oracle WebCenter Portal. Note: In WebCenter Portal, if the Pagelet Producer URL is protected by OAM, the URL to the pagelet catalog must be excluded (mapped directly without access control), or the catalog will appear to be empty when using REST. The pagelet catalog URL is |
Click OK. The new producer appears in the connection table.
To register out-of-the-box pagelet producers using WLST:
Start the WebLogic Scripting Tool:
WCPHOST1> ORACLE_COMMON_HOME/common/bin/wlst.sh
In WLST, connect as the administrator.
For example,
connect("weblogic_wcp","admin password","t3://ADMINVHN:7001",server="WC_Portal1")
Register the pagelet producer by entering the following command.
registerPageletProducer(appName='webcenter', name='PageletProducer', url='http://wcpinternal.example.com/pagelets', server='WC_Portal1')
For command syntax and examples, see registerPageletProducer in WebCenter WLST Command Reference.
You can also use WLST to list or edit the current connection details.
For information on how to run WLST commands, see “Running Oracle WebLogic Scripting Tool (WLST) Commands” in Administering Oracle WebCenter Portal.
You can configure Oracle Secure Enterprise Search (Oracle SES) services and crawlers using procedures in the "Managing Oracle SES Search" section in Oracle Fusion Middleware Administering Oracle WebCenter Portal.
Ensure that:
Oracle Secure Enterprise Search is registered with Oracle Internet Directory and the WebCenter Portal application is configured as an Oracle SES trusted entity, as described in the "Oracle SES - Configuration" section in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
Connection exists between the WebCenter Portal application and Oracle Secure Enterprise Search, as described in the "Setting Up Oracle SES Connections" section in Oracle Fusion Middleware Administering Oracle WebCenter Portal.
Ensure that any new URLs are added to the wcpinternal.example.com host in the wcinternal_vh.conf file as follows:
<Location /rsscrawl>
WLSRequest ON
WebLogicCluster WCPHOST1:9001,WCPHOST2:9001
WLProxySSL OFF
WLProxySSLPassThrough OFF
</Location>
<Location /sesUserAuth>
WLSRequest ON
WebLogicCluster WCPHOST1:9001,WCPHOST2:9001
WLProxySSL OFF
WLProxySSLPassThrough OFF
</Location>
In a WebCenter Portal Enterprise Deployment, if you choose to send notifications using mail, you must configure a connection to your corporate mail server and specify several unique parameters for the sent emails to appear correctly.
To ensure sufficient configuration for your mail server and business requirements, before completing this task, review Managing Mail in Administering Oracle WebCenter Portal for details on the required and optional configurations and parameters.
You can register a mail server using Fusion Middleware Control or WLST commands:
For details on how to register a mail server using Fusion Middleware Control, see Registering Mail Servers Using Fusion Middleware Control in Administering Oracle WebCenter Portal.