SAP Explorer

SAP Explorer Views with Geographical Data

SAP Explorer has become one of the most useful tools in the Business Objects Toolkit, although sometimes we do not appreciate all its potential. If our data set has one or more geographical dimensions, like city, country, state.., we should use the geographical variable types for these dimensions. This kind of dimensions allow us to introduce map analytics in our Exploration Views, which is a plus. Below we will proceed to explain the needed steps in order to set up these dimensions and explain how to better use them. First of all, we need to log on SAP Explorer with an account with permission to "Manage Spaces".

After this step, we should go to "Manage Spaces" and, either select the existing Exploration View that we want to modify with geographical data, or we create a new one.

Then we should go to the "Objects" tab. There, we will put all the dimensions and measures that we want to show in the Exploration View. We will select the geographical dimension, "Zone Destination Detail" in the example, and  change the "Dimension" field to "Geography". dimension geo1 After this, we should click on the "..." field and choose the type of "Geographical Level" this dimension has. We can select "Country", "Level 1", "Level 2" and "City". Level 1 and 2 are for regions, states, etc. dimension geo2 With the "Geographical Level" selected, we need to click on the "Load" button. At this point, the application tries to match the dimension values with a geographical place on the selected level. After few seconds, the below image will appear: dimension geo3 Here we will see the following values:

-"Matching": when the values are found

"To Define": when the application finds something but requests for a check up or there are several similar values  and it asks for a confirmation

- "Unlocalized": when the values are not found

We could "Index" the Exploration Spaces with "To Define" and "Unlocalized" values but they will not appear in the map. At this point, we need to do a manual search and check one by one the not matching values, clicking on "Propositions". We will be able to select one of these options given by the application, hide it with "Hide In Geography Chart" or try to find a place close to the value.

dimension geo4 When we finish selecting all the values that we want to show and the Exploration View is ready, we will proceed to index it.

Finally, we will be able to see the results of using this kind of geographical data. For that, we will open the Exploration View and select the Dimension for "displaying". Then the "Geography" option will be available, we just need to click it and see the results.

dimension geo5We will also be able to create "Information Spaces" of these Dimensions:

dimension geo6

Moreover, this tool allows us to see all this information on the Mobile Application.

dimension geo7 dimension geo71

dimension geo8

As a conclusion, using this kind of dimensions slightly improves the possibilities of our Exploration Views and their analysis.

We hope this post helps you when you start using Geographical Data in your Exploration Views.

If you have any questions or comments, do not hesitate to add a comment below.

Running SAP BusinessObjects Explorer on top of SAP BW

Running SAP Explorer on top of BW This blog describes the only successfully tested way to run SAP Explorer on top of SAP Netweaver Business Warehouse (SAP BW) info-providers. This is not a straight forward configuration and it requires knowledge of Information Design Tool, Data Federator Administration Tool and SAP Logon application for SAP BW.

The supported connection by SAP Explorer to explore data on top of SAP BW info-providers is through a Relational Universe using a JCo (Java Connector). But this connection does not work with just configuring the right parameters for the JCo connector in IDT, it requires some additional adjustments to be done on the SAP BusinessObjects - SAP BW environment.

Here is a quick brief on some topics to be considered (how-to not explained in this blog post):

  1. It is a recommendation from SAP to split (size) the Adaptive Processing Server in up to 6 different APSs and isolate this way some of the services (SAP KBA 1694041)
  2. Make sure Data Federation Service in included as a service in your current APS
  3. Make sure the user you are using for creating the relational connection is propertly granted in SAP BW (SAP KBA 1604227)
  4. Make sure with your IT team that there are no firewall activities or blocked ports that can make the connection fail

Step 1: Creating a Relational Connection in IDT:

Open IDT, create a new Relational Connection - SAP - SAP NetWeaver BW - SAP Java Connector (SAP JCo) and configure all the connection details required. As soon as you finish the configuration and test the connection, you will get the error message #1:

