Merge pull request #190742 from linda33wj/purview

tamarakhader · web-flow · commit 7020a96abde1 · 2022-03-07T13:27:45.000+03:00
Add SAP BW support in Purview
diff --git a/articles/purview/abap-functions-deployment-guide.md b/articles/purview/abap-functions-deployment-guide.md
@@ -6,12 +6,12 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-catalog
 ms.topic: conceptual
-ms.date: 12/20/2021
+ms.date: 03/05/2022
 ---
 
 # SAP ABAP function module deployment guide
 
-When you scan [SAP ECC](register-scan-sapecc-source.md) or [SAP S/4HANA](register-scan-saps4hana-source.md) sources in Azure Purview, you need to create the dependent ABAP function module in your SAP server. Azure Purview invokes this function module to extract the metadata from your SAP system during scan.
+When you scan [SAP ECC](register-scan-sapecc-source.md), [SAP S/4HANA](register-scan-saps4hana-source.md) and [SAP BW](register-scan-sap-bw.md) sources in Azure Purview, you need to create the dependent ABAP function module in your SAP server. Azure Purview invokes this function module to extract the metadata from your SAP system during scan.
 
 This document details the steps required to deploy this module.
 
@@ -20,7 +20,7 @@ This document details the steps required to deploy this module.
 
 ## Prerequisites
 
-Download the SAP ABAP function module source code from Azure Purview Studio. After you register a source for [SAP ECC](register-scan-sapecc-source.md) or [SAP S/4HANA](register-scan-saps4hana-source.md), you can find a download link on top as follows. 
+Download the SAP ABAP function module source code from Azure Purview Studio. After you register a source for [SAP ECC](register-scan-sapecc-source.md),[SAP S/4HANA](register-scan-saps4hana-source.md) or [SAP BW](register-scan-sap-bw.md), you can find a download link on top as follows. You can also see the link when new or edit a scan.
 
 :::image type="content" source="media/abap-functions-deployment-guide/download-abap-code.png" alt-text="Download ABAP function module source code from Azure Purview Studio" border="true":::
 
@@ -30,7 +30,7 @@ Download the SAP ABAP function module source code from Azure Purview Studio. Aft
 
 This step is optional, and an existing package can be used.
 
-1. Log in to the SAP S/4HANA or SAP ECC server and open **Object Navigator** (SE80 transaction).
+1. Log in to the SAP server and open **Object Navigator** (SE80 transaction).
 
 2. Select option **Package** from the list and enter a name for the new package (for example, Z\_MITI) then press button **Display**.
 
@@ -117,9 +117,10 @@ When all the previous steps are completed, follow the below steps to test the fu
 
 4. Put the name of the area of interest into P\_AREA field if a file with metadata must be downloaded or updated. When the function finishes working, the folder which has been indicated in P\_LOCAL\_PATH parameter must contain several files with metadata inside. The names of files mimic areas which can be specified in P\_AREA field.
 
-The function will finish its execution and metadata will be downloaded much faster in case of launching it on the machine which has high-speed network connection with SAP S/4HANA or ECC server.
+The function will finish its execution and metadata will be downloaded much faster in case of launching it on the machine which has high-speed network connection with SAP server.
 
 ## Next steps
 
 - [Register and scan SAP ECC source](register-scan-sapecc-source.md)
 - [Register and scan SAP S/4HANA source](register-scan-saps4hana-source.md)
