Skip to Content
Product Information

Live Data Connect 3.1 for BOBJ is released

Where to find Live Data Connect 3.1

After successful release of Live Data Connect 3.0 in July 2020, we are pleased to announce that version 3.1 has been released this week and available for download in SAP Market Place:

Download Live Data Connect 3.1


As a reminder, Live Data Connect 3.0 for Universes offers following features to our on premise customers:

  • It allows SAP Analytics Cloud to connect to On Premise Data, exposed through the universes
  • It enables a LIVE access towards these data
  • The data are never uploaded into the CLOUD or SAP Analytics Cloud: they stay behind your firewall, into your corporate network
  • And you can access and re-use, as is, all your existing relational universes of type .UNV and .UNX


What is new in Live Data Connect 3.1

With Live Data Connect 3.1, you get now the ability to access not only Universes, but also Web Intelligence Data Models. What does it mean?

From Sap Analytics Cloud, when creating a story with Live Data Connect, yo will be able to select a Web Intelligence document and to build your query on top of the document data providers objects. This means you can leverage all calculations and synchronization efforts made in the Web Intelligence documents.

You ca find more information in the Live Data Connection 3.1 SAP Note


User friendly workflow

These are the steps to follow to create your SAP Analytics Cloud story on to of a Web Intelligence document.



What is next?

Live Data Connect for BOBJ is enhanced every quarter with new features, so stay tuned for the coming release in Q4 2020.

In the meanwhile, enjoy this brand new release !



You must be Logged on to comment or reply to a post.
  • Hello, thank you for this post. If I may, this live connect has kind of issue – function grandtotal is disabled. Have you some kind of way, how to achieve percentage values (in tables, tree charts..)? Or I do something wrong. Thanks a lot.

  • Hi Laura VEGA¬† A customer of mine would like to know how long this update task takes when redeploying?¬† and are there any best-practices around preserving configuration so that they don’t overwrite stuff ?¬† Regards, H

    • For an upgrade from 3.0¬† to 3.1, you just need to backup the “conf”¬† folder contents, and recover it after the 3.1 zip extraction. This is also explained in LDC documentation.

      For an upgrade from 2.x to 3.x, you need more work as configuration has totally changed and been regrouped in one place.



  • Hello,

    From version 3.0 onwards we dropped tomcat deployments as rather complex and cumbersome. With LDC 3.x we use standalone jetty engine instead. And there is one single configuration file called where all the configuration is centralised and which you can carry across future releases. Please refer to product documentation for further details.

    best wishes


  • Hi Laura VEGA Hi Piotr Tesny

    Sorry to bother, i had a question from an interested customer who was asking  whether this new release can be deployed in a clustered BI environment ?

    they were of the opinion that this was a limitation with the previous version so could not adopt, however they are curious to know more as of now?



  • Hello,

    In a nutshell this scenario is described in this guide: Configuring SAP BusinessObjects Live Data Connect


    Parameter Description Mandatory

    Previously known as boe.restUrl

    The URL for the REST Web Services exposed by the BI platform. Yes

    Default value: The server used in the boe.restsdk.url parameter. The port is 6400.

    If there’s an error, use the cluster name value. You’ll find it in the Central Management Console, under Settings  Cluster.

    Name server host and port defining the system to connect to. If your CMS repository is running on a different machine than the one running the REST Web Services, use this parameter to set the server and port used by the CMS repository.

    By default, if you don’t set this parameter, the information is retrieved from the¬†boe.restsdkurl¬†parameter.

    For more information, see The CMS uses two ports.

    For more information, refer to the Business Intelligence Adminstrator Guide.


    best wishes


    • Hello Piotr,

      This phrase is wrong ”¬†If your CMS repository is running on a different machine than the one running the REST Web Services, use this parameter to set the server and port used by the CMS repository.”

      Because :
      a. CMS repository is not a server, it is a database.
      b. boe.nameServer refers to the CMS server or a cluster name of the CMS cluster. So it is a CMS server name and port or a BOE system cluster name.