Working_with_Oracle_PDK-Java_Portlets.pdf

8/13/2019 Working_with_Oracle_PDK-Java_Portlets.pdf

1/23

Enterprise PeopleTools 8.47PeopleBook: Internet Technology,Working with Oracle PDK-JavaPortlets

10/13/2005


2/23

Enterprise PeopleTools 8.47 PeopleBook: Internet Technology, Working with Oracle PDK-Java PortletsSKU tprt_pdk_10132005

Copyright 2005, Oracle. All rights reserved.

The Programs (which include both the software and documentation) contain proprietary information; they areprovided under a license agreement containing restrictions on use and disclosure and are also protected by copyright,patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the

Programs, except to the extent required to obtain interoperability with other independently created software or asspecified by law, is prohibited.

The information contained in this document is subject to change without notice. If you find any problems in thedocumentation, please report them to us in writing. This document is not warranted to be error-free. Except as may

be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced ortransmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf ofthe United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Governmentcustomers are commercial computer software or commercial technical data pursuant to the applicable Federal

Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure,modification, and adaptation of the Programs, including documentation and technical data, shall be subject tothe licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, theadditional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987).Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerousapplications. It shall be the licensees responsibility to take all appropriate fail-safe, backup, redundancy and othermeasures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaimliability for any damages caused by such use of the Programs.

The Programs may provide links to Web sites and access to content, products, and services from third parties.Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risksassociated with the use of such content. If you choose to purchase any products or services from a third party, therelationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party

products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery ofproducts or services and warranty obligations related to purchased products or services. Oracle is not responsible forany loss or damage of any sort that you may incur from dealing with any third party.

Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates.Other names may be trademarks of their respective owners.Open Source Disclosure

Oracle takes no responsibility for its use or distribution of any open source or shareware software or documentationand disclaims any and all liability or damages resulting from use of said software or documentation. The followingopen source software may be used in Oracles PeopleSoft products and the following disclaimers are provided.

Apache Software Foundation

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright

1999-2000. The Apache Software Foundation. All rights reserved.


3/23

THIS SOFTWARE IS PROVIDED AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHESOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT

LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, ORPROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF SUCH DAMAGE.

OpenSSL

Copyright 1998-2003 The OpenSSL Project. All rights reserved.

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit(http://www.openssl.org/).

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT AS IS AND ANY EXPRESSED ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT

SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, ORPROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF SUCH DAMAGE.

SSLeay

Copyright 1995-1998 Eric Young. All rights reserved.

This product includes cryptographic software written by Eric Young ([email protected]). This productincludes software written by Tim Hudson ([email protected]). Copyright 1995-1998 Eric Young. Allrights reserved. THIS SOFTWARE IS PROVIDED BY ERIC YOUNG AS IS AND ANY EXPRESS OR

IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENTSHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.

Loki Library

Copyright 2001 by Andrei Alexandrescu. This code accompanies the book: Alexandrescu, Andrei. Modern C++Design: Generic Programming and Design Patterns Applied. Copyright 2001 Addison-Wesley. Permission to

use, copy, modify, distribute and sell this software for any purpose is hereby granted without fee, provided that theabove copyright notice appear in all copies and that both that copyright notice and this permission notice appear insupporting documentation.

Helma Project


4/23

Copyright 1999-2004 Helma Project. All rights reserved. THIS SOFTWARE IS PROVIDED AS ISAND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THEIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE HELMA PROJECT OR ITS CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON

ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Helma includes third party software released under different specific license terms. See the licenses directory in theHelma distribution for a list of these license.

Sarissa

Copyright 2004 Manos Batsis.

This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser GeneralPublic License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option)any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even theimplied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser

General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this library; if not, write tothe Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.


5/23

Contents

Chapter 1

Implementing PeopleSoft Portlets on Oracle Portal Pages................................. . . . . . . . . 1

Implementation Overview..... ..... ..... ..... ..... ..... ...... ..... ..... ..... ..... ..... ...... ..... ..... ..... .... . . . . . . . 1

Glossary of Terms..... ...... ..... ..... ...... ...... ..... ...... ..... ..... ...... ..... ..... ...... ..... ...... ..... .. . . . . . . . . 1

