Configure Connection
SAP guide
Prepare an SAP service account and the SAP .NET Connector libraries, configure NIM, and test access by retrieving roles.
Before you startDirect link to Before you start
Create a service account following the SAP NetWeaver documentation for your installed version. Work with your SAP administrator to authorize the account for the user and role operations your NIM process needs.
NIM requires Hostname, SysId, SyNr, Client, Username, Password, and the DLL path for SAP_DotNetConnector3_Net40_x64.
Prepare the service account and librariesDirect link to Prepare the service account and libraries
- Create a dedicated SAP service account using the vendor documentation linked above.
- Have your SAP administrator grant the permissions needed to collect users and roles, and to perform the intended provisioning and access changes. Include access to
PRGN_ROLE_GETLIST, which the connector uses for its connection test. - Obtain the SAP hostname, system ID, system number, client, and service account credentials.
- Make the
SAP_DotNetConnector3_Net40_x64DLL directory available on the NIM server and record its full local path.
Enter the connection settingsDirect link to Enter the connection settings
- In NIM Studio, open Systems > Overview and add an SAP system, or select the existing system.
- Open its Connection screen.
- Enter the following settings and save the connection.
| NIM setting | Value |
|---|---|
| Hostname | The SAP server hostname supplied by your SAP administrator. |
| SysId | The SAP system ID. |
| SyNr | The SAP system number, preserving any leading zero. |
| Client | The SAP client number for the environment NIM will access. |
| Username | The SAP service account username. |
| Password | The password belonging to that service account. |
| DLL path | The full local path to the SAP_DotNetConnector3_Net40_x64 directory containing the SAP .NET Connector libraries. |
Test role accessDirect link to Test role access
- Select Test Connection. NIM calls the SAP function
PRGN_ROLE_GETLISTto retrieve a list of roles. - Confirm that the test succeeds. If it fails, verify the hostname, system ID, system number, client, credentials, DLL path, and service account permissions.
- Collect the system and inspect Users, Roles, and UserRoles to confirm that the expected data is available.
- Validate intended user provisioning and role assignment changes with safe test records before enabling scheduled automation.
The connection test retrieves roles. Validate user collection and each intended write operation separately.
Step 1 of 3