1 2 3 31 Previous Next

SAP Enterprise Portal

454 Posts

Overview:  The language that the portal is displayed in depends on the following hierarchy, with the languages at the top of the list taking precedence over those at the bottom:

 

  1. Component (iview) language (defined in the portalapp.xml)
  2. Portal Mandatory language (defined in the prtDefault.properties)
  3. User language (defined in the user’s profile).
  4. Request language (defined by the browser).
  5. Portal Default language (defined in the prtDefault.properties)
  6. System Default language (default locale defined by the OS).

 

Example:  for example, if you have your portal user language (as in point 3) set to Czech, but the language of the iView that is the logon page (as in point 1) set to English, that logon page will be displayed in English.

 

 

blog4 language.PNG

 

 

Property Location:  Regarding the navigation path for the prtDefault.properties kindly refer to the SAP Documentation outlined below which provides a detailed summary and walkthrough regarding the language settings.

 

 

 

 

Useful Reference Documentation:

 

  • SAP Note: 1013521 - Configuration of supported languages within the portal
  • SAP Note: 1661391 - Portal 7.3 is not displayed in the configured language
  • SAP Note: 1696439 - Changing the Default or Mandatory Locale for a 730 EP
  • NW Portal 7.3: SAP Documentation and Guides: http://scn.sap.com/docs/DOC-23349

Remember my blog about IE and Portal which covered many scenarios that exposed rendering issues when running Portal in IE browsers? Just when we thought we’d covered all the possibilities, we discovered we hadn’t…

This blog covers another rendering issue we found in IE11 when running an iView in standalone mode.


What’s standalone mode?

Standalone mode means opening a Portal iView by navigating directly to the PCD path of the iView without using the Portal APIs, or in other words, without any Portal framework page. This is in contrast to opening a Portal iView by navigating to the content area, where the target is displayed in place.

Here’s an example of what a direct call to an iView looks like:

http://myportal:50000/irj/servlet/prt/portal/prtroot/pcd!3aportal_content/Folder1/Folder2/MyWorksets/MyRole/UWL_MOBILE/params?username_field=auser&password_field=apasswork&login_submit=on&login_do_redirect=1

Navigation can be triggered by either of the following:

  • Calling an “EPCM.doNavigate” JavaScript method to get the target as a parameter (there are other parameters to this method but I won’t discuss them here).
  • Navigating to the Portal and adding the target iView as a parameter:

http://myportal:50000/irj/portal?NavigationTarget=ROLES:// aportal_content/Folder1/Folder2/MyWorksets/MyRole/UWL_MOBILE& username_field=auser&password_field=apasswork&login_submit=on&login_do_redirect=1&

 

Navigating to the Portal calls the content area and passes the “NavTarget” (the target iView) as a parameter in the post data. For example:

http://myportal:50000/irj/servlet/prt/portal/prteventname/Navigate/prtroot/pcd!3aportal_content!2fevery_user!2fgeneral!2fdefaultAjaxframeworkContent!2fcom.sap.portal.contentarea?ExecuteLocallyc=true&CurrentWindowId=WID1431257684193&supportInitialNavNodesFilter=true&sapDocumentRenderingMode=EmulateIE8&windowId=WID1431257684193&NavMode=0&PrevNavTarget=navurl%3A%2F%2F52d7253cace28a2e8381980e871f0a18

 

In the HTTPWatch snapshot below, you see the call to the content area and to the NavTarget (the iView that the Portal needs to navigate to) parameter in the “Post Data” tab:

PortalNavigation.png

 

(By the way – I published a blog in the past which discusses an interesting issue caused by calling content directly and not via the navigation APIs)

 

When would an iView run in standalone mode?

Sometimes an application (either an SAP application or a custom application) links directly to Portal iViews instead of calling them via the navigation APIs. BI Launcher is an example of this type of application. They trigger “window.open” and send the “open” method the direct link of the iView.

 

Another case where iViews run directly is when you preview an iView (you can preview an iView when you edit it in content management).

 

What’s the problem with running iViews directly?

As long as an iView is running within a Portal framework (full portal/ separate window/ separate portal window/ separate portal window standard mode, and so on), the browser automatically opens with correct document mode (standard/quirks).  This occurs because the Portal framework sends a parameter in the response header called “x-ua-compatible” to the browser. For example:

  • Running in Ajax framework page – the value is “IE=5,IE=EmulateIE7” (which means quirks).
  • Running “Ajax Standard Mode Framework” – the value would be “Edge” (which means standard).
  • Running in a separate Portal window standard mode – it would be “Edge”.

In the HTTPWatch snapshot below, we see the property sent in the first call of the Portal (by the way, it will be sent only when running in an IE browser because only IE recognizes the property):

 

xuacompatible.PNG

 

Running an iView directly means that the framework “services” are lost, include sending the parameter for the correct document mode. The new standalone browser window containing the target iView opens in the default document mode of the specific IE version.


Why do most rendering issues arise in IE11?

Recently, a lot of customers upgraded their IE browser to IE11 and this issue emerged for many of them: the iViews opened in a new browser window via direct URL are not rendered well.

 

When examining the document mode of the browser, we at SAP could see that it was set to “Edge” instead of “IE5 Quirks” or just “Quirks”.

Why did this suddenly arise in IE11 and not in older versions of IE? That’s because up to IE11, new windows open in “quirks” mode by default. However, since IE11, new windows open in “Edge” mode by default. So we need to instruct it explicitly to open in quirks mode.

 

Of course, there could also be the opposite situation:  an iView requiring standard mode rendering (Edge) and running on an IE older then IE11 opens automatically in quirks mode. But this seems to be an infrequent scenario.

 

What’s the solution?

The solution for this phenomenon is quite simple: add the “x-ua-compatible” property to the iView header.

 

A new property has been added to the root iView of AI iViews. This property is called “Default Document Rendering Mode”. This property has 2 possible values: “Quirks” or “Standard”. The default value for the property is “quirks”.

 

When the value is set to quirks – the header that is added is:

<meta http-equiv="X-UA-Compatible" content="IE=5, IE=EmulateIE7"/>

 

And when it’s set to standard – the header is:

<meta http-equiv="X-UA-Compatible" content="Edge"/>

 

In the HTTPWatch snapshot below, you can see that the property is added to the head of the returned HTML:

htmlHeader.PNG

 

Note that when the property is returned from the framework – it is set in the response header, and in the iView it is set in the HTML head.

Both methods are valid, but if the value is set to both – the response header overrides the HTML head and its value  affects the browser.


Solution evolution

At first, the solution was implemented only in BI iViews, because these were the first scenarios we dealt with.

The SAP Note with the solution for BI iViews is:

2012705 - BI iView's are not render correctly when using Internet Explorer 10 and above

 

