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.

    • Hello. Thanks. That’s a documentation error. I will pass it to the colleagues in charge of the documentation and ask for correction. best regards.

  • Hi everyone,

    I’m new with LDC 3.1, configured successsfully 2.2, 2.3 and 2.4 with SAPBO4.2 SP06+ and https

    Probably is a silly quaestion, but i don’t know what to do with connector.https.keystore.file and connector.https.keystore.password, these parameters are new, please can you help me ??, it’s necessary to define a keystore now ?



  • Hi Laura VEGA


    I’ve followed the steps in the guide and LDC is accessible

    When I try to create a connection from SAC, I get this message :

    Protocol Error: Error [Protocol]: (#73) Unauthorized
    Error [Protocol]: (#401) Unauthorized
    "Messages": [
    "Type": 2,
    "Number": 0,
    "Text": "[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(Unable to connect to CMS <SERVER.IP>:6400. A wrong connection is made to @@<SERVER.NAME>:6400(<SERVER.NAME>:6400). Logon cannot continue.(hr=#0x80042a79)"
    We have tryed and get the same issue with both SAP BI 4.2 and SAP BI 4.3 as source.
    Our BI plateforms are accessible by public IP over internet.


    According to

    we have set paramter boe.nameServer to the exact internal hostname as shown in CMC


    boe.restsdkurl, boe.authenticationMode, connector.https.port, connector.https.keystore.file, connector.https.keystore.password and are also set correctly.

    Is there something we have missed ?


    Thanks a lot for your help.
  • Hello.

    Indeed I am aligned with David on this. Please raise a ticket.

    At the first glance, judging from the screenshot above, your SSL certificate is a self-signed certificate.  That cannot work with SAP Analytics Cloud.

    You must use an SSL certificate signed by a CA (Certificate Authority);

    best regards; Piotr


    • Hi.


      The certificate was one of my guess but I could not find any official SAP documentation about that. Do you know one that says explicitally that it takes a certificate signed by a CA for LDC to work with SAC ?

      Also, is it the LDC certificate only, or the BI platform certificate ? Or both ?


      I’ll try and let you know.


      Thanks a lot for your help Piotr.





  • Hello Ben,

    As mentioned in my first reply this is SAC that requires a secure HTTPS live connection endpoint with a trusted (signed) SSL certificate.

    There is tons of KBs, community briefs etc. on this topic. For instance

    Regarding the 2nd part of the question. I cannot answer it. Please contact SAP Product Support for guidance.

    In a nutshell, a trusted, CA-signed SSL certificate is delivered for a fully qualified domain name. This ensures maximum security; This means one SSL certificate for each HTTPS endpoint.

    However, most of the Certificate Authorities can offer wild-card certificates for the domain name allowing to have one single SSL certificate for a network domain.

    If this were the case then one might use the same SSL certificate between software components residing in the same network domain. Please contact SAP Product Support for further guidance.

    best wishes



  • Hi there,

    great blog and I’m looking forward to using the ‘WebI reports as a data source’ option – but can I deploy LDC 3.1 to a server that is in a .local domain? The need for a non-self-signed cert suggests not.




    • Hello,

      Signed certificate and deployment in a local domain are 2 distinct topics.

      LDC is going to be accessed by the browsers from your users connected to SAC. If all these users are in a local domain, then the LDC server can be in a local domain. I think many deployments rely on such topology.

      Signed certificate is a requirement that originates in browser policies. When a site is accessed in https, all underlying services have to accessed through https as well. In our case SAC is an https website, so LDC (underlying service) has to be accessed through https as well. It doesn’t matter that LDC is in a local domain or not, it is sitting behind SAC from the browser’s point of view.




  • Hi,

    My tenant was upgraded to 2020.21 over the weekend, but I do not see WID files in my list of live universes. I have been using Live Data Connect 3.1 since September. I do see UNV and UNX. Is there a trick to allow WID files to appear? I am using BusinessObjects 4.2 SP8.



    • Hi Brandon,

      yes I forgot to mention you need to set the WID docs you want to see appear in SAC to a specific Category in BOE.

      In the config file, you can use the parameter “boe.webi.category.cuid” to define this category. Only documents present in this category will be listed in the LDC connection.



      • Thanks! It’s working for me.

        A big difference I notice comparing Dashboards (Xcelsius) to SAC with Web Intelligence is that Dashboards uses data from the tables in the WebI documents while SAC seems to be using data from the cached data provider and variables in the document.

  • Hello David MOBBS , Piotr Tesny , Laura VEGA

    I am currently installing the Live Data Connect 3.2 and have run into a few issues with the HTTPS specific parameters and can’t seem to find any documentation on the following:


    1. connector.https.port

    –        The default value of this parameter is 0. What are the implications of leaving this as 0 as it                   says this parameter is not mandatory?

    –        Our SAP Analytics Cloud tenant is HTTPS, so if we need this parameter could you please                  advise on how we find / create this port. Is this a port created in the Windows Firewall on the server that we are installing the LDC?


    2. connector.https.keystore.file & connector.https.keystore.password

    –        If we set the first parameter we then need to set the parameters for the two above. Do you                  have any documentation on how we do this?

    –        Are you able to point me towards any documentation on creating SSL certificates for the                    LDC?



    • Hello,

      Https port and keystore both need to be set.

      Browser policies impose that when connecting to a website in https, all invoked services must rely on https as well. In our case, you are connecting to the SAC tenant using https, to the LDC service which gets invoked must expose https as well.

      These security policies also imply that you need a certificate signed by a valid authority for your server.

      So I would recommend that you reach out to your security or network management colleagues, they should be able to provide you with a signed certificate, or guide you through the process of generating one. This process is specific to every organization.



      • Thank you David MOBBS

        I have now managed to configure all mandatory parameters in the file including the HTTPS / SSL issues I was previously having.

        But when I was running the LDC executable it seems that nothing happens. So I installed the LDC as a Windows Service and run from there and it fails to start.

        I checked the errors in the System Event Log on Windows and it says ‘The remote server has been paused or is in the process of being started’.

        I have also checked the logs folder within the LDC install and each time I try to start LDC it writes a log which does not show any specific error. However I did notice the log ends with ‘ConfigurationFile Loading’ and then nothing afterwards.

        Have you seen this issue before? Or if you’re able to point me in the direction of any relevant documentation that would be great.

        Thanks & Regards,