Troubleshooting

Setup/connection settings

If you have problems setting up the integration, test the availability of the Process Management Gateway Service (typically sap/opu/odata/sap/PROCESSMANAGEMENT/ ):

  1. In the SAP GUI, execute the SAP Gateway Client transaction /IWFND/GW_CLIENT .

  2. Send a GET request against: sap/opu/odata/sap/PROCESSMANAGEMENT/?$format=json .

    You also need to ensure this request is accepted when made from the origin SAP Signavio Process Manager's integration service.

Problem/Error message Solution
URL is not reachable/no message
  • Check which URL you have entered for the Solution Manager. Often this address is an internal one that cannot be reached from the internet. This means the request needs to be rerouted, using a reverse proxy, the SAP Cloud Platform Integration (SCPI), a load balancer, an API management tool, or something similar. The internal domain has to be replaced by the URL of this gateway. The component of the Solution Manager that we access via the API is sap/opu/odata/sap/ProcessManagement.
  • Check the user rights. If the rights are not sufficient, you get an unspecific the error message. In that case, you can view the login of the user in the Solution Manager to confirm that an incorrect URL is not the cause of the problem.
Connection failed (the Solution does not exist) Check the Solution Name you've entered. It has to be the technical name of the Solution that can be found in the properties section of the Solution in the Solution Manager. By default it's the solution name in capital letters.
Connection failed (the Branch does not exist) Check the branch name you've entered. It has to be the technical name of the branch that can be found in the properties section of the branch in the Solution Manager. By default it's the branch name in capital letters.
Credentials are incorrect Check the username and password you've entered to log in to the Solution Manager.
Connection can't be established
  1. Trace the request and check if there is an incoming request of the IPs 3.68.26.78, 3.67.68.183, and 18.192.165.143 (US: 18.235.204.147, 50.16.9.226, and 54.205.22.53, AU 13.236.49.140, 52.64.193.78, and 54.66.30.251) at your firewall and/ or the used gateway.
  2. If there is no incoming request, check the URL you've entered and your firewall settings
  3. If there is an incoming request, check if there is a login or login attempt on the SAP Solution Manager with the credentials entered in the connection settings tab
  4. If there is no login, check your gateway settings
  5. If the login to the Solution Manager is successful but you don't get a message that the connection is established:
    • check the SSL settings of your network. If you use a self-signed certificate inside your network or for your Solution Manager, this certificate needs to be uploaded in the settings.
    • the self-signed certificate is valid for a specific internal IP address. For the SAP Signavio side of the connection, the answer to the request is coming from the gateway and not the internal server IP.
  6. If you still can't establish a connection, please contact our SAP Signavio service experts on the SAP ONE Support Launchpad. To enable our support team to check the logs for your workspace, open the Attribute mappings tab, and note the time you did this.
The connection was established, but diagrams can't be exported
  • For the export, SAP Signavio uses a PUT request, check if your firewall or gateway are blocking these requests.
  • There could be a problem with the session handling and the CSRF Token. For the PUT request SAP Signavio uses the CSRF Token, which is received at the initial login of the session. This CRSF Token could be filtered out of the header at the gateway. It is also possible that the Solution Manager issued a new CRSF Token for each request.
Virus scan error message

If you get the error message Virus scan profile does not exist, SAP Signavio Process Manager cannot access the SAP Solution Manager API.

To have a successful virus scan, an SAP-certified virus scanner software needs to be installed and configured.

If you assume that there is no risk from connections outside your network, for example your SAP Solution Manager server is run in an on-premises structure, it is possible to deactivate the virus scan.

We recommend to configure your virus scan according to the SAP specifics.

Connection test is showing the error Connection failed (Limited connection, cannot modify data on SolMan.) Make sure that in any response the Cross-Site Request Forgery (CSRF) protection token is passed through and not removed. This is necessary to ensure that SAP Signavio Process Manager can modify data in SAP Solution Manager. For details on CSFR, see this section of the SAP Help Portal.

Export

Problem Solution
The connection was established, but diagrams can't be exported
  • For the export, SAP Signavio uses a PUT request, check if your firewall or gateway are blocking these requests.
  • There could be a problem with the session handling and the CSRF Token. For the PUT request SAP Signavio uses the CSRF Token, which is received at the initial login of the session. This CRSF Token could be filtered out of the header at the gateway. It is also possible that the Solution Manager issued a new CRSF Token for each request.
Exports fail

SAP Signavio Process Manager is only able to act as connector to the SAP Solution Manager. This connection is not able to verify the constraints of SAP Solution Manager attributes, for example a size limit. When an attribute is mapped that contains a value that is longer than this size maximum, the export fails. In that case, check the attribute constraints.
Export single models is not possible

You cannot export single models. To export content, select folders that contain the models to be exported. Every model and every subfolder contained in the selected folder is exported.

To export BPM projects to SAP Solution Manager, proceed as described in Export BPM projects to SAP Solution Manager .
Models linked in collapsed subprocesses are not exported

To export a model that links to another model by a collapsed subprocess, the linked model must be in the same top-level folder as the model you want to export. Additionally, make sure that the linked model and the main model are always exported together to ensure that the linked data is consistent.
Export to Solution Manager produces duplicate copies of process and process steps

For exports to update existing structures, the structures need to be included in the scope definition. You need to adjust your scope definition in Solution Manager to include the folder that the SAP Signavio export created. Then all following exports update the content of that folder. See section Scopes.

Scopes are defined in SAP Solution Manager, for details see this section of the SAP Solution Manager WIKI.

Import into the dictionary

Problem/Question Solution
How is the transaction list imported from Solution Manager?

Via the Processmanagement API.

SAP Signavio uses a GET request to retrieve the content of the specified branch. Only executable transactions listed in the Executable Library in this branch are imported.

Is it possible to use an ABAP program from SAP to define the scope of the transaction list that is imported?

The program extracts the executable transactions per system, per module, or per function.

SAP Signavio only imports elements from the Executable Library. If the program can fill the Executable Library or if you can import the program results into that library, you can use the program. SAP Signavio always imports the complete library from the branch.