COMET NAM: Citi Desktop Migration
Guide
Transitioning from Legacy Atom Launcher to Next-Generation Desktop (NGD)
- Introduction The legacy Atom Launcher is officially retiring, and all Atom-based applications will henceforth be launched and managed natively via Citi Desktop. Current migration work has commenced with a separate EMEA team transitioning COMET EMEA into the new architecture. This document outlines the strategic context, architectural updates, and practical steps required by the COMET NAM team to successfully transition the North American stream into Citi Desktop. Since the COMET EMEA transition is a work in progress with minor design decisions pending, the COMET NAM team will closely monitor and align with their progress to ensure architectural parity and consistent desktop launcher configuration methodologies.
- Key Architectural Updates & Capabilities Retirement of Atom Launcher: The legacy desktop launcher is phased out. All operational workflows transition to Citi Desktop, providing a centralized ecosystem for application lifecycle management. Distinct Application Definitions: In the legacy model, regional variants or 'streams' of an application were bundled under a single dropdown menu. Moving forward, this approach is superseded. Each regional stream is treated as an independent, standalone application entity within the global Application Directory. Granular & Separate Setup (e.g., DNAViewer Example): Every stream must possess its own explicit application definition. For context, the DNAViewer application was previously structured as a single system with three regional dropdown choices (NAM, APAC, EMEA). Under the new architecture, it has been decoupled into three separate Application Directory registrations, each utilizing a distinct configuration link. For end-users, this maintains a familiar layout via the Citi Desktop Navigation Menu but ensures a modern, clean backend footprint. Opt-In Multi-Version Support: Citi Desktop introduces native support for concurrent execution of multiple versions of the same application—highly beneficial for engineering, QA, and production support groups validating separate builds. Unlike Atom Launcher, which auto-provisioned multi- stream visibility, this feature is strictly opt-in and disabled by default. Users must manually enable it within their Citi Desktop user preferences. Targeted User Groups within Streams: Application configurations will leverage distinct user groups to drive controlled, phased rollouts. This allows specific binary versions to be pushed to pilot or beta groups independently without impacting the wider user base.
Underlying NGD System Installation: The Next Generation Desktop (NGD) runtime layer controls
physical local delivery. The background deployment agent evaluates the user's specific stream,
environment, and entitlement profile to selectively download binaries.
Dynamic Citi Desktop Detection: The desktop container detects available application runtimes
dynamically by inspecting local NGD configuration manifests. An application option will only appear
active or launchable once the underlying NGD layer has completely deployed the corresponding
assets locally.
- Implementation Steps for COMET NAM
- Register COMET NAM as an entirely independent application definition within the centralized Application Directory, mapping its own dedicated, isolated configuration link.
- Configure and test multi-version capabilities by navigating to Citi Desktop user preferences and explicitly enabling the multi-version toggle within development/QA test profiles.
- Synchronize and audit user group profile mappings. Because the NGD deployment agent strictly matches stream, environment, and user entitlement tags before downloading binaries, ensuring absolute alignment of user metadata profiles is mandatory for successful asset distribution.
- Verify local NGD system execution. Ensure that local NGD configuration manifests are correctly generated and populated on target workstations, allowing the Citi Desktop container to successfully discover and display launchable COMET NAM builds.
- Existing COMET Launcher
[ PLACEHOLDER: Insert Existing COMET Launcher Image Here ]
- Upcoming Comet Launcher
[ PLACEHOLDER: Insert Upcoming Comet Launcher Image Here ]
- Application Directory Navigation and Setup
[ PLACEHOLDER: Insert Application Directory Navigation and Setup Image Here ]
- Reference (Useful Links) Recommended Enterprise Resource Links • Citi Desktop Central Repository: https://citidesktop.internal.citicloud/portal • NGD Provisioning & Manifest Documentation: https://ngd.internal.citicloud/docs/manifest-guide • Application Directory Entry Form: https://appdirectory.internal.citicloud/register • COMET EMEA Migration Alignment Workspace: https://confluence.internal.citicloud/display/COMET+EMEA
Top comments (0)