SAC Connection to On-premise SAP systems.
- Download required software
- Install JDK 1.8 and set the environment path.
- Install SAP Cloud Connector
- Install and config Apache tomcat.
- Deploy C4A_Agent war
- Deploy JCO ( Only for ERP and BW Connections)
- Configure JCO
- Run Apache tomcat
- Check C4A_Agent is deployed
- Add admin S-User account to SAPCC, from which SAC account is created.
- Configure C4A_AGENT in SAPCC
- Configure SAP Analytics cloud agent in your SAC tenant.
Download Required Softwares
- SAP Analytics Cloud Agent 1.0 : C4A_AGENT
- SAP Cloud Connector
- Apache Tomcat
- SAP Java Connector (SAP JCo), version 3.0.12 or higher.
- JDK 1.8
Install JDK 1.8
- Install JDK and JRE 1.8
- Set the Environment variable JAVA_HOME
Install SAP Cloud Connector
- Run the setup
- Specify JDK 1.8 path
- by default, it is installed in C://SAP/sapcc
- Go there and run go.bat file as admin
- Then log in to SAP Cloud connector, https://localhost:8443.
- If you don’t know the port then you can run changeport.bat <port number> to change the port.
- When you log in for the first time the username/ password will be, Administrator / manage.
Install and Config Apache Tomcat
- Install apache tomcat
- edit conf/tomcat-user.xml and add the user details.
<role rolename="manager-gui"/> <role rolename="admin-gui"/> <user username="admin" password="pass@12345" roles="manager-gui,admin-gui"/> <!---- for sap analytics cloud agent--> <role rolename="Services"/> <user username="sacadmin" password="pass@12345" roles="Services"/>
Note: This step is not necessary if only connecting to SAP BPC NW from SAP Analytics Cloud. Proceed to Configure Access Control in SAP HANA Cloud Connector section below and follow the steps specific to creating access control for SAP BPC NW.
The SAP Analytics Cloud Agent(SAAC Agent) is just a war file that can be deployed on a Tomcat application server. This can either be an existing Tomcat Java application server running in your environment or install(like I have done) a separate application server to deploy the SAC Agent war file. My recommendation would be to setup a new Tomcat server to deploy the SAC Agent. The main reason for this recommendation is that SAC Agent is being updated frequently to take advantage of the new connectivity types being offered in SAP Analytics Cloud. As SAP Analytics Cloud is being updated frequently, the SAC agent must also be updated to keep pace with this innovation. This means you may have to deploy a new SAC Agent war file every few weeks, which could result in taking a potential downtime on running an application server that may be hosting other apps. To avoid impacting an existing production application server and potentially take downtime to deploy a new war file, it’s advisable to set up a separate application server for SAC Agent deployment.
To download SAC Agent access https://support.sap.com/swdc
- Extract the downloaded C4A_AGENT_*.rar file.
- Copy and paste it in the apache tomcat > webapps directory
Deploy JCO ( Only for ERP and BW Connection)
- Extract the downloaded software from the SAP Software center.
SAP Java Connector (SAP JCo), version 3.0.12 or higher.
- Copy sapjco3.dll and sapjco3.jar file into tomcat/lib directory.
The default value for -Xms and -Xmx is usually 128MB, and 256MB respectively and is usually not sufficient. Failure to increase these values will usually result in timeout errors when acquiring larger data sets into SAC. Here I’ve set the values to 1024MB and 2048MB, but you may have to increase the Maximum Memory pool(Xmx) to even higher value in your landscape.
- Create a new file setenv.bat in the apache-tomcat/bin directory.
- And write the following line. set“JAVA_OPTS=%JAVA_OPTS% -Xms1024m -Xmx8192m -XX:MaxPermSize=256m -server”
- Then run the apache tomcat server from catalina.bat
Rerun Apache Tomcat
- Go to the apache-tomcat installation directory.
- Go to the bin folder
- Run the bin/startup.bat or bin/catalina.bat
Check C4A_Agent Deployment
Go to http://localhost:8080/C4A_AGENT/deploymentInfo If you see the version then you are good to go.
Add admin S-User account
- run the go.bat file in the sapcc folder
- Login to SAPCC
- Go to Connector and click on add Subaccount
- Fill out the below details and save it.
Configure C4A_Agent in SAPCC
- Go to Cloud to On-premise tab and click on the add system button.
- Add system mapping
- Select Protocol (HTTP / HTTPS)
- Add Internal host name and port name. In my case it’s running on https://localhost:8080/ so
I added my computer name/ server as hostname
and port as 8080
- Add virtual hostname, port name of your choice, this cannot be modified once saved.Here hostname is : mysacagent
- Set principle type as None
- Enter Description
- Check Internal host and Finish.
- You will see new system is added and reachable.
- Under Resources Accessible on <name of your agent> click + to add a new resource.
- Set the URL PATH: /C4A_AGENT/ and choose the option Path and all sub-paths and click Save
- Add other ABAP systems from where you want to access the data in my case I have added the Linux host of the S4HAHA system.
- Your HANA Cloud Connector screen should look like the screen below. Your mapped system should be in green status.
Configure SAP Analytics Cloud Agent in SAC Administration
- Launch your SAC system (tenant) URL and log in with an account that has administrative access.
- Access System >> Administration option
- Click on the DataSource Configuration tab and click the edit button on the top right corner of the screen. Enter the following information:
- Host: <virtual hostname specified during the SAP Cloud Connector configuration>
- Port: <virtual port specified during the SAP Cloud Connector configuration>
- Username: <username specified in tomcat-users.xml file>
- Password: <password specified in tomcat-users.xml file>
- Click the Check Configuration button to validate the configuration.
- Save your configuration.
You are now ready to acquire data from the on-premise BI4 universe, BW, ERP, JDBC, OData, and BPC data sources.
Thanks for Reading 🙂