Import Portal Templates Pane

With the default permissions of the Application Specialist role, or the Portal Templates: Manage All permission, you can import portal templates from a portal archive (.par file) into WebCenter Portal.

On import, all portal templates included in the archive are re-created. If a portal template exists, then it is deleted and replaced. If a portal template does not exist, then it is created.

Newly imported portal templates are not immediately available for general use. You must publish the imported templates to make them available to everyone.

Portal templates that use document services (files, folders, wikis, blogs) automatically own a content folder on WebCenter Portal's back-end content repository. The content folder is included in the portal template archive in 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/pages referenced by the portal template that is stored outside the template's content folder, for example, information displayed through Content Presenter that is not stored in the template's content folder. Similarly, template archives do not include shared assets. You must migrate all dependent content to the target so it is accessible to the imported template. If you do not move all dependent content to the target server it will be missing when you import the portal template.

To import one or more portal templates from a .par file:

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

   • Look On My Computer. Click in the input field or click Browse to open the File Upload dialog and navigate to the .par file on your local file system.

   • Look On WebCenter Portal Server. Enter the path on the server where WebCenter Portal is deployed, including the archive file name. For example, /tmp/MyPortalTemplateExport.par. You can specify any shared location that is accessible from WebCenter Portal.

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

   The names of all the WebCenter Portal templates in the specified archive display in the table. The Type column indicates when there is a conflict between the portal templates in the archive and those which exist on the target:

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

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

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

     If the import process detects a conflict between the portal templates 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 template and create a new export archive, or rename the conflicting portal template in the target application and import the same archive.

3. Click Import.
4. If you are replacing an existing portal template, click Yes to confirm the overwrite.

   Any content in the portal template archive will be included in the import. An information message displays when all templates import successfully.

5. Monitor progress in the Import Portal Templates dialog. When the import is complete, click Close.
6. To publish the portal template to make it available to all WebCenter Portal users, select the template name, click the Actions menu, and select Make Public.

   The template is published and displays on the Portal Templates page in the Home portal for all users.