Managing CMS Connections with Unique Identifiers in 360Suite

Managing CMS Connections with Unique Identifiers in 360Suite

Overview

This article explains how CMS connections are managed in 360Suite starting with version 2026.2, and the limitations of CMS name-based identification in earlier versions.

It is intended for 360Suite administrators managing SAP BusinessObjects CMS environments, emphasizing how stable CMS identification improves data continuity, governance, and user experience when environments evolve.

WarningImportant: If a CMS environment is not enabled:
  • Users cannot connect to that environment.
  • Scheduled or recurring tasks linked to that CMS will not run.

A CMS environment must be enabled for both user access and background executions.

How to enable a CMS after upgrading to 2026.2 or later

After your first upgrade to version 2026.2 or above, you must enable at least one CMS.

  1. ⚙️ Open the Administration Console.
  2. 📂 Go to the CMS tab in the left menu.
  3. ✅ Enable only CMS instances that are actively used.

How to choose which CMS to enable

  • ✅ Enable CMS entries that correspond to active production-like environments.
  • 🚫 Leave duplicate or redundant CMS entries disabled.
  • ⏳ Keep duplicate entries disabled until the CMS merge feature is available.
Info
💡 Tip: If no CMS is enabled, the Enable CMS icon will animate to draw attention.

This action is required only once, after the first upgrade beyond 2026.2.

Key Concepts & Strategy

CMS identification in 360Suite

In earlier versions, 360Suite linked data to the CMS name provided at connection time. This meant references depended on values that could change.

Starting with version 2026.2, CMS management is centralized in the Administration Console. Administrators must register CMS environments before users can connect.

Impact of CMS environment changes

When a CMS is renamed, decommissioned, replaced, or when a node is removed from a cluster, old references can become invalid. This could result in broken links, unusable CMS references, or loss of access to historical data.

With a unique internal identifier, administrators can edit an existing CMS entry and update server configuration to point to a new node without losing previously collected data.

Environment classification and governance

Administrators can classify each CMS (Development, Qualification, Pre-Production, Production) and control availability with enabled or disabled status. This improves governance and reduces incorrect environment usage.

Common Questions

What actions do I need to take after upgrading to 2026.2 or later?

After the first upgrade to version 2026.2 or above, go to the Administration Console and enable at least one CMS.

This step is required for users to connect to 360Suite and access the application.

What is the impact if I do not enable my environment?

If a CMS environment is not enabled:

  • Users cannot connect to that environment.
  • Scheduled or recurring tasks linked to that CMS will not run.

An environment must be enabled for user access and background execution.

Why could CMS renaming cause issues in older versions of 360Suite?

Older versions linked data to the CMS name used at connection time. If the name changed later, references no longer matched, which could cause broken links or inaccessible data.

Who was most affected by these issues?

  • Administrators, who had to maintain CMS consistency.
  • End users, who could lose access to data after CMS changes.

How were these problems identified?

The issues were observed repeatedly through customer feedback and internal support cases, especially during CMS renaming, upgrades, and environment restructuring.

What happens to old resources if a CMS is renamed or changed?

Existing 360Suite resources remain linked to the CMS unique internal ID. If the underlying SAP BusinessObjects environment changes, previously created tasks, backups, and resources remain visible and accessible.

How can I avoid issues for my users?

To avoid disruptions:

  • Register CMS environments in advance in the Administration Console.
  • Disable obsolete CMS entries instead of deleting them immediately.

This ensures users connect only to approved and valid environments.

A Merge action is planned for 2026.3 to allow data to be merged from one environment into another.

Can users connect to any CMS directly?

No, users can connect only to CMS environments that have been registered and enabled by an administrator.

Can I modify a CMS after it is created?

Administrators can modify all CMS properties except the unique internal ID. Connection verification is available, and CMS entries can be disabled or deleted when no longer needed.