This chapter 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.
This chapter includes the following topics:
Configuring the Instant Messaging and Presence (IMP) Server Connection
Configuring a BPEL Server Connection for Worklists and Workflows
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.
To attach the default Web service security policy:
Ensure that WC_Spaces1, WC_Spaces2, WC_Collaboration1, WC_Collaboration2, WC_Portlet1, and WC_Portlet2 Managed Servers are up and running.
Start the WebLogic Scripting Tool:
WCPHOST1> MW_HOME/wc/common/bin/wlst.sh
Connect to the Administration Server as an administrator.
For example:
connect("weblogic","admin password","ADMINVHN:7001")
For information, see the "Running Oracle WebLogic Scripting Tool (WLST) Commands" section in Administering Oracle WebCenter Portal.
Run WLST commands to attach the default OWSM security policy (oracle/wss10_saml_token_service_policy) to each of the following:
WebCenter Portal application (webcenter)
Discussions application (owc_discussions)
WebCenter Services Portlet Producer (services-producer)
WSRP Tools Producer (wsrp-tools)
To attach the default OWSM security policy to WebCenter Portal's "SpacesWebService" on each server in the cluster (WC_Spaces1 and WC_Spaces2), run the following WLST commands:
attachWebServicePolicy(application='/wcedg/WC_Spaces1/webcenter', moduleName='webcenter', moduleType='web', serviceName='SpacesWebService', subjectName='SpacesWebServiceSoapHttpPort', policyURI='oracle/wss10_saml_token_service_policy') attachWebServicePolicy(application='/wcedg/WC_Spaces2/webcenter', moduleName='webcenter', moduleType='web', serviceName='SpacesWebService', subjectName='SpacesWebServiceSoapHttpPort', policyURI='oracle/wss10_saml_token_service_policy')
To attach the default OWSM security policy to the discussions Web service on each server in the cluster (WC_Collaboration1 and WC_Collaboration2), run the following WLST commands:
attachWebServicePolicy(application='/wcedg/WC_Collaboration1/owc_discussions', moduleName='owc_discussions', moduleType='web', serviceName='OWCDiscussionsServiceAuthenticated', subjectName='OWCDiscussionsServiceAuthenticated', policyURI='oracle/wss10_saml_token_service_policy') attachWebServicePolicy(application='/wcedg/WC_Collaboration2/owc_discussions', moduleName='owc_discussions', moduleType='web', serviceName='OWCDiscussionsServiceAuthenticated', subjectName='OWCDiscussionsServiceAuthenticated', policyURI='oracle/wss10_saml_token_service_policy')
To attach the default OWSM security policy to the Services Producer's Web service end point on each server in the cluster (WC_Portlet1 and WC_Portlet2), run the following WLST commands:
attachWebServicePolicy(application='/wcedg/WC_Portlet1/services-producer#11.1.1.6.0', moduleName='services-producer', moduleType='web', serviceName='WSRP_v2_Service', subjectName='WSRP_v2_Markup_Service', policyURI='oracle/wss10_saml_token_service_policy') attachWebServicePolicy(application='/wcedg/WC_Portlet2/services-producer#11.1.1.6.0', moduleName='services-producer', moduleType='web', serviceName='WSRP_v2_Service', subjectName='WSRP_v2_Markup_Service', policyURI='oracle/wss10_saml_token_service_policy')
Run the following WLST commands to attach the default OWSM security policy to the WSRP Tools Producer's Web service end point on each server in the cluster (WC_Portlet1 and WC_Portlet2):
attachWebServicePolicy(application='/wcedg/WC_Portlet1/wsrp-tools#11.1.1.4.0', moduleName='wsrp-tools', moduleType='web', serviceName='WSRP_v2_Service', subjectName='WSRP_v2_Markup_Service', policyURI='oracle/wss10_saml_token_service_policy') attachWebServicePolicy(application='/wcedg/WC_Portlet2/wsrp-tools#11.1.1.4.0', moduleName='wsrp-tools', moduleType='web', serviceName='WSRP_v2_Service', subjectName='WSRP_v2_Markup_Service', policyURI='oracle/wss10_saml_token_service_policy')
Restart the WC_Spaces1, WC_Spaces2, WC_Collaboration1, WC_Collaboration2, WC_Portlet1, and WC_Portlet2 Managed Servers.
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: discussions server admin user name
Discussions Admin Password: discussions server admin 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:
Section 12.2.1, "Creating a Discussions Server Connection Using Fusion Middleware Control"
Section 12.2.2, "Creating a Discussions Server Connection Using WLST"
For more information, see the "Managing Announcements and Discussions" chapter in Administering Oracle WebCenter Portal.
Note:
If you want to provide discussions or announcements you must also configure a security policy for the discussions Web service. For details, see Section 12.1, "Configuring Default Web Service Policies for WebCenter Portal, Discussions, and Portlet Producer Applications".To connect your WebCenter Portal application to a discussions server using Fusion Middleware Control:
Ensure that at least one of the Managed Server on which your application is deployed is up and running.
For example, one of the WC_Spaces Managed Servers.
Log on to the Enterprise Manager Fusion Middleware Control Console at http://SOAHOST1:7001/em.
Navigate to the home page for your WebCenter Portal application.
For example, to navigate to the home page for the WebCenter Portal application, select Farm_wcpedg_domain, WebCenter > Portal > Spaces, and then WebCenter Portal (WC_Spaces1).
From the WebCenter Portal drop-down menu, select Settings, and then Service Configuration.
Click Discussions and Announcements, and then Add.
In the Add Discussion and Announcement Connection screen:
Connection Name: DFConnection
Active Connection: Select this check box to enable the connection
Server URL: http://wcpinternal.example.com/owc_discussions
Administrator User Name: Name of a discussions server user with admin permissions
Authenticated User Web Service Policy URI: Select WSS 1.0 SAML Token Client Policy (oracle/wss10_saml_token_client_policy)
Click OK to save the settings.
Restart the Managed Servers on which the application is deployed.
For the WebCenter Portal application, restart all the Managed Servers in Spaces_Cluster.
To connect your WebCenter Portal application to a discussions server using the WebLogic Scripting Tool:
Start the WebLogic Scripting Tool:
WCPHOST1> MW_HOME/wc/common/bin/wlst.sh
In WLST, connect as the administrator.
For example:
connect("weblogic","admin password","ADMINVHN:7001")
Use the createDiscussionForumConnection command to connect to the discussions server.
For example:
createDiscussionForumConnection(appName="webcenter",name="DFConnection", url="http://wcpinternal.example.com/owc_discussions", adminUser="weblogic_wc",default=1,policyURIForAuthAccess="oracle/wss10_saml_token_client_policy",server="WC_Spaces1")
Where webcenter is the name of the WebCenter Portal application deployed on WC_Spaces1 and weblogic_wc is the name of the discussions server admin user.
See also, "createDiscussionForumConnection" in WebLogic Scripting Tool Command Reference.
Restart the Managed Servers on which the application is deployed.
For the WebCenter Portal application, restart all the Managed Servers in the Spaces_Cluster.
For instructions how to configure Instant Messaging and Presence servers, see the "Registering Instant Messaging and Presence Servers" section in Administering Oracle WebCenter Portal.
Worklists and workflows, such as portal 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.example.com
You can connect to a BPEL server using Fusion Middleware Control or WLST commands:
Section 12.4.2, "Configuring Worklists and Workflows Using Fusion Middleware Control"
Section 12.4.3, "Configuring Worklists and Workflows Using WLST"
Before you connect your WebCenter Portal application to the BPEL server that will host the Worklist and Workflow applications:
Complete prerequisites steps for worklists.
For details, see the "Back-End Requirements for Worklists" section in Installation Guide for Oracle WebCenter Portal.
(WebCenter Portal application only) Complete prerequisites steps for the WebCenter Portal workflows.
For details, see the "Back-End Requirements for WebCenter Portal Workflows" section in Installation Guide for Oracle WebCenter Portal.
To connect your WebCenter Portal application to a BPEL server using Fusion Middleware Control:
Ensure that at least one of the Managed Server on which your application is deployed is up and running.
For example, one of the WC_Spaces Managed Servers.
Log on to the Enterprise Manager Fusion Middleware Control Console at http://SOAHOST1:7001/em.
Navigate to the home page for your WebCenter Portal application.
For example, to navigate to the home page for the WebCenter Portal application, select Farm_wcpedg_domain, WebCenter > Portal > Spaces, and then WebCenter Portal (WC_Spaces1).
Configure a connection for worklists:
From the WebCenter Portal drop-down menu, select Settings, and then Service Configuration.
Click Worklist, and then Add.
In the Add Worklist Connection screen:
Connection Name: WorklistConnection
Active Connection: Select check box to enable the connection for worklists
BPEL SOAP URL: http://wcpinternal.example.com
Click OK to save the settings.
(WebCenter Portal application only) Specify the BPEL server that is hosting WebCenter Portal workflows:
From the WebCenter Portal drop-down menu, select Settings, and then Application Configuration.
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.
Click Apply to save the settings.
Restart the Managed Servers on which the application is deployed.
For WebCenter Portal, restart all the Managed Servers in the Spaces_Cluster.
To connect your WebCenter Portal application to a BPEL server, and specify a BPEL server for worklists and WebCenter Portal workflows using WLST:
Start the WebLogic Scripting Tool:
WCPHOST1> MW_HOME/wc/common/bin/wlst.sh
In WLST, connect as the administrator.
For example:
connect("weblogic","admin password","ADMINVHN:7001")
Configure a BPEL server connection:
For example:
createBPELConnection(appName="webcenter", name="WorklistConnection", url="http://wcpinternal.example.com",server="WC_Spaces1")
Where webcenter is the name of the WebCenter Portal application deployed on WC_Spaces1.
See also, "createBPELConnection" in WebLogic Scripting Tool Command Reference.
Configure worklists to use the BPEL connection:
For example:
addWorklistConnection(appName="webcenter", name="WorklistConnection", verbose=1,server="WC_Spaces1")
See also, "addWorklistConnection" in WebLogic Scripting Tool Command Reference.
(WebCenter Portal only) Specify the connection that points to the BPEL server on which WebCenter Portal workflows are deployed.
For example:
setSpacesWorkflowConnectionName(appName="webcenter", name="WorklistConnection",server="WC_Spaces1") getSpacesWorkflowConnectionName(appName="webcenter",server="WC_Spaces1")
See also, "setSpacesWorkflowConnectionName" in WebLogic Scripting Tool Command Reference.
Restart the Managed Servers on which the application is deployed.
For WebCenter Portal, restart all the Managed Servers in Spaces_Cluster.
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
http://wcpinternal.example.com/portalTools/webClipping/providers
http://wcpinternal.example.com/portalTools/omniPortlet/providers
You can register portlet producers using Fusion Middleware Control or WLST commands:
Section 12.5.1, "Registering Out-of-the-Box Portlet Producers Using Fusion Middleware Control"
Section 12.5.2, "Registering Out-of-the-Box Portlet Producers Using WLST"
For details on how to register portlet producers using Fusion Middleware Control, see the "Managing Portlet Producers" chapter in Administering Oracle WebCenter Portal.
To register out-of-the-box portlet producers using WLST:
Start the WebLogic Scripting Tool:
WCPHOST1> MW_HOME/wc/common/bin/wlst.sh
In WLST, connect as the administrator.
For example:
connect("weblogic","admin password","ADMINVHN:7001",server="WC_Spaces1")
Register all three out-of-the-box WSRP and PDK-Java producers.
For example:
registerOOTBProducers(producerHost='wcpinternal.example.com',producerPort=80, appName='webcenter', server='WC_Spaces1')
Where webcenter is the name of the WebCenter Portal application deployed on WC_Spaces1.
See also, "registerOOTBProducers" in WebLogic Scripting Tool Command Reference.
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 Refer to Administering Oracle WebCenter Portal for detailed steps:
You can configure Oracle Secure Enterprise Search (Oracle SES) services and crawlers using procedures in the "Managing Oracle SES Search" section in 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 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> WebLogicCluster WCPHOST1:9000,WCPHOST2:9000 SetHandler weblogic-handler </Location> <Location /sesUserAuth> WebLogicCluster WCPHOST1:9000,WCPHOST2:9000 SetHandler weblogic-handler </Location>
For details on how to set up the Notifications service for WebCenter Portal applications, refer to the "Setting Up Notifications" section in Administering 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:
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.