Last Updated: | June 23, 2005 |
Status: | Production |
Version: | PDK Release 2 (10.1.2.0.2 and later) |
Introduction
Contents of pdksoftware.zip
Contents of the portalTools Directory
Contents of the libcommon Directory
Deploying the Portal Tools Application
Manually Deploying to a Stand-Alone OC4J Instance
Configuring and Registering the Providers under Portal Tools
Troubleshooting
Advanced Portal Tools Configurations
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.
Portal Tools is a collection of deployable OracleAS Portal tools
built on Oracle's PDK-Java technology.
By using Portal Tools, OracleAS Portal page designers can easily
combine any Web content and publish data from a variety of data sources
to a portal page.
This download includes the following Portal Tools:
Web Clipping is an OracleAS Portal technology that enables content reuse and aggregation. Using Web Clipping, Portal page designers can clip page content from an existing Web site and deliver it as a portlet to a Portal page.
OmniPortlet takes advantage of Portal's parameters and events. It provides wizards that enable Portal page designers to publish SQL, XML, Web Service, Spreadsheet, and existing Web page data directly to a Portal page.
This document contains installation and configuration information on the Portal Tools, and explains how to:
Install and configure the standalone OC4J Server needed to run the Portal Tools. (OC4J stands for "OracleAS Containers for J2EE". For more information about OC4J, refer to the Oracle Technology Network.)
Register the Portal Tools' providers with an OracleAS Portal instance.
Use the portlets contained within the pre-configured providers under the Portal Tools.
If you are upgrading from a previous version of Portal Tools, please see the upgrading.portaltools.html article in the portalTools directory.
Please consult the release notes for up-to-date list of new features, known issues as well as the minimum requirements to deploy the current release of Portal Tools.
Portal Tools is part of the OracleAS Portal Developer Kit (PDK). To install it, first unzip the pdksoftware.zip file into a directory located on the same machine where OC4J is installed. (These instructions will from now on refer to this directory as $unzip_directory.) Unzipping pdksoftware.zip to the $unzip_directory creates the following directory structure:
The portalTools directory is created under $unzip_directory/pdk and contains all the files required by the Portal Tools. The following files are included in this directory:
The libcommon directory is created under $unzip_directory/pdk and contains libraries shared by different components contained in pdksoftware.zip. Some of these libraries may already exist in your OC4J standalone instance installation. If so, you need to selectively copy them into your installation directory by ensuring you only update them if the supplied libraries are newer than your current installation.
Before deploying the Portal Tools application, you need to copy all the required library files to the OracleAS installation home.
copy $unzip_directory/pdk/portalTools/lib/jlib/* to $INSTALL_HOME/jlib/
copy $unzip_directory/pdk/portalTools/lib/portal/jlib/* to $INSTALL_HOME/portal/jlib/
copy $unzip_directory/pdk/portalTools/lib/ultrasearch/lib/* to $INSTALL_HOME/ultrasearch/lib/
copy $unzip_directory/pdk/portalTools/lib/wireless/lib/* to $INSTALL_HOME/wireless/lib/
copy $unzip_directory/pdk/portalTools/lib/bibeans/lib/* to $INSTALL_HOME/bibeans/lib/
copy $unzip_directory/pdk/libcommon/portal/jlib/* to $INSTALL_HOME/portal/jlib/
copy $unzip_directory/pdk/libcommon/webcache/jlib/* to $INSTALL_HOME/webcache/jlib/
copy $unzip_directory/pdk/libcommon/jlib/* to $INSTALL_HOME/jlib/
You only need to copy the following configuration files if they do not already exist in the $INSTALL_HOME.
copy $unzip_directory/pdk/portalTools/conf/portal/conf/* to $INSTALL_HOME/portal/conf/
Notes:
- $unzip_directory denotes the directory where you have unzipped the pdksoftware.zip. The libraries and the components to which they belong are described above.
- Create the target directories if they do not already exist.
- If installing on a standalone OC4J instance, $INSTALL_HOME is $OC4J_HOME (the root directory of your OC4J installation). You will find directories named "bin", "j2ee", "javacache", "jdbc" etc. under this directory.
- Only copy the above files if the supplied libraries are newer than your current installation. It is always good practice to back up existing files in your current installation prior to copying.
- The portaltools.jar file (in $INSTALL_HOME/portal/jlib/portaltools.jar) includes all the required jar files in its Manifest.MF file. This file is already referenced in the deployment library path of the portalTools.ear's orion-application.xml file so you need not include it again in your global application.xml or application specific orion-application.xml file.
This section assumes that you already have a standalone OC4J server installed and configured. If you do not have an OC4J installation, please install and configure it according to its installation instructions.
Portal Tools is now deployed. Please proceed to Configuring and Registering.
Now that Portal Tools is deployed, you should proceed to configure the individual providers before registering them with an OracleAS Portal instance. This can be done from the Portal Tools home page at the following URL:
http://<server>:<port>/portalTools
The home page lists the providers under Portal Tools. Click on each link to display the provider's test page and configure the provider.
Error you are most likely to encounter and possible solutions for them are listed below.
java.lang.OutOfMemoryError
or other "out of memory"
errors.
This section discusses the configurations that need to be performed to accommodate some of these more advanced topics.
This section is only applicable if you installed Portal Tools in an OracleAS installation. If you want to shut down OracleAS Web Cache completely, you must perform the following steps for Portal Tools to function properly:
For more information, refer to the Shutting down OracleAS Web Cache completely section of the OracleAS Portal Configuration Guide.
This section is only applicable if you installed Portal Tools in an
OracleAS
installation. While configuring a provider, you will come across steps
where you need to
edit the provider. The UI displayed when you click on the "Edit"
link, in default installation,
is not secured. This UI can be secured only for OC4J instance
deployment
in OracleAS. To secure the UI, follow the steps described in
the Securing the Edit
Provider UI
article.
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 |