ABAP Connections issues

The ABAP connector fails to connect to your SAP ABAP system

• Timeout error message when testing the connection
• Connection error such as “partner not reached” or “internal error”

• Routing, Firewall or DNS issue

Case 1 : Connecting through message server

• When connecting through a message server (port 36xx), the connection will be redirected to the most available application server, by default on port 33xx.
• Therefore the following prerequisites are important:
  • Routing/Firewall must allow opening TCP connections between Redpeaks collector and all message and application servers hosts and ports
  • Message server and application server host names must resolve.

Case 2 : Connecting directly to an application server

• The ABAP connector can be configured to connect directly to an application server
• This setting can be achieved by activating advanced parameters and setting “Force connection on AS number”
• The application server set in that field will be used to compute remote application server port (ie 00 → 3300)
• In such scenario, connector’s host must be set the the target application server.

• In most cases, the connection problem is caused by either routing, DNS or firewall issue
• Use telnet from the collector’s VM to test each host:port connectivity for all message and application servers.
• If host name cannot be resolved, this can be fixed by manually adding it into the /etc/hosts file
• If the error message reports a logon group problem, you can try using SPACE as logon group

• From Redpeaks connector menu, use the test connector button to validate the connection

• ABAP, Firewall, DNS

• Connection error message such as

No RFC authorization for function module RFCPING

• The connection user must be associated with a mandatory authorization profile
• Use PFCG transaction and look for Z_AGENTIL_SOFTWARE_PROMONITOR
• Check that the below actions have been performed:
  • Use Role→Upload to import the profile in the system
  • Edit the profile and navigate to Authorizations tab
  • Press Change authorization data button
  • Press Generate, then Save
  • Use SU01 to assign the profile to the user
• If the profile already exists:
  • Make sure that the authorization tab does not show any warnings (Must display a green square).
  • If it is not the case, Press Change authorization data button and click Generate
  • The authorization icon should turn green

Don't forget to press generate