Merge pull request #216694 from linda33wj/main

prmerger-automator[bot] · web-flow · commit 4d8c7bbf791e · 2022-11-01T08:25:28.000Z
Update connector articles
diff --git a/articles/purview/create-a-scan-rule-set.md b/articles/purview/create-a-scan-rule-set.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 09/27/2021
+ms.date: 11/01/2022
 ---
 
 # Create a scan rule set
diff --git a/articles/purview/register-scan-oracle-source.md b/articles/purview/register-scan-oracle-source.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 05/04/2022
+ms.date: 11/01/2022
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
@@ -64,13 +64,9 @@ Currently, the Oracle service name isn't captured in the metadata or hierarchy.
         > [!Note]
         > The driver should be accessible by the self-hosted integration runtime. By default, self-hosted integration runtime uses [local service account "NT SERVICE\DIAHostService"](manage-integration-runtimes.md#service-account-for-self-hosted-integration-runtime). Make sure it has "Read and execute" and "List folder contents" permission to the driver folder.
 
-## Register
-
-This section describes how to register Oracle in Microsoft Purview using the [Microsoft Purview governance portal](https://web.purview.azure.com/).
-
-### Prerequisites for registration
+### Required permissions for scan
 
-A read-only access to system tables is required.
+Microsoft Purview supports basic authentication (username and password) for scanning Oracle. The Oracle user must have read access to system tables in order to access advanced metadata. For classification, user also needs to have read permission on the tables/views to retrieve sample data.
 
 The user should have permission to create a session and role SELECT\_CATALOG\_ROLE assigned. Alternatively, the user may have SELECT permission granted for every individual system table that this connector queries metadata from:
 
@@ -102,9 +98,9 @@ grant select on V_$INSTANCE to [user];
 grant select on v_$database to [user];
 ```
 
-### Authentication for registration
+## Register
 
-The only supported authentication for an Oracle source is **Basic authentication**.
+This section describes how to register Oracle in Microsoft Purview using the [Microsoft Purview governance portal](https://web.purview.azure.com/).
 
 ### Steps to register
 
@@ -201,6 +197,8 @@ To create and run a new scan, do the following:
 
 1. Select **Continue**.
 
+1. Select a **scan rule set** for classification. You can choose between the system default, existing custom rule sets, or [create a new rule set](create-a-scan-rule-set.md) inline.
+
 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**.
diff --git a/articles/purview/register-scan-sap-bw.md b/articles/purview/register-scan-sap-bw.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 10/21/2022
+ms.date: 11/01/2022
 ms.custom: template-how-to
 ---
 
@@ -61,12 +61,16 @@ When scanning SAP BW source, Microsoft Purview supports extracting technical met
         > [!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:
+    * Self-hosted integration runtime communicates with the SAP server over dispatcher port 32NN and gateway port 33NN, where NN is your SAP instance number from 00 to 99. Make sure the outbound traffic is allowed on your firewall.
+
+* 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. For scan execution, 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)
+    * Z_MITI_BW_DOWNLOAD (main metadata import, the function module you create following the Purview guide)
+    
+    The underlying SAP Java Connector (JCo) libraries may call additional RFC function modules e.g. RFC_PING, RFC_METADATA_GET, etc., refer to [SAP support note 460089](https://launchpad.support.sap.com/#/notes/460089) for details.
 
 ## Register
 
diff --git a/articles/purview/register-scan-sapecc-source.md b/articles/purview/register-scan-sapecc-source.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 05/04/2022
+ms.date: 11/01/2022
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
@@ -67,9 +67,16 @@ When scanning SAP ECC source, Microsoft Purview supports:
         > [!Note]
         > The driver should be accessible by the self-hosted integration runtime. By default, self-hosted integration runtime uses [local service account "NT SERVICE\DIAHostService"](manage-integration-runtimes.md#service-account-for-self-hosted-integration-runtime). Make sure it has "Read and execute" and "List folder contents" permission to the driver folder.
 
-* 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'll 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)
+    * Self-hosted integration runtime communicates with the SAP server over dispatcher port 32NN and gateway port 33NN, where NN is your SAP instance number from 00 to 99. Make sure the outbound traffic is allowed on your firewall.
+
+* 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'll need an ABAP developer account to create the RFC function module on the SAP server. For scan execution, 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_DOWNLOAD (main metadata import, the function module you create following the Purview guide)
+    
+    The underlying SAP Java Connector (JCo) libraries may call additional RFC function modules e.g. RFC_PING, RFC_METADATA_GET, etc., refer to [SAP support note 460089](https://launchpad.support.sap.com/#/notes/460089) for details.
 
 ## Register
 
diff --git a/articles/purview/register-scan-saps4hana-source.md b/articles/purview/register-scan-saps4hana-source.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 01/20/2022
+ms.date: 11/01/2022
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
@@ -67,9 +67,16 @@ When scanning SAP S/4HANA source, Microsoft Purview supports:
         > [!Note]
         > The driver should be accessible by the self-hosted integration runtime. By default, self-hosted integration runtime uses [local service account "NT SERVICE\DIAHostService"](manage-integration-runtimes.md#service-account-for-self-hosted-integration-runtime). Make sure it has "Read and execute" and "List folder contents" permission to the driver folder.
 
-* 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'll 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)
+    * Self-hosted integration runtime communicates with the SAP server over dispatcher port 32NN and gateway port 33NN, where NN is your SAP instance number from 00 to 99. Make sure the outbound traffic is allowed on your firewall.
+
+* 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'll need an ABAP developer account to create the RFC function module on the SAP server. For scan execution, 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_DOWNLOAD (main metadata import, the function module you create following the Purview guide)
+    
+    The underlying SAP Java Connector (JCo) libraries may call additional RFC function modules e.g. RFC_PING, RFC_METADATA_GET, etc., refer to [SAP support note 460089](https://launchpad.support.sap.com/#/notes/460089) for details.
 
 ## Register
 
diff --git a/articles/purview/register-scan-teradata-source.md b/articles/purview/register-scan-teradata-source.md
@@ -6,7 +6,7 @@ ms.author: jingwang
 ms.service: purview
 ms.subservice: purview-data-map
 ms.topic: how-to
-ms.date: 05/04/2022
+ms.date: 11/01/2022
 ms.custom: template-how-to, ignite-fall-2021
 ---
 
@@ -41,7 +41,7 @@ When setting up scan, you can choose to scan an entire Teradata server, or scope
 
 ### Required permissions for scan
 
-Microsoft Purview supports basic authentication (username and password) for scanning Teradata. The Teradata user must have read access to system tables in order to access advanced metadata.
+Microsoft Purview supports basic authentication (username and password) for scanning Teradata. The Teradata user must have read access to system tables in order to access advanced metadata. For classification, user also needs to have read permission on the tables/views to retrieve sample data.
 
 To retrieve data types of view columns, Microsoft Purview issues a prepare statement for `select * from <view>` for each of the view queries and parse the metadata that contains the data type details for better performance. It requires the SELECT data permission on views. If the permission is missing, view column data types will be skipped.
 
@@ -144,6 +144,8 @@ Follow the steps below to scan Teradata to automatically identify assets. For mo
 
 1. Select **Continue**.
 
+1. Select a **scan rule set** for classification. You can choose between the system default, existing custom rule sets, or [create a new rule set](create-a-scan-rule-set.md) inline.
+
 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**.
