Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SAP Analytics Cloud (SAC) Integration with On-Premise Systems from SAP Basis End #ATR

AJAYTR_ATR66
Participant
‎03-12-2024 1:22 PM
0 Kudos

#ATR(17)

Informative Note:

Created this document to provide steps on how to integrate SAC with On-Premises System.

  • SAC Integration not required for Live Data Model/Connection – BW features. If we need to manually select our created ODATA and perform Analytics/Model, then SAC Integration required.

Live Data Model:

AJAYTR_ATR66_0-1710248616191.png

AJAYTR_ATR66_1-1710248616197.png

SAC Integration:

  • We are going to integrate our S/4HANA, ERP System into SAC from scratch.

Reference Blog: https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/bdf055159cbb4f36b26c9...

Key Notes:

  • Connection to Data Sources (ODATA, S/4 HANA System, SAP IBP, SAP BPC NW) will work fine irrespective of the HA configuration. Connection doesn't need SAC Agent/Tomcat/Java Connector. SAP Cloud connector configuration alone required. Hence, SAC Connection will work even HA takeover occurred. For more information on Cloud Connector High Availability, please refer below blog.

SAP Cloud Connector Upgrade and High Availability Configuration #ATR

  • Connection to Data Sources (SAP ERP, SAP BW) require SAC Agent on Tomcat and Java Connector. Cloud Connector already installed in my scenario. We are going to install SAC Agent, Tomcat & Java Connector in Cloud Connector server itself. SAC Connection to On-Premises will fail if SCC server went down/HA takeover occur since we would install SAC Agent in Primary SCC server only. Even if you make same configuration in Secondary SCC, connection will fail since we would provide Primary SCC details in SAC Data source config.
  • If you need availability even during HA takeover, you can prefer having VIP connection - Active/Passive VM Cluster with SCC installed. It might work.

Short Steps:

  • Get SAC Subaccount details
  • Installation of Apache Tomcat
  • Deploy SAC Agent WAR File
  • Java Connector files
  • Cloud to On-premises Connection
  • Configure On-Premise Data Source in SAC
  • Creating On-Premise User to connect SAC System
  • Creating On-Premise Connection
  • Creating Data Model

Get SAC Subaccount details:

  • SAC -> System -> Data Source Configuration

AJAYTR_ATR66_2-1710248616200.png

  • Provided my Subaccount User (Mail ID) since we are going to connect Subaccount using my email ID.

AJAYTR_ATR66_3-1710248616201.png

  • Added our SAC Subaccount.

AJAYTR_ATR66_4-1710248616207.png

  • Before Configuring “Cloud to On-Premises Connection”, we can complete other configurations.

Installation of Apache Tomcat:

  • Downloaded Apache tomcat 9 version – 9.0.86 and install on your SCC. Tomcat – Opensource.

AJAYTR_ATR66_5-1710248616209.png

AJAYTR_ATR66_6-1710248616217.png

  • Make sure to select “Windows Service” Startup as well.

AJAYTR_ATR66_7-1710248616224.png

AJAYTR_ATR66_8-1710248616228.png

  • Downloaded JRE 8 version and provided the same. Please prefer to use JRE/JDK. I have tried with SAPJVM_8 and got error “Environment error”. Tomcat will launch fine with Manual Start but we will get below error while trying to start via Windows Service.

AJAYTR_ATR66_9-1710248616229.png

AJAYTR_ATR66_10-1710248616230.png

  • I have downloaded compressed archive (x64) and mentioned the same. JRE – opensource.

AJAYTR_ATR66_11-1710248616235.png

AJAYTR_ATR66_12-1710248616243.png

AJAYTR_ATR66_13-1710248616244.png

  • Once installed, we can check configuration via Tomcat Properties. Make sure to increase memory pool alone – Atleast 1 GB recommended.

AJAYTR_ATR66_14-1710248616254.png

AJAYTR_ATR66_15-1710248616266.png

  • Tomcat-users.xml -> Change Admin password. Create one user for SAC Agent with Services role and provide password as well. [Role – Service – SAP defined]
  • File path -> C:\Program Files\Apache Software Foundation\Tomcat 9.0\conf

