Troubleshooting Actions on Pages

Performing Actions on Pages 8-17 I published a page as a portlet, placed it on a page, and displayed selected regions. Now it is displaying blank. This involves the source page and a Portal Template. When you edit or personalize the Page portlet to display selected regions, and a change is made to the portlet’s source page regarding the template—either a template is added or detached or a template region equivalent to a region selected for display on the portlet is deleted—the portlet cannot resolve such changes with its Display Selected Regions setting. The result is that the portlet displays without content—or blank. To resolve this situation, re-edit or personalize the portlet’s region display settings. To personalize a portlet, in page View mode click the Personalize link in the portlet header. For more information on restricting the display of regions in a page portlet, see Section 8.5.3, Selecting Page Portlet Regions for Display . I selected a page for my Page portlet, but it is being ignored. It may be that a Page parameter value is being passed to the portlet, in which case it overrides any page you select when you edit or personalize the Page portlet. When the Page parameter is specified, any page selection you make when you Edit DefaultsPersonalize the Page portlet are ignored. I could not perform a bulk action on a group of selected items. If a bulk action cannot be selected for a group of items, then it probably means that the selected action cannot be performed over all the selected items. Review your item selection, and de-select those for which the action cannot be performed. I want to copy a page to a different page group but no other page groups are listed in the Page Group Map. There are various restrictions for copying pages across page groups. For more information, see Section 8.2, Copying a Page. By default, when you create a page, a local style is created and used for the page. You may need to assign a different style to a page before you can copy it to a different page group. 8-18 Oracle Fusion Middleware Users Guide for Oracle Portal 9 Working with Pages Designed for Mobile Devices 9-1 9 Working with Pages Designed for Mobile Devices In Oracle Portal, you can create mobile pages specifically for mobile devices, such as cell phones. Note that standard pages can also be viewed on mobile devices. However, to provide page designers with more control over the appearance of pages displayed on mobile devices, Oracle Portal enables you to set up mobile pages specifically for display on the small screens of such devices. This chapter describes mobile support in Oracle Portal and explains how to set up and manage mobile pages in Oracle Portal. It includes the following subsections: ■ Section 9.1, Mobile Support in Oracle Portal ■ Section 9.2, Creating a Mobile Page ■ Section 9.3, Adding Content to a Mobile Page ■ Section 9.4, Personalizing Mobile Pages ■ Section 9.5, Viewing Standard Pages on Mobile Devices ■ Section 9.6, Adding MobileXML to Oracle Portal Pages ■ Section 9.7, Viewing Oracle Portal Pages from a Mobile Device ■ Section 9.8, Using the OracleAS Wireless DebuggerSimulator ■ Section 9.9, Troubleshooting Mobile Pages Intended Audience The content of this chapter is intended for users with at least the Manage privilege on the pages they work with. If a particular task requires or can be performed under different privileges, those privileges will be listed before the steps of that task. For more information on page privileges, see Section B.3, Page and Tab Privileges .

9.1 Mobile Support in Oracle Portal

Oracle Portal uses Oracle Application Server Wireless to process requests from wireless devices, and transform content provided by the portal into an appropriate format. To enable mobile access in your portal, your portal administrator must configure how Oracle Portal uses OracleAS Wireless Global Settings: Mobile tab. For more information, see the Oracle Fusion Middleware Administrators Guide for Oracle Portal. You’ll find this guide on the Oracle Portal documentation page of the Oracle Technology Network at http:www.oracle.comtechnologyproductsiasportaldocumentati on.html . 9-2 Oracle Fusion Middleware Users Guide for Oracle Portal What Is a Mobile Page? A mobile page is a page that is specifically designed for display on a mobile device. Mobile pages present information in a hierarchical tree structure. The structure is defined by levels. Any level, including the top level, can contain any number of portlets, items, and levels. This provides the flexibility to represent a large amount of content, yet limits the list displayed at any one time to fit the limited display sizes of most mobile devices. Things to Consider Before You Create a Mobile Page Some things to consider before you create mobile pages: ■ If you use standard pages exclusively, they may not display optimally on the small screens available on mobile devices. On the other hand, if you decide to create a standard and a mobile version of pages, you’ll end up maintaining two sets of portal pages. ■ If you anticipate any mobile access, be sure to test how your standard pages will look on mobile devices. Go to your standard page and click the Mobile: Preview link in the toolbar at the top of the page in Edit mode. ■ Some Oracle Portal features are not available on mobile pages such as item versioning, item level security, and approval chains. Mobile-Enabled Content Any standard page can be displayed in a mobile device but only mobile-enabled content is displayed. When editing a standard page, page designers can preview how the page will look in a mobile device by clicking the Mobile: Preview link in the toolbar at the top of the page. The structure of the standard page is flattened into a list of mobile-enabled portlets and items from which users can make selections. Any tabs on the page are converted into levels, which allow users to drill down and view more content. For more detail, see Section 9.5, Viewing Standard Pages on Mobile Devices . Mobile-enabled portlets are those portlets capable of handling MobileXML. It’s easy to know which portlets are mobile-enabled by noting which portlets are available in the portlet repository when you add a portlet to a mobile page. Mobile-enabled items include any items based on BaseURL, BasePageLink, and BaseSubPageDisplay. This means the item types potentially available for mobile pages include Simple URL, URL, Wireless URL, Simple Page Link, Page Link, LoginLogout Link and SubPage Display. See also Section 9.3, Adding Content to a Mobile Page .

