Webswing Console Defaults to Localhost Instead of Configured Broker

Products

• VMware Smart Assurance

Issue/Introduction

Launching the Webswing Console presents localhost:426 instead of the intended default broker hostname, despite configuring the variable within the environment configuration scripts․

ERROR MESSAGE: "localhost:426"

SYMPTOMS:

• The interface defaults to localhost:426 during launch․

• The configured default broker hostname in runcmd_env․sh is ignored․

CONTEXT: Occurs during Webswing Console launch after a new installation or environment configuration setup․

IMPACT: Users cannot automatically connect to the preferred broker and must manually alter connection settings within the interface․

Environment

Products: VMware Smart Assurance

• Application: Webswing Console

• Version: 25․4․7

Cause

The console application runtime environment does not inherit or respect custom configuration items defined in the traditional properties․conf or webconsole․properties specifications․ Passing explicit parameters directly inside the environment execution arguments resolves the variable masking issue․

Resolution

PREREQUISITES:

• Administrative access to the console host filesystem․

• Text editing tool installed on the host machine․

STEPS: 1․ EDIT WEBSWING APPLICATION CONFIGURATION: Open the application configuration profile to pass JVM arguments directly to the runtime environment․

Path: <SMARTS-BASE-DIRECTORY>CONSOLE/smarts/tomcat/webswing-console/webswing/webswing-app․conf

Add the following attributes inside the "vmArgs" section:

-Dsmarts․remote․broker=[IP-address]:426

-Dcom․smarts․autoAttachDM=[server-name]

-Dcom․smarts․userid=[username]

-Dcom․smarts․password=[password]

 

EXPECTED: Attributes map the remote broker context and credentials successfully into the application scope․

 

2․ RESTART WEBSWING SERVICE: Cycle the web engine process to parse and apply the updated environment parameters․

EXPECTED: The service initializes and loads the modified config baseline without errors․

VERIFY SUCCESS:

• Launch the Webswing Console interface․

• Confirm the remote broker string resolves automatically in the connection panel instead of localhost:426․