There is another connectivity issue (error #2) you might face, after completing the steps, in this blog article you will learn how fix both of them:

com.businessobjects.datafederator.sourcedefiner.connection.ConnectionExce ption: com.sap.connectivity.cs.java.drivers.DBDError: [Data Federator Driver] [Server] [Connector 'SAP Testing'] No RFC destination was defined for the server 'SIA.AdaptiveProcessingServer2'

Step 2: Creating a RFC destination in SAP Logon App:

By using the transaction SE37 and using the function module "RSDRI_DF_CONFIGURE" you will create the RFC destination.

This is the crucial part of this configuration, the RFC destination must be created specifically in the same way SAP recommends in this link:

http://wiki.scn.sap.com/wiki/display/BOBJ/BW+With+RFC+JCO+Connections+In+Information+Design+Tool

Take a look at the section "Steps for Manual Configuration" and complete your RFC destination as follows:

  • Make sure you set an empty value for the I_ONLY_CHECK parameter
  • Make sure you set an empty value for the I_REMOVE_CONFIGURATION
  • Complete I_RFC_DESTINATION as requested. To give an example if your SAP BusinessObjects server is called MYBOSRV the value for I_RFC_DESTINATION must be DF_JCO_MYBOSRV_1

After doing this, error #2 will be gone.

Step 3: Configuring Data Federation Administration tool properly

In Data Federation Administration Tool, under "Connector Configuration" you will find the Relational Connection created in IDT. Create a configuration for the connection mentioned accordingly with the content in the SAP Logon transaction SM59 - TCP/IP Connections (where you will find the DF_JCO_MYBOSRV_1 connection created in Step2).

You must make sure that these three parameters have the correct values as per your DF_JCO_MYBOSRV_1 in SM59:

  • gatewayServiceName: same value as in SM59
  • gatewayHostname: same value as in SM59
  • programIDMapping: concatenate your SIA name + Adaptive Processing Server name = DF_JCO_MYBOSRV_1

Step 4: Modifying "reginfo.dat" file in BW system:

By using SAP Logon transaction SMGW you will have access to the "reginfo.dat" file in which we will perform a quick change. Navigate to Goto - Expert Functions - External Security - Display (Reg. Info).

As per SAP note 1806694, you will add one line in this file. The easiest way to perform that for me was to search in the SAP BW server for the file "reginfo.dat" and edit it manually. After this, go back to SMGW transaction in SAP Logon and go to Goto - Expert Functions - External Security - Reread (global). You should see the line added in SAP Logon when you display the file again. The line to be added is:       P TP=* HOST=<server as per ProgramIDMapping> CANCEL=* ACCESS=*

Where <server as per ProgramIDMapping> means your BO server where SAP Explorer is installed.

Summary

If you have completed all the steps in this blog and you try to test your relational connection in IDT, it will work!

So now, you are able to test the relational connection in IDT as well as able to create a Data Foundation and Business Layer on top of it. After publishing the Relational Universe into your repository, you will find the universe avaiable in SAP BusinessObjects Explorer and you will be able to create an Information Space and index it.

Migrating SAP BusinessObjects Explorer spaces to BI4

This article explains how we overcame the challenges faced when moving the content of Explorer Information Spaces from an old environment to a new one, while doing a SAP BI4 migration for one of our biggest customers.

In case you didn't know, Explorer migration is not supported out of the box in the Upgrade Management Tool or any other tool, which left us no choice but to rebuilt everything our customer had in the old environment (Information Spaces, Exploration Views, Bookmarks, Etc) in a new one.

It was not too straightforward as the universe the Information Space was built on had many objects with the same name, but in different classes, which made it difficult to identify which objects were actually being used.

I will share a set of steps we followed in order to:

  • ease content rebuild through:
    • web intelligence export
    • universe design object name change
  • improve user adoption with tomcat web server redirection

 

Optimizing the content re-build via export to WebIntelligence

Explorer spaces do not show the class an object comes from. This becomes a big issue when dealing with big universes with many objects with the same name. What can you do to overcome this issue?

 1) Within the information space to rebuild (source environment), click on the “export the chart or data” button and choose the WebI option to send the information space to you inbox as a WebI document.

