In the Domain Structure tree, select Deployments.

6-48 Oracle Fusion Middleware Developers Guide for Oracle Portal Extending the Existing WebLogic Domain To extend your existing Oracle WebLogic Server domain with the Oracle WSM Policy Manager, complete the following steps:

1. Select Extend an existing WebLogic Domain and click Next.

The Select a WebLogic Domain Directory screen is displayed. 2. Select your valid domain directory and click Next. The Select Extension Source screen is displayed. 3. Select Oracle WSM Policy Manager - 11.1.1.0 [Oracle_Common] Select the one associated with your Oracle Portal check box from the Extend my domain automatically to support the following added products option and click Next. The Configure JDBC Data Sources screen is displayed.

4. Click Next.

The Test JDBC Data Sources screen is displayed. 5. Click Next. The Configure JDBC Component Schema screen is displayed.

6. Check the OWSM MDS Schema and enter the Host Name, Port, DBMS Service,

Schema Password for the MDS schema. Click Next. The Test Component Schema screen is displayed. 7. Confirm the test is successful and click Next. The Select Optional Configuration screen is displayed.

8. Select Deployments and Services.

9. Click Next.

The Target Deployments to Clusters or Servers screen is displayed. 10. Ensure wsrp-pm is targeted to servers including WLS_WSRP and AdminServer. 11. Click Next. The Target Services to Cluster or Servers screen is displayed

12. Click Next.

13. Review your settings in the Configuration Summary screen, and click Extend.

14. Click Done.

Start the Oracle WebLogic Administration Server, the managed server, and the WLS_ WSRP managed server. Note: You must stop all the servers running in the Oracle Portal domain. Note: This is the schema created for MDS when you run the Repository Configuration Utility RCU at install time. If you did not created this schema already then you need to create this schema first using RCU. Creating Java Portlets 6-49 Adding wsm-pm to the WSRP Managed Server You must add the wsm-pm to the WLS_WSRP managed server, by completing the following steps: 1. If you have not already done so, in the Change Center of the Administration Console, click Lock Edit.

2. In the Domain Structure tree, select Deployments.

The Summary of Deployments page is displayed. 3. Select wsm-pm from the Deployments table. 4. Click the Targets tab, and select wsm-pm from the Component table. 5. Click Change Targets, and then check AdminServer and WLS_WSRP from the Servers section.

6. Click Yes.

Deploying the Sample EAR File To deploy the EAR file, download the wsrp-samples.ear file, from Download the Oracle Portlet Container at http:www.oracle.comtechnologyproductsiasportalpdk.html and do the following:

1. Click Lock Edit.

2. In the Domain Structure tree, select Deployments.

The Summary of Deployments page is displayed. 3. Click Install. 4. Select wsrp-samples.ear from your directory, click Next. 5. Select Install this deployment as an application, and click Next. 6. Check WLS_WSRP from the Servers section, and click Next. 7. Enter a name for the deployment, and click Finish. 8. Click Activate Changes. 9. In the Summary of Deployments page, select the application you have deployed, and then click Start. 10. Now that you have deployed the sample EAR file, you need to test its WSDL URL by entering it into a browser. The WSDL URL is of the form: http:host:portportletappportlets?WSDL You should see a page similar to the one shown in Example 6–1 . Example 6–1 WSRP Producer WSDL Page ?xml version=1.0 encoding=UTF-8 ? definitions targetNamespace=urn:oasis:names:tc:wsrp:v1:wsdl xmlns=http:schemas.xmlsoap.orgwsdl xmlns:wsdl=http:schemas.xmlsoap.orgwsdl xmlns:soap=http:schemas.xmlsoap.orgwsdlsoap xmlns:bind=urn:oasis:names:tc:wsrp:v1:bind import namespace=urn:oasis:names:tc:wsrp:v1:bind location=http:stamf10.us.abc.com:8090wsrp-toolsportletswsrp1?WSDL=wsrp_v1_ bindings.wsdl service name=WSRP_v1_Service