When we received feedback about other iView types, because the solution for BI iViews had proved a good solution, we extended the solution to all AI iViews. The SAP Note is:

2098706 - iView rendered corruptly when using IE10 and above when executing it directly or from headerless window

 

And there’s also SAP Note 2163649 which fixes a regression from SAP Note 2098706

2163649 - More scenarios of opening an iView directly (standalone) with IE10 and above causes rendering issues (continuation of note 2098706)


Troubleshooting and workarounds

  • If you deployed the fix from one of the above notes and this still doesn’t fix the issue – it might be that the iView was not updated with the new property.

You can check it by opening the iView properties via the “Content administration” tab and checking if the  “DefaultDocumentMode” property exists. If it doesn’t, perform the following steps:

  1. Navigate to Content Administration -> Portal Content Management.
  2. In Portal Content, expand the Portal Applications folder, and select com.sap.portal.appintegrator.sap.
  3. From the right-click menu, choose “Update PCD Objects”.
  4. Go to the iView and check that the “Default Document Rendering Mode” property exists.


  • If you have the version with the fix from SAP Note 2012705 and you don’t want to implement the more advanced note – you can use a workaround of adding the “DefaultDocumentMode” property to other iView types manually via the PCD inspector.


        If you want to implement this workaround – follow the steps mentioned in this document


Background: This connector relates to the Notifications received by UWL from Knowledge Management (KM).

 

blOG3 UWL ActionInboxConnector Picture.PNG

 

 

Overview: The ActionInboxConnector provides KM Recent Notifications into the UWL Notification tab, which include document feedback, subscription items, subscription administration, and document approval notifications; in addition, checked out documents appear under Tracking , and documents for approval under Tasks. By default the Action Inbox Connector for UWL is enabled. For more information, see Action Inbox section in the KM Administration Guide.

 

Issues & Why: With the ActionInboxConnector errors and exceptions may appear for a wide range of different reasons. 

 

  1. Are you currently using KM or KMC?
  2. Have you attempted to deactivate (and then reactivate the ActionInbox Connector.)?

 

Common Exception Issue: ActionInboxConnector: Failure in retrieving from Action Inbox.

 

Solution: The main point of analysis interest here is to check the following path > System Administration -> System Configuration -> UWL -> UWL Admin

 

 

  • Important Point: Computer Monitor Service (Under KM) must be working

 

 

Then check the following: when you go to UWL administration and select the system 'ActionInbox' open the tray for 'Universal Worklist Service Configuration' what is the value set for 'Timeout Value for the Connected Systems? If it is 30 seconds you can try and increase its value to 300sec or so.

 

 

Important: Also kindly follow the SAP Note 1133821 to ensure destination service configuration to and from the UWL is setup accordingly.

 

 

Summary: With issues relating to the ActionInboxConnector you need to determine whether or you are using KM functionality. The reason for this is because with KM and KMC and their surrounding functionality examples of what these notifications are based upon vary and include Notification tabs which include document feedback, subscription items, subscription administration, and document approval notifications; in addition, checked out documents appear under Tracking, and documents for approval under Tasks. If you are not using KM and collaboration the connector (ActionInboxConnector) should be deactivated in the UWL configuration page. (It is activated by default).

 

The ActionInbox connector uses resources from the KMC so even if you don't use KM on the portal, this connector is co-dependent on the codefrom KMC. This is the same as the AdHocConnector with the portal.

Background: The UWL (Universal Worklist) functions through a baseline concept known as the UWL Destination Service Configuration.

 

 


BLOG1 UWL Picture.PNG

 
 
 


 
Overview: You can define the connections to systems for Universal Worklist. These systems provide work items via UWL Connectors. The Universal Worklist Systems page is accessible from Portal via navigation to > System Administration > System Configuration > Universal Worklist and
Workflow
> Universal Worklist Administration.

 

Common Issues:

 

  • "Cannot connect to the Provider" when you access tabs e.g. ESS/MSS
  • “Problem occurred while creating JCO client for destination: ABCXYZ”
  • “User is missing credentials for connecting to system alias: ABCXYZ”

 

Why: The RFC destinations have to be maintained so that the UWL can make functional calls to the backend applications. In most cases the exceptions outlined above appear as the calls to the backend fail due to a discrepancy in the configuration setup of the RFC destinations.

 

Solution: SAP Note: 1133821 - UWL Destination Service Configuration.

 

By following the documentation above we can ensure that the RFC destination is missing or is not configured properly.

 

After the note is implemented and the WebFlowConnector re-created the cache should be cleared and the backend re-registered.

 

Important: Check that after applying Note 1133821 the destination names and the UWL connector names exactly match, even considering
case-sensitiveness.

 

If your portal system alias (=UWL connector name) is for example XYZCLNT100, then the RFC destination name should be exactly XYZCLNT100$WebFlowConnector. Please correct the RFC destination accordingly.

 

After you have checked/prepared the RFC destination for the future use please delete that connector in the UWL config UI (Portal->System
Administration->System Configuration->Universal Worklist) with which you would like to use this RFC destination.

 

After that

 

  • Restart the portal cluster
  • Recreate and reregister connector

 

Now retest.  Are you still seeing the issue?

 

 

Summary: These steps are important for the connector to work properly.  So in the portal, there needs to be a deletion on the connector, a restart of the portal cluster, then a recreate and re-register so that the new connector interacts with the RFC destination.

More and more customers are adopting the new Fiori Launchpad (FLP) design on SAP Enterprise Portal (EP) to benefit from a modern and easy to use user interface that also runs nicely on mobile devices. Of course, users also want to access their documents and unstructured content in their Portal in a UI that fits into the new FLP design seamlessly both from desktop and mobile.

 

To achieve this, SAP Mobile Documents is the natural choice. Besides the cool UI, it also allows you to easily integrate content from other sources like Microsoft Sharepoint or the SAP Business Suite. In this blog, I would like to look into the integration from a technical point of view. For more details on business benefits and how you can best leverage SAP Mobile Documents with SAP Enterprise Portal, I recommend reading Annette Fuchs' blog on SAP Mobile Documents and SAP Fiori launchpad on EP integration.

 

 

1. Installation of SAP Mobile Documents

For your on-premise server installation you need an SAP NetWeaver AS Java as a platform to install the SAP Mobile Documents Server. So you might decide to install it on your Portal server. There are already quite some blogs out there on SCN describing the installation in detail.

Check out Martina Kirschenmann's SAP Mobile Documents - Implementation and Integration for a comprehensive overview of all necessary and optional configuration steps and links to more detailed blogs.

 

 

 

2. Configuration of SAP Mobile Documents

MobileDocs2.png

In Mobile Documents, you usually have 3 areas:

  • My Documents where the user can store personal documents and sync them to all connected clients,
  • Shared documents for securely sharing documents with internal and external users according to various security settings
  • Corporate Repositories where managed content can be provided to the users.

 

