1 2 3 8 Previous Next

SAP BusinessObjects Mobile

113 Posts

The compatible MOBI app version with iOS8 will be V 6.0.9. We have already uploaded the new patch (v 6.0.9) to AppStore and should be available for download soon.

 

If you have upgraded your device to iOS8, you might face few UI issues and abnormal exit of application on some specific workflows. We have fixed these issues in the next patch version 6.0.9

 

If you are using older version of MOBI app  (like version 5.x or even 6.0.8)  built using SDK, we recommend you to download the latest SDK package (version 6.0.9) from Service Market Place (SMP) and rebuild the app before moving to iOS8. SDK package will be available for download from SMP once app is live in iTunes.Please continue to use XCode 5.x to build the application. Compilation using XCode 6.x is not yet supported and application may exhibit user interface issues.

 

Feel free to reach out to me if you have further questions

 

Regards

Srikanth

A user can directly import connections from Configuration Server (MOBIServer). In order for end user to be able to do that, mobile server administrator need to add the connections and their details in server.properties.


The list of parameters that can be used while defining connection in MOBI Server are as follows


Parameterin server.propertiesBasicSSOSUPSMPPossible Values
Name of connectionDisplayNameY
Type of connectionBOBJ_MOBILE_CONNECTION_TYPE_STRINGYBOESUPConnection, BOESMPConnection,
BOEConnection etc.
CMS Name or ClusterBOBJ_MOBILE_CMSY
Mobile Server or SUP/SMP Server URLBOBJ_MOBILE_URL (incase of Mobile Server)
BOBJ_MOBILE_SUP_SERVER (incase of SUP Server)
Y
AuthenticationTypeBOBJ_MOBILE_AUTH_METHODYsecEnterprise, secLDAP, secSAPR3, secWINAD
Is it a SSO connection?BOBJ_MOBILE_SSO_ENABLEDYtrue, false
Type of SSO Configured?BOBJ_MOBILE_SSO_TYPEYX509Certificate, SSO2COOKIE, SITEMINDER_BASIC,
TRUSTED_AUTH_Basic, TRUSTED_AUTH_FORM, SSO_Form, SSO2COOKIE_QueryString
If X509 Certificates used, then how are they configured?BOBJ_MOBILE_CERTIFICATE_REQUIRED_FOR_NETWORKYCertificateMandatory, CertificateOptional
URL that will provide SSO2COOKIEBOBJ_MOBILE_SSO_QUERY_URLY
Form that will generate SSO2COOKIEBOBJ_MOBILE_SSO_FORM_URLY
SSO Cookie Name if different than standardBOBJ_MOBILE_SSO_COOKIE_NAMEY
SAP R3 system in case of SSOBOBJ_MOBILE_SSO_SAP_SYSTEMYABC^200, XYZ^100 etc.
SUP Farm IDBOBJ_MOBILE_SUP_FARM_IDY
SUP/SMP Security Configuration NameBOBJ_MOBILE_SUP_SECURITY_CONFIG_NAMEYY
SUP PortBOBJ_MOBILE_SUP_PORTY
SUP/SMP Application IDBOBJ_MOBILE_SUP_APP_IDYY
SMP Proxy Connection NameBOBJ_MOBILE_SUP_PROXY_CONNY


As an administrator if you would like to create connections using SAP BI Links, you would like to have a ready list of parameters that are available to you for defining the connection correctly.

 

Parameter Description in SAP BI URLBasicSSOSUPSMPPossible Values
Name of connectionconnection_nameY
Type of connectionConnectionTypeYBOESUPConnection, BOESMPConnection,
BOEConnection etc.
CMS Name or ClustercmsY
Mobile Server or SUP/SMP Server URLserver_urlY
AuthenticationTypeauthTypeYsecEnterprise, secLDAP, secSAPR3, secWINAD
Is it a SSO connection?isSSOYYES,NO (in SAP BI Link)
Type of SSO Configured?SSOTypeYX509Certificate, SSO2COOKIE, SITEMINDER_BASIC,
TRUSTED_AUTH_Basic, TRUSTED_AUTH_FORM, SSO_Form, SSO2COOKIE_QueryString
If X509 Certificates used, then how are they configured?isCertificateRequiredYCertificateMandatory, CertificateOptional
URL that will provide SSO2COOKIEsso2CookieQueryURLY
Form that will generate SSO2COOKIEssoFormURLY
SSO Cookie Name if different than standardssoCookieNameY
SAP R3 system in case of SSOsapsysYABC^200, XYZ^100 etc.
SUP Farm IDSUP_Farm_IDY
SUP/SMP Security Configuration NameSec_ConfigYY
SUP PortSUP_PortY
SUP/SMP Application IDApplication_IDYY
SMP Proxy Connection NameproxyConnectionY

 

 

