DOMO and IBM Web Sphere Performance

TraffordSeymour
TraffordSeymour Member
in Domo Everywhere

We have a client that utilizes IBM Websphere to manage all of its employees' internet traffic. They currently connect to our site via SSO, and then we link them to a Domo App. We are currently using public embedded links to the Domo App.

We are seeing a significant impact on server performance when loading the Domo App. Sometimes, the data will never load, and the user will get an error message.

Has anyone had issues with IBM Websphere impacting performance?

Answers

  • alagare
    alagare Domo Employee
    edited May 5

    @TraffordSeymour Based on the observations so far, I recommend the following steps to help troubleshoot the performance issues you're experiencing with the Domo App:

    Use Private Embed with SSO Instead of Public Embed: This ensures consistent and secure authentication, which may reduce the likelihood of access issues and improve reliability.

    Whitelist Domo Domains: Please ensure that WebSphere isn’t blocking or throttling any *.domo.com domains. Whitelisting these domains might help improve data and asset loading performance.

    Review WebSphere Settings: While I'm not certain of your current configuration, kindly check if WebSphere has any filtering, (DPI), or caching mechanisms enabled for these pages. These settings could be contributing to the slow or failed loads.

    Test Outside WebSphere: If feasible, try accessing the Domo App outside the WebSphere environment. If it loads successfully on a direct, non-WebSphere network, this will help confirm that WebSphere is the likely bottleneck.

    Check Browser Console & Network Logs: Look for errors, 403s, or failed API calls.

    Please let us know what you find.

Categories