--- title: Set up the SAP ECC IDoc spoke description: Integrate the ServiceNow instance and SAP ECC IDoc spoke by using the Basic Auth credentials to authenticate ServiceNow requests.Configure MID Server using the SAP proprietary JAR files to integrate SAP ECC IDoc account with your ServiceNow instance.Create a credential record for the SAP ECC IDoc account. The SAP ECC IDoc spoke connection and credential alias uses these credentials to authorize actions.Modify the short description to provide spoke specific information.Create a connection record for your SAP ECC IDoc account. The SAP ECC IDoc spoke connection and credential aliases use these connections to perform actions in SAP ECC IDoc. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/integrate-applications/integration-hub/setup-sap-ecc-idoc.html release: australia product: Integration Hub classification: integration-hub topic_type: task last_updated: "2026-03-12" reading_time_minutes: 3 breadcrumb: [SAP ECC IDoc Spoke, Integration Hub spokes, Build integrations, Integration Hub, Workflow Data Fabric] --- # Set up the SAP ECC IDoc spoke Integrate the ServiceNow instance and SAP ECC IDoc spoke by using the Basic Auth credentials to authenticate ServiceNow requests. ## Before you begin - Request an Integration Hub subscription. - Activate the SAP ECC IDoc spoke. - Role required: admin. ## Configure MID Server for the SAP ECC IDoc spoke Configure MID Server using the SAP proprietary JAR files to integrate SAP ECC IDoc account with your ServiceNow® instance. ### Before you begin Role required: admin. ### Procedure 1. Navigate to **All** > **System Properties** > **Security**. **Note:** This is applicable only if your MID Server is installed on a Linux machine 2. Disable the MIME type validation for file attachments. \[Omitted image "mime-type-sap-ecc-rfc.png"\] Alt text: Option to disable the MIME type validation **Note:** This is applicable only if your MID Server is installed on a Linux machine. 3. Navigate to **MID Server** > **JAR Files**. 4. Upload the required SAP proprietary files \(JAR, SO, or DLL\) obtained after contacting your SAP ECC IDoc admin. For more information, see [Synchronize a JAR file to MID Servers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_SynchronizeAJARFiletoMIDServers.md). ### What to do next Ensure that the files are synchronised in the `/agent/extlib` directory. If the files aren't synchronised, restart the MID Server. ## Create a credential record for the SAP ECC IDoc spoke Create a credential record for the SAP ECC IDoc account. The SAP ECC IDoc spoke connection and credential alias uses these credentials to authorize actions. ### Before you begin Role required: admin. ### Procedure 1. Navigate to **All** > **Connections & Credentials** > **Credentials**. 2. Click **New**. The system displays this message: `What type of Credentials would you like to create?` 3. Select **Basic Auth Credentials**. 4. On the form, fill these values. |Field|Description| |-----|-----------| |Name|Name to uniquely identify the record. For example, `SAP ECC IDoc Cred`.| |User name|User name to log in to your SAP ECC IDoc account.| |Password|Password to authenticate and log in to your SAP ECC IDoc account.| |Active|Option to actively use the credential record.| |Order|Order to apply this credential. For example, `100`.| |Credential alias|Credential alias associated with the spoke.| 5. Click **Submit**. ## Create a connection record for the SAP ECC IDoc spoke Create a connection record for your SAP ECC IDoc account. The SAP ECC IDoc spoke connection and credential aliases use these connections to perform actions in SAP ECC IDoc. ### Before you begin Role required: admin. ### Procedure 1. Navigate to **All** > **Connections & Credentials** > **Connections & Credentials Aliases**. 2. Open the alias record for SAP ECC IDoc. 3. From the **Connections** tab, click **New**. 4. On the form, fill these fields. |Field|Description| |-----|-----------| |Name|Name to uniquely identify the record. For example, `SAP ECC IDoc Connection`.| |Credential|Credential record created for SAP ECC IDoc spoke. For example, `SAP ECC IDoc Cred`.| |Connection alias|Alias record associated with this connection.| |Host|Fully qualified domain name of the target host where the SAP ECC IDoc server is installed.| |Active|Option to actively use the connection record.| |Domain|Domain that the action runs in.| |Override default port|Target port used by the connection. If blank, the system uses the default port.| |Use MID server|Option to use a MID Server for this connection. Select the check box and define the fields in the **Advanced MID Server Configuration** tab.| 5. In the **Advanced MID Server Configuration** tab, provide these details.
Field Description
Capabilities Capabilities the MID Server must support to be eligible for selection. The system runs the action or activity from a MID Server that supports the selected capabilities.Required capabilities determine which MID Server is selected at runtime. To learn more about how a MID Server is selected during runtime, see [MID Server selection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_MIDServerSelector.md).
MID Application Application the MID Server must support to be eligible for selection. The system runs the action from a MID Server that supports the selected application.To learn more about how a MID Server is selected during runtime, see [MID Server selection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/c_MIDServerSelector.md).
6. In the **Attributes** tab, provide these details. |Field|Description| |-----|-----------| |Client|Client value of the target host where the SAP ECC IDoc server is installed.| |u\_system\_number|System number of the target host where the SAP ECC IDoc server is installed.| |u\_lang|Language selected in the target host where the SAP ECC IDoc server is installed.| 7. Click **Submit**.