This chapter provides information required for the deployment of Oracle Content Portlet Suite (CPS) as a WSRP producer. Once CPS is deployed, the portlets can be consumed from other WSRP-enabled portal servers. It covers the following topics:
Important:
User IDs on the content server must correspond with user IDs on your portal server.This section provides information on the deployment of Content Portlet Suite (CPS) as a WSRP producer on Oracle WebCenter Portal:
These servers and components are required for installation:
These WSRP consumers are supported with Oracle WebCenter Portal as producer:
Oracle WebCenter Spaces 11g Release 1. See Section 4.1, "Oracle WebCenter Spaces as Consumer" for more information.
To create a new managed server, follow the steps in "Creating and Provisioning a WebLogic Managed Server Using a Jython Script" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
Note:
While modifyingtargetServer.properties, set serverType=Portlet and give a name to your server by setting the mgdServerName property; for example, mgdServerName=CPS_Portlet.The following libraries need to be targeted to the newly created managed server (for example, CPS_Portlet). Note that the libraries for 11gR1 (11.1.1.3) installations of Oracle WebCenter Portal are different from the libraries for 11gR1 (11.1.1.4 and higher) installations.
Libraries for 11gR1 (11.1.1.3) installations of WebCenter Portal:
oracle-ridc-client-app-lib(10.3.2,10.3.2)
oracle-ucm-spi-app-lib(10.3.2,10.3.2)
p13n-app-lib-base(10.3.2,10.3.2)
vcr-app-lib(10.3.2,10.3.2)
oracle.webcenter.framework(11.1.1,11.1.1)
oracle.webcenter.spaces.fwk(11.1.1,11.1.1)
Libraries for 11gR1 (11.1.1.4) and higher installations of WebCenter Portal:
oracle.ucm.ridc.app-lib(11.1.1,11.1.1)
p13n-app-lib-base(10.3.2,10.3.2)
oracle.webcenter.framework(11.1.1,11.1.1)
oracle.webcenter.spaces.fwk(11.1.1,11.1.1)
oracle.webcenter.framework.core(11.1.1,11.1.1)
Follow these steps to target the libraries:
Go to the WebLogic Server Administration Console of your WebCenter Portal instance, and then open the Deployments section.
Click on the library name you want to target; for example, oracle.webcenter.framework(11.1.1,11.1.1).
On the settings page for the selected library, open the Targets tab.
Select the option for the newly created server (for example, CPS_Portlet) and then save and activate the changes.
Repeat this for each of the libraries to be targeted.
Target the mds-SpacesDS data source to the newly created managed server (for example, CPS_Portlet):
Go to the Oracle WebLogic Server Administration Console of your WebCenter Portal instance. In the Domain Structure window, choose Services, then JDBC, and then Data Sources.
In the Summary of JDBC Data Sources section, click mds-SpacesDS.
On the settings page for mds-SpacesDS, open the Targets tab.
Select the option for the newly created server (for example, CPS_Portlet) and then save and activate the changes.
This section describes how to configure WebCenter Portal as a producer using Web Services Remote Portlets (WSRP) for CPS.
Note:
When consuming Oracle Content Portlet Suite 11gR1 (11.1.1.4) on Oracle WebCenter Portal 11gR1 (11.1.1.4) or higher, users will see the exception:java.lang.IllegalArgumentException: IdcContext.setUser() method not valid, do not use this method,
To resolve the issue you may adopt either one of the following two workarounds:
Workaround 1: Edit the weblogic-application.xml
Deploy the library oracle-ridc-client-app-lib(10.3.2,10.3.2) and target it only at the managed server created for CPS. If you do not have this library, please contact Oracle Support.
Extract weblogic-application.xml file from StellentPortlets.ear file.
Edit the file and add the following entry as the first library reference:
<library-ref> <library-name>oracle-ridc-client-app-lib</library-name> </library-ref>
Update the StellentPortlets.ear file with the updated weblogic-application.xml file..
Deploy StellentPortlets.ear to your managed server.
Workaround 2: Use StellentPortlets.ear from Oracle UCM 11gR1 (11.1.1.5) or Oracle WebCenter Content 11gR1 (11.1.1.6)
The StellentPortlets.ear file from the Oracle UCM 11gR1 (11.1.1.5) and Oracle WebCenter Content 11gR1 (11.1.1.6) has the fix for this issue. Thus, you can use this EAR file instead of the EAR file bundled with Oracle UCM 11gR1 (11.1.1.4).
Uncompress the CPS distribution file and extract the CPS zip file to your local directory.
For example:
/oracle/apps/webcenter/cps
Launch the WebLogic Server Administration Console of your WebCenter Portal instance.
Click Lock and Edit.
In the Domain Structure section, click Deployments.
In the Summary of Deployments section, open the Control tab and click Install.
In the Install Application Assistant section, click the Upload your file(s) link.
In the Deployment Archive section, click the Browse button.
Browse to the /portlets directory of the extracted CPS zip file and select the StellentPortlets.ear file.
Click Next.
The CPS EAR file is uploaded and displays in the list of available files.
Enable the option button corresponding to the CPS EAR file.
Click Next.
Select the Install this deployment as an application option.
Click Next.
Select the new custom managed server that you created in Section 3.1.3, "Creating a Custom Managed Server" (for example, CPS_Portlet).
Click Finish to deploy the application.
Access the WSDL URL. Note that after deploying the CPS EAR file to WebCenter Portal as a producer, the WSDL URL for the 11gR1 (11.1.1.3) installation of WebCenter Portal is different from the WSDL URL for 11gR1 (11.1.1.4) or higher installations.
WSRP URL 11gR1 (11.1.1.3) installation of WebCenter Portal:
http://Host_Name:Port/cps/portlets/wsrp1?wsdl
WSRP URL for the 11gR1 (11.1.1.4) or higher installations of WebCenter Portal:
http://Host_Name:Port/cps/portlets/wsrp2?WSDL
From a command-line, launch the WebLogic Scripting Tool (WLST), for example:
WLS_HOME/as11r1wc/common/bin/wlst.sh
Note:
The WebLogic Scripting Tool (WLST) is a command-line scripting environment that you can use to create, manage, and monitor WebLogic Server domains. Refer to the Oracle Fusion Middleware Oracle WebLogic Scripting Tool document for more information.After the WebLogic Scripting Tool initializes, type connect() and press Enter.
You are prompted to enter the username, password and Admin server URL. Enter these values and press Enter.
Once connected to the server, run the following command to register your WSDL:
registerWSRPProducer('webcenter','Provide_Any_Name_for_WSDL_Handle', 'Your_WSDL>',timeout=500)
For example:
registerWSRPProducer('webcenter','StellentWSRP','http://Host_Name:Port/cps/portlets/wsrp1?WSDL',timeout=500
Referencing Your Content Server
The following WLST commands should be used to create, delete, and reset an Oracle WebCenter Content Server connection:
Note:
The custom managed server on which CPS is deployed and the WLS_Spaces server must be restarted after executing the following commands for the changes to take effect.Run the following WLST command to create an Oracle WebCenter Content Server connection:
createJCRContentServerConnection('CPS_Application_Name', 'CSConnection', socketType='socket', serverHost='Content_Server_Host', serverPort='Content_Server_Port')
For example (if the CPS application name is StellentPortlets):
createJCRContentServerConnection('StellentPortlets', 'CSConnection', socketType='socket', serverHost='192.0.2.250', serverPort='4444')
For the CPS Portlets to work, the connection name must be 'CSConnection' as other connection names are not recognized
Run the following WLST command to delete an Oracle WebCenter Content Server connection:
deleteConnection(appName='CPS_Application_Name', name='CSConnection')
Run the following WLST command to reset an existing Oracle WebCenter Content Server connection:
setJCRContentServerConnection('CPS_Application_Name', 'CSConnection', socketType='socket', serverHost='New_Content_Server_Host', serverPort='New_Content_Server_Port')
Run the following WLST command to list the existing Oracle WebCenter Content Server connections:
listJCRContentServerConnections(appName='CPS_Application_Name')
Enable Your Content Server to Communicate with CPS
You must enable your Oracle WebCenter Content Server instance to communicate with CPS. See Section 3.4, "Configuring Oracle WebCenter Content Server for CPS Communication" for instructions.
This section provides information on the deployment of Content Portlet Suite (CPS) as a WSRP producer on Oracle WebLogic Portal.
These servers and components are required for installation:
Oracle WebLogic Portal 10g Release 3 (as producer)
Oracle WebCenter Content Server 11g Release 1, Oracle Content Server 11g Release 1, or Oracle Content Server 10g Release 3
Oracle Content Portlet Suite (CPS) distribution file
These WSRP consumers are supported with Oracle WebLogic Portal as producer:
Oracle WebCenter Interaction 10g Release 3. See Section 4.2, "Oracle WebCenter Interaction as Consumer" for more information.
Oracle WebLogic Portal 10g Release 3. See Section 4.3, "Oracle WebLogic Portal as Consumer" for more information.
This section describes how to configure WebLogic Portal as a producer using Web Services Remote Portlets (WSRP) for CPS.
Important:
Before deploying CPS portlets, select an existing WebLogic domain or create a new WebLogic domain (for example, cps_domain). You must configure this domain to support WebLogic Server, Workshop for WebLogic, and WebLogic Portal.Uncompress the CPS distribution file and extract the WebLogic CPS zip file to your local directory.
Locate the /WEB-INF/config directory.
Open the cps-initialization.properties file in a text-only editor. Edit the host property value to reference the IP address or host name of your Content Server instance. Edit the port property value if your content server is running on a port other than the default port of 4444. Do not remove the new line character at the beginning of the file.
For example:
Host=192.0.2.254 Port=4448
Launch Workshop for WebLogic.
Select File, then New, and then Project.
In the New Project dialog, expand the WebLogic Portal node.
Click Next.
The New Portal Web Project wizard displays.
In the Create a New Oracle WebLogic Portal Web Project step, enter a project name (for example, CPS).
Click Finish.
If the Open Associated Perspective dialog displays, click Yes.
In Workshop for WebLogic, select File, then New, and then Project.
In the New Project dialog, expand the WebLogic Portal node.
Click Next.
The New Portal EAR Project wizard displays.
In the Create a New Oracle WebLogic Portal EAR Project step, enter a project name (for example, CPS Consumer-EAR).
Click Next.
In the Project Facets step, select WebLogic Portal EAR Project Facets from the drop-down list.
Click Next.
In the J2EE Modules to Add to the EAR step, select the portal web project you created (for example, CPS).
Click Finish.
If the Open Associated Perspective dialog displays, click Yes.
Select Project Explorer view and expand the new Portal Web Project node (for example, CPS).
Right-click the WebContent node, and select Import.
The Import wizard displays.
In the Select an Import Source step, expand the General node.
Select File System.
Click Next.
In the File System step, click Browse associated with the From Directory field.
Browse to the /portlets directory of the uncompressed CPS distribution file and click OK.
In the Import Resources from Local File System step, enable the portlets option.
Click Finish.
After the portlets folder is imported, you might notice several errors in the web project. Error files are shown with a red cross prefixed with the file in Project Explorer view. Select the files showing errors and delete them.
In Workshop for WebLogic, select Servers view.
Right-click in Servers view, click New, then Server.
The New Server wizard displays.
In the Choose Type of Server to Create step, accept the default settings and click Next.
In the Specify a WebLogic Domain Directory step, click Browse.
Browse to the new CPS domain directory and click OK.
For example (on Windows):
C:/oracle_weblogic/user_projects/domains/cps_domain
Click Next.
In the Add and Remove Projects step, select the CPS EAR file from the Available Projects section and click Add to add it to Configured Projects.
Click Finish.
In Servers view, right-click on the new server and select Publish to start the server and publish the EAR file.
The WSRP-enabled CPS portlets are available via the WSDL URL.
The URL will be of the format:
http://host_server:host_port/context-root-specified-in-portal-web-project/producer?wsdl
where host_server, host_port, and context-root-specified-in-portal-web-project is replaced with appropriate values.
Enable Your Content Server to Communicate with CPS
You must enable your content server instance to communicate with CPS. See Section 3.4, "Configuring Oracle WebCenter Content Server for CPS Communication" for instructions.
This section provides information on the deployment of Content Portlet Suite (CPS) as a WSRP producer on IBM WebSphere Portal.
These servers and components are required for installation:
IBM WebSphere Portal Version 6.1 (as producer)
Oracle WebCenter Content Server 11g Release 1, Oracle Content Server 11g Release 1, or Oracle Content Server 10g Release 3
Oracle Content Portlet Suite (CPS) distribution file
These WSRP consumers are supported with IBM WebSphere Portal as producer:
IBM WebSphere Portal Version 6.1. See Section 4.4, "IBM WebSphere Portal as Consumer" for more information.
This section describes how to configure WebSphere Portal as a producer using Web Services Remote Portlets (WSRP) for CPS.
Uncompress the CPS distribution file and extract the WebSphere CPS zip file to your local directory.
Start the server and launch WebSphere Portal.
From the main menu, click Administration.
In the Portlet Administration section, click Web Modules.
In the Manage Web Modules section, click Install.
Browse to the /portlets directory of the extracted WebSphere CPS zip file and select the StellentPortlets.ear file.
Click Next.
Provide an enterprise application display name and context root.
Make sure the Start Application option is enabled (default).
Click Finish.
A confirmation message will display in the Manage Web Modules section after successful installation.
Locate the StellentPortlets WEB-INF/config directory:
WebSphere_Portal_Home\wp_profile\installedApps\Node_Name\CPS_App_Display_Name\StellentPortlets.war\WEB-INF\config
Open the cps-initialization.properties file in a text-only editor. Edit the host and port properties to reference your content server instance.
For example:
Host=192.0.2.254 Port=4448
Stop and restart the server.
Launch WebSphere Portal and click Administration from the main menu.
In the Portlet Management section, click Portlets.
Search for the CPS portlets in the list of available portlets.
For each of the CPS portlets perform the following steps:
Click the Provide Portlet icon.
Click OK.
Click the Assign Access to Portlet icon.
The Resource Permissions page displays.
In the Roles column, click the Edit Role icon for the User role.
Click Add.
Enable the Anonymous Portal User option.
Click OK.
In the Add section, click the portlet name.
Repeat the steps above for the Privileged User role: click the Edit Role icon, click Add, enable the Anonymous Portal User option, and click OK.
When you have completed these steps for each of the CPS portlets, click Done.
In the Portlet Management section, click Web Services.
Click New Producer and provide a title for the producer. Select this Web Service Producer when consuming the CPS portlets. See Section 4.3, "Oracle WebLogic Portal as Consumer" and Section 4.4.3, "Consumption Steps" for more information.
Confirm that the entries for your configuration are correct:
Review the URL to WSDL Service Definitions field and edit as needed.
Review the host name. The default host name is localhost. It is recommended that the IP address or machine name be used.
Review the port number. The default port number is 10040. The port number should match the port where your WebSphere Portal is deployed (as displayed in the address bar of your web browser).
After you have confirmed your entries, click Next.
Click Next.
The confirmation message "Created the Producer successfully" displays.
The WSDL for your producer is:
Host_Name:Port/wps/wsdl/service.wsdl
For example:
http://localhost:10039/wps/wsdl/service.wsd
Enable Your Content Server to Communicate with CPS
You must enable your content server instance to communicate with CPS. See Section 3.4, "Configuring Oracle WebCenter Content Server for CPS Communication" for instructions.
To enable your content server instance to communicate with CPS, you must define the IP address of your portal server and edit the content server configuration file (config.cfg) to allow server communication with that IP address.
This section covers the following topics:
You must enable the IP address of the application server. This enables the content server to listen for connections from the application server.
Launch the System Properties editor.
Select Content Server, then instance name, then Utilities, and then System Properties.
Open the Server tab.
Enter your application server specific information for the Hostname Filter and IP Address Filter.
The wildcard (*) is accepted, but IP addresses must take the form x.x.x.x regardless of wildcards, and must be separated by a vertical bar.
For example:
12.34.56.*|12.34.57.*|12.35.*.*
You must restart the content server for these changes to take effect.
You must edit the content server configuration file (config.cfg). The file is located at MW_HOME/user_projects/domains/cs_domain_name/ucm/cs/config.
Add or edit the IntradocServerPort configuration variable to include the port number used by CPS. This entry is present by default in Content Server 10g but must be added to the configuration file for Content Server 11g.
Follow these steps to edit the configuration file:
Log in to the content server as an administrator.
Launch the Admin Server.
Click General Configuration.
In the Additional Configuration Variables field, add or edit the IntradocServerPort entry and the port number.
For example:
IntradocServerPort=4444
Click Save.
Restart the content server.