Mobile Support in Oracle Portal

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. Working with Pages Designed for Mobile Devices 9-5

c. Click Add.

13. Click Finish to create the page.

If you based your mobile page on an existing page, and the existing page is complex, the page creation process may take a while as the existing page is converted into a layout more suited for display on mobile devices. When you click the Finish button, you are given the opportunity of continuing the page creation process in the background so that you can move on to other tasks. If you attempt to edit the mobile page before it is completed, a pop up window will inform you that the page is not yet complete. If you add a portlet to a page that was used as the starting point for a mobile page, that portlet will not appear on the mobile page. If you want the portlet to also appear on the mobile page, you must add it to the mobile page. Additionally, if you want to share any personalizations made to the portlet between the two pages, you must explicitly share the portlet on one page, and then add that shared portlet instance to the other page. For more information, see Section 15.7, Sharing a Portlet Across Multiple Pages .

9.3 Adding Content to a Mobile Page

Whilst mobile and standard pages are accessible from a mobile device, portlets need to be specifically mobile enabled by the portlet developer so that the portlet can produce OracleAS Wireless XML as required. Similarly, only a subset of items are mobile enabled. You can add any item type that is 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 Sub Page Display. This also means that any item types that users create that are based on these types are also potentially available for adding to mobile pages. For example: ■ Simple URL items - link the mobile user away from the portal, to a Web site in an appropriate markup language for the device being used, for example, WML, HDML, or XHTML. Mobile devices receive Simple URLs unchanged so the target defined in the Simple URL link must be able to support the mobile device. ■ Wireless URL items - link the mobile user away from the portal, to a Web site that supports OracleAS Wireless XML rather than device-specific markup such as WML, HDML, or XHTML. The portal’s OracleAS Wireless service rewrites the URL of a Wireless URL item before sending it to the mobile device. Therefore, the target of the Wireless URL must support MobileXML, that is, be a valid target for OracleAS Wireless. Note: If you based your mobile page on an existing page, the new page uses the same access settings as the existing page. You can 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