BOE connection


Add a connectionsapbi://addconnection?ConnectionType=BOEConnection&name=ConnectionName&server_url=ServerName/IP:Port&cms=101.01.01.01:Port&authType=AuthenticationType&default=yes/no
Delete a connection

sapbi://DeleteConnection?

ConnectionType=BOEConnection&name=Tom&server_url=10.53.10.10:8080&cms=10.53.10.10&authType=secEnterprise&default=no

Modify a connection

sapbi://ModifyConnection?ConnectionType=BOEConnection&ConnectionName_Prev=Conn1&ConnectionName_New=Conn2&Server_Url_Prev=10.53.10.10:8080&Server_Url_New=10.10.10.10

:1010&CMS_Prev=10.53.10.10&CMS_New=10.10.10.10&AuthType_Prev=secEnterprise&AuthType_New=secLDAP&default=yes&UserName_Prev=Administrator


SUP connection


Add a connection

sapbi://addconnection?ConnectionType=SUPConnection&Application_ID=MobiApp&Sec_Config=MobiSec&server_url=10.53.129.243&SUP _Port=5001&SUP_Farm_ID=0

Delete a connection

sapbi://DeleteConnection?ConnectionType=SUPConnection

Modify a connection

sapbi://ModifyConnection?ConnectionType=SUPConnection&Application_ID=MobiApp1&Sec_Config=MobiSec1&server_url=10.10.10.10&SUP_Port=5001&SUP_Farm_ID=0


Note: While modifying a connection normally you have to repeat each parameter twice - one with "Prev" and another with "New" suffix. However, in case of SUP connection that is not required. This is because you can have only one SUP connection.

SAP Mobile BI does not allow SSO connections to be created manually.

 

