Export Portal Templates Pane

With the default permissions of the Application Specialist role, or the Portal Templates: Manage All permission, you can export portal templates from WebCenter Portal to a portal archive (.par file) and deploy them on another portal server. Built-in templates cannot be exported.

While export and import utilities are primarily used to move information between WebCenter Portal instances, the portal template export feature is also useful as a backup service, and for sharing and exchanging templates with others.

Portal templates can contain pages, documents, lists, and security information such as custom roles and member details.

When you export a portal template, all this information is packaged in a portal data file (.pdr). The PDR file contains a metadata archive (.mar file) and a single XML file containing security policy information for the template. The export process packages up one or more template .pdr files to an archive that you can save to your local file system or to a remote server file system.

As template data is included in the portal template archive, you do not need to manually migrate any template data to the target server.

Templates that use document tools (files, folders, wikis, blogs) automatically own a content folder on WebCenter Portal’s back-end content repository. When you use WebCenter Portal to export portal templates, the content stored in this folder is automatically included in the portal template archive (.pdr) for easy deployment to another target server. The folder is added to a .zip file located at: transport.mar\oracle\webcenter\lifecycle\importexport\data\oracle-webcenter-doclib\docsexport.zip

Note:

Portal template archives do not include web content or pages referenced by the portal template that is stored at any other location, for example, information displayed through Content Presenter that is not stored in the portal template's content folder. Only the folder assigned to the portal template on WebCenter Portal's back-end content repository is included with the portal template archive.

You can save export archives to your local file system or to a remote server file system.

To export one or more portals templates from WebCenter Portal:

1. If you want to exclude a portal template, click its Delete icon.
2. Change the name of the portal archive (with the file extension .par) or accept the default name.

   The default file name for the portal archive includes a random number to ensure uniqueness: webcenter_random_number.par

3. Click Export.

   Note:

   • Including content folders increases the size of the portal template archive. If you are exporting a large number of portal templates or large content folders, take care that your archive does not exceed the maximum upload size for files (2 GB by default). If necessary, you can ask your system administrator to increase this setting.

   • If you are managing legacy portal templates with assets that store artifacts in MDS, Oracle recommends that you relocate all dependent artifacts from MDS to your content repository. If you choose not to move artifacts stored in MDS, 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/**')Notes

4. Monitor progress in the Export Portal Templates dialog.
5. When the export process is complete, specify a location for the export archive (.par). Select one of:

   • Download. Saves the export .par file to your local file system.

     Your browser downloads and save the archive locally. The actual download location depends on your browser set up.

   • Save to Server. Saves the export .par file to a server location. For example, /tmp. Ensure that there are write permissions on the server directory that you specify.

     After clicking Save to Server, enter the Server Location and then click Save.

6. Click Close.

The export archive (.par) is saved to the specified location.