Installing the PeopleSoft Provider to OC4J.................................................................. . . . . . . . 2

Page Used to Reference the Oracle Portal Web Provider URL...................................... . . . . . . . . 2

Running the Setup Program for the PeopleSoft Pure Internet Architecture........................ . . . . . . . . 2

Referencing the Oracle Portal Web Provider URL... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ... . . . . . . . 4

Registering PSProviders Within the Oracle Portal.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . . . . . . 5Accessing the Register Provider Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . 5

Entering Provider Information.............................................................................. . . . . . . . 6

Defining Connection Information... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... .. . . . . . . . 6

Configuring Context Parameters.............................................................................. . . . . . . . 8

Configuring Single Signon Between the Oracle Portal and PSProvider.............................. . . . . . . . 8

Configuring Portlet Timeout................................................................................ . . . . . . . 9

Setting Up Debug Options.................................................................................. . . . . . . . 9

Chapter 2Adding PeopleSoft Portlets to Oracle Portal Pages.......................................... . . . . . . . .11

Adding PeopleSoft Portlets to an Oracle Portal Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .11

Displaying PSProvider Portlets on an Oracle Portal Page............................................. . . . . . . .11

Unhiding PSProvider Portlets.............................................................................. . . . . . . .12

Adding PSPortlets to an Oracle Portal Page at Design-Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .13

Adding PSProvider Portlets at Design-Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .13

Unhiding PSPortlets...... ...... ...... ..... ...... ...... ...... ..... ...... ...... ...... ...... ..... ...... ...... .. . . . . . . .14

Creating Pagelet Wizard Pagelets For PDK-Java Production............................................. . . . . . . .14

Pages Used to Create Pagelet Wizard Pagelets....................................................... . . . . . . . .15

Creating Pagelets For PDK-Java Production............................................................ . . . . . . .15

Using a PeopleSoft Portlet Within an Oracle Portal Page.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . . . . . . .16

PeopleSoft Proprietary and Confidential


6/23

Contents

vi PeopleSoft Proprietary and Confidential


7/23

CHAPTER1

Implementing PeopleSoft Portlets onOracle Portal Pages

This chapter provides an implementation overview, a glossary of terms, and discusses how to:

Install the PeopleSoft Provider (PSProvider) to OC4J.

Register the PSProvider in the Oracle Portal.

Configure context parameters.

Note. In the planning phase of the implementation, take advantage of all Oracle and PeopleSoft sources ofinformation, including installation guides, hardware and software guides, and PeopleBooks.

Implementation OverviewThe following basic procedure is used to add PeopleSoft portlets to Oracle Portal pages:

1. Install the PeopleSoft Provider for the corresponding Oracle (OC4J) web application server.

2. Navigate through the Pagelet Wizard to create and publish WSRP produced portlets on the PeopleSoftsystem where the PeopleSoft Provider is installed and configured.

Note. This will also produce PDK-Java supported portlets.

3. Deploy the PeopleSoft application through any firewalls so that it is accessible by clients of the OraclePortal.

Note. If single signon is to be configured, the PeopleSoft installation must be within the same cookiedomain as the Oracle Portal. This enables links to PeopleSoft content through a Navigation Collection

pagelet to open using the single signon credentials.

4. Register the PeopleSoft Provider in the Oracle Portal using standard Oracle Portal navigation.

5. Design an Oracle Portal page that includes a portlet (PSPortlet) provided by the registered PeopleSoftProvider.

Glossary of Terms

OC4J Oracle web application server.

PDK-Java Java Portlet Development Kit



8/23

Implementing PeopleSoft Portlets on Oracle Portal Pages Chapter 1

PS PeopleSoft

PWP Pagelet Wizard Pagelet

PSProvider The PeopleSoft PDK-Java Web Provider.

PSPortlet A portlet provided by the PSProvider.

WSRP Web Service for Remote Portlets specification.

Installing the PeopleSoft Provider to OC4JThis section discusses how to:

Run the setup program for the PeopleSoft Pure Internet Architecture.

Reference the Oracle Portal Web Provider URL.

Note. PDK-Java portlets will only be provided from OC4J PIA installations.

See Also

the PeopleTools 8.47 installation guide for your database platform.

Page Used to Reference the Oracle Portal Web Provider URL

