3C Release Manager for Automic Enablement Series – Creating Environments
Welcome to Part 3 of the 3C Release Manager for Automic Enablement Series.
After covering the Snapshot Function in Part 1 and the Diff Function in Part 2, we now focus on a foundational capability: creating and configuring new environments.
If you missed the previous articles, you can read them here:
Part 1 – Snapshot Function
Part 2 – Diff Function
The ability to define structured environments is essential when working with the 3C Release Manager for Automic. Environments represent the technical connections to specific Automic clients and form the basis for snapshots, diffs, and controlled deployments.
Video Walkthrough – Creating a New Environment
In this episode, we demonstrate how to create a new environment from scratch. Within the Environments section, existing client connections are already visible — for example Client 100 and Client 101 connected to the same Automic system via the JCP port 8443.
Instead of cloning an existing configuration, we create a completely new environment. The first step is assigning a meaningful name. Best practice is to include both the Automic system identifier and the client number, for example: AE210 – Client 102.
Next, the JCP endpoint must be defined. In this case, the connection is established via LOCALVM on port 8443. Multiple JCP endpoints can also be specified, separated by semicolons or commas, which is especially useful in high-availability setups.
The Environment Type can then be selected. While this setting has no technical impact, it provides valuable visual categorization — for example distinguishing Production, Test, Migration, or Sandbox systems. Clear categorization is particularly helpful in complex enterprise landscapes.
After defining the connection endpoint, a valid certificate must be provided. The certificate ensures secure communication between the 3C Release Manager and the Automic system.
Finally, authentication details are entered: username, department, client number, and password. Once saved, the system automatically performs a connection test. If successful, the status immediately confirms Connected = True.
Validating the Environment with a Snapshot
As a final validation step, a snapshot is executed. This confirms that the connection is fully operational and that object structures from the target client can be accessed. Once completed, the objects of the connected client become visible within the environment.
With this, the environment is ready for structured release governance — including snapshot baselines, diffs, and controlled transports across DEV, TEST, and PROD.
Stay Connected – Continue the 3C Enablement Series
This article is part of the ongoing 3C Release Manager for Automic Enablement Series. In the next part, we will explore structured versioned transports and controlled multi-environment deployments.
To stay informed about upcoming deep dives, webinars, and technical breakdowns, follow:
Automic Automation by Tricise on LinkedIn
Or subscribe to our LinkedIn Newsletter:
Subscribe to the Tricise LinkedIn Newsletter
