D Troubleshooting

Troubleshoot errors and issues that you encounter while developing WebCenter Portal Cloud Service assets.


D.1 Troubleshooting WebCenter Portal Shared Library Deployment

  • Changes are not available after deployment even though deployment successful.

    WebCenter Portal always uses the latest shared library version. Check that the implementation version in MANIFEST.MF matches the implementation version displayed in the WebLogic Server Administration Console.

    For example, check the value in PortalSharedLibrary/Application Sources/META-INF/MANIFEST.MF is the same as that displayed in the Administration Console under Deployments> extend.spaces.webapp>Overview

  • "DeployerException: Task 9 failed" displays:

    weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 9 failed:
    [Deployer:149117]deploy library com.mycompanyname.shared.lib [LibSpecVersion=,LibImplVersion=] on AdminServer,WC_Portal.

    This error occurs if the implementation version of the new deployment and the existing deployment are the same. Use the Administration Console to verify the current implementation version and if necessary change the version and redeploy the shared library.

  • "java.lang.IllegalArgumentException" displays:

    Restart the managed server on which WebCenter Portal is deployed.

D.2 Troubleshooting Portlet Creation

D.2.1 Cannot Access the Create Portlet Wizard


In the New Gallery, I cannot find the Standards-based Java Portlet (JSR 286) option.


The application in which you are trying to create the portlet was created using WebCenter Portal's Portal Framework template and therefore is not scoped for portlet creation.


Perform the following steps:

  1. Try creating the portlet in a Portlet Producer Application or any application scoped for portlet creation.

  2. In the New Gallery, click the All Technologies tab to list all available options regardless of the technology scope of the application.

D.2.2 Cannot Add the Portlet Functionality that I Want to the Portlet


I cannot find the option to add certain features, for example portlet events or public render parameters, to the portlet in the Create JSR 286 Java Portlet wizard.


The wizard does not provide the option to add certain features to portlets.


After you create a portlet using the Create JSR 286 Java Portlet wizard, edit the portlet.xml file using the Overview Editor to add advanced functionality. For more information, see Developing JSR 286 Java Portlets.

D.3 Troubleshooting Pagelets

Keep the following common configuration errors in mind when troubleshooting resources and pagelets. For details on configuring Pagelet Producer settings, see Configuring Pagelet Producer Settings.

  • If you are using SSL, make sure both HTTP (nonsecure) and HTTPS (secure) ports are configured properly on the Transform page of the Pagelet Producer settings.

  • If you are proxying external sites on a network that requires an HTTP proxy, you must configure the proxy URL on the Proxy page of the Pagelet Producer settings.

  • Confirm that the login_resource and pagelet_api resources, created by default, are present and correctly configured.

  • If you are proxying KD Browser or other CSP pagelets, make sure the image service URL is absolute and the CSP SOAP API URL is set correctly in the CSP page of the Pagelet Producer settings.

  • Due to restrictions in the Sun Java Virtual Machine (JVM), pagelets cannot use HTTPS content where the underlying certificate uses MD2 signing algorithm.

For additional troubleshooting information, use logging. Pagelet Producer logs messages to the standard Oracle Diagnostic Logging facility. In Oracle WebLogic Server, that location is: user-projects/domains/<domain>/servers/ <server>/logs/<server>-diagnostic.log. For details on configuring logging, see How to Configure Logging Settings. For more information on debugging pagelets, see Creating Pagelets.

D.4 Troubleshooting OmniPortlet

This section provides information to help you troubleshoot problems you may encounter while using OmniPortlet.


As the OmniPortlet producer exists and executes in a tier different from WebCenter Portal, and does not have access to the session information, you must expose XML files as PUBLIC in order for OmniPortlet to access them.

Cannot Define OmniPortlet Using the Define Link

You are not able to define the OmniPortlet at runtime.


OmniPortlet only supports a RenderPortletInIFrame value of true, meaning that OmniPortlet must be rendered within an IFRAME. Therefore, the OmniPortlet property, RenderPortletInIFrame, must be set to true. In the Property Inspector, the RenderPortletInIFrame property is available under Display Options.

Currently, the RenderPortletInIFrame property has a value of false. Consequently, when you click the Define link at runtime, the Type tab may not display and you cannot proceed with defining the OmniPortlet.


You can choose Customize from the Action list to define OmniPortlet, or select the OmniPortlet in the Structure window in Oracle JDeveloper, and in the Property Inspector, set RenderPortletInIFrame to true.