6 Administering a Portal

This chapter describes how to administer an individual portal, including how to take a portal offline, close it, or delete it.

This chapter includes the following topics:

Permissions:

To perform the tasks in this chapter, you must be a portal manager or member with Administration: Manage Security and Configuration or Administration: Manage Configuration permission in the portal.

Any user who accesses administration settings for a portal and does not have Manage permission will see only the settings available to their role and permissions.

Note that a user with a role that grants them permissions to create, edit, or publish a portal page, or even manage a portal, is not automatically allowed to view the portal. To view a portal, a user must be explicitly granted the portal-level permission Basic Services: View Pages and Content (standard permissions) or Pages: View Pages (advanced permissions).

For more information about permissions, see About Roles and Permissions for a Portal.

6.1 Accessing Portal Administration

The administration pages for a portal are available through the icons. Users will see only those portal administration icons available to their role and permissions. In general, you can administer a portal only if you are the portal manager or member with Manage Security and Configuration or Manage Configuration permission.

Figure 6-1 Portal Administration Page Icons

Description of Figure 6-1 follows
Description of "Figure 6-1 Portal Administration Page Icons"

The following table describes the portal administration pages accessed by each icon.

Table 6-1 Accessing Portal Administration

Icon Description

Security icon Security

Set security on the portal, such as access level, defining roles and permissions, and managing membership. See Administering Security in a Portal.

Overview icon General

Modify general settings for the portal, such as the title (name) and description, and to perform general actions on the portal, such as closing the portal, adding RSS feeds, or deleting the portal. See Administering General Settings and Actions for a Portal.

Settings icon Settings

Specify settings that define the look and feel of the portal. See Administering Look and Feel Settings for a Portal.

Assets icon Assets

Manage the assets for the portal, such as page templates, resource catalogs, skins, and more. SeeAdministering All Assets in a Portal No Variable.

Device Settings icon Device Settings

Use this page to manage devices and device groups in a device-enabled portal. See Viewing Device Groups for a Portal.

Tools and Services icon Tools and Services

Enable and disable tools and services operating in the portal, such as Announcements, Discussions, Documents, Events, and Lists. See Administering Tools and Services in a Portal.

Deploy icon Deploy

Use this page to deploy, redeploy, and propagate a portal to a target server. Note that you will only see this icon if you have a role that has Portal Server - Deploy permissions See Deploying and Propagating a Portal.

Access to portal administration is available through several paths, all of which display the General page and icons to access other administration pages. You can access portal administration in the following ways:

  • From the portal browser. Open the portal browser in any of the following ways:

    • In the Home portal, click the Portals tab.

    • From the Portals menu, select Portal Browser.

    • From the portal editor or portal administration, click the Back to Portals icon at the top left of the screen.

      Figure 6-2 Portal Editor: Back to Portals Icon

      Portal Editor: Back to Portals Ico

    Locate the portal you want to administer, then click Flip icon to display the portal actions menu and select Administration

    Figure 6-3 Accessing Portal Administration from Portal Browser

    Description of Figure 6-3 follows
    Description of "Figure 6-3 Accessing Portal Administration from Portal Browser"

  • From the portal editor. In the portal editor, the portal administration icons are immediately available in the left navigation pane. Click an icon in the left pane to access the administration settings associated with that icon.

  • From the Portals page in WebCenter Portal administration. From the Portals menu, select Administration, then click the Portals tab. Locate the portal you want to administer, then click the Administer link for the portal. This link is shown only if you are the portal manager or member with Manage Security and Configuration or Manage Configuration permission in the portal.

    Figure 6-4 Accessing Portal Administration

    Description of Figure 6-4 follows
    Description of "Figure 6-4 Accessing Portal Administration"

  • From the portal viewer. When viewing a portal, select Manage, then All Settings. This menu item is shown only if you are the portal manager or member with Manage Security and Configuration or Manage Configuration permission in the portal.

    Tip:

    The location of the Manage action depends on the page template in use. For example, you may access it through an Actions Actions icon menu.

    Figure 6-5 Accessing Portal Administration When Viewing Portal

    Description of Figure 6-5 follows
    Description of "Figure 6-5 Accessing Portal Administration When Viewing Portal"

6.2 Administering Security in a Portal

Note:

To administer security in a portal, you must be a portal manager or have a custom role that includes both of the following permissions in the portal:

  • Manage Security and Configuration

  • Manage Membership

A portal manager has these permissions by default.

For more information about permissions, see About Roles and Permissions for a Portal.

The Security page in portal administration allows you to set security on the portal, such as access level, defining roles and permissions, and managing membership. The following sections describe the Security page tasks:

6.2.1 Accessing Security Administration for a Portal

To access the security administration for a portal, click the Security icon.

You can also enter the following URL in your browser to navigate directly to the Security page, where you can click the Access, Roles, and Members tabs:

http://host:port/webcenter/portal/portalName/admin/security

Figure 6-6 Portal Administration: Security

Description of Figure 6-6 follows
Description of "Figure 6-6 Portal Administration: Security"

6.2.2 Changing the Access to a Portal

Access to a portal is defined when the portal is created (see About Creating a New Portal). This access can be changed to make the portal more visible or less visible.

To change the access to a portal:

  1. On the Security page (see Accessing Security Administration for a Portal), click the Access subtab and select how you want the portal to be exposed:

    Figure 6-7 Security Page for a Portal: Access Subpage

    Description of Figure 6-7 follows
    Description of "Figure 6-7 Security Page for a Portal: Access Subpage"

    • Public: Anyone can visit the portal, whether they are a registered WebCenter Portal user or not. When this setting is selected, the Public-User role in the portal is automatically granted View Pages and Content permission in the portal, which allows public users to view pages, lists, events, links, and notes. To allow public users to view announcements, discussions, and documents, you need to grant these permissions, as described in Granting Public Access to a Portal. Public users do not have edit, create, or manage permissions in the portal.

    • Private: To access the portal, membership is required (either through invitation or self-registration if enabled). The portal will be shown in the list of available portals in the portal browser and will appear in search results.

      Note:

      The Administrator role provides a user with administrative permissions in a private portal (such as managing membership), but does not allow access to a private portal’s page contents.

    • Hidden: To access the portal, membership is required (through invitation). The portal will not be shown in the list of available portals in the portal browser and will not appear in search results. Members can access the portal through direct URL.

      Note:

      Hidden portals can be viewed through WebCenter Portal administration on the All Portals page by users with the permission Portal Server-Manage Configuration or Portals-Manage Security and Configuration, such as a system administrator. While these users can manage the portal (change settings and membership), they cannot see the portal pages and content unless they are a portal member.
  2. Click Save.

