Firewalls and Web Filters

Users having a regular desktop firewall with default security settings should not encounter problems calling home to the servers. However in stricter security environments such as corporate firewalls with more advanced firewall policies or web filtering software that blocks HTTP(S) access to unknown sites, your application could be blocked from connecting to the internet altogether. In such cases your software may be blocked from connecting with the server, so these clients will not be tracked.

The Usage Intelligence SDK is designed to fail silently whenever it is not able to communicate with the server, so your application and user experience should not be affected in any way if you follow our implementation guidelines as specified in the documentation.

Proxy Environments

In environments where a proxy is present, the Usage Intelligence SDK can be configured to use proxy settings to communicate with the server.

Specifying Proxy Settings Manually

ruiSetProxy

Use this method to specify proxy settings which will be used to submit callhome data to the Usage Intelligence servers. Example usage:

ruiSetProxy(myRuiInstance, "192.168.1.250", 8080, "MyUser", "MyPassword");

Testing Connectivity

ruiTestConnection

Use this method to confirm that your application can callhome to the servers. This is typically used in conjunction with ruiSetProxy(). Example usage:

ruiTestConnection(myRuiInstance);

This method will return one of the following status constants:

• RUI_OK (0)
• RUI_NETWORK_COMMUNICATION_ERROR (-400)
• RUI_NETWORK_SERVER_ERROR (-401)
• RUI_NETWORK_RESPONSE_INVALID (-402)
• RUI_TEST_CONNECTION_INVALID_PRODUCT_ID (-420)
• RUI_TEST_CONNECTION_MISMATCH (-421)

More Information

More information on setting proxy settings can be found in the respective SDK documentation:

• Windows: C/C++ | .NET
• Mac: C/C++ | Objective-C
• Linux: C/C++
• Generic: Java