Following are the options for SSO connections


  • You can directly import these connections from the Configuration Server (MOBIServer)
    • Administrator can configure these connections at following location
      • Copy the server.properties from default folder in to custom folder (<WebAppsROOT>\MOBIServer\WEB-INF\config\custom)
      • Then modify the server.properties file in custom folder
    • Choose your new connection identifier, say we choose 'mysso'. Add that to mobi.connections
    • Provide the connection properties and save the server.properties file
    • Now deploy the MOBIServer again after changes mentioned above.Once done, you can execute the following URL to check if the properties are configured correctly or not. [http://<server>:<port>/MOBIServer/MobiConfigurationServlet?RequestType=ServerList ]             

 

       

  • You can use MDM tools to publish connections if devices are IOS7 and above
    • For devices with iOS 7 or higher, Apple provides the "Managed App Configuration" functionality. This functionality allows a Mobile Device Management (MDM) server to push down a configuration dictionary into the managed app's NSUserDefaults for the purpose of remotely configuring settings
    • You can configure a single predefined connection or multiple predefined connections in the application by specifying values for the conn.list.(n) property on the MDM server, where 'n' is the array index starting with a value of 1. Each array item is of the type "String" and the value of each item corresponds to a connection URL.
    • For example, you can specify a predefined connection URL for a BOE server connection with the syntax shown below

               conn.list.1=<specify the sap bi link for SSO connection here>


  • You can use SDK to generate build that already has connection created.


Useful Links


PS: Once you have created SSO connection on your device, you can always share that connection with other users. Choose that connection, click share and that will generate the link for you

Hello Mobi Users,

 

With the iOS 8 set to release this fall, we would like to understand which iOS version you are using today and what plans you may have to upgrade to iOS 8, once it becomes available. Today, App Store distribution by OS  shows us that 90% of iOS devices is already using iOS 7 ( link)

 

So that we can better plan for iOS 8 support, please respond to this short, 2-question survey (link below).

 

If you have additional questions/inputs, you can also reach me via this blog or email

 

Survey link: https://www.sapsurvey.com/cgi-bin/qwebcorporate.dll?idx=CVV5AX

 

Note: This survey ends by 8th August

 

Regards

Srikanth

http://scn.sap.com/servlet/JiveServlet/showImage/38-110215-491572/asugdcodeimage.png

 

Continuing with the Meet the Speaker ASUG SAP d-code speaker series I am pleased to introduce Peter Chen of Deloitte

 

He is presenting on session EA114 Practical Lessons from Deloitte Global's Successful Mobile BI Launch

 

From the abstract:

 

Deloitte Global began their mobile BI journey in late 2012, from prototyping, SAP BusinessObjects Business Intelligence 4.0 upgrade, mobile dashboard development, security evaluation and LDAP authentication, mobile app customization and deployment, to a successful launch. Practical lessons were learned along the way and are ready to be shared.

Peter PIC.png


About Peter (from the abstract) (pictured to the right, photo provided by Peter)

Peter has been working with SAP ERP/BW/BI/BPC since 1998, and has played progressive roles in SAP implementations. Currently Peter is responsible for the Deloitte Global Finance Reporting, which included the CFO dashboarding and Mobile BI roll-out

 

Questions:

 

What is your role at Deloitte?

I have been the Deloitte Global Finance Reporting manager, and the Enterprise BI architect prior to that. I am responsible for designing and delivering  analytical solutions; managing the BI best practices and roadmaps; supporting the DTTL BPC planning and forecasting processes; and implementing  BI projects---which include the Global Finance Mobile BI and Central Finance Mobile BI initiatives.

 

What is your professional background?

I started my career in EDS(HP)and I have been a SAP project leader and BW/BI/BPC Solution Architect with over 15 years of progressive experience in global SAP ERP/BW/BI support and implementations.   I am a member of the ASUG Mobile BI influence Council (see Power of ASUG Influence : How ASUG members Influenced SAP BusinessObjects Mobile BI Solution and Learn how ASUG Members Influenced BusinessObjects Mobile BI Solution

 

 

I have participated in the partners testing for SAP Design Studio, Lumira and Mobile BI.  See his blog The warehousing benefit of the SAP business warehouse......

 

After completing the B.Sc degree in Beijing University, I came to the United States for graduate study. Briefly studied in Georgia Tech, before completing the Ph.D. in biomedical research from Northwestern University, a post-doc program at University of Chicago, and Computer Career Program at DePaul University.

 

 

What are some fun facts about Peter?

 

I am a loyal 49ers fan who recently visited the 49ers’ brand new stadium in Santa Clara.

On the subject of superstition in sports:  My arrival had apparently brought good lucks to his favorite teams:

1) Studied in Georgia Tech in 1990 – coincided with the Yellow Jackets’ only final 4 appearance and football National championship.

2) I arrived in Chicago in 91, when the Chicago Bulls started their historic 6-peat.

3) I visited SF the first time in 94, when the 49ners overcame the Cowboys that had beaten them the previous 2 years.

I am looking forward to his ASUG Mobile BI session at SAP d-code Las Vegas.  For a complete list of ASUG sessions, click this link.

 

 

You can follow Peter on twitter at @ccpg04

 

Join ASUG and other community members at SAP d-code Las Vegas

 

SAP d-code 2014 LAS VEGAS
OCTOBER 20-24
Venetian/Palazzo Congress Center


Save the date Monday, October 20th for ASUG SAP d-code Pre-conference Day


Related:

ASUG SAP d-code SAP BW 7.4 powered by SAP HANA Speaker - Introducing Pawel Mierski

ASUG SAP d-code Sessions Are Published - Featuring SAP Mentors

SAP's Srikanth R Rao K provided this webcast.  Documentation is also now live here – http://help.sap.com/boall_en

 

Mobile BI 6.0.3 for iOS is available today from iTunes.  The Android version will be available in a week (planned)

 

1favorites.png

Figure 1: Source: SAP

 

Figure shows Favorites as an actionable icon

2defaultfavorites.png

Figure 2: Source: SAP

 

If documents are marked as favorites, favorites will default

3doclinks.png

Figure 3: Source: SAP

 