1

2

3

4

2) Once the WebI document is in your inbox, you need to enter the edit mode and click on every object in the query to highlight them in the left pane, this way you will clearly identify which class each object is coming from.

While working in explorer there is not an easy way to know which class the object is coming from, so performance issues could be caused accidentally by choosing a wrong object. Therefore by having WebI and Explorer opened at the same time, we can re-create the Information Space much quicker and safer.

5

 

Ensuring the explorer variables are made from the correct objects

3)  Coming back to Explorer, in the “Add calculated measure” options, the first and second measure box sizes are fixed, this makes it tricky to pick the correct measures when the name is too long, therefore it is recommended to temporally rename the measure at a Universe level to make sure we are picking the right measure. If you don't do it, there is a risk that the measure that Explorer chooses is a random one despite of your selection. Taking the precaution ensures that our query picks up the correct objects.

6

 

4) The new Information Space can be finalized and saved.

 

Using a Tomcat re-direction for existing hyperlinks

A bookmark is a hyperlink fixed address to the Explorer space with a particular data selection and graph configuration. The problem with explorer bookmarks is not only that they cannot be migrated but also that the address will change in the destination so any previously distributed link would become invalid when the old environment is shut down, the solution for this is to recreate the bookmarks from scratch in the new environment.

In our case there were already many bookmarks created within the old environment and the costumer did not want to lose the existing hyperlinks, therefore we came up with a way of redirecting the traffic to the new tomcat server. Here are the steps we followed:

1) Get the bookmarks created in the old environment from the users in order to replicate them in the new environment.

A bookmark looks like this: http://server-name/explorer/index.jsp?application=portal&documentId=c62cffe8-dc4c-45cd-ac74-69a94c5faeae&bookmarkId=1a90a0a6-6def-4653-a1e0-74fbd585787b How it is composed: http://SERVER-NAME/explorer/index.jsp?application=portal&documentId=INFORMATION-SPACE-ID&bookmarkId=BOOKMARK-ID

2) Record & Reproduce selections (measures, facets, sorting) in the Information Space:

Identify every measure, facet and sorting used for every bookmark to reproduce it on the new environment.

 

3)   Create a script to redirect the traffic from the old web server (Tomcat) to the new web server (Tomcat) at the beginning of the index.jsp file in the following path SAP BusinessObjectsTomcat6webappsexplorer to make it impact free for the users.

String Application = (String) request.getParameter("application");
String DocumentId = (String) request.getParameter("documentId");
String BookmarkId = (String) request.getParameter("bookmarkId");
 
if (Application == null && DocumentId == null && BookmarkId== null ) {}
 
else if (DocumentId.contains("A")&&BookmarkId.contains("B"))  {
                   response.sendRedirect("http://nlrat-wias117/explorer/index.jsp?application=portal&documentId="+"C"+"&bookmarkId="+"D");}
 

Where:

Old Environment: A: Information Space ID B: Bookmark ID

New Environment: C: Information Space ID D: Bookmark ID

 

Summary

After following these sets of steps, you should be able to replicate the content of SAP BusinessObjects BI Explorer in a new environment with minimal user impact. The benefits of following these best practices are:

  • High user acceptance of a BI4 migration
  • Ease of migration of SAP BusinessObjects BI Explorer
  • Save hours of work while migrating SAP BusinessObjects BI Explorer

I hope this article is useful to you and it brings positive feedback from your end users. Please feel free to leave a comment or question below.

Scheduling SAP BI Explorer spaces based on events