Page Name Object Name Navigation Usage

Producer Offered Portlets PT_WSRP_PRO_PORT PeopleTools, Portal, WSRPProduction, ProducerOffered Portlets

Reference Oracle Portal WebProvider URL.

Running the Setup Program for the PeopleSoftPure Internet Architecture

In order for the Oracle Portal to discover PeopleSoft Provider portlets, the PeopleSoft Provider (PSProvider)must first be installed for the OC4J web server. This is accomplished using the setup program for thePeopleSoft Pure Internet Architecture. Complete the setup by including the following steps:

To run the setup program:

1. Launch %PS_HOME%\setup\mpinternet\setup.exe.

2. Select your %PS_HOME% installation directory.

3. In Step 2, select the server optionOracle Application Server Containers for J2EE (OC4J).

Note. When the PeopleSoft Pure Internet Architecture setup is complete, the PDK-Java portlet containeris installed by default for the OC4J installation.

The following shows the new Oracle Application Server Containers for J2EE (OC4J)server option:

2 PeopleSoft Proprietary and Confidential


9/23

Chapter 1 Implementing PeopleSoft Portlets on Oracle Portal Page

Setup Program - Step 2

The following step only appears when theOracle Application Server Containers for J2EE (OC4J) optionhas been selected:



10/23


Setup Program - Step 3

Referencing the Oracle Portal Web Provider URL

Access the Producer Offered Portlets page.



11/23


Producer Offered Portlets page

The Oracle Portal Web Provider URL for the PSProvider is displayed for reference on the PeopleSoft WSRPProduction - Producer Offered Portlets page.

Registering PSProviders Within the Oracle PortalThis section discusses how to:

Access the Register Provider wizard.

Enter provider information.

Define connection information.

The oracle Portal Administrator registers the PSProviders within the Oracle Portal using the existing RegisterProvider wizard. When you have navigated through all of the wizard pages and the registration is complete,click Finish.

Note. The procedures described in this section reside within the context of the Oracle Portal.

See Also

Oracle Developers Guide, Registering and Viewing Your Portlet.

Accessing the Register Provider Wizard

Logon to the Oracle Portal as the Oracle Portal Administrator.



12/23


Note. You can access the Register Provider wizard from either the Navigator link or the Administer page.

To access the Register Provider wizard from the Navigator link:

1. Click the Navigator link.

2. Navigate to the Provider page.

3. Click the Registered Providers link from the list of provider types.

4. Click theRegister New... Provider link displayed above the list of registered providers to begin theRegister Provider wizard.

To access the register Provider wizard from the Administer page:

1. Navigate to the Administer page.

2. Select the Portlets tab on the Administer page.

3. Locate the Remote Provider portlet.

4. Select the Register a Provider link within the Remote Provider portlet to begin the Register Provider wizard.

Entering Provider Information

Use one of the above procedures to navigate to the Register Provider wizard

Register Provider wizard - Register Provider page

Display Name Enter the name of the provider that displays during runtime when you addportlets to your page.

Implementation Style SelectWeb.

Defining Connection Information

Click Next to access the Define Connection page.



13/23


Register Provider wizard - General Properties page



14/23


General Properties

Enter information to specify the URL for the Web provider and configure its communication settings.

URL Enter the Oracle Portal Web Provider URL of the PSProvider.

See Referencing the Oracle Portal Web Provider URL.

Web provider in samecookie domain as the portal

Clear this check box. Do not select the check box even if the Oracle Portal andPeopleSoft Provider are in the same cookie domain.

The user has the sameidentity inthe Webproviders application as inthe Single Sign-On identity

Select to specify how the users identity will be set by the Portal whencommunicating with the Web provider. (Default).

User/Session Information

Enter information to specify the type of information the provider requires.

User Select to specify the frequency by which the call to the provider for sessioninitialization is performed. (Default)

Login Frequency SelectOnce Per User Session.

Configuring Context ParametersThis section discusses how to:

Configure single signon between the Oracle portal and PSProvider.

Configure portlet timeout.

Set up debug options.

Configuring Single Signon Between the OraclePortal and PSProvider

To implement single signon you must follow these rules:

