Editing Producer Registration Details Using Fusion Middleware Control

Managing Portlet Producers 23-17 WSRP EAR file, run the WSRP producer predeployment tool located in the Middleware directory at WC_ORACLE_HOME webcentermodulesoracle.portlet.server_11.1.1, as follows: java -jar wsrp-predeploy.jar source EAR target EAR For JSR 286 portlets developed with servlet version 2.3, you must specify Web proxies using the following command: java -Dhttp.proxyHost=proxy host -Dhttp.proxyPort=proxy port -jar wsrp-predeploy.jar source EAR target EAR where: ■ proxy host is the server to which your producer has been deployed. ■ proxy port is the HTTP Listener port. ■ wsrp-predeploy.jar is located in the WC_ORACLE_HOME webcentermodulesoracle.portlet.server_11.1.1 directory. ■ source EAR is the name of the JSR 286 EAR file. ■ target EAR file is the name of the new EAR file to be created. If the file name for the targeted EAR file is not specified, then a new EAR file called WSRP-source EAR is produced. In the following example Web proxy is specified: java -Dhttp.proxyHost=myhttpproxy.com -Dhttp.proxyPort=80 -jar wsrp-predeploy.jar wsrp-samples.ear This example produces WSRP-wsrp-samples.ear. The wsrp-predeploy.jar predeployment tool makes all the necessary changes to a JSR 286 portlet to be able to deploy it to the Oracle portlet container and expose it as a WSRP producer. Here are some examples of what the predeployment tool does: ■ Creates the wsdldeploy directory in the java.io.tmpdir folder. – On UNIX, the default value of this property is tmp or vartmp – On Microsoft Windows, the default value of this property is c:\temp. ■ Unpacks the EAR file into wsdldeployEAR. ■ Unpacks the WAR files into wsdldeploy[warfilename.war]. ■ Inserts WEB-INFWSDLs into the unpacked application. ■ Modifies WEB-INFweb.xml in the unpackaged WAR files. ■ Inserts or modifies WEB-INFwebservices.xml in the WAR files. ■ Inserts or modifies WEB-INForacle-webservices.xml in the WAR files. ■ Repackages the WARs and builds a new EAR file.

23.8.3 Deploying Portlet Producer Applications Using Oracle JDeveloper

You can deploy portlet applications to an Oracle WebLogic Managed Server instance directly from the development environment using Oracle JDeveloper, if you have the necessary credentials to access the WebLogic server. For more information, see the 23-18 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter section Deploying a Portlet Application to an Oracle WebLogic Managed Server Instance in the Oracle Fusion Middleware Developers Guide for Oracle WebCenter.

23.8.4 Deploying Portlet Producer Applications Using Fusion Middleware Control

For information about deploying a portlet producer application using Fusion Middleware Control, see Section 7.1.6.4, Deploying Applications Using Fusion Middleware Control.

23.8.5 Deploying Portlet Producer Applications Using Oracle WebLogic Server Administration Console

For information about deploying a portlet producer application using Oracle WebLogic Server Administration Console, see Section 7.1.6.6, Deploying Applications Using the WLS Administration Console.

23.8.6 Deploying Portlet Applications Using WLST

For information on deploying a portlet application using the WLST command, see Section 7.1.6.5, Deploying Applications Using WLST.

23.9 Troubleshooting Portlet Producer Issues

This section includes the following sub sections: ■ Section 23.9.1, Producer Registration Fails for a WebCenter Portal Application ■ Section 23.9.2, Portlet Unavailable: WSM-00101 Exception

23.9.1 Producer Registration Fails for a WebCenter Portal Application

This section describes producer registration and portlet unavailability issues. Problem You are unable to register a WSRP producer. Solution Ensure the following: ■ Back-end producer is up and running. To test the producer, access the WSDL URL of the producer through a browser window. See, Section 23.3, Testing WSRP Producer Connections. ■ Producer application is packaged accurately. If not, then register the producer at design time in JDeveloper, as described in the section Registering Portlet Producers with a WebCenter Portal Application in the chapter Consuming Portlets in Oracle Fusion Middleware Developers Guide for Oracle WebCenter, and redeploy the application, as described in Section 7.1, Deploying WebCenter Portal Applications. After redeployment, verify that the packaged application includes the MBean, ProducerManager:

1. In Fusion Middleware Control, from the Application Deployment menu,

select System MBean Browser. 2. In the Navigator, expand Application Defined MBeans oracle.webcenter.portlet Application: application_name Producer Manager Producer Manager.