Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
Andrew_ENT
Contributor III
Contributor III

QCDI Connection to SAP Extractor

Good Afternoon Everyone,

Happy New Year.

I'm trying to connect QCDI to SAP (Version is ECC 6.06 (Enhancement Pack 6))

We have an existing Data Movement Gateway that is setup and moving data successfully from Another SAP instance (S4 HANA) and uses the SAP Application and SAP HANA DB connections in QCDI. Are we able to use the same DMG for this additional use case or do we need a new DMG? What are the drawbacks of using it for multiple systems?

Is there a guide for creating this type of connection? I tried using this guide here Using the SAP Extractor Connector | Qlik Connectors Help but ran into further issues/questions. That guide says it's only possible for version 7 onwards. I saw somewhere else it said version 6.4 (which we assumed meant service pack 4?)

That article also doesn't mention using a Data Movement Gateway at all. I tried building the connection without a DMG selected and it wouldn't let me.

Are there additional drivers or anything that need to be installed on to the DMG in order to work with this type of connector?

If relevant, we're moving the data into Snowflake.

Thanks in Advance.

3 Replies
TimGarrod
Employee
Employee

Hi Andrew, 

 

That link is for the analytics connector.   
The link you want for QCDI documentation for extractors is here - https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Global_Common/Content/SharedReplic... 


Unlike typical HANA replication where we are capturing from the database, the extractor based method does require addition configuration on the SAP side of things.   

  • Please follow the pre-req's where you must
    • setup the Java connector
    • deploy transports on the SAP machine
    • activate the extractors.   

 

Regarding use of the gateway - SAP extractors require a gateway.  You CAN use the same gateway for Hana replication, extractors and other data sources.  The typical 'mitigating factors' are - 

  1. Ensure the gateway is deployed 'close to your source'
    1. This reduces network latency for CDC workloads (although extractors are more batchy by nature of the extract process)
  2. Workload size
    1. A typical gateway can manage a hundred tasks or more - dependent on volume of data being moved, memory, disk and CPU requirements

Hope this helps and Happy New Year!

 

Andrew_ENT
Contributor III
Contributor III
Author

Thanks Tim. That's very helpful. We're going to work through that guide and will loop back here in a couple of weeks to mark as the accepted solution if it works.

Andrew_ENT
Contributor III
Contributor III
Author

Hi Tim,

I think we've followed all of these steps correctly. But I'm getting the following error

Status(StatusCode="Internal", Detail="SYS-E-HTTPFAIL, Failed to load dynamic endpoint properties. SYS,GENERAL_EXCEPTION,Failed to load dynamic endpoint properties,Failed to find endpoint type 'SAPExtractor' from endpoint server 'Local' Failed to find endpoint type 'SAPExtractor' from endpoint server 'Local' QEM-19, HTTP request failed, Failed to connect using Data Movement gateway local_repsrv. Verify the status in Management Console > Data gateways is "Connected" and then retry the operation.")

How would you suggest troubleshooting this? We've checked and the Data Movement Gateway is definitely connected and everything looks like it is setup correctly.

What should be our next steps for resolving?