Skip Headers

Oracle9iAS Portal Release Notes
Release 2 (9.0.2)

Part Number A96191-02
Go To Documentation Library
Home
Go To Table Of Contents
Contents

Go to previous page Go to next page

4
Exporting/Importing Issues and Workarounds

This section describes exporting and importing related issues and their workarounds for Oracle9iAS Portal.

4.1 Exporting/Importing Page URLs Correctly

By default, generated page URLs contain installation specific ID numbers that change when the object is exported. This causes broken links when pages are imported into a different site.

Here is an example of a URL generated for a page. If the page is imported on another site, this PAGEID will change.

http://my.portal.com/servlet/page?_pageid=47,49&_dad=portalr2&_schema=portalr2

The same page has this direct access URL:

http://my.portal.com/pls/portalr2/url/PAGE/HRPAGEGROUP/HRHOME/HRBENEFITS

This direct access URL still works on an imported page, providing the name of the page (e.g. HRBENEFITS) and the names of its parent pages (e.g. HRHOME, HRPAGEGROUP) do not change.

To find the direct access URL for a page, look at the page property sheet. A link to the property sheet can be displayed by adding a Property Sheet Smart Link item to the page.

You can also use a Page Link item type to create a link to a page. The Page Link item type dynamically generates the correct link at runtime.

Therefore, to ensure that links do not 'break' when pages are imported into a different site, always use Page Link item types or direct access URLs when creating links to pages.

For more information, refer to 'Direct Access URLs' and 'Page Links' in the Oracle9iAS Portal online help.

4.2 SSO Exporting/Importing Support Issues

SSO Export/Import does not provide support for external and partner applications, and password stores. Any object from these placed on a page will not work correctly when the page is migrated from one portal to another.

4.3 Exporting/Importing Portal Objects to Different OID Servers

Portal Export/Import expects the source (development) and the target (test, production) portal instances to point to the same OID server. If the source and target instances use different OID servers, you must export portal objects (page groups, database providers, etc.) without security.

Once you have successfully imported the portal objects, security privileges must be explicitly assigned on the target.

4.4 Exporting/Importing Pages Containing Custom Item Types

Portal Export/Import of pages overwrites all attribute values of items based on custom item types with custom attributes in the target portal. For this reason, you should create items (based on custom item types) on the source portal only, and migrate them to the target through the export-import process for that page.


Go to previous page Go to next page
Oracle
Copyright © 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Table Of Contents
Contents