To use My Documents and Shared Documents, you first have to create repositories called mydocuments and shareddocuments in the Knowledge Management of your SAP Enteprise Portal.

 

Further repositories from SAP Knowledge Management or other sources can be accessed in the Corporate section. I will talk about that in a separate blog.

Check out

- SAP Mobile Documents Setup Guide for all details on configuration

- Setup connection for SAP Mobile Documents to Microsoft Sharepoint for Microsoft Sharepoint integration

- SAP Mobile Documents - Connecting a File Share as Corporate Repository.

 

 

3. Setting up SAP Fiori launchpad in the Enterprise Portal

Some time ago, I already published a blog on Building your Mobile Portal using Fiori Launchpad on EP. It touches all steps that are necessary for setting up FLP on EP, but since that one was more addressed to the experienced portal admin, I will now go into more details specifically for Mobile Documents and add some more screenshots.

 

 

a. Create a new URL Alias and assign the Fiori desktop to it

In this step, you create a new URL suffix that you can use to call the portal in FLP design directly. Of course, you could also configure your Portal to run with FLP, when calling the standard URL, and use a specific URL alias to access the Ajax Framework page.

 

 

In the Portal, navigate to System Administration > System Configuration > Portal Display > URL Alias Manager. Click New to create a new URL Alias with a meaningful name starting with portal/ like portal/fiori or portal/flp.

URLALias.png

To assign the URL alias to the Fiori desktop, navigate to System Administration > System Configuration > Portal Display > Desktops & Display Rules.

On this page, navigate to Portal Content > Portal Administrators > Super Administrators and open the Master Rule Collection. Click Add IF Expression.

In the IF part of the new expression, select URL Alias from the dropdown and enter your newly created URL alias into the text field right to it. Click Apply.

Now click the THEN part of the expression. In the Portal Content tree, open Portal Content > Portal Users > Standard Portal Users > Fiori Framework Content. Right click Fiori Desktop and select Add Portal Desktop to Expression. Click Submit again. With Move Down, you can bring your new expression to the right place in the Master Rule.

MasterRule.png

In most cases, you will change the Fiori Launchpad theme to better reflect your corporate identity, so you would rather use an adapted copy of the Fiori desktop.

 

 

b. Defining categories for the Tile Catalog

 

You can use categories to allow end users to identify relevant content more easily. The categories that are needed in your company, can be configured as properties of the Fiori Launchpad Categories iView. If you do not define categories, all tiles will appear under one category called General.

MobileCategories.png

In the Portal, navigate to Content Administration > Portal Content Management.
Open folder Portal Content > Portal Users > Standard Portal Users > iViews > Fiori Launchpad.
Right click Fiori Framework Categories to open the Properties. Click All to display all properties.
When you scroll down a bit, you can see Category 01 ID, Order, Title to Category 20 ID, Order, Title. Here you can define up to 20 categories for the tiles in your launchpad.

 

 

c. Create SAP Mobile Documents iViews

 

For each tile in your SAP Fiori launchpad that should open Mobile Documents, you need to create a URL iView.

 

Go to Content Administration and choose create iView from Template. Select the URL iView template. After iView creation, edit the following properties:

 

 

  • On the URL iView tab, enter the URL to start Mobile Documents.You can either display the complete Mobile Documents web client or a direct link to a specific folder.

    • Complete web client: Enter URL /mcm/browser. If SAP Mobile Documents runs on the Portal server, it is not necessary to enter a system. Otherwise, create a system for Mobile Documents in System Administration > System Landscape and enter the alias of this system on the URL iView tab.

          iViewWebClient.png

 

    • Direct link: Enter URL /mcm/browser/v1/open and if necessary, a system. To find out the object ID of the folder to display, open the Mobile Documents web client and navigate to the folder you want to display in the iView.

Select the folder by clicking the checkbox in front it, then click the i to open the folder information. In the web link and mobile link on the information page, you can find the object ID and the repository ID.

 

Repobj.png

 

In your URL iView settings, enter two URL parameters:

      • URL parameter rep with value the repository ID as you find it after rep= in the folder's web link, type String
      • URL parameter obj with value the object ID as you find it after obj= in the folder's web link, type String.

 

          iViewDirectLInk.png

 

 

 

  • Now you have to set some more iView properties that are not Mobile Documents specific, but are important for the iView to show up in Fiori launchpad. Go to tab Properties, click All and Modify Properties. Set the following properties:
    • Object ID of Device group: Enter the ID of all device groups on which the iView should show up. You can find these IDs in System Administration > System Configuration > Portal Display > Device Group Manager. You can find the IDs in the rightmost column. Enter the IDs for all relevant device groups separated by semicolons, e.g. com.sap.portal.dg.desktop;com.sap.portal.dg.smartphone;com.sap.portal.dg.tablet.
    • Mobile App Categories: Enter a list of all categories where the iView should show up in the Tile Catalog according to the categories that you created in part 3b.
    • Default App in Home Page (as of Portal 7.4 SPS 10 or Portal 7.31 SPS 15. In earlier releases, this property is called Permanent in Launcher): If this is set to true, the selected iView is displayed by default on the home page. Otherwise, the end user would first have to go to the Tile Catalog and assign the tile to one of his groups.
    • SAP UI5 icon: Define the icon that is displayed on the tile, e.g. sap-icon://documents or sap-icon://document-text. If you set the Image Type to Image instead of Icon, you can also display an image stored in the Web Resource Repository using the property Icon URI.

 

If you would like to read more details about iView properties, please read Shani Limor's blog on SAP Fiori Launchpad on Portal - Sample Content for Administrators.

 

 

d. Assigning the iViews to roles

 

 

Create a new freestyle role or edit an existing one. Add the new Mobile Documents iViews to the role and make sure that there is an entry point defined for the iView or one ore more levels higher. Make sure the the iView is set to Visible.

Assign the role to a user or a group. Now all iViews in the role are listed in the Tile catalog for the user. The tiles that were defined as Default App in Home Page / Permanent in Launcher are accessible from the user's home page automatically.

 

 

Now the system is set up. Access Fiori launchpad in the Portal with the following URL http://<portalserver>:<portalport>/irj/<your URL alias>. Click the menu icon to access groups and the tile catalog and you can start to play with Mobile Documents in your Portal.


FLP final.png

Definition: The Universal Worklist (UWL) gives users unified and centralized way to access their work and the relevant information in the portal. It collects tasks and notifications from multiple provider systems – SAPBusiness Workflow, Collaboration Task, Alert Framework and Knowledge Management Recent Notifications - in one list for one-stop access.

 

 

BLOG1 UWL Picture.PNG

Performance:  There are many configuration options that affect the performance.

 

 

 

 

