This chapter includes the following sections:
To perform the tasks in this chapter, you need the permissions granted to the
Application Specialist role (or the
Portal Templates-Manage All permission). Note that the
Portal Creator role does not have this permission by default. Users with the permission
Manage Portal Templates can view and manage all portal templates, including private portal templates created by other users, and import or export portal templates and publish portal template for others to use.
Users with the permission
Portal Templates-Create Portal Templates can create and work with portal templates from the Home portal that they have created and have permissions to work with. For more information about creating a new portal template from the Home portal, rename, see Working with Portal Templates.
For more information about permissions, see About Roles and Permissions for a Portal.
When creating a portal, users can base it on one of the out-of-the-box portal templates, their own custom portal template, or a published portal template created by others. Portal templates provide a consistent look and feel and an efficient way to get started creating a portal that is configured exactly as required by an organization. For more information, see About Portal Templates.
Application specialists (or any user with the
Portal Templates-Manage All permission) can manage each portal template from the application-level Portal Templates page (Figure 57-1). You can see which portal templates are currently available and delete portal templates when they are no longer required. You can also publish templates—making them available to everyone—or restrict them to private use only.
It is important to keep the portal template list up to date and valid. Anyone who creates a portal will see public templates as well as their own private templates.
The Portal Templates page also provides import and export options. For more information, see Importing and Exporting Portal Templates.
On the application-level Portal Templates page, you can quickly see who created each portal template, and the date on which it was created. The Actions menu offers additional options for deleting portal templates, and you can publish and hide templates from here, too.
To see a list of every portal template in WebCenter Portal, together with their description, creator, and other useful information:
Figure 57-1 Portals Administration - Portal Templates Page
This section describes how to import and export portal templates:
System administrators can also import and export portals and portal templates using WLST commands. To find out more about these WLST commands and how to migrate the back-end data associated with portals, see Deploying Portals, Templates, Assets, and Extensions in Administering Oracle WebCenter Portal.
Application specialists (and other users with
Portal Templates-Manage All permission) 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. See Publishing and Hiding Portal Templates.
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:
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.
An option to exclude the content folder is available using the
importWebCenterPortals WLST command, described in Importing Portal Templates from an Archive Using WLST in Administering Oracle WebCenter
To import one or more portal templates from a
The Import Portal Templates pane opens (Figure 57-2).
Figure 57-2 Importing Portal Templates
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.
Figure 57-3 Importing Portal Templates
The names of all the 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.
Any content in the portal template archive will be included in the import. An information message displays when all templates import successfully.
Figure 57-4 Import Portal Templates Progress
Initially, newly imported portal templates are available only to you. To make them public, see Publishing and Hiding Portal Templates.
Application specialists (and other users with the
Portal Templates-Manage All permission) can export portal templates from WebCenter Portal to a portal archive (
.par file) and deploy them on another portal server. Out-of-the-box 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, discussions, 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:
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.
You cannot export portals and portal templates into a single archive. Exporting portals is a separate process that can be performed only by a system administrator, as described in Importing One or More Portals from an Archive in Administering Oracle WebCenter Portal.
To export one or more portals templates from WebCenter Portal:
Ctrl+click rows to select more than one template.
The Export Portal Template dialog opens (Figure 57-5). All the portal templates that you select are listed.
If you want to exclude a portal template, click the Delete icon.
Figure 57-5 Exporting Portal Templates
.par) or accept the default name.
The default file name for the portal archive includes a random number to ensure uniqueness:
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, as described in Changing the Maximum File Upload Size in Administering Oracle WebCenter Portal.
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
When the export process is complete, specify a location for the export archive (
Figure 57-6 Export Portal Templates Progress
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.
The export archive (
.par) is saved to the specified location.
You cannot modify the out-of-the-box portal templates described in About Portal Templates, but any user with
Portal Templates-Create permission can create new portal templates for use by all users to create portals. This permission is granted to the
Application Specialist role by default.
To create a new portal template, you start by creating a portal based on an existing template (see Creating and Building a New Portal), and customize it according to your requirements. Then, you can create a new portal template based on the customized portal that you have developed. During the creation of a portal template, you can select to inherit the discussions, documents, lists, member information, roles, or pages from the source portal. The security settings, including Advanced Permissions (if applicable), for the source portal are also copied by the template.
When creating a new portal template, the template does not inherit announcements from the source portal.
As an application specialist (or any user with
Portal Templates-Manage All permission), you can publish any portal template for others to use; otherwise, it remains private and hidden from others.
Portal Creator role does not have default permissions to create or manage portal templates.
Users with the permissions of the default
Application Specialist role (or the application-level
Portal Templates-Manage All permission) can create portal templates to be made available at the application level, and import and export custom portal templates, including seeded data. For more information, see Managing All Portal Templates.
To create a portal template:
There must be at least one portal available to use as the basis for the new portal template. Otherwise, the Create action is not active.
Figure 57-7 Create a Portal Template Dialog: Setup Step
Portal template names can contain only alphanumeric characters and underscores (spaces and special characters, such as
#, are not allowed). The maximum allowable length is 200 characters. The following reserved keywords are not allowed as the full portal template name in either upper or lower case, or a combination of both—
webcenter spaces. These reserved words are allowable as part of a longer name (for example,
Figure 57-8 Create a Portal Template Dialog: Portals Step
The security settings of all pages in the new portal template default to Inherit Parent Security so that the pages in all portals created from the portal template initially inherit access settings from the permissions established for the portal.
Portal templates cannot copy announcements data from a parent portal.
List definitions are always copied; checking Lists in this step specifies that you want to copy the list data, too.
By default, all portal assets are copied. For a full list of portal assets, see About Assets. If you do not want your template to inherit all portal assets, you can later edit the portal template to remove individual assets (such as task flows or data controls) that you do not want to include.
If you select Members Info, the Roles Info option is also selected. By selecting Members Info, you are copying the portal members and custom roles from the portal you selected as the basis for the new template into the new template that you are creating.
If you select Roles Info and do not select Members Info, you are copying only the roles into your new template. Only the custom roles that are included in the portal you selected as the basis for the new template are copied into the new template.
If Advanced Permissions has been specified in the portal that is used to create a new portal template and you select both Members Info (and by default Roles Info) or only Roles Info when creating the portal template, then the specified advanced permissions are included in the portal template (and subsequently in a portal that is created using the template).
If custom page permissions are specified for roles or individual users in a portal that is later used to create a new portal template, then only the custom page permissions specified for the roles (not individual users) are included in the portal template (and subsequently in a portal that is created using the portal template).
Figure 57-9 Create a Portal Template Dialog: Content Step
The new portal template displays on the Portal Templates page. By default, the template is private, which means that other users will not see it on their personal Portal Templates page in the Home portal.
The template is published and displays on the Portal Templates page in the Home portal for all users.
To view information about a portal template:
The About Portal Template dialog opens (Figure 57-10).
Figure 57-10 About Portal Template Dialog
Name: Internal name of the portal template displayed in the portal URL. You cannot change the internal name of a portal template.
Display Name: Display name of the portal template. This name displays in places where the templates are available for selection, such as the Create a Portal dialog and the Portal Templates page. You cannot change the display name of an out-of-the-box portal template. To change the display name of a custom portal template that you create, see Renaming a Portal Template.
Internal ID: ID of the portal template, which other applications may use to reference this portal template.
Description: A description of the portal template, specified when creating the portal template. You cannot modify the description of a portal template, unless you rename the template, where you can enter a new description in the Rename dialog, as described in Renaming a Portal Template.
Created By: User name of the portal template creator.
Date Created: Date and time that the portal template was created.
Global search does not search portal assets, such as portal templates, page templates, resource catalogs, and so on. The Filter field on the Portal Templates page is useful for searching for portal template names or descriptions when your application includes a large number of portal templates.
Portal Creator role does not have default permissions to view or search for portal templates.
To search for a portal template by a string in the Name or Description:
Figure 57-11 Filter Icon
The Portal Templates page displays portal templates where the search string is found in the Name or Description.
Figure 57-12 Clear Filter Icon
To rename a portal template:
You can grant specific users and groups read-only or manage access to a portal template.
To set up access to a portal template:
The Set Template Access dialog opens (Figure 57-13).
Figure 57-13 Set Template Access Dialog
Click Add Users to open the Search Users dialog where you can select from a list of users or search for a user name.
Click Add Groups to open the Search Groups dialog where you can search for a user group.
For tips on searching for a user or group in the identity store, see Searching for a User or Group in the Identity Store.
Select the View check box to grant read-only access to the portal template.
Select the Manage check box to grant full access to the portal template.
While WebCenter Portal can accommodate any number of templates, a limited number of templates is sometimes more effective. On the application-level Portal Templates page, you can maintain the template list that is available to all users.
To publish a portal template, you need the application-level permission
Portal Templates-Manage All. The
Portal Creator role does not have default permissions to work with portal templates. Users with the
Portal Templates-Create permission can create, rename, hide, or delete a portal template, but cannot publish a template without the
Portal Templates-Manage All permission.
For more information about permissions, see About Roles and Permissions for a Portal.
To publish or hide portal templates (including the out-of-the-box templates):
Make Public to publish the template(s) to all WebCenter Portal users.
Remove Public Access to remove the template from the portal template lists in the Home portal for all users, except for the template creator and those users you have specifically been granted View or Manage access in the Set Template Access dialog (see Setting Up Access to a Portal Template).
If another user is in the process of creating a new portal (see Creating a New Portal), and you remove public access from the portal template selected for the portal before the user has completed creating the portal, the template becomes invalid for the portal and the user receives an error.
Out-of-the-box portal templates cannot be deleted. However, you can hide the out-of-the-box templates from everyone's view by making them private, as described in Publishing and Hiding Portal Templates.
Deleting a portal template does not affect the portals that were created using the portal template.
To delete one or more portal templates that are no longer required: