SAP Knowledge Base Article - Public

2897467 - Deploying the Live Universe Connector in a Standalone Tomcat on Linux/Unix for SAP Analytics Cloud (SAC) [HOW-TO]

Symptom

It is required to set up the SAP Analytics Cloud (SAC) Live Universe Connector in a Standalone Tomcat to enable connectivity to SAP BusinessObjects Business Intelligence Platform On-premise Universe.

Environment

  • SAP Analytics Cloud (SAC)
  • SAP BOE Live Data Connect 2.3
  • SAP BusinessObjects Business Intelligence Platform 4.2 SP06+
  • Tomcat
  • Linux

Resolution

The below sections detail the steps to be performed in order:

  1. Deploy the Live Universe Connector
  2. Configure the Live Universe Connector
  3. Start the Live Universe Connector
  4. Testing the Live Universe Connector

Deploy the Live Universe Connector

  1. Download the latest version of Tomcat 8 or Tomcat 9 (Core -> tar.gz) available here:
    https://tomcat.apache.org/download-90.cgi
    Note: Tomcat 10 is not supported yet.

  2. Place and extract this file on the Linux server which is to be used for the Live Universe Connector.

  3. Configure Tomcat SSL with a CA signed certificate according to the Tomcat documentation:
    https://tomcat.apache.org/tomcat-9.0-doc/ssl-howto.html#Create_a_local_Certificate_Signing_Request_(CSR)
    Another reference for setting up SSL is available here: 
    1648573 - How to configure SSL/TLS on Tomcat in BI 4.x

    PLEASE NOTE: 
    Configuring Tomcat SSL is outside the scope of SAP Analytics Cloud support.

  4. Open "tomcatdir/conf/tomcat-users.xml"

  5. Set up a user for the manager app as below in this file:

    Before After (Example only, change username / password as appropriate)

    <user username="role1" password="<must-be-changed>" roles="role1"/>
    -->


    </tomcat-users>

    <user username="role1" password="<must-be-changed>" roles="role1"/>
    -->
    <user username="admin" password="example" roles="manager-gui"/>

    </tomcat-users>

     
  6. Open tomcatdir/webapps/manager/META-INF/context.xml

  7. Allow access to the "manager HTML application" (used for deploying the webapp) from a specific IP or all IPs (by default it's secured to localhost only).

    Before Allow Specific IP Allow all IPs

    <Context antiResourceLocking="false" privileged="true" >
    <Valve className="org.apache.catalina.valves.RemoteAddrValve"
    allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1" />
    <Manager sessionAttributeValueClassNameFilter="java\.lang\.

    <Context antiResourceLocking="false" privileged="true" >
    <Valve className="org.apache.catalina.valves.RemoteAddrValve"
    allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1|YOUR.IP.ADDRESS.HERE" />
    <Manager sessionAttributeValueClassNameFilter="java\.lang\.

    <Context antiResourceLocking="false" privileged="true" >
    <!--<Valve className="org.apache.catalina.valves.RemoteAddrValve"
    allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1" />-->
    <Manager sessionAttributeValueClassNameFilter="java\.lang\.

     
  8. Start (or restart if already started) Tomcat using ./shutdown.sh and ./startup.sh in tomcatdir/bin directory.

  9. Download and extract the current version of the Live Universe Connector from the Support Launchpad onto the Tomcat machine.

  10. Access https://<tomcathost>:<tomcatport>/manager (from the host specified in step 7 if specific IP was specified).

  11. Provide the username and password from step 5.

  12. Go to the 'Deploy section' and provide the context path and full path to .war file extracted from step 9 as below:

    DeployWARLinux.png

  13. Click 'Deploy'.

Configure the Live Universe Connector

  1. Navigate to tomcatdir/conf

  2. Create a new file: "boe.properties".

  3. Add the below text to the file (replace <> parameters and http/https as appropriate):

    New

    BOE Tomcat biprws example BOE WACS biprws example

    # BOE Server info 
    boe.restUrl=http://<BOE_WAS_SERVER_NAME>:<BOE_WAS_SERVER_PORT>/biprws 
    boe.authenticationMode=secEnterprise 

    # LDE configuration 
    lde.port=58080

    # BOE Server info 
    boe.restUrl=http://tomcathost:8080/biprws 
    boe.authenticationMode=secEnterprise

    # LDE configuration 
    lde.port=58080

    # BOE Server info 
    boe.restUrl=http://boehost:6405/biprws 
    boe.authenticationMode=secEnterprise

    # LDE configuration 
    lde.port=58080


    Note: If the biprws (Restful Web Service) is not accessible or deployed on the web application used for BI, then the Web Application Container Server (WACS) servername and port can be used instead in the boe.restUrl parameter. Eg: "http://<host>:6405/biprws".
    If HTTPS is used, then the tomcathost parameter above must reflect the Fully Qualified Domain name (FQDN)

  4. Navigate to "tomcatdir/bin".

  5. Create a file "setenv.sh" and add below content:

    Content Example
    export JAVA_OPTS="$JAVA_OPTS -DBocInaAgentConfigurationFile=<BOE_PROP_PATH>" export JAVA_OPTS="$JAVA_OPTS -DBocInaAgentConfigurationFile=/home/user/tomcat/conf/boe.properties"
     
  6. Navigate to "tomcatdir/webapps/sap#boc#ina/WEB-INF". 

  7. Open the "web.xml".

  8. Change the below lines:

    Original New Example
    <param-name>cors.allowed.origins</param-name>
    <param-value>*</param-value>
    <param-name>cors.allowed.origins</param-name>
    <param-value><SAP_ANALYTICS_CLOUD_TENANT_URL></param-value>
    <param-name>cors.allowed.origins</param-name>
    <param-value>https://exampletenanturl.cloud</param-value>


    Note: ensure there are no trailing slashes (/) at the end of the URL.

  9. Restart Tomcat

Start the Live Universe Connector

  1. Navigate to "https://localhost:<HTTPSPORT>/manager".

  2. Select 'Start' next to the /sap/boc/ina application in 'Applications'.

    StartLUC.png

    The 'Running' Column should go from 'false' to 'true', if it doesn't, check the tomcat stderr.log and catalina.log at tomcatdir/logs for errors.

Testing the Live Universe Connector

To test the Web Application has been deployed correctly, access:
https://<LUCHOST>:<LUCPORT>/sap/boc/ina/GetServerInfo

In Internet Explorer, this will download a file called "GetServerInfo.json".
In Google Chrome, this will display simply the text: {}

If a different result is seen, recheck the steps above.

See Also

Your feedback is important to help us improve our knowledge base.

Keywords

SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC , KBA , luc , LOD-ANA-LDC-UNV , SAC Live Data Connection Universe , How To

Product

SAP Analytics Cloud 1.0