UWL Sizing guide

 

In the process of creation, the sizing guide determines the hardware requirements.

 

  • Number of users
  • Total number of items per user
  • Number of connectors

 

Performance Degradation Factors

 

  • Sometimes specific connectors (BPMUWL) cannot fulfill the get items request. There is 30 seconds timeout defined for the connectors (configurable)
  • Communication channel between UWL and providers (Network, JCo)

 

Performance Configuration Recommendations

 

  • Use Delta Pull mechanism (where applicable)

 

  • Delta Pull period should be no longer than the time that task is required to be updated in the UWL for all new items from the backend. If the items are created more frequently, the period should be shortened and the opposite. Better results for performance will be with higher values but the items may not be always up to date.The minimal value is 60 seconds and it is default value as well.

 

  • Cache validity should have a longer period value than the delta pull.If cache validity has expired then a call to backend will be performed regardless of the fact that delta pull has occurred.

 

  • Page refresh rate, that is accessible from data properties of Personalize Tasks, specifies how often UI will be refreshed with data from the cache. Note that the cache validity period takes precedence.Then the Page refresh rate should have less period value than cache validity. Last comes the Delta Pull period. In short: Cache Validity > Page refresh rate > Delta Pull period.

 

  • The number of users per channel depends on the number of the tasks and the number of theusers. Default value is 40 users per channel. Increasing this number will decrease the number of the invocation to the backend. Note that the higher the number of users per channel, the higher volume of data per invocation will be transferred.

 

  • The IView property “Wait duration for UI refresh while waiting for update” can be increased if UI is not responsive. If the value of this property is set to 0 then user interface will be blocked waiting for the call to the backend to complete.  In this case after call is completed and  cache is updated, items are read from cache displayed in the UI. Assigning value to the property allows  the UI to read the last data found in cache and display it immediately, this  way unblocking UI while the call to backend is performed in background. After the time defined in the property passes, presumably cache already updated with the latest items in background, UI is updated again from cache showing the latest items.

 

  • The number of the custom attributes should be decreased.For every additional attribute an additional call to backend is performed. The setting “Retrieve custom attribute via primary pull” should be switched off.

 

Commonly Reported Issues

 

  • CPU spikes – due to high volume of data. Check performance recommendations
  • Long DB processing time – Oracle DB software is not up to date Refresh is excessively used. The connector is not able to fulfill the request
  • Cache is not cleared in applying new XML configuration
  • Configuration issues – the documentation  has to be read carefully
  • RFC destination is not configured according to the note 1133821
  • Task definition and Task visualization change at backend take effects in UWL only after re-registering WebFlow     connector
  • Delta pull for WebFlow connector is working only if the ABAP reports at backend are configured (RSWNUWLSEL or SWN_SELSEN). 3rd party reporting is not supported.
  • Out of memory exception in updating items from the WebFlow – JCo payload (8-10 kB per item) Real Time refresh must be activated in the backend
  • Deployment issues due to incompatible changes in the DB schema (bug fixing)
  • Misunderstanding of the substitution support in UWL On upgrade: SOM connector does not display the items. Wrong connector is displayed to the item.
  • Users deleted at customer systems.

 

Key UWL Documentation

 

  • KBA 1577547 UWL Performance Tips and Considerations

 

 

In the first part of our „Portal on smartwatch“ blog series my colleague Michael demonstrated the BTEXX mobilePortal prototype for the Pebble smartwatch. Today as the Apple Watch is released in many countries I want to share some information on our Apple Watch prototype with you.

 

 

WatchKit Apps

 

At first I was sceptical about business apps on smartwatches. Who wants to use this tiny screen for more than fitness tracking? After spending a lot of time in the Apple Watch simulator I changed my mind. Don’t think of smartwatches as a replacement for your current tools but as an addition! Your users should be able to choose the right tool for the right time!

 

With our first WatchKit App "My Tasks" you don't have to take out your phone or even your notebook to approve yet another time correction. Browse through your UWL inbox and open your tasks to access detailed information and approve (or reject ) the tasks directly on our wrist!

 

blog_app.png

 

 

Notifications

 

Push Notifications on the Apple Watch are pretty similar to the ones you know from your iPhone. You receive a short text and some custom actions. Here's an example of an UWL notification from our prototype:

 

blog_notification.png

 

You get some basic information on the updated UWL task and the available actions. You can approve the request directly on your watch without using your iPhone. Of course sometimes you can’t decide without further information. In this case just open the task on your iPhone with the BTEXX mobilePortal or in the iOS Notification Center.

 

 

 

 

Architecture

 

architecture_app.png

 

For our prototype we completely reused our BTEXX mobilePortal 2.0 backend. The app itself is implemented in Swift and uses the Apple WatchKit Library.

 

WatchKit Apps are basically just extensions to native iPhone apps. Right now the code of third party apps runs on the iPhone while the Apple Watch acts as an external touchscreen. Later this year Apple will provide the possibility to develop fully native Apple Watch Apps. This should bring some improvements regarding features and performance.

 

At the moment wearables are still a research field for us - we’re trying to figure out what can be done and more importantly what should be done with smartwatches in the business context.

 

I’m looking forward to your feedback and questions!

 

Best regards

Conrad

 

 

 

About BTEXX

 

Based on the connection between user perspective, SAP technology and process know-how, BTEXX implements user-friendly solutions that make companies more efficient and users happy.

In the upcoming ASUG event in Orlando several SAP Portal oriented sessions will be offered, which you can find in the session catalog of the agenda builder of ASUG Annual Conference. In the agenda builder, you find the sessions by choosing "Browse ASUG tracks", then you scroll down and find the track "Portals".

 

These are the main topic areas:

  • SAP Portal portfolio and roadmap (session PO1310) : learn about the transformation of the SAP Portal portfolio into cloud (mainly for external facing scenarios) and into the SAP Fiori UX paradigm.
  • Fiori Launchpad (sessions PO1343, PO799, PO836) : SAP Fiori launchpad running on SAP Enterprise Portal is a key milestone in aligning the SAP UI Clients (Fiori launchpad, Portal, NWBC) with the Fiori UX design. In this session you learn how to renew your SAP Enterprise Portal with the new multi-channel, personalized framework page following the Fiori design. You will also get the latest news about our planned release for NW 7.4 SPS11/7.31 SPS16 providing new cool features like for example remote catalogs, which allow the integration of catalogs and groups from ABAP backend systems. Or you have locked areas on the homepage which you can use for example for company information, which should not be changed by the end user. Join our Fiori launchpad sessions to get the latest updates on existing and planned features - or contact one of our experts directly. Learn also about Fiori launchpad deployment best practices (ABAP, SAP Portal and HANA Cloud Platform) and common architectures.
  • Cloud Portal (sessions PO801, PO762): Learn how to create business driven sites using SAP HANA Cloud Portal and how to extend business solution using HANA Cloud Portal and Fiori Launchpad on HANA Cloud Platform.
  • Customer Sessions (PO460, PO80, PO1126): Listen to our customers Johnson and Johnson, Roche and the University of Mississippi and learn about their Portal projects.
  • Mobile Documents (session PO358): Learn how to renew and enhance the SAP Portal experience using SAP Mobile Documents

 