Users frequently find their explorer spaces and exploration views displaying outdated information. Indeed this can happen if the source data is not ready when the indexing process is scheduled to start at a fixed time, so a manual re-run is needed when the data is available to ensure data freshness. Unfortunately scheduling explorer spaces is not possible in the current 3.x or 4.x versions of SAP BusinessObjects BI, but a workaround has been recently applied in one of our customers which we detail in this article.

 

Emulating the trigger effect

The idea is to schedule explorer spaces processes very frequently during the day under a SAP BusinessObjects account specifically created for these spaces. This account will have its password changed automatically when the indexing is not desired causing the process to automatically fail.

When the indexing is needed the password will be set automatically to its original value for a short time so it triggers the information update.

The change of account password technically occurs using a Program object which can be added and managed from the CMC (Central Management Console) and it is written in .NET SDK language

What happens behinds the scenes is totally transparent for the users, as they will just see 1 single indexing process executed once a day, at the desired variable time.

 

The process

 At a high level the process involves the following steps:

1) Check platform prerequisites for this method

2) Create an auxiliary BusinessObjects Enterprise account with a password associated to the  “non-working” status of the schedule and sufficient rights to schedule the space

3) Create of a VBS script that changes this password to the one password associated to the  “working” status of the schedule for around 20 minutes, then back to the previous password

4) Schedule a program containing the VBS script in BOE

5) Configure the scheduled explorer space, using the auxiliary account and the password associated to the  “working” status of the schedule, to be run every 10 minutes

 

The process explained

The process will be explained using a real example.

Let’s choose “explorerBPE” as a BO account name, and choose “Inactive01” and “Active01” as passwords. The BO server name is “CMSNAME” and the data readiness is indicated when the event “BPESourceReady” is triggered.

1) The following conditions need to be met for the process to work correctly:

1.1  BOE needs to allow running scripts (CMC > Applications > CMC > Program Object Rights): Run scripts/binaries & Run java programs

1.2  BOE needs to have the following properties  unticked from CMC > Authentication > Enterprise :

i. Cannot reuse the N most recent password(s)

ii. Must wait N minutes(s) to change password

 

2) Create a BusinessObjects Enterprise account “explorerBPE” with the password “Inactive01” and sufficient rights to index the explorer space.

Explorer BPE

 

3) Create a VBS script that changes this password to “Active01” for around 20 minutes, then back to “Inactive01”, find it below. You can copy and paste this text inside a file and rename it with the .vbs extension. The letters in bold can be customized according to your needs.

BPEexplorerChangePassword.vbs

Dim oSess
Dim Users, User
Dim UserInterface
Dim dteWait
Const CMS = "CMSNAME:6400"
Const UserID="explorerBPE"
Const Password = "Inactive01"
Const Aut = "Enterprise"
Set oSessionManager = CreateObject("CrystalEnterprise.SessionMgr")
Set oSess = oSessionManager.Logon(UserID, Password, CMS, Aut)
Set iStore = oSess.Service("", "InfoStore")
Set Users =  iStore.Query("SELECT SI_ID FROM CI_SYSTEMOBJECTS WHERE SI_PROGID='CrystalEnterprise.USER' and SI_NAME ='" +  "explorerBPE" + "'")
Set User = Users.Item (1)
Set UserInterface = User.PluginInterface ("")
UserInterface.ChangePassword "Inactive01","Active01"
iStore.Commit (Users)
dteWait = DateAdd("s", 1200 , Now())
Do Until (Now() > dteWait)
Loop 
UserInterface.ChangePassword "Active01","Inactive01"
iStore.Commit (Users)
oSess.Logoff()

 

4) Schedule the program on BOE, based on a source Trigger

 Upload the .vbs program as a Program Object:

 

.vbs program as a Program Object

 

Schedule to start every day at midnight:

Scheduling recurrence

Configure the schedule to run depending on a BusinessObjects event:

4

 

5) Configure the Explorer space Scheduling to use the “explorerBPE” and “Active01”, to be run every 10 minutes

