Communities
|
Social Applications
Networks
Support
|
|
C-Level Executives
Other Roles
|
|
Support
Education
Partner
Other Tasks
|
Middleware
Application Server
| Last Updated: | January 23, 2006 | |
| Status: | Production | |
| Version: | PDK Release 10.1.2.0.2 |
Introduction
Contents of pdksoftware.zip
Contents of the jpdk/v2 Directory
Installing or Upgrading to This Version of PDK-Java
Manually Installing to a Stand-Alone OC4J Instance
Testing the Deployment
Registering the Sample Providers
Migrating PDK-Java Applications
Deploying Your Own Providers
Note: Starting with PDK 9.0.4.1.0, the PDK download is intended to be installed and deployed in a standalone OC4J instance only. If you plan to use PDK in an Oracle Application Server instance, you must get and install the corresponding Oracle Application Server releases or patchsets.
Welcome to the PDK-Java. The PDK-Java Framework includes the tools and documentation to build Web portlets. This download includes the PDK-Java Framework and Web Provider Samples to help you get started. You can use the PDK-Java framework to develop your own web providers and portlets. Please refer to the PDK documentation on Web Providers for more information.
This document is an installation and configuration guide for the PDK-Java Framework and samples. It explains how to
The PDK-Java and sample providers are part of the Portal Developers Kit (PDK). To begin the installation process you first need to unzip the file called pdksoftware.zip into a directory located on the same machine as your OC4J instance. (The remainder of the instructions contained in this document will refer to this directory to as $unzip_directory.) Unzipping pdksoftware.zip in the $unzip_directory creates the following directory structure:
pdk
The jpdk/v2 directory is created under $unzip_directory/pdk and contains all the files required by the PDK-Java. The following files are included in this directory:
Before proceeding, note the minimum supported application server versions stated in the release notes. If you want to upgrade PDK-Java applications currently deployed on older application server versions, you will need to install PDK-Java on one of the supported application server versions first, and then proceed to migrate the applications from the older application server. See the document Migrating Applications to PDK-Java Release 9.0.4 and later for details on how to do this.
Note: If your upgraded portlets had previously been invoked in Edit Defaults mode by users logged in with multiple Portal session languages, you may have to use the Preference Store Migration Utility to ensure that the appropriate locale specific portlet preferences data is visible to your upgraded portlets. See the release notes for more information on the Preference Store Migration Utility.
This section assumes that you already have a stand-alone OC4J server installed and configured. If you do not have an OC4J installation, please install and configure it according to its installation instructions.
java -jar admin.jar ormi://localhost admin $admin_password -shutdown
Notes:
$OC4J_HOME
is the root directory of your OC4J installation. You will find directories named "
bin", "
j2ee", "
javacache", "
jdbc" etc. under this directory.
$OC4J_HOME/j2ee/home/config/application.xml
Dependent library references:
<library path="../../../portal/jlib/pdkjava.jar"/>
<library path="../../../portal/jlib/portaltools.jar"/>
<library path="../../../portal/jlib/ptlshare.jar"/>
<library path="../../../portal/jlib/tidy.jar"/>
<library path="../../../jlib/ldapjclnt9.jar"/>
<library path="../../../jlib/regexp.jar"/>
<library path="../../../jlib/share.jar"/>
<library path="../../../jlib/uix2.jar"/>
<library path="../../../jlib/ojmisc.jar"/>
<library path="../../../webcache/jlib/jawc.jar"/>
<library path="../../home/jazn.jar"/>
Note: if the PDK-Java sample application (typically called "jpdk") is already installed in your target OC4J instance or you are not interested in running any of the sample portlets, you may skip this section. If you want to replace an existing PDK-Java enterprise application in your target OC4J instance, you should proceed with extreme caution, as there may be important meta data and user customization data stored under the $OC4J_HOME/j2ee/home/applications/jpdk/jpdk/WEB-INF directory. For this reason, it is recommended that you avoid taking this step in a production environment and you always deploy to a new J2EE application with a unique name (e.g. "jpdk1") rather than redeploying on top of an existing application. You should only undeploy an old jpdk enterprise application when you are sure that all meta data has been safely transported to the new one.
where:
- $admin_password is the OC4J administration password you set on installation
- $application_name is the unique name that should be given to the application for administrative purposes. Typically this is "jpdk", but see the above note.
The PDK-Java v2 and Sample Providers are now deployed. Please proceed to Testing the Deployment
The PDK-Java v2 Sample Providers application is now deployed. To test the application, access the "sample" provider's test page at the following URL:
Access the provider test page using the following URL:
http://$host:$port/jpdk/providers/sample
where:
This page lists the portlets that are included with the provider that has a service name of "sample". The test pages of other providers can be accessed using a similar URL. Simply replace "sample" with the service name of the provider.
The service names of the other providers included with the PDK-Java v2 Sample Providers application are:
The service names of the URL Services sample providers are:
The majority of the providers require additional configuration of some kind. For each of these providers there is an installation document detailing the additional configuration steps and instructions for using the provider. The installation documents can be found in $unzip_directory/pdk/jpdk/v2/doc/{service name}
After deploying the PDK-Java Sample Providers, you must register the provider with OracleAS Portal before adding the sample portlet(s) to a page.
Note: When registering a new provider with OracleAS Portal, only the user who registered the provider has privileges to see the provider/portlets. If necessary, go to the Folder with the name of the provider within the Portlet Repository content area and update the provider privileges as required.
Display the contents of the Portlet Repository and review the sample portlets.
Add any of the sample portlets listed under the Provider called "SampleWebProvider" to a Portal page.
Please refer to OracleAS Portal online documentation for more information on adding portlets to a page.
You have now successfully installed and setup the Web Provider Samples.
Review the article Packaging and Deploying Your Provider for detailed instructions on how to package and deploy your own providers
For detailed information regarding creating new providers, refer to the Portal Developer's Guide on OTN.
| Revision History: |
|
| Oracle Corporation
World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065, USA http://www.oracle.com/ |
Worldwide Inquiries:
1-800-ORACLE1 Fax 650.506.7200 |
Copyright and Corporate Info |
</xmp>
</body>
</td></tr>
<tr>
<td>
</td></tr>
</table></td>
</tr>
</table>
<table><tr>
<td><div><table>
<tr><td><div><div>
<table>
<tr>
<td>
<table><tr>
<td>
</td></tr>
</table></td>
<td>
<table><tr>
<td>
<table><tr><td>
E-mail this page
</td>
</tr><tr><td>
Printer
View
</td></tr></table>
</td></tr>
</table><table><tr>
<td>
<div>
</div>
<table>
<tbody><tr>
<td>
</td>
<td>
About
Oracle
|
Oracle and Sun
|
|
Careers
|
Contact
Us
|
Site Maps
|
Legal
Notices
|
Terms of Use
|
Privacy</td>
</tr>
<tr><td>
</td></tr>
</tbody></table>
</td></tr>
</table></td>
<td>
<table><tr>
<td>
</td></tr>
</table></td>
</tr>
</table>
</div>
</div></td></tr>
</table>
</div></td></tr>
</table><table><tr>
<td>
<meta>
<meta>
<meta>
</td></tr>
</table></td>
<td>
<table><tr>
<td>
</td></tr>
</table></td>
</tr>
</table>
</td>
</tr>
</table>
</body>