AJAYTR_ATR66_16-1710248616269.png

  • I’m not having any restrictions/compliance. Hence, I have provided all access in addition to service role.
  • We need to use “sacagent” user and password in SAC.
  • No need to confuse on Tomcat “Catalina Home/Base”. Everything will be setup automatically if you use Windows X64 installer.
  • We can also check parameter config by starting Tomcat manually.
  • File path -> C:\Program Files\Apache Software Foundation\Tomcat 9.0\bin\startup.bat

Installation of Tomcat completed.

Deploy SAC Agent WAR File:

  • Stop Apache -> Download SAC Agent and just place inside Webapps folder -> Start Tomcat. Tomcat will automatically deploy WAR File. Please don’t delete WAR file. It needs to be present inside Webapps folder permanently.
  • File path -> C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps

AJAYTR_ATR66_17-1710248616283.png

AJAYTR_ATR66_18-1710248616285.png

AJAYTR_ATR66_19-1710248616292.png

  • We can also use “Tomcat Web Application Manager” to select and deploy WAR file but make sure to increase upload file size ~125MB since C4A_AGENT WAR file will come around 105 MB.

AJAYTR_ATR66_20-1710248616293.png

  • File Path -> C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\manager\WEB-INF\web.xml

AJAYTR_ATR66_21-1710248616295.png

AJAYTR_ATR66_22-1710248616297.png

AJAYTR_ATR66_23-1710248616298.png

  • Version information should be reflected. You will get “Access denied” error if sacagent user does not have “Services” role (SAP Defined)
  • SAC Agent deployed successfully.

Java Connector files:

  • Downloaded “Java Connector” -> Extract Files and Place in Tomcat Lib folder.
  • File Path: C:\Program Files\Apache Software Foundation\Tomcat 9.0\lib

AJAYTR_ATR66_24-1710248616309.png

  • Java Connector configuration completed.

Tomcat/JCo/SAC Agent Config completed

Resuming Cloud connector Configuration.

Cloud to On-premises Connection:

  • Connection to S/4HANA System as well as SAC agent working fine. I have created two sample connection for viewer’s reference.
  • Don’t use full FQDN for SAC Agent – SCC Internal host. There were lot of restrictions out of which (.) is not allowed and it will affect SAC Agent detection in SAC. Simply use Short DNS.

S/4 HANA:

AJAYTR_ATR66_25-1710248616315.png

For Other On-Premises (ERP):

AJAYTR_ATR66_26-1710248616318.png

  • Don’t use Principal Propagation while adding connection.

AJAYTR_ATR66_27-1710248616319.png

  • Cloud to On-Premises connection for SAC [ SAC Agent and S/4HANA System] via SCC completed.

Configure On-Premises Data Source in SAC:

  • Path -> System – Data Source Administration – On-premises Data Sources.
  • We haven’t used Location ID. Hence, we can edit default location itself.
  • Provide SWDSCC – Tomcat Internal hostname in Host which is ShortDNS/ShortFQDN. Port will be Tomcat -HTTP-8080.
  • For S/4 HANA, SAC will use SCC Config -> Cloud to On-Premises -> S/4 HANA system connection details and allowed SAP Path /sap/ directly.
  • For ERP, SAC will search SAC agent details which we provided in data source – Tomcat SCC Host & 8080.
  • Hence, SAC will use SCC Config -> Cloud to On-Premises -> SCCInternalHost (Tomcat - 8080) connection details and allowed /C4A_AGENT/ path which will have all SAP ERP config details (SAP Defined).
  • Once ERP Config details fetched from Tomcat 8080, it will be sent back to SCC 8443. Tomcat 8080 will use SAP Jco library files as well if required to fetch config details. Hence, Tomcat with SAC Agent will just act as an Intermediator for getting ERP config details and help SCC to provide details to SAC.

AJAYTR_ATR66_28-1710248616320.png

  • Provide SAC Agent user and password to connect SAC agent.