Documents requiring an online connection have distinct thumbnail

4wifi.png

Figure 4: Source: SAP

 

Automatic updates of documents when connected to WiFi

5offline.png

Figure 5: Source: SAP

 

Work offline button is available as shown in Figure 5.

6smp.png

Figure 6: Source: SAP

 

SAP Mobile Platform 3.0 is and Cloud is supported by MobI (except Dashboards is not supported on SMP Cloud)

7mdm.png

Figure 7: Source: SAP

 

Figure 7 covers configuration support for iOS7 devices

8webi.png

Figure 8: Source: SAP

 

Figure 8 shows Geo enhancements for SAP BusinessObjects Web Intelligence

9chart.png

Figure 9: Source: SAP

 

Figure 9 shows chart improvements and the server dependency.

10filters.png

Figure 10: Source: SAP

 

Offline table filter is similar to Excel, table with 100 rows and apply filter on columns

11persviewenh.png

Figure 11: Source: SAP

 

Starting this release support personal views with Prompts

 

Also supports sections with personal views

12persvieinput.png

Figure 12: Source: SAP

 

Show meaningful filter values

 

Only see filter values selected in the prompt window

 

Hierarchical input controls supported

13alias.png

Figure 13: Source: SAP

 

Alias is easier for you to remember

 

Table actions performed and can be retained - sort

 

14alerts.png

Figure 14: Source: SAP

 

Figure 14 shows updates for personal views; can access offline

15webiperf.png

Figure 15: Source: SAP

 

Complex server operations now avoided; being more efficient

 

Users do not need edit rights to mobilize documents

 

Note server dependency

16lumira.png

Figure 16: Source: SAP

 

For Lumira, they have enabled caching – subsequent access will be faster

 

Available in apps store – download to today and test new features

 

SDK version is available

 

Documentation is live too

 

Android

17ui.png

Figure 17: Source: SAP

 

Android is up to speed of iOS

 

More features are seen on the Android.

 

Favorite document is now available in Android

18newcat.png

Figure 18: Source: SAP

 

Category management was not available on Android device – assign documents to categories

 

Also includes BI Inbox Support

 

SSO support for Androids as well

 

SSO Kerberos for Android is not supported yet

25DESIGNSTUDIOONANDROID.png

Figure 19: Source: SAP

 

Figure 19 shows support for SAP BusinessObjects Design Studio on the Android.

 

Other Android Features coming:

 

  • Personal views from Web Intelligence now supported on Android
  • Catchup features include Micro Bar Chart supported on Web Intelligence – follow special syntax
  • Geo enhancements POI for Android


Android will be available in 1 week

SDK in SMP in 1 week

 

26biplatformdep.png

Figure 20: Source: SAP

 

Figure 20 shows the server prerequisites.

 

Question and Answer

Q: Is there any plans to allow opendocument documents to saved to personal views?

A: Opendoc links can be accessed for offline - not saved to personal views - something to consider for future.‑

________________________________________________________________

Q: is the new version of Mobile 6.0 is BOE platform dependent - meaning does it work on BOE 4.1 SP2 or only works after 4.1 SP03 onwards...?

A: See slide for prerequisites‑

________________________________________________________________

Q: are these saved prompts on the client or on the BO servers?

A: Saved prompts are on the client.‑

________________________________________________________________

 

Q: For security reason, we had to disable the Document download icon. Since then, we are unable to assign Favorites and Categories. When will the Document download "unlink" from Favorites/Categories?

A: Working on this feature for H2 release‑

________________________________________________________________

 

Q: do you have any plan to support PDF files exposed thru mobile devices. e.g. if you create a hyperlink in BOE to read a PDF document and assign it to mobile category. From mobile, click on the report icon, and open the PDF file inside of the mobile app.

A: This works as of today. ‑

________________________________________________________________

Q: What is the roadmap for a Win 8.1 version?

A: Closely monitoring the market for Windows 8‑

________________________________________________________________

Q: any plan to make it work inside of mobile

A: PDF works within Mobile; if want to access agnostic documents - currently not possible but considering going forward‑

________________________________________________________________

Q: Availability date  of Mobi 6 SDK ?

A: Available today for iOS‑

________________________________________________________________

 