6.2.3 Managing Roles and Permissions in a Portal

To manage the roles for assigning permissions in a portal:

  1. On the Security page (see Accessing Security Administration for a Portal), click the Roles subtab.
  2. To work with portal roles, refer to Managing Roles and Permissions for a Portal.

6.2.4 Managing Members in a Portal

To manage the membership in a portal:

  1. On the Security page (see Accessing Security Administration for a Portal), click the Members subtab.
  2. To work with portal membership, refer to Managing Members and Assigning Roles in a Portal.

6.3 Administering General Settings and Actions for a Portal

The General page in portal administration allows you to modify general settings for a portal, such as the title (display name) and description, the internal name, and to perform general actions on a portal, such as closing an inactive portal, taking a portal offline to perform maintenance tasks, adding RSS feeds, or deleting the portal. The following sections describe the General page tasks:

6.3.1 Accessing the General Settings and Actions for a Portal

To access the overview settings and actions for a portal, click the General icon.

You can also enter the following URL in your browser to navigate directly to the General page:

http://host:port/webcenter/portal/portalName/admin/overview

Figure 6-8 Portal Administration: General Settings

Description of Figure 6-8 follows
Description of "Figure 6-8 Portal Administration: General Settings"

6.3.2 Changing the Title of a Portal

A portal title displays at the top of the portal and other places where portals are available for selection, such as the Portals page. In prior releases, the title was referred to as the display name.

Note:

Changing the title does not affect the internal name and URL for the portal. To change the internal name of a portal (and consequently the URL that directly accesses the portal), see Changing the Internal Name (and URL) of a Portal.

To change the title (display name) of a portal:

  1. On the General page (see Accessing the General Settings and Actions for a Portal), under Portal Information, modify the Title as desired (Figure 6-9).

    Figure 6-9 Renaming a Portal

    Description of Figure 6-9 follows
    Description of "Figure 6-9 Renaming a Portal"

    The title that you enter here is the display name that displays at the top of the portal and other places where portals are available for selection, such as the Portals menu and the Portals page. Portal titles can contain alphanumeric characters, underscores, spaces, multibyte characters, and special characters such as & and #. The maximum allowable length is 200 characters. The following reserved keywords are not allowed as the full portal name either in upper or lowercase, or a combination of both—admin, builder, group, groups, home, last, page, pages, my portals, my spaces, portal, portals, space, spaces, system, webcenter, webcenter administration, WebCenter Portal, webcenter portals, webcenter space, webcenter spaces. These reserved words are allowable as part of a longer name (for example, Sales Group).

    Note:

    WebCenter Portal removes any unsupported special characters (such as -) and character spaces in the display name specified here to derive the initial internal name for the portal. For example, the Title My Mega-Portal generates the internal name MyMegaPortal. The URL to this portal is http://host:port/webcenter/portal/MyMegaPortal.

  2. Click Save.

6.3.3 Modifying the Acronym for a Portal

When a portal displays as a color tile in the portal browser, it is overlaid with a portal acronym, which is useful to quickly identify a portal in the portal browser, in combination its tile color and name (Figure 6-10).

Figure 6-10 Default Display of Portal in Portal Browser

Description of Figure 6-10 follows
Description of "Figure 6-10 Default Display of Portal in Portal Browser"

When a portal is created, WebCenter Portal generates an acronym for the portal as follows:

  • If the portal's display name is three or more words, the acronym is the first letter of the first three words, capitalized. For example, the acronym for a portal named My XYZ company is MXC.

  • If the portal's display name is two words, the acronym is the first letter of each word, capitalized. For example, the acronym for a portal named Team 999 is T9.

  • If the portal's display name is one word and the length of word is two or more letters, the acronym is the first two letters of the word, capitalized. For example, the acronym for a portal named Philatelists is PH.

  • If the portal's display name is only one letter, the acronym is that letter, capitalized.

  • The same acronym for multiple portals is allowable.

  • You can change the acronym for a portal, as described in this section.

The acronym is shown only when the portal displays as a color tile in the portal browser. If the portal displays a logo instead of a color tile, the acronym is not shown.

Note:

For information about changing the default color or logo, see:

To change the acronym for a portal:

  1. On the General page (see Accessing the General Settings and Actions for a Portal), under Portal Information, modify the Acronym as desired (Figure 6-11).

    Note:

    The following limitations apply to portal acronyms:

    • No more than 5 alphanumeric characters, uppercase or lowercase.

    • The following reserved keywords are not allowed as the acronym name either in upper or lowercase, or a combination of both—admin, group, home, last, page, pages, space.

    Figure 6-11 Modifying the Acronym for a Portal

    Description of Figure 6-11 follows
    Description of "Figure 6-11 Modifying the Acronym for a Portal"
  2. Click Save.

6.3.4 Modifying the Description for a Portal

A portal description appears in the listing of the portal on the Portals page.

To change the description for a portal:

  1. On the General page, under Portal Information, modify the Description as desired.

    Figure 6-12 Modifying the Description for a Portal

    Description of Figure 6-12 follows
    Description of "Figure 6-12 Modifying the Description for a Portal"
  2. Click Save.

6.3.5 Modifying the Color for a Portal

By default, a portal is shown in the portal browser as a color tile, overlaid with an acronym and portal name.

Figure 6-13 Default Display of Portal in Portal Browser

Description of Figure 6-13 follows
Description of "Figure 6-13 Default Display of Portal in Portal Browser"

