SOI 4.3 Console fails to launch via Proxy

Products

• CA Service Operations Insight (SOI)

Issue/Introduction

After migrating to SOI 4.3, the SOI Console (oneclick.jnlp) fails to launch when accessed through a proxy server. The launch may hang, redirect repeatedly, or fail with initialization errors in the OpenWebStart (OWS) logs.

Environment

• CA Service Operations Insight (SOI) 4.3
• Access via Proxy
• OpenWebStart / IcedTea-Web

Resolution

Step 1: Verify JNLP Configuration

Ensure the codebase in the JNLP files is correctly mapped to the proxy URL as described in KB 4406.

Step 2: Apply Engineering Debug Fix

Replace the following .jar files with the versions provided for SOI 4.3 (attached to this case):

CA\SOI\SamUI\webapps\sam\lib\soi.common.sam-4.3.0-oneclick.jar
CA\SOI\SamUI\lib\soi.common.sam-4.3.0-ui.jar
CA\SOI\tomcat\lib\soi.common.sam-4.3.0-manager.jar

Step 3: Disable OWS Credential Dialog

If the server redirects too many times or authentication fails prematurely, modify the deployment.properties file for OpenWebStart:

Locate C:\Users\[User]\.config\icedtea-web\deployment.properties.
Set deployment.security.authenticator=false.