The Oracle Portal web server host and the host supplying the PSProvider MUST be in the same cookiedomain. Therefore, they must have a common DNS suffix in their qualified DNS names. For example:

Oracle Portal web server: portal.mycompany.com

PSProvider server: psprovider.mycompany.com

Note. The PeopleSoft Authentication Domain can be specified initially during installation or configuredlater using the PeopleSoft Web Profile.

If you are implementing Oracle as a partner application, set the EnableJPDKSingleSignoncontext parametertotrue.



15/23


This context parameter is in the /pspc/WEB-INF/web.xml file in the PeopleSoft domain on the OracleApplication Server that is acting as the Web Provider for the Oracle Portal. When you set this parameter totrue(default isfalse), the portlet container responds to single signon information coming from the OraclePortal, and therefore does not require a separate PeopleSoft login per PDK-Java portlet. This parameterapplies only to single signon configuration for PDK-Java portlets within the Oracle Portal and does not affecWSRP technology. Here is the relevant section from the web.xml file within the domain:

EnableJPDKSingleSignon

false

See PeopleBook Update "Implementing Single Signon."

If a proxy server is positioned between the Oracle Portal web server and the PSProvider server, it mustalso reside inthe same cookie domain.

When registering the PSProvider, select the Web provider in same cookie domain as the portal check box onthe Define Connection page.

Note. This permits cookie transfer from the PSProvider through the Oracle Portal to the users browser.

See Also

PeopleTools 8.46 Internet Technology PeopleBook, Configuring the Portal Environment, ConfiguringWeb Profiles.

the PeopleTools 8.47 Installation Guide for your database platform.

Registering PSProviders Within the Oracle Portal, Defining Connection Information.

Configuring Portlet Timeout

To set up the time, in seconds, that the Oracle Portal waits for the PeopleSoft portlet to timeout, edit theJPDKPortletTimeoutcontext parameter. This parameter is defined in the pspc web.xml file.

Here is the relevant section from the web.xml file:

JPDKPortletTimeout

4000

Setting Up Debug Options

This table lists the two context parameters in the pspc web.xml file that are provided to assist in debugging:



16/23


Context Parameter Usage

UseJPDKDebugLogLevel Set to true to enable debug-level logging.

JPDKRunMode Set to DEBUG to enable debugging mode. Whenthis feature is enabled, exceptions and error reports

are output in HTML format to the Oracle Portal. If theJPDKRunModecontext parameter is set to any other value,the debugging feature is disabled.

Here is the relevant section from the web.xml file showing these context parameters:

UseJPDKDebugLogLevel

false

JPDKRunMode

Log Files

Log files are stored in the directory pspc/WEB-INF/providers and named JPDKlog.n (where n is 02). Theinformation included in the log files depends on how you set up the UseJPDKDebugLogLevelcontext

parameter:

IfUseJPDKDebugLogLevelis set tofalse, the log files contain exceptions reports.

IfUseJPDKDebugLogLevelis set to true, the log files contain exception reports and application server dialogdetails including requests from and responses to the PeopleSoft application server.



17/23

CHAPTER2

Adding PeopleSoft Portlets to Oracle Portal Pages

This chapter discusses how to:

Add PeopleSoft portlets to an Oracle Portal page.

Add PSPortlets to an Oracle Portal page at design-time.

Create Pagelet Wizard pagelets for PDK-Java production.

Use a PeopleSoft portlet within an Oracle Portal page.

Adding PeopleSoft Portlets to an Oracle Portal PageThis section discusses how to:

Display PSProvider portlets on an Oracle Portal page.

Unhide PSProvider portlets.

Note. Procedures discussed in this section are performed completely within the context of the Oracle Portal.

Displaying PSProvider Portlets on an Oracle Portal PageTo display PSProvider portlets on an Oracle Portal page, logon to the Oracle Portal as an end user, thennavigate to the page where you will add the PSProvider portlet:

Portal Builder page

1. Select Customize (located in the upper right corner), to go to the Customize Page page.

PeopleSoft Proprietary and Confidential 1


18/23

Adding PeopleSoft Portlets to Oracle Portal Pages Chapter 2

Note. Not all pages will enable the customize feature. Please contact your Oracle Portal Administrator ifthe feature is disabled for your page.