The default color is inherited from the portal template selected during portal creation. On the portal administration Settings page, you can specify whether the portal tile should display a color or logo in the portal browser.

To change the color used to display a portal in the portal browser:

  1. On the General page, under Portal Information, click Choose Color to select a new color for the portal tile in the portal browser.

    Figure 6-14 Modifying the Color for a Portal

    Description of Figure 6-14 follows
    Description of "Figure 6-14 Modifying the Color for a Portal"
  2. Click Save.

6.3.6 Modifying the Keywords for a Portal

Keywords are useful to make a portal more easily discoverable in search results. You can specify keywords for a portal when you create the portal or add, change, and delete them later, as described in this section.

To add, change, or delete keywords for a portal:

  1. On the General page, under Portal Information, modify the Keywords as desired. Separate keywords with a space.

    Figure 6-15 Modifying the Keywords for a Portal

    Description of Figure 6-15 follows
    Description of "Figure 6-15 Modifying the Keywords for a Portal"
  2. Click Save.

6.3.7 Changing the Internal Name (and URL) of a Portal

If necessary for some purpose, you can change the internal name of a portal. It is important to note that when you change the internal name, you are also changing the pretty URL that other people use to navigate to the portal. The format of a portal pretty URL is as follows:

http://host:port/webcenter/portal/portalName

For example: http://mycompany:8888/webcenter/portal/philatelists.

This means that when you change the internal name of a portal, existing bookmarks to the portal URL will no longer work. You can change the portal title; that is, the display name for the portal.

To change the internal name of a portal:

  1. On the General page in portal administration, under Portal Details, click Rename next to the portal name.

    Figure 6-16 Changing the Internal Name of a Portal

    Description of Figure 6-16 follows
    Description of "Figure 6-16 Changing the Internal Name of a Portal"
  2. In the Rename Portal dialog, enter a new internal name for the portal, then click Rename.

    Note:

    Use only alphanumeric characters for the internal name for a portal.

    The pretty URL that can be entered in a browser to directly access the portal changes to use the new internal name:

    http://host:port/webcenter/portal/newInternalPortalName

6.3.8 Closing or Activating a Portal

By default, a portal is active. You can close a portal that is no longer being actively used. Closing a portal archives its content. When you close a portal, it is removed from everyone's Portals menu and displays in the portal browser only when a user selects Closed from the Show list.

Figure 6-17 Show Menu in Portal Browser

Description of Figure 6-17 follows
Description of "Figure 6-17 Show Menu in Portal Browser"

