---
title: docuflow ECM
slug: docuflow-for-filenet/docuflow-ecm
createdAt: 2020-02-25T01:43:25.000Z
---

At this point no additional configuration is required to establish connectivity and docuflow ECM connectivity testing can be done so via: 

1. The test connection buttons at the Enterprise Connector level for both SAP and P8 endpoints (refer to <u>Base docuflow Enterprise Connector Configuration – docuflow ECM Only</u>)
2. Using transaction SM59 within SAP to ensure the RFC connection configured in <u>Configure SAP RFC destinations – docuflow ECM Only</u> can now communicate with the docuflow Enterprise Connector.

\* Make sure the Enterprise Connector server is turned on (windows service “VersaFile docuflow Enterprise Connector”) prior to executing the SM59 test connection. 

Select the Connection Test button. You should see a successful connection with timing similar to the below: 

::Image[]{src="https://api.archbee.com/api/presign/image_4a8fbfb4-f881-4c2c-b3c6-da296f8029bb.png" size="52" position="center" showCaption="false"}

In addition, via the docuflow System Dashboard, you should now see a green light under the column “API” as shown below. This indicates that SAP has the RFC connection to the matching docuflow Enterprise Connector middleware and configuration. 

![](https://archbee-doc-uploads.s3.amazonaws.com/image_67b8f9a8-fb25-4d09-93e9-260759a4f081.png)

Note that until the API destination(s) and CMS Use Tags are utilized in a docuflow processing rule such as DocManager or Migrator, etc., they will show as “unused”.