Configure Explorer Space

 

Now we can test the solution in our space:

Test the solution

 

For an event which happens around 6am every day, the load has succeeded at 6:11am, which is what we wanted to achieve.

 

Benefits

With this method our data actualization in SAP BI Explorer 3.x or 4.x will be more reliable and error proof,  reducing the dependency on manual intervention.

If you have questions about this method, or if you want to share your experience or tips, please feel free to leave a comment.

Using Google Chrome with SAP BusinessObjects

We all know that there are many internet browsers available, but definitely Google Chrome is one of the most used nowadays and therefore we have had a lot of feedback from our customers related to using chrome with SAP BusinessObjects.

A main problem found by users is that when using Google Chrome on InfoView or BiLaunchPad a missing plug-in error screen appears when you are trying to modify a report and it also shows a HTTP Status 500 error screen when trying to log in to SAP BusinessObjects Explorer. In this blog I will provide a solution these issues.

The solution we have found is to use a Google Chrome add-on called “IE tab”, which emulates Internet Explorer on Chrome.

Steps to install it:

  1. From Google Chrome, introduce the link in the url bar and install the add-on.                                                                                       https://chrome.google.com/webstore/detail/hehijbfgiekmjfkfjpbkbammjbdenadd
  1. Once installed you will see a small folder with the IExplorer logo on the top right corner of google chrome.
  1. Click on the folder and another url bar will appear
  1. Introduce the Infoview / BI LaunchPad link in the new bar and start working with it.

Moreover, in case you need to click on an Open Document link and you want Google Chrome to be opened up automatically with it you will need to add your server’s url so it can open successfully, for this you need to follow these steps:

  1. Right click on the small folder with the IExplorer logo
  1. Choose Options
  1. Add the server’s address text in the Auto URL’s field

The outcome

SAP BusinessObjects web based applications can be successfully used with Google Chrome, see below the following examples:

Summary

The main benefits of applying these tips are, with the help of Google Chrome:

  • Modify documents on Infoview / BILaunchPad
  • Log in and manage spaces in SAP BusinessObjects Explorer
  • Increase the speed of navigation while going through the platform folders

According to the SAP’s official PAM (Product Availability Matrix), Google Chrome is not entirely supported due to its fast development speed, so the use and frequent update of this add on is highly recommended.

Hope this will help you have a better experience when working with SAP BusinessObjects. If any doubts or suggestions please leave a comment below.

SAP BusinessObjects Explorer 3.2: Creating Row-Level Security

