# RFC connection

> To create an integration between your Test Manager project and your SAP system to collect data periodically, using an RFC connection to your SAP system, follow these steps:

To create an integration between your Test Manager project and your SAP system to collect data periodically, using an RFC connection to your SAP system, follow these steps:

## 1. Integrate SAP NetWeaver RFC SDK - Automation Suite

This task demonstrates how to integrate the SAP NetWeaver RFC SDK with your SAP system, so you can use the heatmap in Test Manager deployed with Automation Suite, via an RFC connection.

* Test Manager installed with Automation Suite.
* [SAP Netweaver RFC SDK 7.50](https://support.sap.com/en/product/connectors/nwrfcsdk.html)
* [Test Manager migrator shell script](https://download.uipath.com/testmanager_migrator.sh). Make sure you meet the following environment requirements:
  + `kubectl` configured with a connection to the Automation suite cluster.
  + `jq` (install it using the following command: `yum install jq`)
  + `argocd` CLI ([Installation - Argo CD - Declarative GitOps for Kubernetes](https://argo-cd.readthedocs.io/en/stable/cli_installation/#download-with-curl))
  + `rclone` ([Install Rclone](https://rclone.org/install/))

1. Download the [SAP Netweaver RFC SDK 7.50](https://support.sap.com/en/product/connectors/nwrfcsdk.html) and extract it.
2. Navigate to the `lib` folder and save this folder path.

   In the `lib` folder you'll find the libraries as `.so` files.
3. Copy the libraries to your Automation Suite storage, using the **[Test Manager migrator shell script](https://download.uipath.com/testmanager_migrator.sh)**.
   * For **External object storages** - run the following command in Powershell:
     ```
     ./testmanager_migrator.sh -sap <storage_folder_location> -y
     ```
   * For **InCluster Ceph Object storages** - run the following command in Powershell:
     ```
     ./testmanager_migrator.sh -sap <storage_folder_location> -is -y
     ```

     Replace `storage_folder_location` with the path you saved at Step 2.

After you move the SAP libraries to your Automation Suite storage locations, perform the following validation steps:

1. Check if you can access Test Manager inside Automation Suite.
2. You can create a custom connection with your SAP system in a Test Manager project.

## 2. Create the SAP connection

1. Open your project in Test Manager, and go to **Project Settings** &gt; **Integration**.
2. Select **SAP** from the **New Connection** dropdown. The **Edit connection** dialog pops up.
3. Fill in the fields according to the data from your SAP system:
   1. **Name** - name the integration between Test Manager and SAP.
   2. **Description** - describe the integration between Test Manager and SAP.
4. From **Data Source** select **Connect to SAP instance with RFC**:
   1. **Application Server**—IP address or URL that your SAP system is working on.

      For example, a URL can have the following format: `mysapserver.com`.
   2. **System name**—three-letter SAP system ID.
   3. **Instance Number**—SAP system number.
   4. **Client**—SAP client to log into.
   5. **User**—SAP user name.
   6. **Password**—SAP password.
   7. **Polling Interval**—time interval when data is brought from the SAP system. The minimum value for this is one hour.

      Figure 1. Create new connection with RFC
   ![Create new connection with RFC](https://docs.uipath.com/api/binary/test-manager/2/592050/552232)
5. After you finish the configuration of the integration, select **Save**.
6. Refresh your project. The **Heatmap** page appears in the left-hand menu of your Test Manager project.

## 2. Configure Change Impact Analysis

After you set up RFC connection, choose how to enable Change Impact Analysis, and define which SAP system it connects to:

1. Open your existent SAP connection, or select **SAP** from the **New Connection** dropdown list.
2. Select **Change Impact Analysis connection**.
3. Under **Impact Analysis Access** select the view tabs corresponding to SAP change types that you want to display in your Change Impact Analysis:
   1. **UI**: Selected by default, displays transactions impacted by the selected transports.
   2. **API**: Displays the technical interfaces impacted by the selected transports, such as SAP BAPI, SAP RFC, SAP QUERY, and SAP IDOC.
   3. **Security**: Displays security transactions and corresponding users impacted by the selected transports.
4. Under **Connection Source** select one of the following:
   1. **Same as Heatmap**: Keep the same SAP connection details that you are using for the [Heatmap](https://docs.uipath.com/test-manager/automation-suite/2024.10/user-guide/heatmap). This means both functionalities will collect data from the same SAP system.
   2. **New connection**: Create a separate SAP connection for **Change Impact Analysis**. This option allows you to use different authentication details while maintaining the same connection type as the Heatmap.
      :::note
      We recommend you to connect the Heatmap to your production system and Change Impact Analysis to your quality system for optimal risk evaluation.
      :::
      Follow the same steps as above, for creating a web service connection.
   3. If your Heatmap connection uses a CSV file: You must create a new connection for Change Impact Analysis. Follow the same steps for creating either an RFC or .