2. Locate the page region to add the portlet and select its Add Portlet icon to go to the Add Portlets toRegion page.

Add Portlet icon

The Portlet repository appears on the lower left.

3. Select the link for the corresponding portlet provider category.

Use Search if you know the name of the portlet, but not its provider.

Note. If the Oracle Portal Administrator does not further categorize newly registered PSProviders in thePortlet Repository, the portlets will appear within the Portlet Staging Area category. This category isused for newly registered, uncategorized portlets.

4. Select the link for the PSProvider to view the list of available portlets.

Within the Portlet Staging Area provider category, the PSProvider will be listed under the Display Namegiven during Oracle Portal provider registration.

See Registering PSProviders within the Oracle Portal.

5. Select the link for one or more portlets to include them within the Selected Portlets area on the right.

All of the PSProvider PSPortlets will appear listed using the descriptive metadata provided by each.

Note. More than one instance of the same portlet can be added to each page region.

6. Rearrange the selected portlets within the region by using the Move Top, Move Up, Delete, Move Down,

and Move Bottom buttons.

7. Click OK to return to the Customize Page page.

The added portlets will be listed to appear within the page region.

8. Click Close to return to the original page and see the added portlets displayed within the page region.

Unhiding PSProvider Portlets

To unhide PSProvider portlets:

1. Logon to the Oracle Portal.

2. Navigate to the page where the PSProvider portlet will display.

3. Select the Customize link to go to the Customize Page page.

Note. Not all pages will enable the customize feature. Please contact your Oracle Portal Administrator ifthe feature is disabled for your page.

4. Locate the region to unhide the portlet.

Hidden portlets appear listed in grey text within the region.



19/23

Chapter 2 Adding PeopleSoft Portlets to Oracle Portal Page

5. Select the check box for the portlet you want to unhide.

6. Select the Show button.

7. Select OK to exit the Customize page and return to the original page.

The previously hidden portlet will now display.

Adding PSPortlets to an Oracle Portal Page at Design-TimeThis section discusses how to:

Add PSProvider portlets at design-time.

Unhide PSPortlets.

Note. Procedures discussed in this section are performed within the context of the Oracle Portal.

Adding PSProvider Portlets at Design-Time

To display PSProvider portlets on an Oracle Portal page at design-time:

1. Logon to the Oracle Portal as an Oracle Portal developer.

2. Select the Navigator link, (located in the upper right corner of the Oracle Portal homepage), to enterthe Navigator Portal.

3. Go to the Page Groups page.

4. Drill down to the page group that contains the page where the portlet will be added.

5. Locate the page to modify, then select its Edit link.

You are now in Page Editmode.6. Locate the page region to add the portlet and select its Add Portlet icon to go to the Add Portlets to

Region page.

Add Portlet icon

The Portlet repository appears on the lower left.

7. Select the link for the corresponding portlet provider category.

Use Search if you know the name of the portlet, but not its provider.

Note. If the Oracle Portal Administrator does not further categorize newly registered PSProviders in the

Portlet Repository, the portlets will appear within the Portlet Staging Area category. This category isused for newlyregistered, uncategorized portlets.

8. Select the link for the PSProvider to view the list of available portlets.

Within the Portlet Staging Area provider category, the PSProvider will be listed under the Display Namegiven during Oracle Portal provider registration.

See Registering PSProviders within the Oracle Portal.



20/23


9. Select the link for one or more portlets to include them within the Selected Portlets area on the right.

All of the PSProvider PSPortlets will appear listed using the descriptive metadata provided by each.

Note. More than one instance of the same portlet can be added to each page region.

10. Rearrange the selected portlets within the region by using the Move Top, Move Up, Delete, Move Down,and Move Bottom buttons.

11. Click OK to return to the Customize Page page.

The added portlets will be listed to appear within the page region.

12. Click Close to return to the original page and see the added portlets displayed within the page region.

Unhiding PSPortlets

To unhide PSPortlets:

1. Logon to the Oracle Portal as an Oracle Portal developer.

2. Enter the Portal Navigator by selecting the Navigator link in the upper right corner of the Oracle Portalhomepage.

3. Go to the Page Groups page.

4. Drill down to the page group that contains the page where the PSportlet is currently hidden.

