Test Hermes SAP ECC RFC Connectivity

Run this test from the server where Hermes will run, or from a server with the same network route and security controls. It verifies that Hermes can establish an SAP RFC connection using the configured technical user.

This probe is read-only. It opens an RFC connection, runs RFC_PING, and calls SAP's standard STFC_STRUCTURE test function. It does not create, change, or delete SAP data.

Before you begin

Make sure you have:

• A Hermes installation for the operating system of the test host.
• An SAP ECC non-production endpoint approved for RFC access from the Hermes host.
• An SAP technical RFC user and its credentials.
• The SAP application-server connection details: host name, system number, client, and logon language. If SAP Basis has provided a named RFC destination, SAProuter route, load-balanced connection, or SNC requirements, use their supplied connection configuration instead.

SAP Basis and network teams should confirm the approved RFC route, firewall rules, endpoint, and any SNC requirements. Do not assume a particular SAP port or route from this test alone.

Configure the test connection

In the Hermes installation directory, create or edit production.json. Configure the ECC adapter and its ECCParams connection settings:

{
  "adapterType": "SAP_EH8",
  "ECCParams": {
    "hostAddr": "<ECC_RFC_HOSTNAME>",
    "sysnr": "<SYSTEM_NUMBER>",
    "client": "<CLIENT>",
    "user": "<HERMES_RFC_USER>",
    "passwd": "<HERMES_RFC_PASSWORD>",
    "lang": "EN"
  }
}

Replace the placeholders with values provided by SAP Basis. Keep production.json protected because it contains credentials. Do not send this file to Graphite Support.

Using a named destination or SAProuter? Configure the RFC destination or route exactly as SAP Basis provides it. The connection test supports the ECCParams.dest setting as an alternative to a direct host configuration.

Run the probe

Stop the Hermes service first if it is already running so the test and service do not use the same configuration or technical user at the same time.

Linux

From the Hermes installation directory:

chmod +x test.sh
./test.sh

Windows

Open Command Prompt in the Hermes installation directory and run:

test.cmd

Confirm a successful result

The console output should include:

SAP RFC connection successful.
STFC_STRUCTURE response: ...

This confirms that, from the test host:

• The configured SAP RFC endpoint is reachable.
• The technical user can authenticate.
• The user can execute the probe RFC calls.

It does not confirm authorization for Hermes vendor synchronization. Before production use, validate the least-privilege user role and the required vendor create/update scenarios in a non-production ECC environment.

Troubleshoot a failed probe

Common causes include an incorrect endpoint, blocked network path, SAProuter or SNC configuration that has not been applied, invalid credentials, a locked/expired SAP user, or missing authorization for the probe function.

If requested by Graphite Support, rerun the probe with additional diagnostics:

Linux or macOS

HERMES_TEST_VERBOSE=1 ./test.sh

Windows

set HERMES_TEST_VERBOSE=1
test.cmd

Before sharing output, remove passwords, user names, host names, IP addresses, SAProuter strings, and any other customer-sensitive information. Never share production.json.