Unable to Access Spectrum OneClick Webswing with Error SPC-OCC-10248

Products

• Network Observability

Issue/Introduction

Users are unable to launch or access the DX NetOps Spectrum OneClick Webswing application.

The following error is displayed:

SPC-OCC-10248: Could not obtain codebase:

java.lang.ClassNotFoundException: javax.jnlp.ServiceManager

Environment

DX Netops Spectrum 24.3.x & 25.3.x Releases

Cause

This error typically indicates an issue with the Webswing server's codebase URL configuration, specifically

when running in an SSL/HTTPS environment. The Webswing client is attempting to fetch necessary resources

from a codebase URL that is either incorrect, inaccessible, or still configured for HTTP when HTTPS is expected

(or uses localhost when an external FQDN is required). This often occurs after an initial SSL configuration or a

change in the OneClick server's network identity.

Resolution

The SPC-OCC-10248 error is generally resolved by ensuring the Webswing codebase URLs within the OneClick

server's configuration are correctly set for your SSL/HTTPS environment.

SPC-OCC-10248: Could not obtain codebase:

java.lang.ClassNotFoundException: javax.jnlp.ServiceManager

There are two primary methods to achieve this, as detailed in the DX NetOps documentation:

Method 1: Using the sslConfig.sh Utility (Recommended)
The sslConfig.sh utility automates the process of configuring OneClick for SSL, including the necessary Webswing

settings. This is the recommended approach for ease of use and to ensure all relevant files are updated correctly.

• Steps: Refer to the official Broadcom documentation for the specific steps to use the sslConfig.sh utility.
  • For DX NetOps 25.4: Use sslConfig Utility

Method 2: Manual Configuration
If the sslConfig.sh utility cannot be used or for advanced troubleshooting, you can manually update the relevant

configuration files. This typically involves modifying properties that define the Webswing server's base URL and

WebSocket URL to reflect the correct HTTPS hostname and port.

• Steps: Refer to the official Broadcom documentation for detailed manual configuration steps.
  • For DX NetOps 24.3 (or similar versions): Configure OneClick for Secure Sockets Layer - Web Server Section
  • Key areas to check manually include:
    • webswing-sessionpool.properties (or similar Webswing configuration files)
    • Ensure webswing.server.websocketUrl is set to the correct FQDN and HTTPS port (e.g., wss://your_oneclick_hostname:9443/spectrum) and does not contain localhost.

Action Plan:

1. Verify your current OneClick Webswing configuration, paying close attention to any SSL/HTTPS settings and the defined Webswing URLs.
2. Choose the appropriate resolution method (either sslConfig.sh or manual configuration).
3. Follow the steps provided in the respective Broadcom TechDocs link for your DX NetOps Spectrum version.
4. Restart the OneClick services as required after making configuration changes.
5. Test access to the OneClick Webswing application.