|
Oracle® Application Server Portal Developer's Guide
10g Release 2 (10.1.2) Part No. B14134-01 |
|
 Previous |
 Next |
|
Oracle® Application Server Portal Developer's Guide
10g Release 2 (10.1.2) Part No. B14134-01 |
|
|
Previous |
Next |
This appendix describes common problems that you might encounter when using OracleAS Portal and explains how to solve them. It contains the following topics:
This section describes common problems and solutions. It contains the following topics:
In JDeveloper, when you try to open the Java Portlet Wizard by choosing File > New > Web tier , the Portlets menu selection is not present.
Problem
The Java Portlet Wizard is not installed.
Solution
Install the Java Portlet Wizard, as described in the Installing the Oracle JDeveloper 10g Portal Add-in document on Portal Studio:
http://portalstudio.oracle.com/pls/ops/docs/folder/community/pdk/utilities/jdev/jdev.addin.install.guide.html
On Portal Studio (http://portalstudio.oracle.com), you can find this document in the Integration/Utilities section.
When you try to compile the code for your portlet, a compilation error occurs.
Problem 1
The Portlet Development library is not selected.
Solution 1
Make sure that Portlet Development library is selected for the project, as follows: edit your project's properties and select the Profiles > Development > Libraries entry in the pane on the right. Make sure that the Portlet Development library is listed under Selected Libraries.
Problem 2
There is a syntax error in the portlet's Java code.
Solution 2
Check the portlet's Java code syntax.
In JDeveloper, the Application Server Connection Test fails with the message Connection refused: connect.
Problem 1
OC4J is not running.
Solution 1
Make sure you OC4J is up and running by trying to access it on its default port, 8888: type the following URL in your browser: http://yourhostyourdomain:8888
Problem 2
The connection information is incorrect.
Solution 2
Verify the connection information that you provided in the Connection Setup wizard.
When accessing the provider test page with your browser, an error is shown.
Problem 1
The provider.xml syntax is incorrect.
Solution 1
Correct the provider.xml syntax. Refer to the PDK-Java XML Provider Definition Tag Reference document on Portal Studio:
http://portalstudio.oracle.com/pls/ops/docs/folder/community/pdk/jpdk/v2/xml_tag_reference_v2.html
Problem 2
JAR files are missing from the deployment environment.
Solution 2
Locate the missing JAR files and add them to the classpath.
When you register your provider with OracleAS Portal, the provider registration fails with the message: WWC-43176 The provider URL specified may be wrong or the provider is not running.
Problem 1
The provider is down.
Solution 1
Make sure that you can access the provider test page from your browser: enter the provider registration URL in your browser's address bar.
Problem 2
The provider is not accessible from your OracleAS Portal middle tier.
Solution 2
Try to access the provider node from your OracleAS Portal middle tier by pinging it: $> ping providerhost
Problem 3
The provider node host name is not recognized.
Solution 3
Replace the provider node host name with the provider node IP address in the provider registration URL.
Problem 4
Provider registration fails due to related circumstances.
Solution 4
Use logcfg.sql to gather more diagnostic information.
In OracleAS Portal, when you access a portal page, the portlet does not display on the page.
Problem 1
The provider is not running.
Solution 1
Make sure that the provider is up and running by accessing the provider test page from your browser: enter the provider registration URL in your browser's address bar.
Problem 2
The security manager for the provider is preventing the portlet from displaying.
Solution 2
In the provider definition file, provider.xml, delete or comment out the security manager, if any.
In OracleAS Portal, when you access the portal page, the portlet initially displays on the page, but returns error messages in subsequent display attempts.
Problem
The provider session information is incorrect.
Solution
Check whether or not the provider uses sessions. If it does, edit the provider registration information to make sure that you registered it accordingly, as follows:
Login Frequency: Once per User Sessions
In addition to specific issues listed in the preceding sections, the following information may help you to troubleshoot other portlet problems.
Problem 1
In OracleAS Portal, when accessing the portal page, the portlet does not display or displays an error message.
Solution 1
Check the application log file, located in J2EE_HOME/application-deployments/web_application_name: look for errors.
Problem 2
Pertinent information that may help solve the problem is not being recorded in the log file.
Solution 2
Increase the provider's log level to produce more detailed logging information by adding the following entry to the orion-web.xml file: <orion-web-app deployment-version="9.0.4.0.0" jsp-cache-directory="./persistence" temporary-directory="./temp" servlet-webdir="/servlet/"><env-entry-mapping name="oracle/portal/log/logLevel">6</env-entry-mapping></orion-web-app>.
You may have to restart your OC4J to ensure that the changes made to the configuration file take effect.
When you create a new provider group, the provider group is not created.
Problem 1
There is a problem in mod_osso.
Solution 1
Check for a mod_osso midtier registration problem.
Problem 2
There is a problem in the jpdk application classpath.
Solution 2
Check the jpdk application log for errors.
Attempting to display your portlet through URL generates the following error message: 500 INTERNAL SERVER ERROR
Problem
The httpProxyHost is not defined correctly.
Solution
In your provider.xml file, check the default proxy information. For example:
<proxyInfo class=""oracle.portal.provider.v1.http.ProxyInformation""> @ <httpProxyHost>www-proxy.us.oracle.com</httpProxyHost> <httpProxyPort>80</httpProxyPort> </proxyInfo>
Change the httpProxyHost and httpProxyPort proxy settings or remove these settings if you do not use proxy. Restart the OC4J instance to test if this resolves the problem.
This section provides information to help you troubleshoot problems you may encounter while using OmniPortlet.
To view errors that occur during the execution of OmniPortlet:
Open the application log file: $OC4J_HOME/j2ee/home/application-deployments/portalTools/ application.logor $IAS_HOME/j2ee/OC4J_instance/application-deployments/ portalTools/OC4J_instance_default_island_1/application.log
Display the HTML source (for example, in Microsoft Internet Explorer brower, choose View > Source), and locate the errors embedded in the output HTML as comments.
To alter the logging level of the OmniPortlet Provider:
Open the web.xml file and modify the context-param value of oracle.portal.log.LogLevel to the possible values ranging from 1 to 7 (where 7 means debug). The web.xml file is located at: $OC4J_HOME/j2ee/home/applications/portalTools/ omniPortlet/WEB-INF/web.xmlor $IAS_HOME/j2ee/OC4J_instance/applications/portalTools/ omniPortlet/WEB-INF/web.xml
The OmniPortlet errors that you are most likely to encounter, and possible solutions, are:
On UNIX, when you select the Layout Style of Chart, the chart is not displayed.
Problem
The DISPLAY environment variable is not set up correctly.
Solution
Specify a valid DISPLAY setting in either of the following ways:
Set the DISPLAY environment variable environment variable to an X server that you can access: setenv DISPLAY localhost:0.0java -jar oc4j.jar
Or, with JDK 1.4 or above, specify a "headless" display when starting your JVM: java -Djava.awt.headless=true -jar oc4j.jar
When you access an HTTPS URL, the following error displays:
java.lang.NoClassDefFoundError: at oracle.security.ssl.OracleSSLCipherSuite.isSSLLibDomestic when accessing HTTPS site with certificate
Problem
The required SSL library is not in the library path.
Solution
See the section "Library For HTTPS Access in Standalone OC4J Installation" (under "OmniPortlet Provider Test Page") in the OracleAS Portal Developer Kit (PDK) Configuring the OmniPortlet Provider document, which is part of the PDK zip file on OTN at http://www.oracle.com/technology/products/ias/portal/pdk.html (click the link Download the PDK Content).
Your OmniPortlet displays errors or does not not display the correct content.
Problem 1
The URL is not active.
Solution 1
Type the URL directly in your browser Address field to test that it is a valid URL.
Problem 2
If a proxy server is required to reach the site, the proxy settings are not valid. The following messages may display:
Failed to open specified URL. Cannot open the URL specified because of connection timeout.
Solution 2
Check that your proxy settings are valid: in the OmniPortlet Provider Test Page, click the Edit link for the HTTP Proxy Setting to specify the proxy server settings.
Problem 3
The message OmniPortlet timed out displays in your OmniPortlet.
Solution 3
If a proxy server is required to reach the site, see Solution 3.
If the URL request take a long time to process (for example, if it executes a long running query), try increasing the timeout value (in seconds) in the OmniPortlet provider.xml file in the $IAS_HOME/j2ee/OC4J_instance/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet directory. If you do this, you also need to do the following:
Bounce your middle-tier.
Increase the provider registration Timeout value of the Portal instances with which this provider is registered.
Problem 4
If HTTP authentication is required, the user name and password are missing or not valid. The following message displays:
Authorization failed when connecting to the URL specified. Provide correct user name and password to connect.
Solution 4
To configure the Secured Data (Web Clipping) Repository Setting, click the Edit link in the OmniPortlet Provider Test Page, and configure your settings. Then, in the Source tab, click Edit Connection, and enter a valid username and password.
Problem 5
If opening a URL of an HTTPS site with a certificate, the certificate is identified as not valid with the following error message in the portlet:
SSL handshake failed for HTTPS connection to the specified URL. The certificate file needs to be augmented.
Solution 5
See the section "Adding Certificates for Trusted Sites" in the "Securing OracleAS Portal" chapter in the Oracle Application Server Portal Configuration Guide.
Problem 6
If the proxy server requires authentication, the user name and password are missing or not valid. The following message displays:
Invalid or missing user proxy login information.
Solution 6
Check that your proxy server user name and password are valid: see Section B.3.2.2, "Proxy Authentication".
After changing portlet properties in the edit defaults page, your portlet content is not refreshed.
Problem 1
Web cache invalidation is not configured properly.
Solution 1
See the section "Web Cache" in the OracleAS Portal Developer Kit (PDK) Configuring the OmniPortlet Provider documentdocument, which is part of the PDK zip file on OTN at http://www.oracle.com/technology/products/ias/portal/pdk.html (click the link Download the PDK Content).
Problem 2
You have customized the portlet.
Solution 2
Select the Reset to Defaults option on the Customize page in order for the Edit Defaults changes to appear.
When you customize the portlet at runtime using the Customize link, the new property values are not reflected in the customized version of the portlet.
Problem
When you customize the portlet, a complete copy of the personalization object file is created. Since all properties are duplicated, subsequently modifying the portlet through Edit Defaults will not be reflected in the customized version of the portlet.
Solution
To ensure the latest changes are made to the portlet, you must click Customize again (after the modifications through the Edit Defaults wizard are made), then select the Reset to Defaults option.
This section provides information to help you troubleshoot problems you may encounter while using the Web Clipping provider or Web Clipping Studio:
You can use the Web Clipping Provider Test Page to determine whether or not the provider is functioning properly. To access the Test Page, click Web Clipping Provider from the Portal Tools Application Welcome Page, which is located at:
http://Hostname:Port/portalTools
The Provider Test Page: Web Clipping is displayed. It provides the following information:
Portlet information: Information about the Web Clipping portlet (The Web Clipping provider contains only one portlet.)
Provider initialization parameters and values.
Provider status, with links to pages to edit the configuration.
For more information about using the Test Page, see the "Administering Web Clipping" appendix in the Oracle Application Server Portal Configuration Guide.
If you encounter difficulties making or maintaining connections to the site to be clipped or a site that was clipped, note the following:
If a proxy server is needed to connect to HTTP servers outside of a firewall, make sure that the proxy servers are configured correctly. See Section B.3.2.1 for more information.
If the proxy servers are configured for proxy authentication, you will receive HTTP error code 407 when you attempt to clip a page outside the firewall unless you have manually configured proxy authentication. See Section B.3.2.2 for information about manual configuration.
If a reverse proxy is used, make sure that the reverse proxy server is configured correctly. See the "Performing Advanced Configuration" chapter of the Oracle Application Server Portal Configuration Guide for information about configuring a reverse proxy.
If you are attempting to add a clip to a Web Clipping portlet, and experience difficulty making or maintaining connections, the cause may be that the configuration includes a load balancer, but the configuration was not set correctly:
If multiple OC4J instances are set up behind a load balancer, the Web Clipping Repository and HTTP proxy must be configured to be identical on all OC4J instances before you join the OC4J instances to the Load Balancer.
Web clippings have definitions that must be stored persistently in the Web Clipping Repository hosted by an Oracle Database server. In a multiple middle-tier environment, all instances of OC4J must be configured to store definitions in the same repository.
In addition, all instances of OC4J must have identical configurations for the HTTP proxy.
The Load Balancer must be session-enabled. If it is not, the first request connects, but subsequent requests, which may be routed to a different instance, fail.
For more information about configuring with a load balancer, see the "Performing Advanced Configuration" chapter of the Oracle Application Server Portal Configuration Guide.
To be sure a URL is correct, test the URL that you want to clip in a browser before you attempt to clip it. Also test the URL from the provider middle tier to be sure that it is accessible from there.
If you cannot clip a page, make sure that the page is not overpopulated with IFrames. View the page in a browser, looking at the page source. If it contains IFrames, start with the URL pointed to by the IFrame "src" attribute.
If images in a clipping are not retrieved when the rest of the clipping is retrieved, check your browser proxy settings. Because images are treated as links (using the "src" attribute of the IMG tag), images from clipped sites are served directly from the original sites. If the images required that the proxy setting be enabled during creation of the clipping or Show mode, disabling the browser proxy setting disables viewing of the images in a clipping. Enable the browser proxy setting.
If you cannot connect, check the error log. (See Section B.3.3 for information about the error log.) Check to see if the log contains a message about logon to the database being denied. If this is the case, the PORTAL schema password in the infrastructure database may have been modified manually and no longer matches the password stored in Oracle Internet Directory. Refer to the Oracle Internet Directory Administrator's Guide for more information about setting the password.
If a proxy server is needed to connect to HTTP servers outside of a firewall, make sure that the proxy servers are configured correctly.
To configure the proxy servers, go to the Web Clipping Provider Test Page, as described in Section B.3.1. In the Web Clipping Provider Test Page, click Edit in the Actions column of the HTTP Proxy row. In the Edit Provider page, specify the HTTP Proxy Host and the HTTP Proxy Port for the HTTP Proxy.
For access to servers that are inside the firewall, you can specify a list of domain names that do not require going through the firewall by selecting No Proxy for Domains beginning with and entering the URL. You do not need to restart OC4J for the new settings to take effect.
For more information about configuring proxy servers, see the "Administering Web Clipping" appendix of the Oracle Application Server Portal Configuration Guide.
Web Clipping supports global proxy authentication, and per-user authentication. You can specify the realm of the proxy server and whether all users will automatically log in using a user name and password you provide, each user will log in using an individual user name and password, or all users will log in using a specified user name and password. For more information about configuring proxy authentication, see the "Administering Web Clipping" appendix of the Oracle Application Server Portal Configuration Guide.
By default, the logging level of Web Clipping is set to level 3, which provides information about configuration, severe errors, and warnings. This is a reasonable level for day-to-day operation. To view information that is useful for debugging, set the logging level to 7.
To set the logging level, edit the web.xml file and specify the level for the oracle.portal.log.LogLevel parameter. The web.xml is located at:
OracleHome/j2ee/OC4J_Portal/applications/portalTools/webClipping/WEB-INF
For example, to set the level to display debugging information, set the value of the parameter oracle.portal.log.LogLevel to 7, as shown in the following example:
<context-param>
<param-name>oracle.portal.log.LogLevel</param-name>
<param-value>7</param-value>
</context-param>
Errors that occur when accessing the Test Page or during the execution of the Web Clipping portlet are written to one of the following files:
OC4J_HOME/j2ee/home/application-deployments/portalTools/application.log IAS_HOME/j2ee/OC4J_instance/application-deployments/portalTools/OC4J_instance_default_island_1/application.log
You can find more solutions on Oracle MetaLink, http://metalink.oracle.com. If you do not find a solution for your problem, log a service request.
|
See Also:
|
