This chapter describes issues associated with Oracle Portal. It includes the following topics:
In addition to the known problems and workarounds described in this document, Oracle recommends that you read the My Oracle Support note 834615.1 - Oracle Fusion Middleware 11g Portal (11.1.1) Support Status and Alerts. This article contains known issues that were discovered after the release of Oracle Portal 11g Release 1 (11.1.1).
This section describes general issues and workarounds. It includes the following topics:
Section 35.2.1, "Oracle Portal 11g Release 1 (11.1.1) with Oracle Application Server Wireless"
Section 35.2.3, "Moving Content When Approval Is Enabled Does Not Require Approval"
Section 35.2.4, "Firefox and Safari Browsers Do Not Display Tooltips on Oracle Portal Screens"
Section 35.2.5, "Non-ASCII URLs Cannot be Decoded in Some Scenarios"
Section 35.2.6, "Adding a Zip File with a Non-ASCII Character Name"
Section 35.2.7, "Manual Changes to Oracle Portal Default Schema Objects"
Section 35.2.11, "Portal Throws Discoverer Provider is Busy Error Message"
Section 35.2.13, "Error When Adding Sample RSS Portlets to a Page"
Section 35.2.15, "IPv6 Support in Oracle Portal 11g Release 1 (11.1.1)"
Integrating Oracle Application Server Wireless 10g with Oracle Portal 11g Release 1 (11.1.1) requires you to complete a set of manual steps, as described in the My Oracle Support note 837837.1 (Oracle Portal 11g Release 1 (11.1.1) with Oracle Application Server Wireless). In addition, see the following My Oracle Support notes for information about deprecated features in 10g:
If the database where the portal schema is installed is version 10.2 or later, then users must re-enter the remote user's password when they rename or edit a database link from the Portal Navigator's Database Objects tab. This is applicable only for those database links that are created with the Specific User option.
Moving content between pages or between regions of the same page does not trigger approvals. For example, when a target page is configured with an approval process and a contributor moves content from a source page to the target page, the moved content does not trigger the approval process on the target page, even when approval is required for all users.
Firefox and Safari browsers do not support the display of tooltip text, which is set using the ALT attribute for image descriptions.
As a workaround, you can download and install browser-specific add-ons, such as Popup ALT Attribute for Firefox (see https://addons.mozilla.org/en-US/firefox/addon/1933).
If the JVM default character encoding is set to ISO8859-1, the Portal repository database character set must match with the JVM default character encoding. If this condition is not satisfied, non-ASCII URLs may become inaccessible.
If you are adding a zip file to a page under a pagegroup using non-ascii character name, and when you unzip the file, it throws the following exception:
IllegalArgumentException: null and unzip will be failed.
To avoid this exception, you must use ascii character as the zip file name.
Any manual changes to Oracle Portal default objects, such as tables, views, packages, or indexes are not supported. Such changes may render Oracle Portal unusable. Note that the internal structure of Portal objects can change between versions.
For more information, see the 403179.1 My Oracle Support note.
If you are using Secure Enterprise Search (SES), then by default, the search result of your Portal displays durable URL format for an item or a page. To display your URL as a readable format, perform the following steps:
Run sbrsrxml.sql, located at ORACLE_HOME\upgrade\portal\admin\plsql\wws in Windows and ORACLE_HOME/upgrade/portal/admin/plsql/wws, in UNIX, using your Portal schema password.
Enter the value 0, for example @wws\sbrsrxml.sql 0 in Windows.
After you run a full SES crawl, your URL is displayed in a readable format. And if you want your URL to display the durable URL format, then run sbrsrxml.sql and enter the value 1.
This section describes how to encrypt a password in the mod_oradav.conf file. Perform the following tasks:
To edit the password in the mod_oradav.conf file, do the following:
Open your mod_oradav.conf file, located at ORACLE_INSTANCE/config/OHS/ohs1/moduleconf (UNIX).
Locate the DAV entry for which you wish to change the password. In a default portal instance, you can find the DAV configuration entry in the following directive:
<Location /dav_portal/portal>
In the DAV entry, remove the directive ORACRYPTPASSWORD (For example, DAVParam ORACRYPTPASSWORD BS50NfrosVZOjfgc9hUQ9wcbFFxLSYT/BA==), and replace with the clear text password using the following syntax:
DAVParam ORAPASSWORD <your_password_here>
For example:
If you want to have a password of passwd123, add a line as follows: DAVParam ORAPASSWORD passwd123.
Save the file.
After editing the DAV password, it is recommended that the DAV password be obfuscated by running the oradavTool.pl script located at ORACLE_HOME/bin in UNIX and ORACLE_HOME\bin in Windows. To do so, perform the following steps:
If necessary, change the user to the Oracle software owner user, typically oracle, using the following command:
su - oracle
Set the ORACLE_HOME environment variable to specify the path to the Oracle home directory for the current release, and set the PATH environment variable to include the directory containing the Perl executable and the location of the oradavTool.pl script (Located at ORACLE_HOME/ohs/bin in UNIX and ORACLE_HOME\ohs\bin in Windows).
Bourne, Bash, or Korn shell:
$ ORACLE_HOME=new_ORACLE_HOME_path;export ORACLE_HOME PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH;export PATH
C or tcsh shell:
% setenv ORACLE_HOME new_ORACLE_HOME_PATH % setenv PATH ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:PATH
On Microsoft Windows, set the PATH and PERL5LIB environment variable:
set PATH=ORACLE_HOME\bin;%ORACLE_HOME%\perl\bin;%PATH% set PERL5LIB=ORACLE_HOME\perl\lib
On UNIX platforms, set the shared library path environment variable
Include the ORACLE_HOME/lib or lib32 directory in your shared library path. Table 35-1 shows the appropriate directory and environment variable for each platform.
Table 35-1 Shared Library Path Environment Variable
| Platform | Environment Variable | Include Directory |
|---|---|---|
|
AIX Based Systems |
|
|
|
HP-UX PA-RISC |
|
|
|
Solaris Operating System |
|
|
|
Other UNIX platforms, including Linux and HP Tru64 UNIX |
|
|
For example, on HP-UX PA-RISC systems, set the SHLIB_PATH environment to include the ORACLE_HOME/lib directory:
$SHLIB_PATH=$ORACLE_HOME/lib:$SHLIB_PATH;export SHLIB_PATH
Change directory to the ORACLE_HOME/bin (UNIX) directory, as this is the location of the oradavTool.pl script.
Invoke the following Perl script to encrypt the mod_oradav.conf password:
perl oradavTool.pl -f mod_oradav.conffilename
Where mod_oradav.conffilename is the filename for mod_oradav.conf, which includes the full path to the mod_oradav.conf file.
For example, in UNIX:
perl oradavTool.pl -f /u01/app/oracle/as11gr1/ORACLE_INSTANCE/config/OHS/<ohs_name>/moduleconf/mod_oradav.conf
The directive ORAPASSWORD is updated with the new directive ORACRYPTPASSWORD, and your password is obfuscated.
Restart your Oracle HTTP Server.
When migrating an external application during the cloning process, you must run the ssomig utility after the import is completed as follows:
Open the tnsnames.ora file, and enter connect string entries to the sso database in tnsnames.ora file.
Set the TNS_ADMIN environment variable to the tnsnames.ora file location.
Run the ssomig utilty (Located at INFRA_HOME/sso/bin):
$INFRA_HOME/sso/bin/ssomig -import -overwrite -s orasso -p <<ORASSO_SCHEMA_PASSWORD>> -c <<TNS_ALIAS>> -d ssomig.dmp -log_d <<ABSOLUTE_PATH_FOR_MREXPDIR>> -discoforce
Portal throws an error message The Discoverer Provider is busy, please try again later. This occurs when you perform the following steps:
Click Edit Portlet defaults
Click Update for Database section
Change selection for User not logged sub-section
Click Next to fetch worksheet list
To workaround this issue perform the following steps:
Add stall timeout to $DOMAIN_HOME/servers/WLS_PORTAL/
stage/portal/portal/configuration/appConfig.xml
For example: <stall>200</stall>
Restart WebLogic Server Portal
If RCU portal schema creation fails with the error message ORA-24246: empty access control list (ACL) not allowed, do the following:
Connect to the database as a SYS user.
At the SQL prompt, run the following command:
BEGIN
DBMS_NETWORK_ACL_ADMIN.drop_acl (
acl => '/sys/acls/portal-permissions.xml');
COMMIT;
END;
/
When you try to add the sample Scrolling RSS Portlet or the sample Simple RSS portlet to a Portal page, an error message is displayed.
The error occurs because the RSS used by the sample portlets are no longer available.
Currently, there is no workaround for this problem.
If you have Oracle Text enabled, the following internal server error may occur when you are searching for Pages:
Internal error (WWC-00006) An unexpected error has occurred (WWS-32100) Unknown Exception (WWC-45131) User-Defined Exception (WWV-11230) Unexpected error - ORA-00600: internal error code, arguments: [qkeIsExprReferenced1], [], [], [], [], [], [], [] (WWC-35000)
If this error occurs, you must download and install database updates from http://updates.oracle.com/download/7041059.html.
Oracle Portal 11g Release 1 (11.1.1) is not directly supported on Internet Protocol Version 6 (IPv6). The supported configuration comprises the following:
An IPv4/IPv6 reverse proxy setup on an IPv4/IPv6 dual stack machine.
The Portal mid-tier and the backend database on IPv4 machines, and clients accessing the Portal server through the proxy.
This section describes the upgrade issues and workarounds. It discusses the following topics:
When you upgrade SSL environment from Oracle Portal 10g to Oracle Portal 11g Release 1 (11.1.1), you will not able to login to Oracle Portal, when you have SSO and Portal Midtier on the same hostname. Internet Explorer has a problem redirecting back and forth on the same hostname between two different ports under SSL mode. As a workaround, you can use Mozilla Firefox.
This section describes the interoperability issues and workarounds. It discusses the following topics:
For this interoperability scenario to work, you must download and install updates from http://updates.oracle.com/download/7685124.html and see note 816929.1 in My Oracle Support.
For this interoperability scenario to work, you must download and install updates from http://updates.oracle.com/download/7971335.html.
In Portal 11g 1 (11.1.1), you cannot create webproviders when you are using 11g midtier with 10g portal repository.
This section describes issue and workaround related to the Oracle Portal user interface. It includes the following topic:
Cannot Set Privileges Using List View on Pages Inheriting Privileges from Parent or Template
If you use the List View to set access privileges for one or more pages, then privileges will not be set on pages inheriting privileges from a parent page or template. As a workaround, change the privileges for such pages individually, that is, using the Access tab for the subpage.
This section describes issues and workarounds related to export and import in Oracle Portal. This section includes the following topics:
If you include Reports Server Components within a transport set, then they are deleted on export and import. In addition, do not configure the Oracle Reports item type in any page groups intended for export and import. If you do, then the following error is displayed when you try to configure item types in the imported page group (by clicking the Content Type and Classifications Edit link on the Configure tab for the page group):
Internal error (WWC-00006) Unexpected error - User-Defined Exception (WWC-35000) Unexpected error - ORA-01403: no data found (WWC-35000)
After you complete the transport set transfer, click Display Manifest to display the transport set manifest. Ensure that you save the transport set before performing the precheck of the transferred data. This step takes the manifest changes.
Importing a page group may fail with the following error message:
[Error: (WWU-80338)] context = Schema Validation user = ORCLADMIN There were some inconsistencies found and hence import process is aborted.Check the debug log for further details. Fix those inconsistencies, by running schema validation in cleanup mode to proceed
This problem might occur after deleting a page group containing shared portlets. You must run SVU in cleanup mode to ensure a smooth export or import process.
This section describes issues and workarounds related to OmniPortlet, Web Clipping, Simple Parameter Form, Page portlet, and WSRP providers. This section includes the following topics:
Section 35.7.1, "Registering WSRP Producers in Enterprise Configurations"
Section 35.7.2, "Setting up the WSRP and JPDK Applications in Oracle Portal"
Section 35.7.3, "Issue When Accessing Page Portlet Using Federated Portal Adapter"
Section 35.7.5, "SSL Support for Oracle Portal Integration Solutions (Microsoft Exchange)"
When you register a WSRP producer in an Enterprise configuration, you must create a Web Services Definition Language (WSDL) document manually, then register the WSRP producer using that WSDL. This is because the dynamically generated WSDL creates URLs using the HTTPS protocol and the HTTPS port while WSRP producers use HTTP.
Note:
A producer for WSRP portlets is analogous to a provider for PDK-Java portlets.To create a WSDL document manually, perform the following tasks:
View the dynamically generated WSDL through your browser (preferably Internet Explorer).
To view the WSDL for our WSRP samples, go to:
http://host:external http port/portletapp/portlets?WSDL
Save the file from the browser to any externally available location.
For our WSRP Samples, save the file from the browser into the following directory:
ORACLE_HOME/j2ee/home/applications/portletapp/wsrp-samples
Save the file as wsrpsamples.wsdl.
Edit the file, replacing https with http and correcting the ports to be the external http ports.
View the file through a browser.
For example, for our WSRP Samples use the following URL:
http://host:external http port/portletapp/wsrpsamples.wsdl
Use the URL to your *.wsdl file (such as the URL under Step 4) when you register the WSRP producer.
For more information about Enterprise configurations, see the Oracle Fusion Middleware Enterprise Deployment Guide for Java EE.
This section describes steps to manually configure the WSRP and JPDK application and deploying them on the Oracle WebLogic Server. This section includes:
To configure the WSRP, complete the following steps:
You can create a WebLogic Managed Server on an existing domain using the Oracle WebLogic Server Administration Console to create the managed server instance and provision the shared libraries required to run a custom Oracle Portal application. To create the WSRP Managed Server, complete the following steps:
Log on to the Oracle WebLogic Server Administration Console.
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit.
In the Domain Structure tree, expand Environment, and then select Servers.
The Summary of Servers page is displayed.
Click New.
The Create a New Server page is displayed.
In the Create a New Server page enter the following information:
Server Name: Enter the name of the server, for example WLS_WSRP.
Server Listen Port: Enter the port number from which you want to access the server instance. For example, 9003.
Select the No, this is a stand-alone server radio button.
Click Finish.
In the Summary of Servers page, click on the Server (WLS_WSRP) you have created.
Select your machine name from the Machine drop-down list and click Save.
Click Activate Changes.
Adding the Required Libraries to the WSRP Managed Server
For a portlet producer application, you must deploy the following libraries to the new Managed Server or cluster:
oracle.portlet-producer.wsrp(11.1.1,11.1.1)
oracle.portlet-producer.jpdk(11.1.1,11.1.1)
DMS Application (11.1.1.1.0)
oracle.jrf.system.filter
oracle.jsp.next(11.1.1,11.1.1)
oracle.wsm.seedpolicies(11.1.1,11.1.1)
wsil-wls
To add the libraries, complete the following steps:
Click Lock & Edit.
In the Domain Structure tree, select Deployments.
The Summary of Deployments page is displayed.
Select oracle.portlet-producer.wsrp(11.1.1,11.1.1) from the Deployments table.
The Settings for oracle.portlet-producer.wsrp(11.1.1,11.1.1) page is displayed.
Note:
If the oracle.portlet-producer.wsrp(11.1.1,11.1.1) does not appear in the Deployment table, then click Customize this table, and disable the Exclude libraries when displaying deployments check box. Click Apply.Click the Targets tab, and select AdminServer and WLS_WSRP from the Servers section.
Click Save.
Go to your Summary of Deployments page, and for each shared library, click the Targets tab, and then check AdminServer and WLS_WSRP from the Servers section.
To add the wsil-wls library, complete the following steps:
Select wsil-wls from the Deployments table.
Click the Targets tab, and select wsil-wls from the Component table.
Click Change Targets, and then check AdminServer and WLS_WSRP from the Servers section.
Click Yes.
Click Activate Changes.
Starting the WSRP Managed Server
To start the managed server, complete the following steps:
Click Lock & Edit.
In the Domain Structure tree, expand Environment, and then select Servers.
The Summary of Servers page is displayed.
Click the Control tab, and check your created server (WLS_WSRP).
Click Start.
The Server Life Cycle Assistant page is displayed.
Click Yes, to start the managed server.
To map the portletPrefs datasource targets to the managed server (WLS_WSRP), do the following:
In the Domain Structure tree, expand Services, and then select and expand JDBC and click Data Sources.
The Summary of JDBC Data Sources page is displayed.
Click the Name associated with the jdbc/portletPrefs JNDI.
Click the Targets tab, and check WLS_WSRP from the Servers section.
Click Save.
Click Activate Changes.
Extending the Existing WebLogic Domain
To extend your existing Oracle WebLogic Server domain with the Oracle WSM Policy Manager, complete the following steps:
Note:
You must stop all the servers running in the Oracle Portal domain.Go to the oracle_common\common\bin directory and run the config.sh.
The Welcome window is displayed.
Select Extend an existing WebLogic Domain and click Next.
The Select a WebLogic Domain Directory screen is displayed.
Select your valid domain directory and click Next.
The Select Extension Source screen is displayed.
Select Oracle WSM Policy Manager - 11.1.1.0 [Orhome] (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.
Click Next.
The Test JDBC Data Sources screen is displayed.
Click Next.
The Configure JDBC Component Schema screen is displayed.
Check the OWSM MDS Schema and enter the Host Name, Port, DBMS/ Service, Schema Password for the MDS schema. Click Next.
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.The Test Component Schema screen is displayed.
Confirm the test is successful and click Next.
The Select Optional Configuration screen is displayed.
Select Deployments and Services.
Click Next.
The Target Deployments to Clusters or Servers screen is displayed.
Ensure wsrp-pm is targeted to servers including WLS_WSRP and AdminServer.
Click Next.
The Target Services to Cluster or Servers screen is displayed
Click Next.
Review your settings in the Configuration Summary screen, and click Extend.
Click Done.
Start the Oracle WebLogic Administration Server, the managed server, and the WLS_WSRP managed server.
Adding wsrp-pm to the WSRP Managed Server
You must add the wsrp-pm to the WLS_WSRP managed server, by completing the following steps:
In the Domain Structure tree, select Deployments.
The Summary of Deployments page is displayed.
Select wsm-pm from the Deployments table.
Click the Targets tab, and select wsm-pm from the Component table.
Click Change Targets, and then check AdminServer and WLS_WSRP from the Servers section.
Click Yes.
To deploy the EAR file, download the wsrp-samples.ear file, from http://www.oracle.com/technology/products/ias/portal/pdk.html and do the following:
Click Lock & Edit.
In the Domain Structure tree, select Deployments.
The Summary of Deployments page is displayed.
Click Install.
Select wsrp-samples.ear from your directory, click Next.
Select Install this deployment as an application, and click Next.
Check WLS_WSRP from the Servers section, and click Next.
Enter a name for the deployment, and click Finish.
Click Activate Changes.
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:port/portletapp/portlets?WSDL
You should see a page similar to the one shown in Example 35-1.
Example 35-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.org/wsdl/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:bind="urn:oasis:names:tc:wsrp:v1:bind"> <import namespace="urn:oasis:names:tc:wsrp:v1:bind" location= "http://stamf10.us.abc.com:8090/wsrp-tools/portlets/wsrp1?WSDL=wsrp_v1_bindings.wsdl" /> - <service name="WSRP_v1_Service"> + <port name="WSRPServiceDescriptionService" binding="bind:WSRP_v1_ServiceDescription_Binding_SOAP"> <soap:address location="http://stamf10.us.oracle.com:8090/wsrp-tools/portlets/WSRPServiceDescriptionService" /> </port> - <port name="WSRPBaseService" binding="bind:WSRP_v1_Markup_Binding_SOAP"> <soap:address location="http://stamf10.us.oracle.com:8090/wsrp-tools/portlets/WSRPBaseService" /> </port> - <port name="WSRPPortletManagementService" binding="bind:WSRP_v1_PortletManagement_Binding_SOAP"> <soap:address location="http://stamf10.us.abc.com:8090/wsrp-tools/portlets/WSRPPortletManagementService" /> </port> - <port name="WSRPRegistrationService" binding="bind:WSRP_v1_Registration_Binding_SOAP"> <soap:address location="http://stamf10.us.abc.com:8090/wsrp-tools/portlets/WSRPRegistrationService" /> </port> </service> </definitions>
To view the WSDL URL using the Oracle Web Cache port, edit the portal.conf file (Loacated at ORACLE_INSTANCE\config\OHS\ohs1\moduleconf (Windows) as follows:
<Location /portletapp>
SetHandler weblogic-handler
WebLogicHost servername.domain.com
WebLogicPort 9003
</Location>
Save your file and now you should be able to access the WSDL URL through the Oracle Portal port (The default port is 8090).
Registering and Viewing Your Portlet
After you've created and deployed the provider and its portlets, you should register the provider with Oracle Portal. For more information, see Registering and Viewing Your JSR 168 Portlet in the "Oracle Fusion Middleware Developer's Guide for Oracle Portal."
To configure and deploying the JPDK, perform the following:
Creating the JPDK Managed Server
You can create a WebLogic Managed Server on an existing domain using the Oracle WebLogic Server Administration Console to create the managed server instance and provision the shared libraries required to run a custom Oracle Portal application. To create the JPDK Managed Server, do the following:
Log on to the WebLogic Server Administration Console.
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit.
In the Domain Structure tree, expand Environment and then select Servers.
The Summary of Servers page is displayed.
Click New.
The Create a New Server page is displayed.
In the Create a New Server page enter the following information:
Server Name: Enter the name of the server. For this step use WLS_JPDK as an example.
Server Listen Port: Enter the port number from which you want to access the server instance. For this step use 9004 as an example.
Select the No, this is a stand-alone server radio button.
Click Finish.
In the Summary of Servers page, click on the Server (WLS_JPDK) you have created.
Select your machine name from the Machine drop-down list and click Save.
Click Activate Changes.
Adding the Required Libraries to the JPDK Managed Server
For a portlet producer application, you must deploy the following libraries to the new Managed Server or cluster:
oracle.portlet-producer.jpdk(11.1.1,11.1.1)
DMS Application (11.1.1.1.0)
oracle.jsp.next(11.1.1,11.1.1)
To add the libraries, do the following:
Click Lock & Edit.
In the Domain Structure tree, select Deployments.
The Summary of Deployments page is displayed.
Select oracle.portlet-producer.jpdk(11.1.1,11.1.1) from the Deployments table.
The Settings for oracle.portlet-producer.jpdk(11.1.1,11.1.1) page is displayed.
Note:
If the oracle.portlet-producer.jpdk(11.1.1,11.1.1) does not appear in the Deployment table, then click Customize this table, and disable the Exclude libraries when displaying deployments check box. Click Apply.Click the Targets tab, and select AdminServer and WLS_JPDK from the Servers section.
Click Save.
Go to your Summary of Deployments page, and for each shared library, click the Targets tab, and then check AdminServer and WLS_JPDK from the Servers section.
Click Activate Changes.
Starting the JPDK Managed Server
To start the managed server do the following:
Click Lock & Edit.
In the Domain Structure tree, expand Environment and then select Servers.
The Summary of Servers page is displayed.
Click the Control tab, and select your created server (WLS_JPDK).
Click Start.
The Server Life Cycle Assistant page is displayed.
Click Yes, to start the managed server.
To map the portletPrefs datasource targets to the managed server (WLS_JPDK), do the following:
In the Domain Structure tree, expand Services, and then select and expand JDBC and click Data Sources.
The Summary of JDBC Data Sources page is displayed.
Click the Name associated with the jdbc/portletPrefs JNDI.
Click the Targets tab, and check WLS_JPDK from the Servers section.
Click Save.
Click Activate Changes.
To deploy the JPDk, do the following:
Click Lock & Edit.
In the Domain Structure tree, select Deployments.
The Summary of Deployments page is displayed.
Click Install.
The Install Application Assistant page is displayed.
In the Path field, enter the location of the jpdk.ear file (Located at ORACLE_HOME/archives/applications for Windows and ORACLE_HOME\archives\applications for UNIX).
Select jpdk.ear, and click Next.
Select Install this deployment as an application, and click Next.
Check WLS_JPDK from the Servers section, and click Next.
In the Name field, enter a name for the deployment.
Click Finish.
Click Activate Changes.
Click Lock & Edit.
From the Summary of Deployments page, select the application and click Start and then, Servicing all requests.
From the Start Application Assistant, click Yes.
Now that you have deployed the sample EAR file, you need to test its URL by entering it into a browser. The URL is of the form:
http://host:port/jpdk/providers/sample/
For more information, see Creating Java Portlets in the Oracle Fusion Middleware Developer's Guide for Oracle Portal.
The Federated Portal Adapter enables you to display remote portal pages in your portal. However, if both portal instances do not share the same Oracle Single Sign-On server, then you cannot display a remote portal page as a page portlet, even if the remote page is public. A message is displayed instead of the page portlet, as shown in the following example:
Portlet 257,75057 responded with content-type text/plain when the client was requesting content-type text/html
As a workaround, configure both portal instances to use the same Oracle Single Sign-On server.
When you redeploy your portlets to the portlet container, all existing sessions between the producer and all of its consumers are lost. If a consumer tries to reuse an existing producer session, then it may receive an error message the first time it tries to contact the producer after redeployment, as shown in the following example:
Error: Could not get markup. The cookie or session is invalid or there is a runtime exception.
To reestablish the producer's session, refresh the portal page. You will not see this error message if you are reaccessing the portlet from a new browser session because it automatically establishes a new producer session.
SSL support is not available for Oracle Portal Integration Solutions (Microsoft Exchange). This is a known limitation.
Oracle Portal Developer Kit (PDK) version 10.1.2 is included with the Portal and Wireless installation. Release notes for the PDK-Java and PDK-PL/SQL can be found at the following middle-tier ORACLE_HOME locations:
PDK-Java: ORACLE_HOME/portal/pdkjava/v2/pdkjava.v2.releasenotes.html
PDK-PL/SQL: ORACLE_HOME/portal/pdkjava/v2/pdkplsql.release.notes.html
New versions of the Oracle PDK are released periodically providing new features, new APIs, and additional documentation. To take advantage of all the latest features, download the latest PDK from the PDK downloads page on the Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/ias/portal/pdk.html.
Release notes for the latest Oracle PDK version are available on Oracle Portal on OTN and also in these PDK download locations:
pdk\plsql\pdkplsql.release.notes.html
pdk\jpdk\v2\pdkjava.v2.release.notes.html
This section describes issues and workarounds related to Globalization Support in Oracle Portal. It includes the following topics:
Section 35.9.1, "Text Entry Always Right to Left in BiDi Languages"
Section 35.9.2, "Non-ASCII Character Limitations in Oracle Portal"
The direction of all text areas and fields is right to left (RTL). However, you may want some text areas to work left to right (LTR). Internet Explorer users can change this by pressing the left hand side Ctrl and Shift keys.
When you copy and paste an item URL containing non-ASCII characters from one browser Location or Address field into another, you may not be able to access the item if your login credentials have not been authenticated through OracleAS Single Sign-On.
As a workaround, log in to the portal before you access the item and copy the item URL.
In some scenarios, multibyte characters in log files may get corrupted.
For example, when the WLS_PORTAL managed server is started from the Oracle WebLogic Server Administration Console, multibyte characters, such as username, password, and is starting, may get corrupted.
Workarounds:
Change -Dfile.encoding=iso-8859-1 to -Dfile.encoding=utf8 in the WLS_PORTAL start-up parameter through the Oracle WebLogic Server Administration Console.
Change -Dfile.encoding=iso-8859-1 to -Dfile.encoding=utf8 in the setDomainEnv.sh file (Located at MW_HOME/user_projects/domains/DomainName/bin).
For more information, see the 403179.1 Metalink note.