Also see Power of ASUG Influence : How ASUG members Influenced SAP BusinessObjects Mobile BI Solution

Late today I saw on twitter that the latest release of BusinessObjects Mobile 6.0.3 iOS was released.  So what is new?  It is listed on iTunes at SAP BusinessObjects Mobile on the App Store on iTunes

 

What's New in Version 6.0.3

• Support for SAP Mobile Platform 3.0

• Support for SAP Mobile Platform, cloud edition

• User experience improvements

• MDM configuration support for iOS 7 devices

• Support for local table filtering for SAP BusinessObjects Web Intelligence documents

• Personal views, geo analysis, and performance enhancements for SAP BusinessObjects Web Intelligence documents

• Technical enhancements

 

Source: iTunes/SAP

 

Looking at the user experience improvements, I noticed the following:

 

fig1.PNG

 

Figure 1

 

Figure 1 shows adding to favorites is available as a separate action.

2fig.PNG

Figure 2

 

Figure 2 shows new icons for what can be downloaded to the device and what cannot.  I also selected eFashion document as a "favorite".

3fig.PNG

Figure 3

 

The next time I log on to Mobile BI, it takes me straight to "Favorites" instead of "All Reports" as shown in Figure 3.

4figwifi.PNG

Figure 4

 

Figure 4 shows a new feature to automatically update documents when connected to wi-fi.

5fig.PNG

Figure 5

 

Figure 5 shows the Work Offline button is now available in the Connections listing on the left panel.

 

On twitter, I was told this:

I haven't downloaded the ESRI trial and I am not a big user of Web Intelligence, but I may try.

 

The SAP Help has not been updated yet but when it is it will be at SAP BusinessObjects Mobile for iOS – SAP Help Portal Page

 

I am sure we'll hear more details next week on this ASUG webcast:

Read me

SAP BI Mobile Server Single Sign On Support


This is a specific case where mobile server does not support what you want. This option allows you to write your own java class which implements the method "public String getUser(HttpServletRequest request)". At run-time, when configured for custom scenario, mobile server will call this method of given class and provide it with HTTP Servlet Request. In this method you can write your custom code to parse the request and return the user id back. Mobile server will take this user id and log you on to BOE using trusted connection.


[Sample class attached]


The class can be packaged and deployed as follows

  • You need to place the class in respective package inside <WebAppsROOT>\webapps\MobileBIService\WEB-INF\classes
  • If you have any dependent libraries you should copy them to <WebAppsROOT>\webapps\MobileBIService\WEB-INF\lib. Just ensure that your libraries are not already present in this folder.
  • You must note that, when you upgrade mobile server. You need to backup the class and respective libraries that you had copied and apply the changes again to make SSO work.


Now, lets see how to configure mobile server for this scenario


Prerequisites

  • Your environment should ensure the authentication of user
  • After authentication is done, your custom class is responsible for parsing the request and provide user Id
  • SAP Business Objects BI platform configured for trusted authentication


First step

is to enable the Authentication Scheme

  • Copy the authscheme.properties from default folder in to custom folder (<WebAppsROOT>\webapps\MobileBIService\WEB-INF\config)
  • Then modify the authscheme.properties file in custom folder
  • Un-comment line 'TRUST_CUSTOM=com.businessobjects.mobilebi.server.logon.impl.TrustedCustom'
  • Save and close the file


Second Step

is to define the default SSO configuration

  • Copy the sso.properties from default folder in to custom folder (<WebAppsROOT>\webapps\MobileBIService\WEB-INF\config)
  • Then modify the sso.properties file in custom folder
  • Choose your default CMS identifier
    • "default.cms.identifier=abc"
  • Now define your authentication scheme (the one that you have enabled in first step)
    • abc.authentication.scheme=TRUST_CUSTOM
  • Now configure all the properties using this identifier as below
    • abc.aliases=boe.xyz.corp:6400
    • abc.authentication.type=secEnterprise
    • abc.product.locale=en_GB
    • abc.preferred.viewing.locale=en_GB
    • abc.trusted.auth.sharedsecret=<copy the shared secret here>
    • abc.authentication.type=secEnterprise
  • You need to additionally configure the header name that you shall be using to provide the user ID
    • abc.trusted.auth.user.param=<fully qualified name of your custom class>
    • abc.trusted.auth.user.retrieval=CUSTOM
  • Save the sso.properties file.

 

