1. WebCenter Mobile Features
Changren (eSolution)
25 Feb. 2015

2. Concepts Configuration Tools Demo Issues and Concerns Reference
Content
Concepts
Configuration
Tools
Demo
Issues and Concerns
Reference
9/20/2018

3. Concepts-Device and Device Group
Device: a representation of a physical device, like a smart phone or tablet, that users use to interact with a portal.
Pre-configured devices: iPhone, iPad, iPad mini, Samsung Galaxy Nexus, and others
Device Group: a collection of devices that share similar display requirements.
Pre-configured device groups: Desktop Browsers, iOS Phones, Android Phones, iOS Tablets, and Android Tablets.
Each time a portal page is requested, WebCenter Portal determines the type of device from which the request originated. This information enables the portal to decide what category of devices or "device group" the device is associated with
9/20/2018

4. Concepts-Page Variant and others
Page Variant: a page variant is an alternative view of an existing, or "base," page designed to be used with specific devices
Fallback Page: whenever a page does not have a page variant, then the base page is rendered by default; however, you can override this behavior so that no page is displayed in this circumstance.
Default Device Group: one device group is always specified as the default. Out-of-the-box, the default device group is Desktop Browsers. This means all pages in a new portal are associated with the Desktop Browsers device group. If a request comes from an unrecognized device, the portal page is rendered according to the default device group settings.
9/20/2018

5. Configuration-Device
Creating/Editing/Deleting/Copying/Downloading/Uploading device
9/20/2018

6. Configuration-Device Attributes
WebCenter Portal identifies a device by comparing the user agent string passed in the request header and the string specified in this field.
This parameter does not have to be a literal match with the request header. It is taken to be a regular expression, and you can enter any valid regular expression in this field.
9/20/2018

7. Configuration-Discover Device Attributes
If You Need Information About the Requesting Device
In some cases, it is useful to obtain information about the device used to access the portal and discover which device settings the portal is mapping the device to. Oracle provides example code that a developer can use to create a task flow that echoes back this device information.
9/20/2018

8. Configuration-Device Group
Creating/Editing/Deleting/Copying/Downloading/Uploading/Hiding/Showing/Ordering/Setting as default
When a user accesses WebCenter Portal using a device, portals are rendered using the
assets like page template and skin associated with the device group to which that
device belongs. However, a device may be associated with multiple device groups. In
such cases, the ordering of the device groups in the Device Groups tab determines the
precedence of device groups.
9/20/2018

9. Configuration-Device Group
Setup devices for device group
Usually we setup asset for device group at Portal level instead of at Application-level
Setup assets for device group at Application-Level
9/20/2018

10. Configuration-Device Group
Configure device group at Portal-level (override Application-level configuration)
9/20/2018

11. Configuration-Support New Device
Discover the user agent string that the new device sends to the portal.
Create a new device that has a user agent string that can match the new device's user agent string.
(Optional) create a new device group for all devices that share similar rendering characteristics to the new device.
(Optional) apply an appropriate skin and page template to the device group.
Add the new device to the device group.
Test the portal on the new device to ensure it renders properly.
9/20/2018

12. Configuration- Page fallback setting
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.
Portal-Level Setting for Page Fallback
9/20/2018

13. Configuration- Page fallback setting
When using a device (such as a smart phone, tablet, or desktop browser) 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
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
Page-Level Page Fallback Setting (override the portal-level setting)
9/20/2018

14. Configuration-Page Variant
Page Variant is created for Device group
Page variant can’t be created for some navigation model items such as link, content item, and folder.
9/20/2018

15. Configuration-Preview Page Variant
Very convenient out-of-box tool to preview page variant in different device
9/20/2018

16. Configuration-Use Case
9/20/2018

17. Configuration-Use Case (Steps)
When a request comes in to the server, the user agent string is examined in the header of the request.
WebCenter Portal looks for a device that matches that user agent (a regular expression string).
If multiple devices are defined whose user-agents can potentially map to the incoming user-agent, then the server tries to map the request to the most appropriate device. The most appropriate device is one whose user-agent has the maximal possible match.
9/20/2018

18. Configuration-Use Case (Steps) con’t
When a device is identified, WebCenter Portal looks to see if it is in a device group. If it is in more than one group, the first one in the list of device groups for the portal is used. (That’s why device group order matters)
If no device is identified, then WebCenter Portal assigns the "default device group" to the current request.
The appropriate skin, page template associated with the device group, and page variant (if one exists) are returned and the page renders on the device. If a page does not have a page variant, then the base page is rendered, by default; however, you can override this behavior so that no page is displayed in this circumstance.
9/20/2018

19. Tools-RegExr and User Agent Overrider
RegExr: an online tool to learn, build, and test Regular Expressions. (Very helpful for troubleshooting device setting)
User Agent Overrider: An Add-ons for Firefox to change user agents in Firefox . (simulate mobile device)
9/20/2018

20. https://itunes.apple.com/ca/app/junos-pulse/id381348546?mt=8
Tools-Junos Pulse
Junos Pulse: Provides secure connectivity over SSL VPN for Mobile device to access DEV WebCenter Portal.
For Android:
For iOS:
9/20/2018

21. (device/device group/page variant/page fallback/etc.)
Demo
Demo
(device/device group/page variant/page fallback/etc.)
9/20/2018

22. Issues and Concerns-Best practices
In short, we have known mobile setting and mechanism in WebCenter Portal based on research.
Best Practices for Device Settings
Avoid Changing the Default Device Group for a Production Portal
Changing the default device group in a production portal can lead to unexpected behaviors. It is best to avoid changing the default device group after your portal is in production.
2. Avoid Deleting a Custom Device Group for a Production Portal
If you delete a custom device group for a production or portals, the server does not warn you that existing portals use that device group, leading to incorrect page renderings in some cases.
3. If You Accidentally Delete a Device Group
You can create another device group with the same name as the one that was deleted. When a device group is deleted, the page variants are not removed from the system. These page variants are associated using the name of the device group. Recreating a device group with the same will bring back all those pages.
9/20/2018

23. Issues and Concerns
Create page variants for each device group (too much work? More flexible than adaptive way?)
Visual design (header/footer/menu/look and feel/layout)
Mobile setting (page variant, page fallback setting) and different navigation model item can impact the menu display.
Page variant can’t be created on some navigation model items like link, folder, and content item.
Have to set the first level menu item not navigable.
Deploy ESR taskflows into Webcenter Portal.
Use Expression language to hide the left column in mobile page variant or  edit the mobile page variants directly to hide the left column without using expression language. Either way some manual work is needed. ……
The navigation behavior in Mobile devices is different from desktop. In desktop we can just hover the mouse on the first level menu to have the second menu open, but in Mobile, we need to touch (like click in desktop)the first level menu to either (not both) open the link behind the first level menu item or expand the second level menu. As a result, we have to make the first level not clickable.
9/20/2018

24. Any questions and concerns?
Reference
Any questions and concerns?
For more information:
9/20/2018