The content of a closed portal remains accessible and searchable to those who still want to reference it and portal members can continue working in the portal either by displaying closed portals on the Portals page, or by pretty URL (http://host:port/webcenter/portal/closedPortalName).

When a portal is closed, any activities performed in the portal are no longer reflected in the Activity Stream in the Home portal. Only the Home page of the closed portal shows activity in the portal.

To close down a portal temporarily, take the portal offline instead.

To close a portal, on the General page in portal administration, under Status, deselect the Active check box.

Figure 6-18 Closing or Activating a Portal

Description of Figure 6-18 follows
Description of "Figure 6-18 Closing or Activating a Portal"

To reactivate the portal, select the Active check box.

Note:

An alternate way to close and reactivate a portal is:

  • From the Portals menu, select Administration, then click the Portals tab. On the Portals page, select the portal that you want to close or reactivate, then click the Actions icon in the toolbar and select Close or Activate:

    Actions menu showing Activate and Close actions

6.3.9 Taking a Portal Offline or Online

By default, a portal is online. You can take a portal temporarily offline for maintenance. For example, if you notice inappropriate content, you can take a portal offline to modify its content, then bring it back online. Only the system administrator or portal members with Manage Configuration permission can access a portal that is offline, or bring it back online. Other members see the Portal Unavailable page.

To take a portal offline:

To bring the portal back online, select the Online check box.

Note:

An alternate way to take a portal offline or bring it back online is:

  • From the Portals menu, select Administration, then click the Portals tab. On the Portals page, select the portal that you want to close or reactivate, then click the Actions icon in the toolbar and select Take Offline or Bring Online.

    Actions menu showing Take Offline and Bring Online actions

6.3.10 Enabling or Disabling RSS News Feeds for a Portal

Portal members can find out what is happening in a portal through RSS news feeds. By default, RSS news feeds are disabled. When you enable RSS news feeds within the context of a portal, members can:

  • Track contributions to discussion forums.

  • View announcements.

  • Watch for revisions to lists.

For more information about publishing RSS new feeds, see Adding RSS Feeds to a Portal.

To allow members access to portal information through RSS feeds:

To disable RSS feeds for this portal, deselect the Publish RSS check box.

6.3.11 Deleting a Portal

When a portal has been closed or inactive for some time and is no longer needed, you can remove it permanently from WebCenter Portal. A portal manager or member with Manage Security and Configuration permission can delete the portal. Deleting a portal is permanent; it cannot be restored after it is deleted.

When you delete a portal:

  • All pages associated within the portal are deleted.

  • Links, lists, notes, tags, and events associated with the portal are deleted.

  • Portal roles and membership details are deleted.

  • Content managed by discussions and announcements is deleted, when it is stored in the default forum or category created by the portal. Content managed by nondefault forums or categories is not deleted (for details, see Modifying Discussion Forum Settings for a Portal).

  • The portal mail distribution list that is automatically created byWebCenter Portal is deleted. However, distribution lists that are customized by the portal manager are not deleted (see Configuring the Mail Distribution List for a Portal).

  • Content managed by external services, such as content repositories, mail, and so on, is removed.

To delete a portal:

  1. On the General page in portal administration, under Actions, select the Delete this Portal.

    Figure 6-21 Deleting a Portal

    Description of Figure 6-21 follows
    Description of "Figure 6-21 Deleting a Portal"

    Note:

    Alternate ways to delete a portal are:

    • In the portal browser, locate the portal you want to delete, then click Flip icon to display the portal actions menu and select Delete.

      Actions menu in Portal Browser showing Delete action

    • From the Portals menu, select Administration, then click the Portals tab. On the Portals page, select the portal that you want to delete, then click the Actions icon in the toolbar and select Delete.

      Actions menu in WebCenter Portal administration showing Delete action
  2. In the confirmation prompt, click Delete to confirm or Cancel to preserve the portal.

If the delete process fails for any reason, the portal is not removed from your Portals tab. This sometimes happens when a back-end server cannot be contacted. If you click Delete again, the portal is removed.

6.4 Administering Look and Feel Settings for a Portal

The Settings page in portal administration allows you to change the appearance of your portal and its pages through setting the page template, skin, footer, copyright and privacy statements, language, attributes, icon, and logo. This page also allows you to define the resource catalogs that contain the components you can add to pages, page templates, page styles, and task flow assets. You also use this page to specify the behavior when the page is displayed on another device. The following sections describe the Settings page tasks:

6.4.1 Accessing Look and Feel Settings for a Portal

  • To access the assets, options, icon, and logo settings for a portal, click the Settings icon.

You can also enter the following URL in your browser to navigate directly to the Settings page:

http://host:port/webcenter/portal/portalName/admin/settings

Figure 6-22 Portal Administration: Look and Feel Settings

Description of Figure 6-22 follows
Description of "Figure 6-22 Portal Administration: Look and Feel Settings"

6.4.2 Disabling and Enabling Page Drafts in a Portal

When portal members edit portal pages, the portal administration settings specify whether changes are applied pages immediately, or applied to a page draft that must be published to allow others to view the changes. By default, page drafts are enabled.

To enable or disable page drafts in a portal:

To enable or disable page drafts in a portal, on the Settings page in portal administration, under Page Drafts:

  • Deselect the Enable check box to apply page updates immediately, without creating a page draft.

  • Select the Enable check box (default) to apply page updates to page drafts. This allows users to refine their changes in draft mode in one or more editing sessions. When satisfied with the page updates, an approver can publish the page.

Figure 6-23 Disabling and Enabling Page Drafts in a Portal

Description of Figure 6-23 follows
Description of "Figure 6-23 Disabling and Enabling Page Drafts in a Portal"

6.4.3 Changing the Page Template for a Portal

A page template defines how individual pages and groups of pages display on a user's screen. For more information, see Working with Page Templates.

WebCenter Portal provides several built-in page templates (see About the Built-In Page Templates). Alternatively, portal designers can create custom page templates to offer more ways to display pages on the screen, as described in Creating a Page Template. Within a portal, you can copy or customize an existing page template, as described below and in Administering All Assets in a Portal No Variable.

Each page template works together with a skin to determine the overall look and feel of the pages in your portal. While the page template controls the location and behavior of components on the page, the skin controls the visual appearance of those components, such as the colors, fonts, and various other aspects.

See Also:

Working with Skins

Each page template can define a preferred skin to identify the skin that works best with that page template. When the page template is selected as the default page template for a portal or as the system default, the default skin automatically updates to the page template's preferred skin.

See Also:

Setting the Preferred Skin for a Page Template

By default, a portal inherits the page template defined for the portal template that you select when you create the portal.

Note:

If the portal template does not specify a page template, the portal uses the default page template specified by the system administrator, as described in Choosing a Default Page Template in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

You can optionally select a different page template for an individual portal, overriding the default page template settings. To change the page template for a portal:

  • On the Settings page in portal administration (see Accessing Look and Feel Settings for a Portal), under Assets, select a new Page Template (Figure 6-24).

    Figure 6-24 Changing the Page Template for a Portal

    Description of Figure 6-24 follows
    Description of "Figure 6-24 Changing the Page Template for a Portal"

    The page templates that are listed are those that are made available to the portal on the Shared Assets or Assets page (see Showing and Hiding Assets). The [system default] selection applies the page template specified as the default for all portals by the system administrator, as described in Choosing a Default Page Template in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

    You can add custom page templates for the portal to this list by copying an existing page template into a new page template, completely separate from the original, as described in Administering All Assets in a Portal No Variable.

    An Expression Editor is available for entering custom values using Expression Language (EL) expression, allowing page template to be determined dynamically based on certain criteria. Click the Expression Editor icon icon next to the Page Template drop-down list, then select Expression Builder to open the editor. If you need EL assistance, an application developer can provide an EL expression; see Expression Language Expressions in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

6.4.4 Changing the Skin for a Portal

A skin defines the appearance and look and feel of a portal. For more information, see Working with Skins.

WebCenter Portal provides several built-in skins (see About Skins). Alternatively, portal designers can develop custom skins to reflect a personality, or to incorporate specific branding, as described in Creating a Skin. Within a portal, you can copy an existing skin, as described below and in Administering All Assets in a Portal No Variable.

By default, a portal inherits its skin from the default specified for all portals by the system administrator, as described in Choosing a Default Skin in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

Each page template can define a preferred skin to identify the skin that works best with that page template. When a page template is selected as the new default page template for a portal or as the system default, the default skin automatically updates to the page template's preferred skin.

See Also:

Setting the Preferred Skin for a Page Template

You can optionally select a different skin for an individual portal, overriding the default skin setting. When you change the skin for a portal, the skin is applied to all the pages of the portal. However, the portal administration pages are not affected. They always appear with the default skin, Alta.

WARNING:

changing the default skin to something other than the preferred skin for the selected default page template may produce unexpected results.

To change the skin for a portal:

  • On the Settings page in portal administration (see Accessing Look and Feel Settings for a Portal), under Assets, select a new Skin (Figure 6-25).

    Figure 6-25 Choosing a Skin for a Portal

    Description of Figure 6-25 follows
    Description of "Figure 6-25 Choosing a Skin for a Portal"

    The skins that are listed are those that are made available to the portal on the Shared Assets or Assets page (see Showing and Hiding Assets). The [system default] selection applies the skin specified as the default for all portals by the system administrator, as described in Choosing a Default Skin in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

    You can add custom skins for the portal to this list by copying an existing skin into a new skin. For more information, see Administering All Assets in a Portal No Variable.

    An Expression Editor is available for entering custom values using Expression Language (EL) expression, allowing a skin to be determined dynamically based on certain criteria. Click the Expression Editor icon icon next to the Skin drop-down list, then select Expression Builder to open the editor. If you need EL assistance, an application developer can provide an EL expression; see Expression Language Expressions in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper

6.4.5 Changing the Resource Catalogs in a Portal

When you edit a page or page template in a portal, the resource catalog lists items that you can select to add to the page or page template. For more information about resource catalogs, see Working with Resource Catalogs.

WebCenter Portal includes three built-in resource catalogs:

  • Default Portal Catalog, assigned to portal pages by default, contains resources to add to pages and task flow assets in a portal.

  • Default Home Portal Catalog, assigned to pages in the Home portal by default, contains resources to add to a personal or business role page.

  • Default Page Template Catalog, assigned to page templates and page styles by default, contains a Navigations folder and a Portal Components folder, which provide access to resources specifically used in page templates and page styles. Note that all pages in a portal use the same page template, though there may be several page templates available as portal assets.

Alternatively, portal designers can develop custom resource catalogs, as described in Creating a Resource Catalog. Within a portal, you can create a new resource catalog from scratch or copy an existing resource catalog into a new resource catalog, as described below and in Administering All Assets in a Portal No Variable.

To change the resource catalogs used in a portal:

  • On the Settings page in portal administration (see Accessing Look and Feel Settings for a Portal), under Assets, select a new resource catalog (Figure 6-26):

    • Resource Catalog for Pages specifies the resource catalog to use when editing individual pages and task flow assets in a portal.

    • Resource Catalog for Page Templates specifies the resource catalog to use when editing page templates and page styles. Note that all pages in a portal use the same page template, though there may be several page templates available as portal assets.

    Figure 6-26 Choosing a Resource Catalog for a Portal

    Description of Figure 6-26 follows
    Description of "Figure 6-26 Choosing a Resource Catalog for a Portal"

    The [system default] selection applies the resource catalogs specified as the default for all portals by the system administrator, as described in Choosing Default Resource Catalogs in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

    You can add custom resource catalogs for the portal to this list by creating a new resource catalog from scratch or by copying an existing resource catalog into a new resource catalog. For more information, see Administering All Assets in a Portal No Variable.

    An Expression Editor is available for entering custom values using Expression Language (EL) expression, allowing the resource catalog to be determined dynamically based on certain criteria. Click the Expression Editor icon icon next to the Resource Catalog drop-down list, then select Expression Builder to open the editor. If you need EL assistance, an application developer can provide an EL expression; see Expression Language Expressions in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

6.4.6 Displaying or Hiding a Page Footer in a Portal

A page footer can display copyright details for the portal and a link to its Privacy Statement.

To display or hide a page footer for a portal:

  1. On the Settings page in portal administration, under Options, select the Footer check box to display a page footer, or deselect the check box to hide the page footer.

    Figure 6-27 Displaying or Hiding the Page Footer in a Portal

    Description of Figure 6-27 follows
    Description of "Figure 6-27 Displaying or Hiding the Page Footer in a Portal"
  2. Click Save.

6.4.7 Customizing the Copyright Statement and Privacy URL in a Portal

When enabled, the copyright statements and URL to the privacy statement specific to the portal display in the page footer of the portal:

Figure 6-28 WebCenter Portal Copyright Statement

Description of Figure 6-28 follows
Description of "Figure 6-28 WebCenter Portal Copyright Statement"

Figure 6-29 WebCenter Portal Privacy URL in Page Footer

Description of Figure 6-29 follows
Description of "Figure 6-29 WebCenter Portal Privacy URL in Page Footer"

To customize the copyright statement and privacy URL for a portal:

  1. On the Settings page in portal administration, under Options, select Footer to display the area at the bottom of the portal for the copyright statement and privacy URL. Deselect the check box to hide the page footer, including the copyright statement and privacy URL.

    Figure 6-30 Customizing the Copyright Statement and Privacy URL

    Description of Figure 6-30 follows
    Description of "Figure 6-30 Customizing the Copyright Statement and Privacy URL"
  2. In the Copyright and Privacy URL fields, enter appropriate values. If you wish to expose the page footer, but not include a copyright statement and/or privacy URL, remove the existing contents and leave the field blank.
  3. Click Save.

6.4.8 Setting a Portal Display Language

You can optionally set a portal display language to control the language in which the user interface (UI) elements of a particular portal render in WebCenter Portal. UI elements include button and field labels, application links, screen text, and so on.

For more information about working with languages in WebCenter Portal, and the different levels at which a display language can be set, see Translating Portals into Other Languages.

Within the scope of viewing a portal, the portal display language setting is given precedence over all other language settings. For example, if a portal named Sales Team has its display language set to English, and Monica (a member of Sales Team) has set her personal user preference language to Dutch, assuming no other language settings are in effect:

  • Monica views the Sales Team portal in English, and cannot change this language setting.

  • Monica views other parts of WebCenter Portal, outside the Sales Team portal, in Dutch.

Note:

If you create a portal based on a portal template that is defined to use a specific language, that language setting is not inherited by the portal. Instead, the initial language setting for a new portal is based on the order of precedence.

To set a portal display language:

  1. On the Settings page in portal administration, under Options, select a language for the portal from the Default Language list.

    Figure 6-31 Setting the Portal Display Language

    Description of Figure 6-31 follows
    Description of "Figure 6-31 Setting the Portal Display Language "
  2. An Expression Editor is available for entering custom values using Expression Language (EL) expression, allowing the language to be determined dynamically based on certain criteria. Click the Expression Editor icon icon next to the Language drop-down list, then select Expression Builder to open the editor. If you need EL assistance, an application developer can provide an EL expression; see Expression Language Expressions in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper
  3. To customize the languages displayed in the Default Language list, click Customize. For example, your WebCenter Portal application might be available in 27 different languages, but you may only need to display the content in your portal in three or four different languages, so you could filter the list to display a subset of languages.

6.4.9 Setting the Page Behavior for a Portal When No Page Variant Exists

Page variants are alternative views of an existing page for specific device groups to target specific device size and characteristics. The base page and the page variant have the same URL, security, parameters, and so on.

When using a device (such as smart phones, tablets, and desktop browsers) in a device group that does not have a page variant defined, and the device group is not the default device group for the portal, the page fallback setting determines how to render the page when it is viewed on that device. As the portal manager, you can set the page fallback behavior for all pages in the portal. To override the portal-level setting for an individual page, see Setting Page Behavior for a Specific Page When No Page Variant Exists.

This setting is honored based on the following rules:

  • If the request is from a device in the default device group for the portal, then the default (base) page will be displayed no matter what is set for Page Fallback. The default setting always overrides the Page Fallback setting.

    Note:

    This means that even if there is a page variant for the device group, the default (base) page will be displayed.

  • If the request is from a device that is not in the default device group for the portal, then:

    • If there is a page variant for that device group, the page variant is displayed on the device.

    • If no page variant exists for the device group, then the Page Fallback setting is used by the device

Note:

At the application-level, your system administrator performs the following tasks described in Oracle Fusion Middleware Administering Oracle WebCenter Portal:

To set the fallback behavior for all pages in the portal when displayed on a device in a device group that does not have a page variant defined, and the device group is not the default device group for the portal:

  1. On the Settings page in portal administration (see Accessing Look and Feel Settings for a Portal), under Devices, select the required Page Fallback setting (Figure 6-32):

    • Display default page to display the original base page on the device.

    • Display no page to display the Page Not Available page on the device.

    Figure 6-32 Setting Page Fallback Behavior When No Page Variant Exists for Current Device

    Description of Figure 6-32 follows
    Description of "Figure 6-32 Setting Page Fallback Behavior When No Page Variant Exists for Current Device"
  2. Click Save.

Note:

A portal member with the Basic Services: Edit Page Access, Structure, and Content permission can override the default setting by changing the fallback behavior for the individual page, as described in Setting Page Behavior for a Specific Page When No Page Variant Exists.

6.4.10 Working with Portal Attributes

Every portal includes built-in attributes such as name, description, date created, icon, and so on. In addition to these built-in attributes, you can add custom attributes that are unique to the portal and its characteristics to specify additional portal information (metadata). Custom attributes are propagated throughout the portal.

In addition to portal-specific attributes, system administrators can define global custom attributes, which are available for use by any portal

In addition to portal-specific attributes, system administrators can add and manage global attributes in WebCenter Portal Administration. Global attributes are available for use by any portal.

A custom attribute is simply a name value pair (such as customerId=400, orderId=11, or userName=Smith).

For example, if you build a portal for customer analysis purposes, it might contain several custom task flows that take the parameter customerId as an input: task flows such as Customer Sales History, Customer Satisfaction Rating, Future Sales Prospects, or Customer Contact Information. With a custom attribute defined named customerId with an appropriate value, all the task flows that can accept a customerId can display information specific to that customer.

A custom attribute can also be retrieved using Expression Language (EL) expressions. For example, an EL expression may read a value that is passed in through the URL that displays a portal (for example, customerid=10). Any portal pages, task flows, or portlets that deliver customized content based on parameter values can accept global custom attribute values and display content accordingly using the following Expression Language (EL) syntax to access the global custom attribute value:

  • For portal-specific attributes:

    #{spaceContext.currentSpace.metadata.customAttributes[attributeName]}

  • For global attributes:

    #{WCAppContext.application.applicationConfig.customAttributes[attributeName]

For more information, see Passing Parameter Values Through the Page URL. If you need EL assistance, an application developer can provide an EL expression; see Expression Language Expressions in Oracle Fusion Middleware Developing WebCenter Portal Assets and Custom Components with Oracle JDeveloper.

When you create a new portal that is based on a portal template that includes custom attributes, the new portal inherits the template's custom attributes and their values. You can enter new values for the attributes when you create the new portal.

To work with custom attributes for a portal:

  1. On the Settings page in portal administration, under Attributes, add a new attribute, edit an existing attribute, or delete an attribute:

    • To add a new attribute, click Add Attribute.

      Figure 6-33 Entering Custom Attribute Name and Value

      Description of Figure 6-33 follows
      Description of "Figure 6-33 Entering Custom Attribute Name and Value"

      In the Add Attribute dialog:

      • Enter a unique Name for the attribute. Valid names start with an alphabetic character and contain only alphanumeric characters.

      • Enter a Value for the custom attribute. The value you type is treated as a string value.

      • Click Add to save the custom attribute and display it in the attributes list.

    • To edit a custom attribute for a portal, modify the value directly in the value field. An attribute name cannot be modified.

    • To delete an attribute, click the Delete icon next to the attribute. In the confirmation dialog, click Delete to remove the attribute from the portal.

6.4.11 Changing the Portal Icon

The portal icon displays alongside the portal display name in menus and smaller areas. For example, it may display on the Portals menu at the top of the portal, or on the Portals administration page.

Figure 6-34 Portal Icon in Portals Menu

Description of Figure 6-34 follows
Description of "Figure 6-34 Portal Icon in Portals Menu"

Figure 6-35 Portal Icon at Top of Portal

Description of Figure 6-35 follows
Description of "Figure 6-35 Portal Icon at Top of Portal"

Figure 6-36 Portal Icon on Portals Administration Page

Description of Figure 6-36 follows
Description of "Figure 6-36 Portal Icon on Portals Administration Page"

A default icon is provided by the portal template used when you create the portal, but you can assign a different icon if desired.

To change the portal icon:

  1. On the Settings page in portal administration, under Icon and Logo, click Change next to the current portal icon to open the Select Icon dialog.

    Figure 6-37 Changing the Portal Icon

    Description of Figure 6-37 follows
    Description of "Figure 6-37 Changing the Portal Icon"

    Figure 6-38 Select Icon Dialog

    Description of Figure 6-38 follows
    Description of "Figure 6-38 Select Icon Dialog"
  2. In the Select Icon dialog, either:

    • Select Upload image, then Choose File to navigate to the icon you want to use.

      The icon image file can be up to 150 KB, and should be no larger than 16 x 16 pixels for best results. Supported file types are .gif or .GIF, .png or .PNG, and .jpg or .JPG. If the file is not uploading, check the size of the file you are trying to upload. The file name must contain alphanumeric characters only.

    • Select Enter URL to image, then enter the URL to an icon image (beginning with http://).

  3. Click OK.

6.4.12 Changing the Portal Logo

By default, a new portal is shown in the portal browser as a color tile, overlaid with an acronym and portal name.

Figure 6-39 Default Display of Portal in Portal Browser

Description of Figure 6-39 follows
Description of "Figure 6-39 Default Display of Portal in Portal Browser"

The default color is randomly assigned during portal creation.

If you select Show portal logo instead of color tile in the steps below, then the portal tile displays its logo instead of a color in the portal browser, and the portal name is shown beneath the logo. The default logo is inherited from the portal template, but you can upload any logo image for the portal.

To change the portal logo:

  1. On the Settings page in portal administration, under Icon and Logo, click Change next to the current portal logo to open the Select Logo dialog.

    Figure 6-40 Changing the Portal Logo

    Description of Figure 6-40 follows
    Description of "Figure 6-40 Changing the Portal Logo"

    Figure 6-41 Select a Logo Dialog

    Description of Figure 6-41 follows
    Description of "Figure 6-41 Select a Logo Dialog"
  2. In the Select Logo dialog, either:

    • Select Upload image, then Choose File to navigate to the logo you want to use.

      The logo image file can be up to 150 KB, and should be no larger than 64 x 64 pixels. Supported file types are .gif or .GIF, .png or .PNG, and .jpg or .JPG. If the file is not uploading, check the size of the file you are trying to upload. The file name must contain alphanumeric characters only.

    • Select Enter URL to image, then enter the URL to a logo image (beginning with http://).

  3. Click OK.
  4. Notice that Show portal logo instead of color tile is automatically selected when you change the portal logo. This means that the new portal tile will display a logo in the portal browser. To switch back to a color tile, deselect Show portal logo instead of color tile.

6.4.13 Changing the Portal Preview Image

When you create a new portal template from the current portal, the portal preview image is used to represent a preview of a new portal created with the portal template. This image is exposed in the portal creation wizard on the portal specification page.

Figure 6-42 Portal Specification Screen

Description of Figure 6-42 follows
Description of "Figure 6-42 Portal Specification Screen"

In other words, this image applies only if the current portal is used as the basis for new portal template. For example, if you create a portal for a retail site, and want to use the portal to create a portal template for portals for other retail sites, you may wish to change the portal preview image to represent such a portal, such as an image of a product selection page in the portal.

A default preview image is provided by the portal template used when you create the portal, but you can assign a different preview image if desired.

To change the portal preview image:

  1. On the Settings page in portal administration, under Icon and Logo, click Change next to the current portal preview image to open the Select Preview Image dialog.
  2. In the Select Preview Image dialog, either:

    • Select Upload image, then Choose File to navigate to the image you want to use.

      The icon image file can be up to 150 KB. Supported file types are .gif or .GIF, .png or .PNG, and .jpg or .JPG. If the file is not uploading, check the size of the file you are trying to upload. The file name must contain alphanumeric characters only.

    • Select Enter URL to image, then enter the URL to a preview image (beginning with http://).

  3. Click OK.

6.5 Administering All Assets in a Portal No Variable

The Assets page in portal administration allows you to manage the assets for the portal, such as page templates, resource catalogs, and skins. The following sections describe the Assets page tasks:

6.5.1 Accessing Assets Administration for a Portal

To access the assets administration for a portal, click the Assets icon.

You can also enter the following URL in your browser to navigate directly to the Assets page:

http://host:port/webcenter/portal/portalName/admin/assets

See Also:

WebCenter Portal Pretty URLs

Figure 6-43 Portal Administration: Assets

Description of Figure 6-43 follows
Description of "Figure 6-43 Portal Administration: Assets"

6.5.2 Working with Portal Assets

To work with the assets for a portal, see Working with Portal Assets.

6.6 Viewing Device Groups for a Portal

The Device Settings page in portal administration allows you to view the various device groups available for use in the portal. The following sections describe the Device Settings page tasks:

6.6.1 About Device Settings

Enterprise portal users access portals from a range of devices, from smart phones to tablets to desktop browsers. Device settings and related features control exactly how your portal pages render on different devices. Device settings can be configured only at the application level and not at the portal level. Application-level device settings apply to all portals. As a portal manager, you can view the device settings that apply to your portal.

System administrators can add support for a new type of device or device group or change the way portal pages render on certain devices.

Note:

The built-in page templates Mosaic and Unicorn are designed to be responsive to automatically adjust to the display device. Therefore, pages that use these templates do not need device-specific settings or page variants.

If your portal pages use a non-responsive page template, the display on different devices may exhibit formatting issues, such as overlapping text.

6.6.2 Accessing Device Settings for a Portal

To access the device settings administration for a portal, click the Device Settings icon.

You can also enter the following URL in your browser to navigate directly to the Device Settings page:

http://host:port/webcenter/portal/admin/portals/admin/portalName/device

Figure 6-44 Portal Administration: Device Settings

Description of Figure 6-44 follows
Description of "Figure 6-44 Portal Administration: Device Settings"

6.6.3 Filtering Device Groups

The Filter field lets you filter the list of device groups shown in the device group table. You can filter searches based on device group names, display names, and descriptions.

To filter the device groups for a portal:

  1. Click the Device Settings icon to access the Device Settings page.
  2. In the Filter field, enter a string containing full or partial device group name, display name, or description. Then, click the Filter arrow icon to the right of the field.
    The device groups table lists the device groups matching the filter in name or description.

6.7 Administering Tools and Services in a Portal

The Tools and Services page in portal administration allows you to enable and disable tools and services operating in the portal, such as Announcements, Discussions, Documents, Events, and Lists. The following sections describe the Tools and Services page tasks:

6.7.1 Accessing Tools and Services Administration for a Portal

To access the tools and services administration for a portal:

  • Click the Tools and Services icon.

You can also enter the following URL in your browser to navigate directly to the Tools and Services page:

http://host:port/webcenter/portal/portalName/admin/services

Figure 6-45 Portal Administration: Tools and Services

Description of Figure 6-45 follows
Description of "Figure 6-45 Portal Administration: Tools and Services"

6.7.2 Working with Tools and Services

Most tools and services configuration is the responsibility of the system administrator, who configures and maintains connections to make the tools and services available in WebCenter Portal.

You can check the Tools and Services page for a portal to see which tools and services are available, and enable or disable as required. If not shown on the Tools and Services page, then the system administrator has not configured that tool or service connection. When you enable a tool or service in a portal, you are automatically granted Manage permissions on that tool or service.

To work with the tools and service for a portal, see Working with WebCenter Portal Tools and Services

6.8 Deploying and Propagating a Portal

When you deploy a portal to another portal server, you make a copy of the source portal on the target server and you can include all or some of the source portal's data.

Deploying a new portal on the target server and redeploying an existing portal are exactly the same. When you deploy a portal that already exists on the target, it is simply deleted and recreated as a new portal.

Note:

To deploy a portal:

  • you must have the Portal Manager role (or Delegated Manager role) for the portal you want to deploy

  • the system administrator must assign you to a role that has the application-level permission Portal Server-Deploy

  • the target server must be configured by the system administrator on the Device Settings page in WebCenter Portal Administration

For more information about deploying and propagating a portal, see Deploying Portals, Templates, Assets, and Extensions in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

To deploy a portal:

  1. In the portal administration, click the Deploy icon.

    You can also enter the following URL in your browser to navigate directly to the Tools and Services page:

    http://host:port/webcenter/portal/portalName/admin/services

    Note:

    You will not see the Deploy icon unless you are granted the application-level permission Portal Server-Deploy.

    Figure 6-46 Portal Settings - Deploy Page

    Description of Figure 6-46 follows
    Description of "Figure 6-46 Portal Settings - Deploy Page"
  2. Select the target server and other options for deployment on the Deploy page.

    Note:

    The Target Server must be configured by the system administrator. For more information, see Creating a Portal Server Connection in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

    For the steps to deploy a portal, see Deploying a Portal Using WebCenter Portal in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

  3. Click Deploy.

    The Deploy Portals dialog displays the progress and status of portal deployment. While the portal is being deployed, you can choose to work on the portal if required.

  4. Click Close.

    After the portal is deployed, the status of deployment can be viewed on a status page. You can view only the history of the portals that you have deployed (see Viewing Portal Deployment History in Oracle Fusion Middleware Administering Oracle WebCenter Portal).

6.9 Exporting and Importing a Portal

Exporting and importing a portal is primarily done by the system administrator. However, the default permissions of the Portal Manager allow portal managers to perform these tasks.

Note:

For detailed information about portal permissions and exporting and importing a portal, see Permissions Required to Perform WebCenter Portal Life Cycle Operations and Exporting and Importing a Portal in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

This section includes the following topics:

6.9.1 Exporting a Portal

Exporting a portal is primarily a system administrator task. However, portal managers can also export portals.

For more information about exporting a portal, see Exporting Portals to an Archive in Oracle Fusion Middleware Administering Oracle WebCenter Portal

To export a portal:

  1. From the Portals menu, select Administration, then click the Portals tab.
  2. Click Managed to view a list of portals that you manage.

    To portal managers, the export action is available only on the Managed page, and not on the All Portals page under the Portals tab.

    Figure 6-47 Managed Portals

    Portals page showing Managed portals
  3. Select the portal you want to export or ctrl-click to select more than one portal, then click Export.
    The Export Portals pane opens. If you selected more than one portal, the portals you selected are listed.

    Figure 6-48 Export Portals Pane

    Export Portals pane
  4. Select Include Shared Assets to export the shared assets used in the portal and click Export.
    The progress information is displayed during the export process.
  5. Specify a location for the export archive (.par file) when the export process is complete.

    Figure 6-49 Portal Export In Progress

    Description of Figure 6-49 follows
    Description of "Figure 6-49 Portal Export In Progress"

    Select either of the following:

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

      Your browser downloads and saves the archive locally. The actual download location depends on your browser settings.

      Some browsers have settings that restrict the size of downloads. If your export archive is large and does not download, check your browser settings.

    • Save to Server - Saves the export .par file to a server location. The .par file is saved to the default path DOMAIN_HOME/WC_Archives, where DOMAIN_HOME refers to the domain location where WebCenter Portal is installed.

      When the file is saved, click OK to close the Information dialog.

  6. Click Close to close the Export Portals dialog.

6.9.2 Importing a Portal

Importing a portal is primarily done by the system administrator. However, users with Create Portals permissions can import a portal. This permission is granted by default to the Authenticated-User role.

Note:

To re-import a portal that already exists your instance of WebCenter Portal (for example, if you have made any changes to it in another application such as JDeveloper), you must have Portals: Manage Security and Configuration and Create Portals permissions.

To import a portal:

  1. From the Portals menu, select Administration, then click the Portals tab.
    (Optional) Enter the result of the step here.
  2. On the Portals page, click Import .

    The Import Portals dialog opens.

    Import Portals pane on the Portals page
  3. 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.

  4. 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.

  5. Set import options as required.
    Field Description

    Include Portal Content

    (Only displays if the archive specified includes a content folder for one or more portal.)

    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.

    Include Shared Assets

    Select to import shared assets, like skin and page templates, used in the portal.
  6. 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/**')

    An information message displays.

  7. Click Yes to confirm that you want to import the portals.

    An information message displays when all portals import successfully.

  8. Click Close to dismiss the Import Portals window.