Third Step

is to now deploy the MobileBIService again after changes mentioned above. Once done, you can validate if your SSO has been setup correctly by executing following URL from browser

 

http://<server>:<port>/MobileBIService/MessageHandlerServlet?message=CredentialsMessage&requestSrc=ipad&data=<logon logonViaSSO="true"/>

 

Note: While executing the URL in browser, you should be sending the request with the authentication data that you expect your custom class to parse.


Read me

SAP BI Mobile Server Single Sign On Support


SSO connections for Mobile BI Client - Users do not create these connections manually, instead they can directly import these connections from the Configuration Server (MOBIServer)

 

Steps

  • Administrator can configure these connections at following location
    • Copy the server.properties from default folder in to custom folder (<WebAppsROOT>\MOBIServer\WEB-INF\config\custom)
    • Then modify the server.properties file in custom folder
  • Choose your new connection identifier, say we choose 'mysso'. Add that to mobi.connections
    • mobi.connections=mysso
  • Choose a display name for your connection
    • mysso.DisplayName=Corporate_BI
  • For any SSO connection the first property that you need to enable is
    • "mysso.BOBJ_MOBILE_SSO_ENABLED=true"
  • For providing identity on client via Basic Auth
    • mysso.BOBJ_MOBILE_SSO_TYPE=TRUSTED_AUTH_BASIC
  • Else for providing identity on client via Form Auth
    • mysso.BOBJ_MOBILE_SSO_TYPE=TRUSTED_AUTH_FORM
  • Configure CMS as follows (It should be noted that this value should match with <id>.aliases properties configured in sso.properties at mobile server, else you will get MOB00902 error, null is not a valid authentication scheme)
    • mysso.BOBJ_MOBILE_CMS=boe.xyz.corp:6400
  • Additionally following properties need to be configured
  • Save the server.properties file


Now deploy the MOBIServer again after changes mentioned above. Once done, you can execute the following URL to check if the properties are configured correctly or not


http://<server>:<port>/MOBIServer/MobiConfigurationServlet?RequestType=ServerList


In response, you should be seeing an XML with the configured properties as Key Value Pairs inside connection tag.



Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document

Hi All,

 

We know, there are Mobile logs available which give us some insight while accessing documents, refresh, view, filters , crash reports etc.

However, no information is captured for network communication between the device and the BO server.

 

Most of us are aware about a tracing tool called Fiddler (www.telerik.com/fiddler)

We can try to enable fiddler in such a way that , it captures all the traffic between your Mobile device ( ipad/iphone/android/BB) to your SAP BI Servers.

It turns out to be useful, when you have HTTPS or SSO configured. It can also be used simply to understand, how the network traffic is routed.

 

Pre-requisite:

  • Mobile device connected to your BO server/Mobile Server.
  • Enable to open and view documents on your device.
  • Knowledge about proxy settings.
  • Ensure you have administrator access on your machine/BO server.

 

Lets Start:

 

Download and install Fiddler on your Server. Before you start Fiddler, make sure all browsers are closed, else it will start capturing all the network traffic instantly.

 

fiddlersetoptins.png

 

Navigate to Tools> Fiddler Options.

 

 

fiddlerconnections.png

Go to Connections tab. Check Allow remote computers to connect. The default port fiddler communicates is 8888. You can alter it as per your requirements.

 

proxy.PNG

 

Go to your mobile device, i am using IPAD. General> Settings>Wi-Fi

Under your connection, go to HTTP Proxy.

 

Assign IP address or hostname of your BO Server and assign Port 8888 ( Fiddler listening port )

We have done this to ensure that our network traffic is routed through BO server, which will enable Fiddler to listen and capture traffic.

 

We are now ready to start tracing...

At this stage, try to login to your SAP BI application from the device and check if you see some readings observed in Fiddler.

If you are getting nothing in there, you need to check and verify the following:

 

1) Proxy connection route

2) Firewall blocking port 8888

 

If you are attempting this on a local server with direct wifi access to ipad, it will be much simpler.

In case of fortified environments, it is best that you take assistance of your Network administrator to know the proxy routes or internet settings to be done.

 