Check out our SAPPHIRE/ASUG page where you can find the latest information on our sessions and our Portal experts, you can meet in Orlando.

 

Sessions in Details

TopicSession Title and NumberContent
Portal RoadmapPO1310 SAP Portal Roadmap - Innovations for Cloud and On Premise (Lecture)SAP Portal is with over 10,000 productive customers strong and growing. With the introduction of new options in the portfolio such as SAP HANA Cloud Portal or the inclusion of Fiori Launchpad, the options for customers are growing. In this session we will update on the Portal strategy and roadmap, introduce customer testimonials and answer FAQ.
Fiori LaunchpadPO1343 Renewing your SAP Enterprise Portal implementation with SAP Fiori launchpad (Lecture)Join this session to learn how to renew your SAP Enterprise Portal with the new multi-channel, personalized framework page following the Fiori design, new multi-channel SAP Fiori apps running in the portal, and new multi-channel Fiori apps developed with SAP Web IDE and consumed via the SAP Portal.
PO799 SAP Fiori launchpad deployment options recommendations for SAP Portal customers (Lecture)SAP Fiori launchpad provides end users a role-based personalized aggregation point for SAP business applications and analytics. Join this session to learn about Fiori launchpad deployment best practices (ABAP, SAP Portal and HANA Cloud Platform) and common architectures. This session will focus on the use cases for existing SAP Portal customers.
PO836 Exploring ways to make Fiori adoption easier and faster (Panel Discussion)Join this session to hear a panel of experts discussion various strategies and best practices to expedite SAP Fiori adoption - Whether by use exploration tools, custom development or by adopting cloud based components to your Fiori implementation.
Cloud PortalPO801 SAP HANA Cloud Portal - Overview, Innovations, Showcases and Future Directions (Lecture)Join this session to learn how to easily create business driven sites using SAP HANA Cloud Portal. The session highlights the solution market approach, benefits and capabilities as well as key implementation scenarios.
PO762 Extending your business scenarios with SAP HANA Cloud Portal - Scenarios, Use Cases, Best Practices (Lecture)Get an overview on how to extend business solutions using HANA Cloud Portal and Fiori Launchpad on HANA Cloud Platform.
Customer SessionsPO460 Learn How Johnson and Johnson Redesigned its Global SAP Enterprise Portal (Lecture)Join this session to learn how Johnson and Johnson leveraged the SAP Enterprise Portal to create an enjoyable, modern, personalized, and multi-channel aggregation point based on the SAP portal platform.
PO80 Co-Innovation Roche/SAP: Cross Browsers and Device Support, One Portal (Lecture)Roche has created a unique point of access for any SAP application: “One Portal”. After a migration phase the focus was set on usability. The concept is called “Simply One” and it has been implemented with a completely new user experience based on HTML5 with responsive design. This session is focused on sharing the Simply One experience and outcome
PO1126: Success with a responsive, accessible and intuitive to use SAP Enterprise Portal Implementation (Lecture)The University of Mississippi re-designed its SAP Enterprise Portal and implemented it to be very accessible to visually challenged users, responsive to work across mobile devices and desktop computers and intuitive and easy to use. Join this session to learn from experiences of this cost effective successful implementation.
Mobile DocumentsPO358 Enhance Your SAP Portal Experience Using SAP Mobile Documents (Lecture)Join this session to learn how to renew and enhance the SAP Portal experience using SAP Mobile Documents. See how documents from SAP Portal KM, Microsoft Sharepoint, or SAP Business Suite can easily be consumed across different devices – in the cloud or on premise.

 

Contact our Experts

Feel free to reach out to our experts for on-site discussions on our product portfolio and the latest innovations. You can also contact them before the event for organizing an on-site meeting:

experts.png


Aviad Rivlin: aviad.rivlin@sap.com Twitter:@aviadrivlin

Inbal Sabag: inbal.sabag@sap.com Twitter: @inbalsab

Guy Bavly: guy.bavly@sap.com Twitter: @GuyBavly

Lev Segev: lev.segev@sap.com Twitter: @segevle

Yariv Zur: yariv.zur@sap.com Twitter: @vlvl

 

Let's get Social

During and before SAPPHIRE NOW and ASUG you can also keep yourself up-to-date by checking SCN and our Social Media Channels.

 

SCN Spaces

Watch the following SAP Community Network Spaces:
SCN Space for SAP Portal

SCN Space for Cloud Portal

 

Twitter

Follow the official SAP Portal twitter account @Portal_SAP

Portal Hashtags on Twitter:
#SAPPortal – SAP NetWeaver Portal hashtag
#hanacloudportal - Cloud Portal hashtag

#SAPFiori launchpad

 

LinkedIn and Facebook

Follow the event also on LinkedIn and Facebook.

 

Note:

More information on our SAPPHIRE NOW and ASUG plans will follow in the upcoming weeks, bookmark this blog to be up-to-date.


INTRODUCTION


URL iViews

 

Mostly all projects in SAP Portal use iViews that retrieve content directly from a Web page.

 

A URL iView is a collection of Meta attributes, one of which is the URL to the information source. A built-in browser available in the URL iView Wizard and Editor enables you to navigate easily within a Web site in order to retrieve the URL of the source Web page to display in the iView.

 

There are some scenarios where URL iView’s are directly referring intranet link like a help link to SDN.( www.sdn.sap.com). For these the iView properties do not change on migration to different portal systems in landscape.

 

However there are scenarios where SAP Portal interacts with many different SAP systems like

 

  • SAP Business Warehouse
  • SAP Solman,
  • SAP Governance Risk and Compliance solution ( GRC)
  • SAP ECC and so on.

Users may use BW reports or launch other SAP systems using the links from SAP Portal.

 

For E.g. , URLs for the iView’s may start with

 

Fin and HR internet

https://<SAP ECC server name>/sap/bc/gui/sap/its/webgui/!

SAP BW Reports

https://<SAB BW server name>/sap/bw/BEx

GRC Reports

https://SAP GRC Server name>/sap/bw/BEx

Solman

https://<SAP Solman Server name>/sap/bc/webdynpro/sap/

 

 

In above case the server names will change as per landscape and environments. They will be different for Development, Test and Production.

 

If the links are copied statically then there has to be manual action during migration of these iViews to change the URL for them.

 
 

Technical Solution:

 

