Skip to main content

Get help for ARIS Process Mining functions and services

Use a proxy server for Process Extractor

You can use an HTTPS proxy server to connect Process Extractor to ARIS Process Mining. You can configure a proxy that considers both external and internal communication.

To configure a proxy for Process Extractor, you must modify the custom_wrapper.conf file. The file is located in the Process Extractor installation directory <installation directory>/wrapper/conf.

Procedure. Procedure

  1. Open the custom_wrapper.conf file in a suitable editor.

  2. Set the proxy for an external communication

    1. If Process Extractor needs to communicate with the Process Mining Cloud (mc.ariscloud.com or processmining.ariscloud.com) via an https proxy, add the following to the custom_wrapper.conf file:

      wrapper.java.additional.20=-Dhttps.proxyHost=<your proxy host parameter>

      wrapper.java.additional.21=-Dhttps.proxyPort=<your proxy port parameter>

    2. Replace <proxy_host> with the hostname or IP address of your proxy server, and <proxy_port> with the port number.

  3. Disable the proxy for an internal communication:

    1. If Process Extractor communicates with internal services (like source systems or ARIS Process Mining OnPrem) that should not use the HTTPS proxy, you must set the following exclusions:

      wrapper.java.additional.22=-Dhttp.nonProxyHosts=<internal_host1>|<internal_host2>

    2. If Process Extractor communicates via a socket connection, add the following line to exclude the communication with these systems from the proxy:

      wrapper.java.additional.23=-DsocksNonProxyHosts=<internal_host1>|<internal_host2>

    3. Replace <internal_host1> and <internal_host2> with the internal hosts that should bypass the proxy.

    4. To exclude any localhost communication, add this text to your hosts list:

      |localhost|127.*|[::1]|0.0.0.0|[::0]

      Example

      wrapper.java.additional.23=-DsocksNonProxyHosts=sqlserver.mydomain.com|localhost|127.*|[::1]|0.0.0.0|[::0]

  4. Handling of different scenarios:

    1. No proxy required: If your application does not require a proxy, ensure that no proxy settings are configured in the custom_wrapper.conf.

    2. Only external proxy: Only set the external proxy settings as mentioned in step 2.

    3. Both external and internal: Set both external proxy settings and the nonProxyHosts for internal services as mentioned in step 3.

  5. Restart Process Extractor after making changes to the custom_wrapper.conf file.

You configured a proxy to use Process Extractor for an internal or external communication.

Notes

  • If your source system is an internal system and not accessible via the SSL proxy, the log shows a 502 Bad Gateway error. In this case you must add the following line to exclude the internal service from the proxy connection (see step 3).

    wrapper.java.additional.22=-Dhttp.nonProxyHosts=<hostname of source system>|localhost|127.*|[::1]|0.0.0.0|[::0]

    Both HTTP and HTTPS use the http.nonProxyHosts parameter to exclude proxies.

    If the connection continues to fail with a 502 Bad Gateway error, the JDBC driver is most likely connecting via a socket connection. In this case you must add add the following line as well. (You can keep the added line mentioned above.)

    wrapper.java.additional.23=-DsocksNonProxyHosts=<hostname of source system>|localhost|127.*|[::1]|0.0.0.0|[::0]

  • Proxy authentication is not tested and not supported for Process Extractor.

  • The usage of different proxies for external and internal communication is not tested and not supported for Process Extractor.