5. Locate the page to modify and select its Edit link.

You are now in Page Edit mode.

6. Locate the portlet you want to unhide, then select that portlets Action icon to go to the Select Action page.

Action icon.

Note. If the portlet is not currently hidden, the Action icon will appearwithout the word Hidden.

7. Select the Show link.

The previously hidden portlet will now display.

Creating Pagelet Wizard Pagelets For PDK-Java ProductionThis section discusses how to create pagelets for PDK-Java production.



21/23


Pages Used to Create Pagelet Wizard Pagelets

Page Name Object Name Navigation Usage

Specify Pagelet Information PTPPB_WIZ_INFO PeopleTools, Portal, PageletWizard, Pagelet Wizard

Enter the information thatwill be used to identify andcategorize your pagelet.

Select Data Source PTPPB_WIZ_DATASRC Click Next on the SpecifyPagelet Information page.

Select the type of data andspecify thesource, whichcontains the data you wantdisplayed in your pagelet.

Specify Data Source

Parameters

PTPPB_WIZ_DATAPRMS Click Next on the SelectData Source page.

Specify the parameters andtheir association optionsspecific to the data sourceyou selected.

Select Display Format PTPPB_WIZ_DISPFRMT Click Next on the SpecifyData Source Parameterspage.

Select the format in whichyou want your pagelet datarendered.

Specify Display Options PTPPB_WIX_DISP_PST Click Next on the SelectDisplay Format page.

Specify visual optionsrelated to the display formatfor yourpagelet.

Specify Publishing Options PTPPB_WIZ_PUBOPT Click Next on the SpecifyDisplay Options page.

Specify how to publish yourpagelet.

Creating Pagelets For PDK-Java Production

To create a pagelet for PDK-Java production:

1. Sign on to the PeopleSoft Portal.

2. Navigate to the Pagelet Wizard.

3. Complete steps 1 thru 5 of the Pagelet Wizard as usual.

4. In step 6 of the Pagelet Wizard:

a. Selectthe WSRP Portlet checkbox.

b. Select the Enable Caching check box if caching of the remote portlet should be provided on the PeopleSoftPortal side.

5. Select Save to complete the wizard and produce a pagelet for both WSRP and PDK-Java.

6. View the WSRP pagelet content reference for your new pagelet by going to PeopleTools, Portal, Structureand Content, Portal Objects, WSRP Produced Portlets.

Go to the list of content references and click the Edit link associated with your pagelet



22/23


Pagelet Wizard - Specify Publishing Options page

Note. In PeopleSoft 8.47, when running on OC4J, all WSRP produced pagelets will automatically be exposedas PDK-Java produced pagelets to Oracle Portal via the PSProvider.

Using a PeopleSoft Portlet Within an Oracle Portal PageWhen using PSProvider portlets within an Oracle Portal page at runtime, the end user will either be directed

back to the PeopleSoft system through the PSProvider portlet or go directly to the PeopleSoft Portal, leavingthe Oracle Portal.

To bedirected back to the PeopleSoft system through the PSProvider portlet:



23/23


1. The Oracle Portal end user sees markup generated by the PWP portlets from the PeopleSoft system.

2. Clicking a link within the markup, or using the windowchromeof Oracle Portal, the end user is directedback to the PeopleSoft system through the PSProvider portlet. (Except when editing the portletspreferences).

3. The end user is presented the PeopleSoft Portal page without having to sign into the PeopleSoft Portal.

To go directly to the PeopleSoft Portal:

1. The Oracle Portal end user sees markup generated by the PWP portlets from the PeopleSoft system.

2. Clicking a link within the markup, or using the windowchromeof Oracle Portal, the end user goes directlyto the PeopleSoft Portal, leaving the Oracle Portal.

3. The end user is presented the PeopleSoft Portal page without having to sign into the PeopleSoft Portal.

Note. The PeopleSoft system generating the portlet markup (where the PSProvider resides) must be exposed tothe users of the Oracle Portal through any firewall. Specifically, the ports for /PORTAL web access mustbeopen to the clients of the Oracle Portal.

Working_with_Oracle_PDK-Java_Portlets.pdf

Documents

Transcript of Working_with_Oracle_PDK-Java_Portlets.pdf