If all is good, you can try to open a report on device and see the trace captured in fiddler as shown below:

 

refresh.PNG

 

Access a document on your device and hit refresh.

 

trace.png

Observe traces being generated from your ipad to the BO server.

 

The communication is currently capturing default port 8080, as well as 8443 which is SSL enabled server.

On the right side, you can see the report id, sent for refresh.

 

Hope this helps!

 

Do share your feedback

 

Regards,
Atul B

Folks,

 

This blog is for those who have recently acquired mobile devices and want to allow user to access it and restrict rights for the same.

For the REST, feel free to go through and share your feedback for any improvement.

 

To start with, lets see what are we dealing with:

 

You have a scenario set up already. Users are accessing reports. Daily work is going on fine. Then one fine day, you have 20 ipad devices to be deployed and customized for use.

Now comes the task of assigning users, categories, reports on ipad.

 

For getting started: Read This First

 

How to Connect SAP BO Mobile to a BI Server 4.0

 

How to Add Categories in Mobile

 

If you are already familar to the concept, below is the step to JUST DO IT

 

I will explain a step by step scenario to get this done.

 

PLEASE NOTE: This is what i did on my test machine. Hence, would request all readers to kindly play on a test machine first, rather than messing up the rights on your working system. As you all know, how frustating that can be!!

 

======================================================

We start with a test user: ipad and his folder called : ipad

Category: FINANCE

Report added to ipad folder

======================================================

 

newuser.png

  Create a test user ipad

 

ipadandfolder.png

ipad folder created and a report is assigned to it.

rootfolderrights.png

To make sure that ipad user is only able to view ipad folder and its contents

ipadfolderright.png Universesrights.png

 

 

 

 

 

 

 

Universe, connections and folder rights assigned for the ipad user as shown

  connsecurity.png

categories.png

Category Finance created

financecategorysecurity.png

Assign full control for the user ipad under FINANCE category

reportassingedtofinance.png

Report assigned to finance category.

PLEASE NOTE: this report should also be present under Mobile category, without which it wont be eligible to be displayed on the mobile device

 

mobilecategorysecurity.png

 

 

 

 

 

 

 

 

 

 

 

 

 

Rights for the principal ipad for Mobile category ( if you have MobileDesigned category as well, same applies )

 

 

The configuration part is done.

Ensure now, that you are able to login to launchpad with the test user, able to see the folder, ipad, the report inside it. Able to refresh it ( if given rights for the same )

 

Now, login to ipad with the test user ipad.

connection.PNG

                                                                                 ipad user login details

 

finale.PNG

                                                               Able to see the FINANCE category and the report assigned to it.

 

Success finally!!

 

Check the Categories note added in the beginning of this blog, if you need clarifications about categories.

 

Hope this helps.

Please share your feedback.

 

Regards,

Atul B

Read me

SAP BI Mobile Server Single Sign On Support


SSO connections for Mobile BI Client - Users do not create these connections manually, instead they can directly import these connections from the Configuration Server (MOBIServer)

 

Steps

  • Administrator can configure these connections at following location
    • Copy the server.properties from default folder in to custom folder (<WebAppsROOT>\MOBIServer\WEB-INF\config\custom)
    • Then modify the server.properties file in custom folder
  • Choose your new connection identifier, say we choose 'mysso'. Add that to mobi.connections
    • mobi.connections=mysso
  • Choose a display name for your connection
    • mysso.DisplayName=Corporate_BI
  • For any SSO connection the first property that you need to enable is
    • "mysso.BOBJ_MOBILE_SSO_ENABLED=true"
  • Configure CMS as follows (It should be noted that this value should match with <id>.aliases properties configured in sso.properties at mobile server, else you will get MOB00902 error, null is not a valid authentication scheme)
    • mysso.BOBJ_MOBILE_CMS=boe.xyz.corp:6400
  • Additionally following properties need to be configured
  • If you intend to perform single sign on via X509 certificate
    • mysso.BOBJ_MOBILE_SSO_TYPE=X509Certificate
  • If web application server that hosts mobile server, mandates incoming requests to have certificates
    • mysso.BOBJ_MOBILE_CERTIFICATE_REQUIRED_FOR_NETWORK=CertificateMandatory
  • If web application server that hosts mobile server, does not mandate incoming requests to have certificates i.e. optional. If user denies to use the certificate User/Password would be the fall back option
    • mysso.BOBJ_MOBILE_CERTIFICATE_REQUIRED_FOR_NETWORK:CertificateOptional
  • Save the server.properties file