To avoid the manual action and as a result any issue with that during migrations we can define URL aliases in Portal for all such backend systems.

Basis need to create http systems for all such backends and these systems should have proper parameters

1) Hostname – URL of the backend system

2) Port number – if any

3) Protocol- HTTPS

 

Once the httpsystems are configured the URL iViews need to be modified to get the URL from this system.

 

 

1.       System Creation


Basis needs to create Http Systems:

 

1) Go to System Administration- System Landscape and create systems with below parameters

A. Hostname – URL of the backend system

B. Port number – if any

C. Protocol- HTTPS

 

1.png

 

Once all backend systems are created you can check the httpsystems under System type.

 

2.png

 

 

2.  iViews Modification

Once the systems are tested for connection, we need to modify the iView properties :

    1. System- Select the required HTTP system as per backend
    2. Check the box “ Use system in URL”
    3. URL has static content of URL which does not change with system landscape migrations

 

 

3.png

 

The URL will be called with the link as https://<SAB BW server name>/sap/bw/BEx at runtime.

 

3.   Migration :


During migration of iViews, Basis needs to create the systems in respective environments. There will be no manual action for iViews and they will point to corresponding backends as per landscape automatically using URL alias.

 

 

Conclusion

Thus we can have URL aliases for URL iViews to ensure no manual action for changing the iView’s during migrations and hence maintenance of iViews becomes easy.

Also in case the server names changes in future we just need to update the System alias for httpSystem and need not change all iViews using that server.

Interested in knowing what is going on in SAP Enterprise Portal for SAP NetWeaver 7.4 SPS10 / 7.31 SPS15? Then this is the right blog for you.

 

With the release of SAP NetWeaver 7.4 SPS7 / 7.31 SPS11/12 the Fiori launchpad is running on Enterprise Portal. For every support package new features are added to make the Fiori experience in Enterprise Portal better and better. In SAP NW 7.4 SPS10 we also included new features for the UI Theme Designer.

And now let's jump to the details.


SAP Fiori Launchpad on Enterprise Portal


Relevant for Users


Now - by default - the My Home group is delivered empty and will not appear on the home page. It will only appear on the home page, when users add iViews and pages to the My Home group through the tile catalog:

add_tile_my_home.png

 

Users can search for tiles in the tile catalog:

tile_search_15.png

 

Relevant for Administrators


You can set up predefined groups to be displayed by default on the home page. Before SPS10 there was no possibility for an administrator to define a predefined group with a predefined set of tiles for the users.With SPS10 the administrator can fill the Fioir launchpad already with content and when a user logs on for the first time, he or she will not see anymore an empty launchpad.

An adminstrator configures portal categories to represent predefined groups, according to the category, to which the iView or page is assigned.
To set up tiles to appear in a predefined group, the adminstrator configures the Default App in Home Page property for the relevant iView or page in the properties editor (please click on image for better reading):

app_homepage.png

Users can reset a predefined group they have personalized to restore the default configuration set up by the administrator (click on image for better reading):

reset_group3.png

 

Before SPS10 we only supported navigation modes, which open the apps in a new window with quirks\standards modes. Starting SPS10 we also support a navigation mode, which opens the app in-place. The administrator has to maintain the property value Display in Portal Content Area in the property editor (click on image for better reading)::

display_portal_content_area.png

 

Administrators can add a portal runtime page as a tile. This enables users to launch more than one iView in a tile. All page types are supported.

The use case are mainly scenarios in which customers have a page that contains more than one iViews, which are connected. In this case a page can be defined as a tile and it will open all three iViews together (click on image for better reading)::

page_as_tile.png

 

With the function scope of  NW 7.4 SPS10 it is also possible for Portal content administrators to set up tasks to enable SAP Fiori Launchpad on SAP Enterprise Portal for BI Portal scenarios. For more details, check out this blog by Irena Kull.

 

 

UI Theme Designer


There is enhanced support for the UI theme designer in SAP NetWeaver Portal. You can now do the following:

  • Delete a custom theme
  • Change the name and ID of a custom theme
  • Save a custom theme before publishing it
  • Customize a theme for a portal tile in the home page and see the changes through the Fiori Framework Page preview

theme_designer.png

 

 

For more details check out the SAP documentation and release notes.

 

Bookmark this page to be up-to-date on SAP Fioir launchpad on Portal

 

I hope this summary was helpful for you. We are planning some more features for the next release SAP NetWeaver SPS11. You will have to wait for some weeks and around SAPPHIRE we will update you on the next feature wave for Enterprise Portal.

Welcome to the first edition of this year's SAP Portal news blog. We have lots of news for you in the following topic areas:

  • SAP Fiori / SAP Fiori Launchpad on Enterprise Portal
  • HANA Cloud Portal News
  • Enterprise Portal News
  • Partner News

 

SAP Fiori / SAP Fiori Launchpad on Enterprise Portal

 

SAP Fiori, Demo Cloud Edition

The SAP Fiori, Demo Cloud Edition, is a unique opportunity for you to discover SAP Fiori experience. Explore the new experience, read this blog and watch this demo video:

 

 

How to Renovate your BI Portal with SAP Fiori Launchpad

For SAP NW 7.31 SPS15 (or higher) and SAP NW 7.4 SPS10 (or higher) SAP Portal provides a new visual design, based on SAP Fiori launchpad, which enables a modern, intuitive user experience for integrated reporting scenarios with multi-channel access to reports. This offer is available as part of the standard Portal delivery on premise, as well as in SAP managed cloud (HANA Enterprise Cloud), for customers aiming to simplifying the handling of big data with intuitive analytic dashboards and BW scenarios. Have also a look at this product demo:

 

 

How to Develop, Deploy, Configure and Consume SAP Fiori Apps

The availability of SAP Fiori launchpad running on SAP HANA Cloud Platform was announced in November 2014. This is a big milestone in aligning SAP’s user experience with the Fiori user experience, while focusing on fast, easy and secured implementation, delivered via Cloud deployment. How can you get SAP Fiori launchpad running on SAP HANA Cloud Platform? Read this blog and get the details.

 

SAP Fiori launchpad on Enterprise Portal: Update of SCN page

We updated the SCN page on SAP Fiori launchpad on Enterprise Portal. Among other updates we added a table showing a SAP Fiori launchpad feature comparison in SAP NetWeaver 7.4 releases (+ SAP NW 7.31 releases).

 

User Interface Add-On SPS11 for SAP NetWeaver

Check out the new and changed features of SAP Fiori launchpad in User Interface Add-On SPS11 for SAP NetWeaver.


All about SAP Fiori
You can read all about SAP Fiori in the new SCN community.

 

Cloud Portal News


Release Notes Overview

We have created a new SCN page for Cloud Portal release notes. You can bookmark the page to be updated on our release information.


Development Hands-On Tutorial