+- [Register and scan SAP Business Wareouse (BW) source](register-scan-sap-bw.md)
diff --git a/articles/purview/azure-purview-connector-overview.md b/articles/purview/azure-purview-connector-overview.md
@@ -40,6 +40,7 @@ The table below shows the supported capabilities for each data source. Select th
 || [MySQL](register-scan-mysql.md) | [Yes](register-scan-mysql.md#register) | No | [Yes](register-scan-mysql.md#scan) | No |
 || [Oracle](register-scan-oracle-source.md) | [Yes](register-scan-oracle-source.md#register)|  No | [Yes*](register-scan-oracle-source.md#lineage) | No|
 || [PostgreSQL](register-scan-postgresql.md) | [Yes](register-scan-postgresql.md#register) | No | [Yes](register-scan-postgresql.md#lineage) | No |
+|| [SAP Business Warehose](register-scan-sap-bw.md) | [Yes](register-scan-sap-bw.md#register) | No | No | No |
 || [SAP HANA](register-scan-sap-hana.md) | [Yes](register-scan-sap-hana.md#register) | No | No | No |
 || [Snowflake](register-scan-snowflake.md) | [Yes](register-scan-snowflake.md#register) | No | [Yes](register-scan-snowflake.md#lineage) | No |
 ||    [SQL Server](register-scan-on-premises-sql-server.md)| [Yes](register-scan-on-premises-sql-server.md#register) |[Yes](register-scan-on-premises-sql-server.md#scan) | No* | No|
diff --git a/articles/purview/media/register-scan-sap-bw/register-sap-bw.png b/articles/purview/media/register-scan-sap-bw/register-sap-bw.png
diff --git a/articles/purview/media/register-scan-sap-bw/scan-sap-bw.png b/articles/purview/media/register-scan-sap-bw/scan-sap-bw.png
diff --git a/articles/purview/register-scan-sap-bw.md b/articles/purview/register-scan-sap-bw.md
@@ -0,0 +1,153 @@
+---
+title: Connect to and manage an SAP Business Warehouse
+description: This guide describes how to connect to SAP Business Warehouse in Azure Purview, and use Azure Purview's features to scan and manage your SAP BW source.
+author: linda33wj
+ms.author: jingwang
+ms.service: purview
+ms.subservice: purview-data-map
+ms.topic: how-to
+ms.date: 03/05/2022
+ms.custom: template-how-to
+---
+
+# Connect to and manage SAP Business Warehouse in Azure Purview (Preview)
+
+This article outlines how to register SAP Business Warehouse (BW), and how to authenticate and interact with SAP BW in Azure Purview. For more information about Azure Purview, read the [introductory article](overview.md).
+
+[!INCLUDE [feature-in-preview](includes/feature-in-preview.md)]
+
+## Supported capabilities
+
+|**Metadata Extraction**|  **Full Scan**  |**Incremental Scan**|**Scoped Scan**|**Classification**|**Access Policy**|**Lineage**|
+|---|---|---|---|---|---|---|
+| [Yes](#register)| [Yes](#scan)| No | No | No | No| No|
+
+The supported SAP BW versions are 7.3 to 7.5. SAP BW4/HANA is not supported.
+
+When scanning SAP BW source, Azure Purview supports extracting technical metadata including:
+
+- Instance
+- InfoArea
+- InfoSet
+- InfoSet query
+- Classic InfoSet
+- InfoObject including unit of measurement, time characteristic, navigation attribute, data packet characteristic, currency, characteristic, field, and key figure
+- Data store object (DSO)
+- Aggregation level
+- Open hub destination
+- Query including the query condition
+- Query view
+- HybridProvider
+- MultiProvider
+- InfoCube
+- Aggregate
+- Dimension
+- Time dimension
+
+## Prerequisites
+
+* An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
+
+* An active [Azure Purview resource](create-catalog-portal.md).
+
+* You need Data Source Administrator and Data Reader permissions to register a source and manage it in Azure Purview Studio. For more information about permissions, see [Access control in Azure Purview](catalog-permissions.md).
+
+* Set up the latest [self-hosted integration runtime](https://www.microsoft.com/download/details.aspx?id=39717). For more information, see [the create and configure a self-hosted integration runtime guide](manage-integration-runtimes.md). The minimal supported Self-hosted Integration Runtime version is 5.15.8079.1.
+
+* Ensure [JDK 11](https://www.oracle.com/java/technologies/javase-jdk11-downloads.html) is installed on the machine where the self-hosted integration runtime is installed.
+
+* Ensure Visual C++ Redistributable for Visual Studio 2012 Update 4 is installed on the self-hosted integration runtime machine. If you don't have this update installed, [you can download it here](https://www.microsoft.com/download/details.aspx?id=30679).
+
+* The connector reads metadata from SAP using the [SAP Java Connector (JCo)](https://support.sap.com/en/product/connectors/jco.html) 3.0 API. Make sure the Java Connector is available on your machine where self-hosted integration runtime is installed. Make sure that you use the correct JCo distribution for your environment, and the **sapjco3.jar** and **sapjco3.dll** files are available.
+
+    > [!Note]
+    > The driver should be accessible to all accounts in the machine. Don't put it in a path under user account.
+
+* Deploy the metadata extraction ABAP function module on the SAP server by following the steps mentioned in [ABAP functions deployment guide](abap-functions-deployment-guide.md). You need an ABAP developer account to create the RFC function module on the SAP server. The user account requires sufficient permissions to connect to the SAP server and execute the following RFC function modules:
+
+    * STFC_CONNECTION (check connectivity)
+    * RFC_SYSTEM_INFO (check system information)
+    * OCS_GET_INSTALLED_COMPS (check software versions)
+    * Z_MITI_BW_DOWNLOAD (main metadata import)
+
+## Register
+
+This section describes how to register SAP BW in Azure Purview using the [Azure Purview Studio](https://web.purview.azure.com/).
+
+### Authentication for registration
+
+The only supported authentication for SAP BW source is **Basic authentication**.
+
+### Steps to register
+
+1. Navigate to your Azure Purview account.
+1. Select **Data Map** on the left navigation.
+1. Select **Register**.
+1. In **Register sources**, select **SAP BW** > **Continue**.  
+
+On the **Register sources (SAP BW)** screen, do the following:
+
+1. Enter a **Name** that the data source will be listed within the Catalog.
+
+1. Enter the **Application server** name to connect to SAP BW source. It can also be an IP address of the SAP application server host.
+
+1. Enter the SAP **System number**. It's an integer between 0 and 99.
+
+1. Select a collection or create a new one (Optional).
+
+1. Finish to register the data source.
+
+    :::image type="content" source="media/register-scan-sap-bw/register-sap-bw.png" alt-text="Screenshot of registering an SAP BW source." border="true":::
+
+## Scan
+
+Follow the steps below to scan SAP BW to automatically identify assets and classify your data. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
+
+### Create and run scan
+
+1. In the Management Center, select Integration runtimes. Make sure a self-hosted integration runtime is set up. If it isn't set up, use the steps mentioned [here](./manage-integration-runtimes.md) to create a self-hosted integration runtime.
+
+1. Navigate to **Sources**
+
+1. Select the registered SAP BW source.
+
+1. Select **+ New scan**
+
+1. Provide the below details:
+
+    1. **Name**: The name of the scan
+
+    1. **Connect via integration runtime**: Select the configured self-hosted integration runtime.
+
+    1. **Credential**: Select the credential to connect to your data source. Make sure to:
+
+        * Select Basic Authentication while creating a credential.
+        * Provide a user ID to connect to SAP server in the User name input field.
+        * Store the user password used to connect to SAP server in the secret key.
+
+    1. **Client ID**: Enter the SAP Client ID. It's a three-digit numeric number from 000 to 999.
+
+    1. **JCo library path**: The directory path where the JCo libraries are located.
+
+    1. **Maximum memory available:** Maximum memory (in GB) available on the Self-hosted Integration Runtime machine to be used by scanning processes. This is dependent on the size of SAP BW source to be scanned. 
+
+        :::image type="content" source="media/register-scan-sap-bw/scan-sap-bw.png" alt-text="Screenshot of setting up an SAP BW scan." border="true":::
+
+1. Select **Test connection**.
+
+1. Select **Continue**.
+
+1. Choose your **scan trigger**. You can set up a schedule or ran the
+    scan once.
+
+1. Review your scan and select **Save and Run**.
+
+[!INCLUDE [create and manage scans](includes/view-and-manage-scans.md)]
+
+## Next steps
+
+Now that you have registered your source, follow the below guides to learn more about Azure Purview and your data.
+
+- [Search Data Catalog](how-to-search-catalog.md)
+- [Data insights in Azure Purview](concept-insights.md)
+- [Supported data sources and file types](azure-purview-connector-overview.md)
diff --git a/articles/purview/toc.yml b/articles/purview/toc.yml
@@ -182,6 +182,8 @@ items:
       href: register-scan-power-bi-tenant.md
     - name: Salesforce
       href: register-scan-salesforce.md
+    - name: SAP Business Warehouse
+      href: register-scan-sap-bw.md
     - name: SAP ECC
       href: register-scan-sapecc-source.md
     - name: SAP HANA 
