1 Live Data Connection to SAP Universes You can create a Live Data Connection to SAP Universe using the SAP BusinessObjects Enterprise (BOE) Live Data Connector component deployed on your application server. Prerequisites for Live Data Connection to SAP Universes: • SAP BusinessObjects Enterprise BI 4.2 SP4 system installed • Java application server. If you use Tomcat, it must be configured in Secure Sockets Layer (SSL) For a list of supported system types and limitations, please see System Requirements and Technical Prerequisites and Limitations to SAP Universes. 1. Deployment and setup of the SAP BOE Live Data Connect component 1. Create a context for the component: a. Open the server.xml file located in the conf folder of your Tomcat installation directory NOTE: In the below examples, we are using Apache Tomcat shipped with SAP BOE BI Platform.
15
Embed
Live Data Connection to SAP Universes - SAP Analytics … · Live Data Connection to SAP Universes ... SAP BI Platform to make sure that BI users can view universes and access their
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
Live Data Connection to SAP Universes
You can create a Live Data Connection to SAP Universe using the SAP
BusinessObjects Enterprise (BOE) Live Data Connector component deployed on your
application server.
Prerequisites for Live Data Connection to SAP Universes:
• SAP BusinessObjects Enterprise BI 4.2 SP4 system installed
• Java application server. If you use Tomcat, it must be configured in Secure
Sockets Layer (SSL)
For a list of supported system types and limitations, please see System Requirements
and Technical Prerequisites and Limitations to SAP Universes.
1. Deployment and setup of the SAP BOE Live Data Connect component
1. Create a context for the component:
a. Open the server.xml file located in the conf folder of your Tomcat installation directory
NOTE: In the below examples, we are using Apache Tomcat shipped with SAP BOE BI Platform.
2. Create a boe.properties file in the same conf folder
a. Open the boe.properties file and update it with the following lines
# BOE Server info
boe.hostname=http://<BOE_SERVER_NAME>:6405
boe.authenticationMode=secEnterprise
boe.language=en-US
compatibleUniverseFolder=Universes/Samples
temporaryDocumentFolder=BOELiveProviderTempFolder
NOTE: By the above specification we configure the Universes/Samples folder to be accessible in English language while using enterprise authentication. You may be able
3
to specify a higher level folder then add view rights only for particular folders in CMC later. You can specify “localhost” as well if you’re using the Tomcat deployed on the same machine as the Central Management System of the BI Platform, where 6405 is the default port. Like in the below example: http://localhost:6405
3. Stop Tomcat and point to the boe.properties file you have just created. You have multiple ways to perform this action according what type of Tomcat you are using.
• Standalone Tomcat (batch) i. Open bin/startup.bat file ii. Set the JAVA_OPTS variable at the beginning of the file:
• Standalone Tomcat (Service) i. Run the executable bin/tomcat8w.exe file
ii. In the Java tab, add the following line in Java options: -DBocInaAgentConfigurationFile=<BOE_PROP_PATH>
NOTE: If your Tomcat runs on Linux or you’re using the Tomcat shipped with SAP BOE BI Platform, follow the steps as described in our SAC Documentation.
4. Download and deploy the SAP BOE Live Data connect component
a. Go to SAP Software Downloads page and login with your SAP Credentials
b. Enter “Live Data Connect” into the search bar at the top
c. Download the latest version of the SAP BOE Live Data Connect
component
d. Extract the zip file and copy the file cs_ina_agent.war to your Tomcat
> webapps directory
e. Start Tomcat
5. Configuring Cross-Origin Resource Sharing (CORS) When deploying the component, you can configure CORS requests so that the browser accepts requests coming from the SAP Analytics Cloud server. It's a way to secure the component by making sure that you control what servers are accessing your BI system via the component.
6
NOTE: If you are using a reverse proxy, you don't have to set up CORS. Please follow the SAC Documentation how to set up Reverse Proxy for SAC and Live Universe Connection
a. After starting the Tomcat a cs_ina_agent folder should appear in the
webapps folder, meaning that the component has been deployed
successfully
b. Go to the webapps > cs_ina_agent > WEB-INF folder and open the
web.xml file using Notepad
c. Locate the <param-name>cors.allowed.origins</param-name> line