Troubleshooting the integration with the SAP Solution Manager

This sections offers solutions to known issues that can occur when installing and configuring the Signavio SAP Solution Manager Connector.

The setup page is empty/blank

Please check the recent log file of the SolMan connector at logs/solmanconnector.log.

You might find this exception error statement:

2015-01-07 17:18:53,577 ERROR ( - Error in request <SignavioURL>

at Method)






The problem could be caused by the following:

  • Your network connection might require a proxy to make outgoing requests to the Signavio server (see above).
  • The URL of the Signavio server cannot be resolved to an IP address (
    via DNS.

Please try to solve the issue as follows:

Check check if the network port is already used by another application:

  • On Windows CMD: netstat -aon | more
  • On Unix bash: netstatt -aon | grep LISTEN

Check if the BSI* web service of SAP Solution Manager reports detailed errors.

The Signavio Connector for SAP Solution Manager leverages several SOAP web services of SAP Solution Manager. In case the Signavio Connector for SAP Solution Manager reports a problem using one if this web service we can check SAP Solution Manager’s error log to investigate the root cause of this error.

Below you find an example excerpt of the connector log:

2015-01-30 10:40:32,467 ERROR ( - Unexpected exception HTTP transport error: Connection refused

The SAP transaction code SRT_UTIL provides access to the error log:

Enter the transaction code  'SRT_UTIL'.

Enter the transaction code ‘SRT_UTIL’.

Click Error log to open the log:

Open the error log.

Open the error log.

Configuration of a firewall or SSL proxy

If your network security team has configured a SSL firewall proxy, it might happen that the SSL connection to the Signavio server is intercepted for security scanning. In some cases the SSL proxy adds its own SSL certificate to the certificate chain and therefore the Signavio connector for SAP Solution Manager cannot validate the SSL handshake as the proxy’s certificate is unknown to the connector.

At logs/solmanconnector.log you will find a message similar to this:

2015-01-20 14:13:34,009 ERROR ( - Error in request PKIX path building failed: unable to find valid certification path to requested target...
Caused by: unable to find valid certification path to requested target
at at
... 57 more

To activate Java SSL debug output for the connector, the last line of the startup script has to be modified:

Start the Signavio SAP Solution Manager 7.1 Connector:

%JAVA_HOME%\bin\java.exe -jar solman71connector.jar start

This will create debug output on the command line, which helps to identify the untrusted SSL certificate.

Shortened example output:

abc-123455-24, READ: TLSv1 Handshake, length = 1024
*** Certificate chain
chain [0] = [[Version: V3 Subject: O=Fortinet Ltd., CN=FG... Signature Algorithm: SHA1withRSA, OID = 1.2.345.67890543345.1.1.1...// cut //
abc-123455-24, SEND TLSv1 ALERT:  fatal, description = certificate_unknown

There are two possible solutions:

  • Change the configuration of the SSL proxy/firewall to allow trace from Signavio connector for SAP Solution Manager to the Signavio server.
  • Add the SSL certificate as a trusted certificate to the Java keystore of the connector:
keytool.exe -import -trustcacerts -file fortinet.cer -keystore

The keytool can be found in sapjvm_8\bin.

The Connector does not start because the SAP JVM 8.1 cannot be found

Make sure you downloaded the SAP JVM 8.1 and unpacked it in the installation directory Signavio Solution Manager Connector.

Read more at Downloading and extracting the SAP JVM 8.1.


In case you installed the SAP JVM somewhere else, you can adjust the corresponding paths in the startup, shutdown and (for Windows) service scripts.

You find more information about the SAP JVM in the SAP Documentation.