This blog narrates the procedure of Google BigQuery & SAP SLT integration. The Source system is SAP ECC & target is Google BigQuery while tables get replicated using SAP SLT.
System Environment
SLT 2.0 SP 18
DMIS 2011 SP 18
NW 7.5 SP 18
Cloud Provider – GCP
BigQuery Connector Version - 2.5
Architecture:
Below diagram shows the architecture of two projects, one having Data Analytics & second one has standalone SAP SLT installed. Since the SAP SLT is installed on Google Cloud, BigQuery API endpoint connects directly to BigQuery Connector, without requiring a Cloud VPN connection or Cloud Interconnect.
Installation:
BigQuery connector is installed as a Business Add-In (BadI) captured in a Transport Request within an SAP LT Replication Server instance.
Enable the required Google cloud APIs on SAP SLT VMs
Login to https://console.cloud.google.com/ & enable ‘The Big Query API’ & ‘The IAM Service Account Credentials API’ APIs on the SLT VMs where BigQuery connector will be installed. Also, allow full access to cloud APIs.
Install the GCLOUD CLI on SLT VMs.
Use SIDADM to install the CLI.
Establish Trust between SAP SLT & Google BigQuery
Now that the GCLOUD CLI is installed, the next step is to Import certificates into SSL Client (standard) in strust. Download GTS Root R1 and GTS CA 1C3 & import under SSL client SSL Client (Standard) in Strust from Google Trust Services repository for handshake between SAP SLT system & Google BigQuery
Install BigQuery SAP connector
Copy the Cofile & data file under /usr/sap/trans respective directories. Import the TR in your SLT system using STMS_IMPORT T-Code. To confirm installation of the connector, check the BAdI implementation in se80 ->/GOOG/EI_IUUC_REPL_RUNTIME_BQ
Also, validate table IUUC_REPL_APPL if below entries are present using se16.
/GOOG/SLT_BQ & ZGOOG_SLT_BQ.
Configure Replication
Specify access settings in SM30 -> /GOOG/CLIENT_KEY
Once you are done configuring BigQuery Connector for SAP and testing your connection to Google Cloud, Google recommends token caching to be enabled
Configure RFC Destinations
RFC destinations are used to connect to BigQuery and IAM APIs by the BigQuery Connector for SAP.
Change the RFC name to customized RFC Name.
Under Logon & Security tab, Set SSL to Active & use DEFAULT SSL Client (Standard) Certificate.
Select HTTP 1.1 under special options.
A response containing 404 Not Found is acceptable and expected because the endpoint specified in the RFC destination corresponds to a Google Cloud service and not a specific resource hosted by the service.
In the table /GOOG/SERVIC_MAP, create entries as shown.
Create an SAP LT Replication Server replication configuration.
Go to LTRC in SLT system & Click Create.
Select RFC connection or DB connection based on your architecture.
Select SLT SDK
Value for below application will be picked from table IUUC_REPL_APPL
Click Next, review your configuration & click Create. This concludes the SLT & Source system configuration.
To proceed with Target side configuration, create a mass transfer configuration for BigQuery. Use the custom T-Code /GOOG/SLT_SETTINGS & maintain settings as shown.
Table level settings can be modified as shown below. More details
This concludes the overall configuration of SAP SLT & Google BigQuery Setup. Hope this blog helps you to configure BigQuery as a target using SLT in your Landscape.
Reference: https://cloud.google.com/solutions/sap/docs/bq-connector/latest/planning
https://cloud.google.com/solutions/sap/docs/bq-connector/latest/install-config-on-gc#download-instal...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
7 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 | |
3 | |
3 |