9.2 Creating a Mobile Page

Mobile pages provide a way to design pages to display portlets and items specifically within mobile devices, such as cell phones. Standard pages can also be displayed in mobile devices; however, the standard page design environment is more suited to creating pages for larger display devices, such as computer monitors. If you base your mobile page on an existing standard page, the layout of the existing page is flattened so that it is more suitable for display on mobile devices: ■ The standard page is examined and its regions are processed in a logical order. ■ The mobile content in these regions is copied to the new mobile page. Non-mobile content is not copied over to the new mobile page. Non-mobile content includes Working with Pages Designed for Mobile Devices 9-3 any portlets that are not mobile-enabled, and any item types that are not based on the BaseURL, BasePageLink, and BaseSubPageDisplay item types. ■ The portlet personalizations on the mobile portlets are shared between the standard page and the mobile page. This means that any personalizations made to either page affect the other page. For example, if a user personalizes a stock portlet on a page with a specific portfolio, and that page was used as the initial content for a mobile page, then the user will see the same personalizations on the mobile page. Even though the portlets are shared, they will not be listed in the Portlet Repository. ■ Any tabs on the standard page are converted into levels on the new mobile page. ■ The access control settings on the standard page are copied to the new mobile page. You can edit the mobile page to change these settings later. Privileges that do not apply to mobile pages are converted as follows: – Manage Items With Approval becomes Manage Content – Manage Style becomes Personalize Portlets Full – Personalization Style becomes View To create a mobile page:

1. In Oracle Portal, click the Build tab to bring it forward.

2. Go to the Page Groups portlet, and select a page group that will own the new page from the Page Group drop-down list.

3. Click Create a Page.

4. In the Page Type list, choose Mobile.

If Mobile is not included in this list, the Mobile page type is not included in the page group. If you have administrative privileges, you can add this type to the list of available types by clicking the Configure link next to the Page Type field. Use this to configure the page group that owns this page to include the Mobile page type.

5. In the Display Name field, enter a descriptive name for the page.

Use up to 256 characters of any kind, including spaces. This is the name that is displayed in the Portal Navigator.

6. Optional In the Description field, enter a description for the page.

Use up to 2000 characters. The description is displayed only when you edit the page. It does not appear to the user. 7. Select a page caching option. For more information, see Section 21.1, Page Caching .

8. Click Next.

9. Select: ■ Blank Page to create a blank mobile page. Note: To create a page, you must have the Create global privilege on All Pages, and at least the Manage privilege on the parent page of the new page. 9-4 Oracle Fusion Middleware Users Guide for Oracle Portal ■ Base On Existing Page to populate the mobile page with the same content as an existing page. Click the Browse icon next to the Existing Page field, and the Return Object link next to the page you will use as the starting point for your mobile page.

10. Click Next.

11. Optional Select Display Page To Public Users if you want everyone, including

users who are not logged in to the portal, to be able to view the page. When this option is selected, the page becomes a crawlable data source for Oracle Ultra Search. See also Oracle Fusion Middleware Administrators Guide for Oracle Portal available on the Oracle Portal documentation page of the Oracle Technology Network at http:www.oracle.comtechnologyproductsiasportaldocument ation.html . 12. Optional To explicitly grant privileges to specific users or groups:

a. In the Grantee field, enter the name of the user or group you will allow to

access this page. Alternatively, click the Users or Groups icon, and select from the list provided. b. In the list, choose a privilege level. Alternatively, click the Users or Groups icon, and select from the list provided. Note: You can base a mobile page only on a Standard page. If you want to create a new mobile page based on an existing mobile page, copy the mobile page, then edit the copy. Note: Oracle Portal uses the Oracle Internet Directory for identity management, serving as the repository for users and groups. In the Oracle Internet Directory, groups are uniquely identified by their distinguished name DN. Each group has a unique DN, though many groups can share a common name, in the same way that two people can share a common name, yet have completely different lineage for example, John Smith and John Doe. When working within the portal, groups created from within that portal are displayed simply with their common names. However, when the portal references a group from some other location in the Oracle Internet Directory—such as a group from some other portal associated with the same Identity Management Infrastructure—the DN of the group is displayed to distinguish it from the portal’s locally defined groups.