AJAYTR_ATR66_29-1710248616326.png

  • Connection to On-Premises Data Sources successful.

AJAYTR_ATR66_30-1710248616329.png

Creating On-Premises User to connect SAC System:

  • For ERP, we can use any technical user for ERP system connection. SAP_ALL profile preferred. [SCC_USER – In my scenario]
  • For S/4 HANA without Finance requirement (Financial Planning and Analysis, Mostly, we can use any technical user with SAP_ALL profile.
  • To do finance analysis/If ODATA service didn’t fetch, we need to enable all gateway services for S/4 HANA system and Access needs to be provided to On-premise user.
  • FYI. My On-premise system doesn’t have any separate gateway. It’s just normal S/4 HANA System with all services embedded/registered locally.
  • Tasklist -> SAP_GATEWAY_ACTIVATE_ODATA_SERV
  • Select and Activate ODATA services mentioned in SAP documentation.

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/48f4b4785b8e45938ac44a67be8032d9/c7ad6de319494356b06...

  • Some of the ODATA services won’t be available in your system based on the versions. We can ignore those ODATA services.

AJAYTR_ATR66_31-1710248616339.png

AJAYTR_ATR66_32-1710248616349.png

  • ODATA services will work any type of processing mode - both Routing-Based/Co-deployed since gateway already embedded in S/4 HANA System. We need to set and change routing-based (With RFC) – SYSTEM ALIAS – LOCAL/SIDCLNT based on your preference if separate gateway server installed or service not registered locally on your system. I’m using Co-Deployed only.

AJAYTR_ATR66_33-1710248616364.png

AJAYTR_ATR66_34-1710248616373.png

  • Once ODATA service activated, we can provide ODATA service access to our On-premise user (SCC_USER – In my scenario).
  • SAP Role SAP_FIN_PLANNING_SAC already have access to all these ODATA services w.r.t V2 - IWSV. Copy and create new role to assign to our SCC_USER.
  • SAP recommended to provide same ODATA service access w.r.t Gateway - IWSG as well. Create new role -> provide ODATA service access with IWSG -> Assign to SCC_USER.
  • Prefer to assign SAP_ALL profile as well.

AJAYTR_ATR66_35-1710248616375.png

AJAYTR_ATR66_36-1710248616382.png

All SAC Integration configuration completed.

For S/4HANA:

Creating Connection:

  • You can create new connection while creating new data model itself OR create new connections via System -> Connections and then proceed to create Model.

AJAYTR_ATR66_37-1710248616384.png

AJAYTR_ATR66_38-1710248616385.png

AJAYTR_ATR66_39-1710248616387.png

  • Connection created successfully. There won’t be any option to check connectivity. We can able to check connection while creating data model only.

Creating Data Model:

  • Create new data model by selecting S/4 HANA Data source.
  • Select our created connection.

AJAYTR_ATR66_40-1710248616391.png

  • SAC will retrieve data from S/4HANA. Errors will be popped up if any issues occurred in Connection.
  • All data fetched successfully. We can able to see manually created ODATA service for PoC as well.

AJAYTR_ATR66_41-1710248616394.png

For ERP:

  • Create connection for ERP. Just select ‘SAP ERP’ Data Source instead of S/4 HANA and provide relevant details.

AJAYTR_ATR66_42-1710248616397.png

  • Once connection created, Create New data Model with SAP ERP Data Source via Classic data Model. ERP Systems will be available via Classic Model type only.
  • Select our created connection.

AJAYTR_ATR66_43-1710248616403.png

AJAYTR_ATR66_44-1710248616406.png

 

We have successfully integrated our On-Premise System to SAC. Also SAC Integration steps which we completed support any kind of On-Premise data type (S/4HANA, ERP, SAP BW, BW/4HANA, BPC, ODATA, etc.,)

 

Thanks for Visiting!

Please do connect and follow my Linked In Profile.

https://www.linkedin.com/in/ajaytr66/

AJAY TR - ATR - SAP BASIS ADMINISTRATOR

Labels in this area
Popular Blog Posts