3C Release Manager Light Edition for Automic

The 3C Release Manager Light Edition shows what differs between your Automic environments: it captures scheduled snapshots, compares DEV and PROD object by object and keeps an audit trail. It is included in the Tricise Service Tiers Silver and Gold.

Compatible with

Automic Automation V21/V24/V26

Edition

Light Edition

Included in

Service Tiers Silver and Gold

Support

Ongoing

Price

On Request

Overview

The Light Edition is the entry point to the 3C Release Manager, Tricise’s release governance solution for Automic Automation. It focuses on transparency: which objects exist in which environment, what has changed since the last snapshot, and who did what.

A snapshot is a representation of an Automic environment’s configuration at a specific point in time. Snapshots are stored incrementally: the first one builds the baseline, later ones only save what has changed. A diff compares two snapshots or two environments and shows newly created, deleted, modified and moved objects.

When you want to transport what you have found, the full 3C Release Manager adds deployment packages with rollback, recursive transports with deep scan, bulk changes, the four-eyes principle and optional Git/Bitbucket integration.

Features

Object management:
  • Object list for every connected environment
  • History view for each object
  • Deleted objects stay visible in the history
DEV ↔ PROD diffs:
  • Compare two snapshots or two environments
  • Created, deleted, modified and moved objects at a glance
  • XML and tree view for every object
Scheduled snapshots:
  • Snapshots on a schedule
  • Incremental storage after the first baseline
  • Optional automatic diff after every snapshot
Audit trail:
  • Every important action is logged
  • With user, timestamp and module

Before you start

Who it is for

  • Automic teams that want to know exactly how DEV, TEST and PROD differ
  • Operations and audit teams that need a history of configuration changes
  • Teams that want transparency first and structured transports later

Technical requirements

  • Automic Automation Engine V21 or higher, connected through the Automic Java API over TLS
  • One or more configured Automic clients per instance
  • Installation and operation are described in the Full Guide.

How to get it

  • The Light Edition is part of the Tricise Service Tiers Silver and Gold.
  • Platinum includes the full 3C Release Manager
  • Pricing is provided on request

Light Edition or full version?

The Light Edition gives you transparency across your environments. The full version adds transports, bulk changes, the four-eyes principle and Git integration.

FunctionLight EditionFull version
Object management✓✓
DEV ↔ PROD diffs✓✓
Scheduled snapshots✓✓
Audit trail✓✓
Recursive transports with deep scan—✓
Bulk changes—✓
Four-eyes principle—✓
Git/Bitbucket integration (optional)—✓
Included in the Tricise Service TiersSilver & GoldPlatinum

Need transports, bulk changes or a second approval? Take a look at the full 3C Release Manager.

Videos & documentation

3C Release Manager Enablement Series

Two short videos cover the functions of the Light Edition:

  1. Snapshot Function
  2. DIFF Function

Watch the full playlist on YouTube

Documentation

Further reading on the 3C Release Manager:

Frequently asked questions

What is the difference between the Light Edition and the full version?

The Light Edition covers object management, DEV ↔ PROD diffs, scheduled snapshots and an audit trail. The full version adds recursive transports with deep scan, bulk changes, the four-eyes principle and optional Git/Bitbucket integration, and is available as SaaS or on-premise.

Which Tricise Service Tiers include the Light Edition?

Silver and Gold include the Light Edition. Platinum includes the full 3C Release Manager.

Can I transport objects with the Light Edition?

Transports are part of the full version. The Light Edition shows you what differs between your environments, and the full 3C Release Manager moves those changes in deployment packages with rollback.

What is the difference between a snapshot and a diff?

A snapshot is a representation of an Automic environment’s configuration at a specific point in time. A diff is a comparison between two snapshots – or between two environments, in which case the snapshots are created on the fly.

Why does the first snapshot take longer than later ones?

The first snapshot of an environment downloads every configuration object. Every later snapshot only stores the objects that have changed since the previous one, which reduces both runtime and database size.

Ready to move forward

Book a quick 30-minute session to turn your ideas into action and uncover what’s possible with the right partner by your side.

Scroll to Top