Read this development tutorial to learn how to develop business applications for SAP HANA Cloud Portal sites, leveraging on premise and cloud solutions.


Danone movie

Watch in this testimonial how our customer Danone is running SAP HANA Cloud Portal:

 

 

Trial version Update

SAP Fiori launchpad is now available for all HANA Cloud Platform trial users. The launchpad is available as a site in Cloud Portal, and provides a range of services, including navigation, application configuration, and embedded support.

 

Enterprise Portal

 

SAP Maintains its Leadership Position in Gartner’s Magic Quadrant for Horizontal Portals

Gartner recently updated its Magic Quadrant report for Horizontal Portals. In the new report, SAP maintains its status in the Leader Quadrant with a strong rating on the ability to execute and an increase in its completeness of vision.

 

New SAP Portal Roadmap

Check out new edition of SAP Portal roadmap. The document covers the two product lines: SAP Enterprise Portal (deployed on premise or via managed cloud) and SAP HANA Cloud Portal (public cloud, Portal Platform as a Service)


Highlights of SAP Portal in SAP NetWeaver 7.4

This presentation provides an overview on “SAP Enterprise Portal 7.4” and the benefits, key capabilities, deployment options (on premise | managed cloud) and recent innovations such as the integration with SAP Fiori.


Updated Enterprise Portal Sizing Guide

 

An updated sizing guide is available including information on Enterprise Portal running on SAP HANA: Sizing Guide -> Sizing Guidelines -> Database and Technology -> SAP NetWeaver -> SAP Enterprise Portal (SMP user for login necessary).

 

How to Configure Federated Portal Network

A new blog describes the way to configure FPN connections, considering the different possible landscapes.

 

How To prevent PcdInconsistentUpdateException

This blog explains all about PcdInconsistentUpdateException and also helps Enterprise Portal developers, who are already familiar with the Portal Content Directory concept and APIs, how to prevent it.

 

Using the URL-iView in SAP Enterprise Portal

In this blog some of the abilities and limitations of the URL-iView are discussed, it is aimed at developers and users, who have a basic understanding and knowledge of Portal navigation.

 

Setting the iView Language in the Portal

In this blog, you find information how to set the iView (application) language in the Portal, and how the language (locale) is determined by the Portal mechanism.

 

Partner News

 

SAP Portal on Smartwatch

As part of an innovation project at our partner BTEXX they implemented a couple of Smartwatch prototypes based on SAP Portal backend data. It is planned to share the BTEXX experience in a “Portal on Smartwatch” blog series. Read the first part which is "Introduction and Portal Scenarios on Pebble Smartwatch".

pebble_watch1.png

Substitution is a feature of the UWL that allows business users to take over items from other users and to assign items to other users .These cases are defined by certain substitution rules, which can be managed through the Substitution screens.

 

Business scenarios:

 

• Users can assign another user to manage your tasks if you are absent or unavailable.

 

• Users can define a nominee to receive your tasks or fill in for you.

 

• Users can create multiple substitution rules to cover all eventualities.

• Users can also accept tasks of other users (if they have assigned them to you).

 

Create Substitution Rules

 

1) Click and choose Manage Substitution Rules.

UWL_1.jpg

2)In the My Substitution Rules table, choose Create Rule .

UWL_2.jpg

3)Type userid  to select a nominee. Choose Select

UWL_3.jpg

4)Select user and click on next button

UWL_4.jpg

5)User can select radio button at once or on particular date

UWL_5.jpg

6)My substitution rule table will be updated

UWL_6.jpg

 

Above explained procedure is standard functionality of substitution ,but when it comes to the portal 7.4 SP5 we have faced some strange issue.

 

Managing substitutions rules the user picker shows the message “No name found for: *”

UWL_7.jpg

  UWL People picker does not show user details and also users search for substitution rules doesn't work.

 

No search results displayed with error message :"No name found for:(Userid)/*.

 

If you verify log files then you can find following error message

 

Cannot clear ICM server cache by [718ac393010411e3a1fa000000d23c1e] etagIP address


To resolve above people picker issue I have created one role and assigned UME action UWLSearchUnrestricted to the portal role.

UWL_8.jpg

  Above role is assigned to Every user group. Other wise you can assign UME action UWLSearchUnrestricted to desired role.

SAP Web Dispatcher (WD) is the entry point of your users that access your web enabled applications. These can be any HTML service or app you have running on NetWeaver, or other systems like HANA XS. For over a decade WD offers reverse proxy functionality for SAP systems, and while until shortly its main usage area was SAP Portal and Web Dynpro applications, with the rise of Fiori WD is more exposed. Naturally, more and more companies will use it. Of course WD can be integrated into SolMan and therefore can be managed and monitored.

 

While this is nice, analytical requirements for a web application can be quite complex. A standard approach is to use a web analytics application that helps you to find out how your site is used (sessions, entry/exit points, campaigns). While this gives you transparency about the site experience of your end users, it is not really useful when it comes to a more administratively driven approach: what kind of content is passed through WD, impact on configuration parameters: CSS, Javascript, response times, data throughput. Besides, your users must be OK with the tracking code and modern browsers allow users to deactivate tracking cookies and related technology (do not track).

 

WD is the single point of entry to web applications; it contains viable information about their usage. This information can heavily influence the understanding of the app. Think about finding the bottlenecks of the app, the most accessed resources, usage patterns, and so on. The log of the web dispatcher contains all this kind of information. You only have to gather it, store it and analyze it.

 

Basically, WD is a reverse proxy, and in the non-SAP context, Apache is one of the most used reverse proxies. Analyzing HTTP traffic is a common task for web site administrators, and so it is not a big surprise to find a huge list of Apache traffic analyze log tools available. The Swiss army knife among them is logstash. Now, logstash does not really analyze web server logs. It rather parses them and can send them to another tool for storing and analyzing the data. Like elasticsearch.

 

To learn how to configure your own system for WD, logstash, please read the how to document I posted here.


This is the default use case of logstash: Parse logs, extract the information and send it to elasticsearch for storing and retrieval. After the information is stored in elasticsearch, it can be used by Kibana for retrieving information like statistics and analytical data. Think about access statistics or trends.

 

The vantage of the combination of logstash, elasticsearch and Kibana over a web analytic app is that you do not have to install a tracking / analyzing part in your web application. You can also analyze part of your web page normally invisible, like resources. Depending on your WD configuration, you gain insights into how WD works, like how long it takes to retrieve files from the SAP system.

 

Information retrieval

After connecting Kibana to elasticsearch it is easy to surf the data and to create your own dashboard. Drilling down is no problem and while logstash is running in the background adding new data, the dashboard can reflect this instantly. A few sample reports may include:

Total number of files served by WD

kibana1.jpg

Total number of MB transferred