In the past few months I had the chance to implement a solution based on the combination of SAP BusinessObjects Explorer and mobile devices. The challenge was: “I want to explore the same information that I see on my dashboards with SAP BusinessObjects Explorer on my iPad. In this particular case, some of the customer`s dashboards were really complex and we had to deal with many issues. Today I would like to share with you how we solved one of these issues:

How to implement row-level security into a space of Explorer?

The solution to this challenge cannot be based in any case of security implemented at universe level, in SAP BO Explorer the information of the spaces is retrieved when we index the space, this means that any kind of security applied at universe level will have a direct impact when we index the space. What we needed was a space with all the information but able to be filtered on demand based in some personalization rules.

With SAP BO Explorer 3.2 we are able to generate and apply this kind of security by creating two spaces: one reference space with all the possible information to explore and one personalized, where we will be able to filter the information displayed on demand based on the rules of personalization and making use of the reference space.

Definition of the scenario

To be able to follow the implementation of the solution, assume that we start from:

  • SAP BusinessObjects XI 3.1 installed and fully operational
  • SAP BusinessObjects Explorer 3.2 installed and fully operational

To make it easy to follow I will make use of the eFashion universe and we will need to create users in BO according with the list of values of Name of Manager dimension (Store -> Store Details->Name of manager).Note that the name of the users should be exactly the same as the values of the dimension.

We will create a new space based on the eFashion universe information. The personalization rule is that the Store managers will have access to the space but they will only be able to see the information related to their Store(s).

Creating the e-Fashion Reference space

First open SAP BO Explorer and login with administrator credentials. Click in Manage Spaces, select e-Fashion Universe and press New

In the tab Properties introduce a Name, in our case eFashion Ref, and select a folder under Public Folders, for the example Public Folders -> Explorer Spaces

The users should not be able to access this space, so remember to uncheck the option Show on Home Page

In the tab Objects select the objects that we will use in the space, in the example this tab will look like this

Then click Validate the space and then OK to save the space

Now you will have to Index the space, to do this just press the Index buttonOnce the status check shows the following symbol the space is successfully indexed.

Creating e-Fashion Personalized Space

Now we will implement the space to be accessed by the users, in this space we will make use of the eFashion Reference space created before to build a space with the personalization rules defined.

Log in with Administration rights into SAP BO Explorer, go to Manage Spaces, select the eFashion universe and press New. In the tab Properties introduce a Name, in our case eFashion Pers, and select a folder under Public Folder, for the example Public Folder -> Explorer Spaces

Select the same objects that we have used to create the eFashion Ref space

Go to tab Personalization, check Personalize information space Exploration and Select the eFashion Ref space from the list Select an information space

Now select User, from the table To Filter, and select Name of the Manager in the drop-down list in the column Filtered By.

We will link the rest of the dimensions of the personalized space with their corresponding ones on the reference space. The Personalization tab should finally look like this:

Validate the space and press Ok to save it and Index the new space eFashion Pers

Security Topics

Before testing the solution, and to avoid strange behaviors of the SAP BO Explorer spaces, we will have to review the security applied to the different components involved in SAP BusinessObjects. To “make our lives easier” I suggest creating a User Group (i.e. Explorer Users) in SAP BO and I strongly recommend reviewing this list of topics to ensure that the group has:

  • Granted access to Explorer application
  • Granted access to the Universe
  • Granted access to the Connection used on the universe
  • Granted access to the folder where the spaces will be stored.

In this example, what I did was to grant View On Demand access to all of the items of the list.

Finally the solution is ready to test!

Testing the solution

Log on in SAP BO Explorer with one of the users we have created, i.e. Quinn, from the Home tab we will access the eFashion Pers space and see only the data belonging to manager Quinn

If you log on with another user created, i.e. Steve, from the Home tab we will access the eFashion Pers space and see only the data that belongs to Steve

I hope you found this article interesting. For any queries regarding the contents of this article please leave a comment and I will readily reply.

SAP BusinessObjects Mobility Solutions (Part 1 - SAP Explorer)

As you might have already noticed we live in a mobile world. The increasing use of mobile devices for everyday tasks has become a common place in the course of the last decade. Business Intelligence has not fallen behind on this trend. On this series of two blog posts on SAP Business Objects Mobility Solutions, we will analyze mobile applications that SAP Business Objects has made available to bring BI to mobile devices (more specifically the Ipad): SAP Explorer and SAP BI Mobile.

Through this analysis we will learn what is the process to install the applications and review a few important things we need to consider. We will focus only on their mobility piece (Explorer for example can also be accessed on non-mobile devices) and we will also review some details of server side installation for each tool.

Both of these tools can be downloaded through SAP Marketplace (if you are an SAP partner).

If you are not an SAP partner but still feel like trying out these tools you can download the mobile applications from the app store and try out the demo servers SAP has made available.

First off, let us give you some details on our test environment and the software that was installed in it.

Software:

Business Objects XI 3.1 SP3 Enterprise

  • SQL Server 2005
  • SAP Explorer 3.2
  • BI Mobile 3.1 SP4

Hardware (Virtual Machine):

  • Windows Server 2003
  • 4GB RAM
  • 2 processors
  • 30 GB hard drive

With the above setup ready let’s start with our first Mobile tool from SAP Business Objects.

 

SAP Explorer

This is the first SAP tool based on in-memory technology. It is aimed for casual users who require an agile and pre-built framework for reporting but that still allows them to filter and search data intuitively. It was initially released as a web application only but the mentioned characteristics make it an obvious candidate for mobile devices, so the mobile application came out shortly after.

Here you can find the full commercial brochure of the tool.

Once you have the installer files downloaded from SAP Marketplace it is time to install it on our Business Objects environment.

Installation

The installation of SAP Explorer is pretty straightforward. You will find that there are very few screens that we need to pay full attention to and these are the ones we will focus on during this post.

You would install the application and web server components together or separated, depending on your system configuration. In our example we will install the whole product on a single machine.

For environments where the web server is not located on the same machine you will have to install independently the Web Application Server Component in the list above. However, it is also possible to install, for example, the indexing server on a separate machine to optimize efficiency. The index server is the one in charge of generating the space and might require a heavy load of processing power depending on your configuration.

Administrator credentials will be required during installation, so make sure you have them handy, as well as CMS name and port.

Finally the node name will be requested. This is used to identify the installation in multiple/parallel Explorer setup. For example, to link an isolated indexing server to its Master server. In our case we will leave the node name with the default name (which on this case is the computer name) as all of our installation resides on the same place.

Once the installation is complete we can test it by accessing the following url: http://yourserver:8080/polestar

If everything is setup correctly you will see the login screen for Explorer.

NOTE: If you would like to review the installation process in more detail it is best to review the Installation Guide also available in the SAP Marketplace.

Creating and Configuring a Space

Next step is to create a space.  The space is the indexed data that Explorer builds based on a Universe or File. To build it we will need to do the following:

  • Login to SAP explorer
  • Click on the Manage Spaces option
  • Select a universe
  • Select New

Provide the necessary information to build the space. We will need to provide at least:

  • Space name
  • Storage location
  • The dimensions and facts that will be computed on the space

Once the space has been configured we now need to index it. This process can be executed on demand or it can be scheduled, as a one time only or recurrent event. Depending on the size of the data selected from your universe this process might take from minutes to hours, so be aware of this before long running queries are configured to build a space. Once the space has finished indexing its data it will be marked with a green check.

Now we can plugin our mobile device to the space!

The Mobile Application

Before we plugin your device, first we need to download the application from the app store. We will find it under the name "SAP Explorer".

Once downloaded we need to configure a new connection with the following details:

  • Connection Name
  • CMS System name
  • Username (with permissions to use Explorer)
  • Password
  • Type of Authentication

There are no complex requirements on this configuration screen. Just make sure you provide the correct data for each component (web server, cms, cms port, etc).

NOTE: the official SAP Explorer Mobile installation guide specifies that installing SAP BI Mobile servers is a requirement. In reality, this is only optional and by installing SAP Explorer server you should be able to access Explorer with your mobile device.

You should now be able to start the connection to the Explorer server and work with the space created before. On this example we will use the SAP Experience connection that comes configured by default on the Ipad application.

If the connection is successful you should find the following screen listing all available spaces:

Once a space is selected from the list we would face a screen that looks pretty similar to what you have seen in the web version of Explorer.

The mobile version of SAP Explorer has no differences on functionalities against is Web-based version and only minor changes have been done to adapt for touch interaction on the Ipad.

As you have seen, installing and preparing SAP Explorer Mobile is a no-brainer.  Run through the installation process and you are setup to start using spaces and in-memory analysis on the Ipad.

As of now there are no other apps released by SAP for other mobile platforms (i.e. Android). Some might say this is not necessary due to other platforms support of flash technology, but the responsiveness of the Ipad application definitely sets this version appart. We hope to see dedicate applications to come out for other mobile devices soon.

The next mobile application - SAP BI Mobile - will be covered in the next article of the series, that should be out in early January.

If you are interested or have worked with this application, or if you feel it might be useful in your organization, please leave a comment below.

EspañolEnglish