Import Portals

With Portal Server-Manage All or Manage Configuration permission, you can import portals from a portal archive through WebCenter Portal Administration.

To import one or more portals from a .par file:

1. Specify the location of your portal archive (.par file). Select one of:

   • Look on My Computer - Enter the location in the text box. Alternatively, click Browse to locate the directory on your local file system where the .par file is stored.

   • Look on WebCenter Portal Server - Enter the path on the server where WebCenter Portal is deployed, including the archive filename, in the text box. For example, /tmp/MyPortalExport.par. You can specify any shared location accessible from WebCenter Portal.

2. Click Browse Archive to review the content available for import.

   The names of all the portals in the specified archive display in the table. The Type column indicates when there is a difference between the portals in the archive and those that exist on the target:

   • New - A portal with this name does not exist on the target. On import, a new portal is created.

   • Replace - A portal with this name and the same GUID exists on the target. The existing portal is deleted on import and replaced with the version in the portal archive.

   • Conflict - A portal with this name exists on the target but the portal on the target has a different GUID to the portal you are trying to import. Or similarly, this portal has the same GUID as one of the portals in the target but the portal names do not match.

     If the import process detects a conflict between the portals you are trying to import and those which exist on the target, you must resolve the issue. For example, if the conflict is due to matching names but different GUIDs you could either change the name of the source portal and create a new export archive, or rename the conflicting portal in the target application and import the same archive.

3. Set import options as required.

   Field	Description
   Include Shared Assets	Select to import shared assets, like skin and page templates, used in the portal.
   Include Portal Content	(This option is displayed only if the content repository is WebCenter Content Server and the archive specified includes a content folder for one or more portals.) Select to import all content folders included in the archive. Folders that exist on the target are overwritten on import. Deselect this option to exclude portal content folders (if any). This option is useful when migrating between stage and production environments where test content is no longer required. Note: Portal archives that contain large content folders may exceed the maximum upload size for files (2 GB by default). Oracle recommends that you use the importWebCenterPortals WLST command to import any portal archive that exceeds the current upload size.

4. Click Import.

   • If you try to import portals that exist in the target WebCenter Portal application, the Confirm Replace Portal dialog displays. You must confirm whether you want to overwrite the existing portals.

     To delete existing portals and replace them with imported versions, click Yes. Click No to cancel the import process.

   • If the import process detects a conflict between the portals you are trying to import and those which exist on the target, a message displays to help you resolve the issue. For example, conflict messages display if a portal on the target application has the same name but a different GUID to a portal you are trying to import. In this instance you could change the name of the source portal and create a new export archive, or rename the conflicting portal in the target application and import the same archive.

   • If the portal archive exceeds the maximum upload size for files (2 GB by default) you cannot import the portals. Oracle recommends that you use the importWebCenterPortals WLST command to import any portal archive that exceeds the current upload size.

   Note:

   • If you are working with legacy portals with assets that store artifacts in MDS, Oracle recommends that you relocate all dependent artifacts from MDS to your content server. If you choose not to move artifacts stored in MDS and do not include MDS content within the asset archive, you can use MDS WLST commands exportMetadata/importMetadata to move the MDS content another time. For example:

     exportMetadata(application='webcenter', server='WC_Portal',
      toLocation='/tmp/content',
      docs='/oracle/webcenter/siteresources/scopedMD/shared/**')
     
     importMetadata(application='webcenter', server='WC_Portal',
      fromLocation='/tmp/content',
      docs='/oracle/webcenter/siteresources/scopedMD/shared/**')

5. In the information message, click Yes to confirm that you want to import the portals.

   An information message displays when all portals import successfully.

6. Click Close.