Now deploy the MOBIServer again after changes mentioned above. Once done, you can execute the following URL to check if the properties are configured correctly or not


http://<server>:<port>/MOBIServer/MobiConfigurationServlet?RequestType=ServerList


In response, you should be seeing an XML with the configured properties as Key Value Pairs inside connection tag.



Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document

Read me

SAP BI Mobile Server Single Sign On Support


SSO connections for Mobile BI Client - Users do not create these connections manually, instead they can directly import these connections from the Configuration Server (MOBIServer)


[In case you are using SUP Legacy connection or SMP Rest connection, have a look at the attached server.properties files]

 

Steps

  • Administrator can configure these connections at following location
    • Copy the server.properties from default folder in to custom folder (<WebAppsROOT>\MOBIServer\WEB-INF\config\custom)
    • Then modify the server.properties file in custom folder
  • Choose your new connection identifier, say we choose 'mysso'. Add that to mobi.connections
    • mobi.connections=mysso
  • Choose a display name for your connection
    • mysso.DisplayName=Corporate_BI
  • For any SSO connection the first property that you need to enable is
    • "mysso.BOBJ_MOBILE_SSO_ENABLED=true"
  • Configure CMS as follows (It should be noted that this value should match with <id>.aliases properties configured in sso.properties at mobile server, else you will get MOB00902 error, null is not a valid authentication scheme)
    • mysso.BOBJ_MOBILE_CMS=boe.xyz.corp:6400
  • Additionally following properties need to be configured
  • If your mobile server is deployed in such a way that a custom application logs on to SAP system and comes back with a logon ticket, in that case the steps for creating a connection would be as follows
  • If your mobile server is deployed in a way to present a FORM to the end user
  • Save the server.properties file


Now deploy the MOBIServer again after changes mentioned above. Once done, you can execute the following URL to check if the properties are configured correctly or not


http://<server>:<port>/MOBIServer/MobiConfigurationServlet?RequestType=ServerList


In response, you should be seeing an XML with the configured properties as Key Value Pairs inside connection tag.



Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document

Read me

SAP BI Mobile Server Single Sign On Support


SSO connections for Mobile BI Client - Users do not create these connections manually, instead they can directly import these connections from the Configuration Server (MOBIServer)

 

Steps

  • Administrator can configure these connections at following location
    • Copy the server.properties from default folder in to custom folder (<WebAppsROOT>\MOBIServer\WEB-INF\config\custom)
    • Then modify the server.properties file in custom folder
  • Choose your new connection identifier, say we choose 'mysso'. Add that to mobi.connections
    • mobi.connections=mysso
  • Choose a display name for your connection
    • mysso.DisplayName=Corporate_BI
  • For any SSO connection the first property that you need to enable is
    • "mysso.BOBJ_MOBILE_SSO_ENABLED=true"
  • Configure CMS as follows (It should be noted that this value should match with <id>.aliases properties configured in sso.properties at mobile server, else you will get MOB00902 error, null is not a valid authentication scheme)
    • mysso.BOBJ_MOBILE_CMS=boe.xyz.corp:6400
  • Additionally following properties need to be configured
  • For Siteminder configured for Basic Auth
    • mysso.BOBJ_MOBILE_SSO_TYPE=SITEMINDER_BASIC
  • For Siteminder configured for Form Auth
    • mysso.BOBJ_MOBILE_SSO_TYPE=SITEMINDER_FORM
    • mysso.BOBJ_MOBILE_SSO_FORM_URL=<logon form URL>
  • Save the server.properties file


Now deploy the MOBIServer again after changes mentioned above. Once done, you can execute the following URL to check if the properties are configured correctly or not


http://<server>:<port>/MOBIServer/MobiConfigurationServlet?RequestType=ServerList


In response, you should be seeing an XML with the configured properties as Key Value Pairs inside connection tag.



Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document

Actions

Filter Blog

By author:
By date:
By tag: