12 Configuring External WebCenter Portal Services for an Enterprise Deployment

This chapter describes how to configure external 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.

This chapter contains the following sections:

• Section 12.1, "Configuring the Discussions Server Connection"

• Section 12.2, "Configuring the Instant Messaging and Presence (IMP) Server Connection"

• Section 12.3, "Configuring a BPEL Server Connection for Worklists and Workflows"

• Section 12.4, "Registering Portlet Producers"

• Section 12.5, "Registering the Pagelet Producer"

• Section 12.6, "Configuring Search Services"

• Section 12.7, "Configuring the Mail Server for Notifications"

12.1 Configuring the Discussions Server Connection

If you want to provide Discussions or Announcement services in a WebCenter Portal application you must connect your application to a discussions server. To configure a connection for the WebCenter Portal Enterprise Deployment, the following values are required:

• Server URL: http://wcpinternal.mycompany.com/owc_discussions

• Admin User: discussions server admin user name

• Admin Password: discussions server admin password

You can connect to a discussions server using Fusion Middleware Control or WLST commands:

• Section 12.1.2, "Creating a Discussions Server Connection using WLST"

• Section 12.1.1, "Creating a Discussions Server Connection Using Fusion Middleware Control"

For more information, see "Managing the Announcements and Discussions Services" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.

12.1.1 Creating a Discussions Server Connection Using Fusion Middleware Control

To connect your WebCenter Portal application to a discussions server using Fusion Middleware Control:

1. Ensure that at least one of the managed server on which your application is deployed is up and running.

   For example, for the Spaces application, one of the WC_Spaces managed servers.

2. Log on to the Enterprise Manager Fusion Middleware Control Console at http://SOAHOST1:7001/em.

3. Navigate to the home page for your WebCenter Portal application.

   For example, to navigate to the home page for the Spaces application, select Farm_wcpedg_domain, WebCenter > Portal > Spaces, and then webcenter (WC_Spaces1).

4. From the WebCenter Portal drop-down menu, select Settings, and then Service Configuration.

5. Click Discussions and Announcements, and then Add.

6. In the Add Discussion and Announcement Connection screen:

   • Connection Name: DFConnection

   • Active Connection: Select check box to enable the connection

   • Server URL: http://wcpinternal.mycompany.com/owc_discussions

   • Administrator User Name: Name of a discussions server user with admin permissions

7. Click OK to save the settings.

8. Restart the managed servers on which the application is deployed.

   For the Spaces application, restart all the managed servers in the Spaces_Cluster.

12.1.2 Creating a Discussions Server Connection using WLST

To connect your WebCenter Portal application to a discussions server using the WebLogic Scripting Tool:

1. Start the WebLogic Scripting Tool:

   WCPHOST1> MW_HOME/wc/common/bin/wlst.sh
   

2. In WLST, connect as the administrator.

   For example:

   connect("weblogic","admin password","ADMINVHN:7001")
   

3. Use the createDiscussionForumConnection command to connect to the discussions server.

   For example:

   createDiscussionForumConnection(appName="webcenter",name="DFConnection",
   url="http://wcpinternal.mycompany.com/owc_discussions",
   adminUser="myDS_admin",default=1,server="WC_Spaces1")
   

   Where webcenter is the name of the Spaces application deployed on WC_Spaces1.

   See also, "createDiscussionForumConnection" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

4. Restart the managed servers on which the application is deployed.

   For the Spaces application, restart all the managed servers in the Spaces_Cluster.

12.2 Configuring the Instant Messaging and Presence (IMP) Server Connection

For instructions how to configure Instant Messaging and Presence servers, see "Registering Instant Messaging and Presence Servers" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal

12.3 Configuring a BPEL Server Connection for Worklists and Workflows

The Worklist service and workflows, such as Spaces membership workflows, require a connection to a BPEL server. To configure a connection for the WebCenter Portal Enterprise Deployment, the following value is required:

• SOAP Server URL: http://wcpinternal.mycompany.com

You can connect to a BPEL server using Fusion Middleware Control or WLST commands:

• Section 12.3.1, "Before You Start"

• Section 12.3.2, "Configuring Worklists and Workflow using Fusion Middleware Control"

• Section 12.3.3, "Configuring Worklist and Workflow using WLST"

12.3.1 Before You Start

Before you connect your WebCenter Portal application to the BPEL server that will host the Worklist and Workflow application:

1. Complete prerequisites steps for the Worklist service.

   For details, see "Back-End Requirements for the Worklist Service" in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.

2. (Spaces application only) Complete prerequisites steps for the Spaces workflows.

   For details, see "Back-End Requirements for WebCenter Portal: Spaces Workflows" in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.

12.3.2 Configuring Worklists and Workflow using Fusion Middleware Control

To connect your WebCenter Portal application to a BPEL server using Fusion Middleware Control:

1. Ensure that at least one of the managed server on which your application is deployed is up and running.

   For example, for the Spaces application, one of the WC_Spaces managed servers.

2. Log on to the Enterprise Manager Fusion Middleware Control Console at http://SOAHOST1:7001/em.

3. Navigate to the home page for your WebCenter Portal application.

   For example, to navigate to the home page for the Spaces application, select Farm_wcpedg_domain, WebCenter > Portal > Spaces, and then webcenter (WC_Spaces1).

4. Configure a Worklist connection:

   1. From the WebCenter Portal drop-down menu, select Settings, and then Service Configuration.

   2. Click Worklist, and then Add.

   3. In the Add Worklist Connection screen:

      Connection Name: WorklistConnection

      Active Connection: Select check box to enable the connection for the Worklist service

      BPEL SOAP URL: http://wcpinternal.mycompany.com

   4. Click OK to save the settings.

5. (Spaces application only) Specify the BPEL server that is hosting the Spaces workflows:

   1. From the WebCenter Portal drop-down menu, select Settings, and then Application Configuration.

   2. From the Connection Name dropdown, choose the BPEL server connection where the workflows are deployed.

      If the BPEL server connection you want is not listed, follow step 4 to set up the connection.

   3. Click OK to save the settings.

6. Restart the managed servers on which the application is deployed.

   For the Spaces application, restart all the managed servers in the Spaces_Cluster.

12.3.3 Configuring Worklist and Workflow using WLST

To connect your WebCenter Portal application to a BPEL server, and specify a BPEL server for the Worklist service and Spaces workflows using WLST:

1. Start the WebLogic Scripting Tool:

   WCPHOST1> MW_HOME/wc/common/bin/wlst.sh
   

2. In WLST, connect as the administrator.

   For example:

   connect("weblogic","admin password","ADMINVHN:7001")
   

3. Configure a BPEL server connection:

   For example:

   createBPELConnection(appName="webcenter", name="WorklistConnection", url="http://wcpinternal.mycompany.com",server="WC_Spaces1")
   

   Where webcenter is the name of the Spaces application deployed on WC_Spaces1.

   See also, "createBPELConnection" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

4. Configure the Worklist service to use the BPEL connection:

   For example:

   addWorklistConnection(appName="webcenter", name="WorklistConnection", verbose=1,server="WC_Spaces1")
   

   See also, "addWorklistConnection" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

5. (Spaces application only) Specify the connection that points to the BPEL server on which Spaces workflows are deployed.

   For example:

   setSpacesWorkflowConnectionName(appName="webcenter", name="WorklistConnection",server="WC_Spaces1")
   
   getSpacesWorkflowConnectionName(appName="webcenter",server="WC_Spaces1")
   

   See also, "setSpacesWorklfowConnectionName" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

6. Restart the managed servers on which the application is deployed.

   For the Spaces application, restart all the managed servers in the Spaces_Cluster.

12.4 Registering Portlet Producers

Several out-of-the-box portlet producers can be registered with WebCenter Portal applications. In the WebCenter Portal Enterprise Deployment, the required producer URLs are as follows:

• WSRP Producer URL: http://wcpinternal.mycompany.com/wsrp-tools/portlets/wsrp2?WSDL

• WebClipping Producer URL: http://wcpinternal.mycompany.com/portalTools/webClipping/providers

• OmniPortlet Producer URL: http://wcpinternal.mycompany.com/portalTools/omniPortlet/providers

You can register portlet producers using Fusion Middleware Control or WLST commands:

• Section 12.4.1, "Registering Out-of-the-Box Portlet Producers using Fusion Middleware Control"

• Section 12.4.2, "Registering Out-of-the-Box Portlet Producers Using WLST"

12.4.1 Registering Out-of-the-Box Portlet Producers using Fusion Middleware Control

For details on how to register portlet producers using Fusion Middleware Control, see "Managing Portlet Producers" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.

12.4.2 Registering Out-of-the-Box Portlet Producers Using WLST

To register out-of-the-box portlet producers using WLST:

1. Start the WebLogic Scripting Tool:

   WCPHOST1> MW_HOME/wc/common/bin/wlst.sh
   

2. In WLST, connect as the administrator.

   For example:

   connect("weblogic","admin password","ADMINVHN:7001",server="WC_Spaces1")
   

3. Register all three out-of-the-box WSRP and PDK-Java producers.

   For example:

   registerOOTBProducers(producerHost='wcpinternal.mycompany.com',producerPort=80, appName='webcenter', server=WC_Spaces1')
   

   Where webcenter is the name of the Spaces application deployed on WC_Spaces1.

See also, "registerOOTBProducers" in Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

12.5 Registering the Pagelet Producer

If you want to expose WSRP and Oracle JPDK portlets and OpenSocial gadgets as pagelets in WebCenter Portal applications, you must register the Pagelet Producer. In the WebCenter Portal Enterprise Deployment, the required Pagelet Producer URL is:

http://wcpinternal.mycompany.com/pagelets

You can register the Pagelet Producer using Fusion Middleware Control or WLST commands Refer to the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal for detailed steps:

• Registering the Pagelet Producer for WebCenter Portal Applications Using Fusion Middleware Control

• Registering the Pagelet Producer for WebCenter Portal Applications Using WLST

12.6 Configuring Search Services

You can configure Oracle Secure Enterprise Search (Oracle SES) services and crawlers using procedures in "Managing Oracle SES Search in WebCenter Portal" in Oracle Fusion Middleware Administrator's Guide for 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 "Oracle SES - Configuration" 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 "Setting Up Oracle SES Connections" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.

Ensure that any new URLs are added for both WEBHOST Oracle HTTP Server configurations as follows:

<Location /rsscrawl>
 WebLogicCluster WCPHOST1:9000,WCPHOST2:9000
 SetHandler weblogic-handler
</Location>

<Location /sesUserAuth>
 WebLogicCluster WCPHOST1:9000,WCPHOST2:9000
 SetHandler weblogic-handler
</Location>

See also, Section 10.11.1, "Configuring Oracle HTTP Server for the WC_Spacesn, WC_Portletn, WC_Utilitiesn, and WC_Collaborationn Managed Servers".

12.7 Configuring the Mail Server for Notifications

For details on how to set up the Notifications service for WebCenter Portal applications, refer to "Setting Up Notifications" in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.

In a WebCenter Portal Enterprise Deployment, if you choose to send notifications using mail you must set an additional property on the mail server connection named 'mail.user.emailAddress' which overrides any Sender Mail Address that is configured for mail notifications (that is, the 'From' field). If you do not set this additional property, one of the server names in the cluster appends to the Sender Mail Address, for example sender_mail_address@server1.

You can set additional properties for mail server connections using Fusion Middleware Control or WLST. For details, see:

• Registering Mail Servers Using Fusion Middleware Control (Table 17-7)

• Registering Mail Servers Using WLST

For example, using WLST:

setMailConnectionProperty(appName='webcenter', name='myMail_Server_Connection_Name', key='mail.user.emailAddress', value='myShared_User_Email_Address')

Where:

myMail_Server_Connection_Name - Name of the mail server connection used by the Notification service.

myShared_User_Email_Address - The SHARED mail address. This is the mail address associated with the user specified in the external application's shared credentials. Ensure you can login with this mail address to your mail server.