Portal UI fails to load after MySQL database restoration - DX NetOps Portal
search cancel

Portal UI fails to load after MySQL database restoration - DX NetOps Portal

book

Article ID: 443597

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

After restoring the netqosportal and em MySQL databases to a new environment or during a migration, the DX NetOps Portal web interface fails to load properly. Users may see a blank page, login redirection loops, or raw renderer strings such as LayoutContainerRenderer. This occurs because the internal Single Sign-On (SSO) settings in the restored database still point to the original source environment's hostname or IP address.

http://<Portal>:<port>/pc/desktop/page

LayoutContainerRenderer
TopBarRenderer
LayoutContainerRenderer
LayoutContainerRenderer
LayoutContainerRenderer
LayoutContainerRenderer
ViewContainerRenderer
GridRenderer
ViewContainerRenderer
GridRenderer
ViewContainerRenderer
GridRenderer
LayoutContainerRenderer
LayoutContainerRenderer
LayoutContainerRenderer
LayoutContainerRenderer
ViewContainerRenderer
GridRenderer
ViewContainerRenderer
GridRenderer
LayoutContainerRenderer

Environment

  • DX NetOps Portal (All Versions)
  • MySQL Database Restoration/Migration

Cause

The restored netqosportal database contains "Remote Value" and "Local Override" settings for the Web Site Host and Web Site Port from the source server. The Portal services attempt to redirect traffic to the old environment, resulting in UI failures.

Resolution

Update the SSO configuration to match the new environment's identity.

1. Launch the SsoConfig Utility

  • Log in to the DX NetOps Portal server as root.
  • Navigate to the installation directory: cd /opt/CA/PerformanceCenter
  • Execute the utility: ./SsoConfig

2. Update Remote Values

  • Select 1. DX NetOps.
  • Select 3. Performance Center.
  • Select 1. Remote Value.
  • Update the following properties to the new server's FQDN or IP:
    • Web Site Host
    • Web Service Host
  • Ensure the Web Site Port (e.g., 8181 for HTTP or 8182 for HTTPS) and Web Site Scheme match the new environment.

3. Clear Local Overrides

  • Return to the Performance Center menu.
  • Select 2. Local Override.
  • Review each property. If any entry shows the old hostname/IP (####), select that property and use the Reset option to clear it. This ensures the configuration defaults to the "Remote Value" set in the previous step.

4. Restart Portal Services

  • Exit the tool and run: systemctl restart caperfcenter_sso systemctl restart caperfcenter_console

5. Clear Browser Cache

  • Open a fresh Incognito/Private window or clear the browser cache entirely. The Portal UI components are heavily cached and will continue to fail if the old state is retained.

Additional Information