kibana2.jpg

Hits to resouces

kibana3.jpg

You can correlate this data to find out interesting stuff like:

  • Number of requests: a cached resource is served locally by browser, this can decrease drastically the load on WD and backend.
  • Requests for a specific file / site
  • Average response time for CSS or JS files: does it make sense to use WD as a web cache? Think about it: the data may indicate that WD waits to retrieve a file from ICM, multiply it with the numbers of requests it takes for a user to access a resource and you have an idea of time wasted.
  • Data send by serving static files: is your cache configuration correct?
  • What is the largest file requested?
  • Usages: your application is accessible only internally, does the access statistics reflect this?
  • Hitting a lot of 304, 404 or 500? What is causing this?
  • Monitor ICM admin resources to find out possible attack vectors.

Hi,

 

Since HTML5 adoption is really high I heard from several customers that they would like to have an HTML5 based login page.

 

Out of the box the SAP Enterprise Portal doesn't give you the configuration to add the needed doctype attribute in order to allow HTML5 login page.

 

This blog will help you to add the doctype attribute to the document, so lets get started..

 

* The procedure described will work for all versions higher than the version stated in this SAP note 1713259

 

 

1)        Under the content catalog, copy from Portal Applications -> com.sap.portal.runtime.logon -> certlogon and paste as PCD object in a folder under "Portal Content".

12-03-2015 13-31-58.png12-03-2015 13-33-22.png12-03-2015 13-38-23.png

 

 

 

2)      Edit the permissions of the newly created iView add the Group Everyone with both Admin read and "End User" checked.

 

12-03-2015 13-54-47.png

 

3)      Edit the iView using the support PCD Inspector tool and add to it a String property with id " com.sap.portal.prt.html5.compliant" and value "true"

 

12-03-2015 13-57-14.png12-03-2015 13-56-38.png

 

 

4)      Apply SAP steps 2a, 2b, 2c from note "1713259 - PRT support for HTML5 doctype" Setting the PRT html5.compliant property to "iViewDependent "

 

12-03-2015 14-02-17.png

 

 

5)      Follow http://help.sap.com/saphelp_nw73/helpdata/en/1a/3afd4e641b8f42ac07bb77fe30375b/frameset.htm

create your own authscheme.xml file in the custom file replace the entries

" <frontendtarget>com.sap.portal.runtime.logon.certlogon</frontendtarget>" with "<frontendtarget>pcd:portal_content/<your folder>/certlogon</frontendtarget>".

 

 

6)      Restart the whole cluster for the authscheme.xml configuration to take effect.

 

 

And that's it, your'e done.

 

Now your logon page will have the HTML5 doctype declaration in a standalone scenario.

 

Cheers,

Saar

2015 will probably be the year of wearables. As part of an innovation project at BTEXX we tried to unmistify the magic behind it and implemented a couple of Smartwatch prototypes based on SAP Portal backend data, because you do not need to wait for S/4HANA to build a fancy SAP Smartwatch App …

 

We are happy to share our experience in a “Portal on Smartwatch” blog series. Which we would like to divide in 3 parts:

 

Introduction to Wearables

 

Current research studies, e.g. from Forrester, have shown that end users and enterprises are interested in wearables and are planning to use them or are willing to invest in business cases based on them. Forrester has published the following 5 predictions of wearables:

  • The people want it
  • The business wants it even more
  • Companies are inventing new business and service models around wearables
  • Wearables involve surprises
  • The target can be an all-body network

Source: CIO/Forrester (German Site) or an alternative English blog about the topic

 

Pebble Smartwatch

 

If you are following the smartwatch market, you have probably heard of Pebble. Pebble was successfully funded via the crowd-funding platform Kickstarter in 2012 and till now they have sold over 1 Mio. Smartwatches. Currently they are funding their new edition “Pebble Time”, which will be again the biggest campaign on Kickstarter. On the first day of the campaign they have raised over 5 Mio. dollar alone… 

 

For our development we used the “Pebble Steel” which works as companion watch for Apple iPhones or Android Phones. The watch has a 144 x 168 pixel black and white e-ink display and you can implement the following kind of watch apps:

  • Watchfaces: Modern or classic watchface enriched via smart information, e.g. from an SAP System
  • Notifications: Push notifications, primarily the Pebble is displaying notifications from the connected smartphone
  • Watch Apps: Custom smart watch app implementations based on the Pebble SDK

 

What I loved during the development/prototyping was the cloud based development environment, without a local setup I was able to develop my first watchface in a couple of minutes and was able to deploy and test the development on the watch. A good start for Pebble developers is the Pebble Developer Site, which offers good tutorials and API documentation.

 

But now let’s have a look what scenarios/prototypes we have implemented for the Pebble.

 

Portal Scenario 1: UWL Watchface

 

Simple UWL (Universal Worklist) watchface implementation, which shows next to the time (it’s still a watch) the total number of open tasks (e.g. 8 tasks) and details of the latest task, in this case a HR time correction request (Clock-in) of Dieter Martens…

 

uwl_watch_en.PNG

 

Update (08.03.2015) based on the new Pebble SDK 3.0 (Pebble Time, Platform: Basalt)

 

The screens show the migrated watchface to the new SDK 3.0, which supports colors, and two screens of the BTEXX mobilePortal companion app to show the workflow/interaction:

 

PebbleTime_Watchface_with_mobilePortal.PNG

Update (17.03.2015): Picture of the watchface on the unpublished Pebble Time

Thanks to the Pebble development team I got an picture how our watchface would look on a real (unpublished) Pebble Time. Good to know that the watchface works also on the real watch

Pebble_Time_Live.PNG

Portal Scenario 2: BTEXX mobilePortal on Pebble

 

This menu based smartwatch application displays the latest news, tasks and services…

 

mobilePortal_1_en.PNG

The UWL tasks can even be approved/rejected via the watch…

 

mobilePortal_2_en.PNG

 

Architecture

 

pebble_architecture.PNG

 

The native watch apps are implemented in C (Layout and Business Logic) and Javascript (Connectivity to the Internet/REST Services) and are running directly on the watch on top of the Pebble SDK.

Via bluetooth coupling between the watch and the smartphone the Pebble SDK on the watch can connect via the Pebble Companion App on the smartphone to our REST API of the BTEXX mobilePortal to access e.g. Universal Worklist entries, etc…

 

I hope you found the provided information valuable! I am looking forward to your feedback or questions!

 

Stay tuned for the Portal Scenarios on Android Wear and on the Apple Watch… hopefully we will find time to write the blogs in the next weeks...

 

Best regards,

Michael

 

About BTEXX

Based on the connection between user perspective, SAP technology and process know-how, BTEXX implements user-friendly solutions that make companies more efficient and users happy.

Actions

Filter Blog

By author:
By date:
By tag: