Storage Management is a middleware software. It is used by various Datavard products for a seamless connection to secondary databases or storages.
This document describes individual storages, their parameters, minimal requirements, and setup procedures.
Supported Technologies
AWS | Azure | Hadoop | Standard DB | |
|---|---|---|---|---|
 |
|
|
|
|
| S3 | Azure Blob | Google Cloud Storage | HDFS | DB2/DB6 |
| Redshift | ADLS Gen1 | BigQuery | Hive | MaxDB |
| ADLS Gen2 | Impala | HANA | ||
| HDInsight | MSSQL | |||
| Databricks | Oracle | |||
| Managed SQL | SybaseIQ | |||
| Sybase ASE |
Technical overview
Datavard Storage Management (SM) is a gateway between SAP and external storages.
In the most cases the secondary DB connection, which is defined in SAP, is used to access an external storage.
An alternative way is when SAP accesses an external storage (special Big Data technologies) through the intermediate SM module.
Communication flow (internal only)
SM translates ABAP commands into a DB specific language.
SAP system uses Storage management to access an external database. Storage management translates an SAP command to a DB specific command, which the external database understands. Based on the configuration, the DB command is executed through Open SQL or Native SQL interface.
Software layout diagram (internal only)
The modules stack of the SM implementation logic.
SM External Metadata - software layer responsible for management of storage metadata. For example it handles special mapping between external storage structures and SAP structures.
SM External Reader - software layer responsible for reading from an external storage. For example it translates a SAP read command into DB specific Data Manipulation Language (DML) statements.
SM External Writer - software layer responsible for writing into an external storage. For example it translates SAP write commands into DB specific DML statements.
SM Storage Setup - Setup of individual storages and storage-IDs is described in the sub-pages of this document.