Skip to main content
Skip table of contents

Understand Environment Core Concepts

What are IT Environments?

IT Environments refer to the hardware and software systems that support the different business functions or processes of the organization.

Golive will help you to build a structured inventory of your IT Environments. This is a must-have to successfully manage your IT environments.

What is an Environment in Golive?

In Golive, focus is put on business value and services provided by your various environments, independently of their technological stacks and implementation details. You can manage highly heterogeneous IT environments in a unified way, using a few simple concepts.

Golive Environment Model

An Environment serves as the foundation for running an application effectively. Each Golive Environment is uniquely identified by a name and defined by combining an Application type (such as eCommerce, Payment Service, SAP, etc.) and a Category (like Dev, Test, Demo, Staging, Prod, etc.).

Within each Environment, you can expect to find:

  • Status: Indicates the current state of the Environment, whether it's Up, Down, Running Slowly, Restarting, etc.

  • Environment Attributes: These encompass various characteristics of the Environment, such as the type of database being used (e.g., Postgresql), the operating system (e.g., Windows), and any other pertinent details.

  • Dependencies: Describes any reliance the Environment has on other Environments to function correctly.

  • Tiers: Represents the different layers or segments within the Environment.

  • Deployment: Refers to the process of releasing a version of the Application within the Environment.

A Deployment consists of:

  • Deployed Version/Build Number: Identifies the specific version or build of the Application that has been deployed. This can often be linked to an existing Jira Version for tracking purposes.

  • Deployed Jira Issues: Lists any relevant Jira issues associated with the deployed version.

  • Deployment Attributes: Includes additional details related to the Deployment, such as Release Notes, Artifact URL, and other relevant information.

Environment Core Concepts Relationships

Environment Model - Concepts Connections (1).png

Apwide Golive Core Concepts

Example of an Environment Visualization in Golive

What is an Application?

An application represents a software service hosted within a specific environment. This service can be categorized as:

  • Business Application: These support various business functions, such as eCommerce platforms, payment processing systems, or Enterprise Resource Planning (ERP) software like SAP.

  • Technical Service: These provide technical functionalities to support other applications. Examples include container orchestration platforms like Kubernetes or operating systems (OS) themselves.

Relationships and Structure

  • Dependencies: Applications can rely on other applications to function properly. These dependencies create connections between them within the environment.

  • Tiers: Complex applications are often structured with multiple tiers, each performing specific tasks.


Refers to the specific version of an application currently running in a particular environment. This ensures everyone is working with the same version and facilitates tracking changes.

Below is a visual representation illustrating the connections between the concepts covered in this article:

Environment Model - Concepts Connections (1).png

Apwide Golive Core Concepts

What is a Category?

A Category is a key and necessary feature that helps users identifying an environment in Golive.

Categories may also be referred as the Stage of an Environment.

Environment Model - Concepts Connections (1).png

Apwide Golive Core Concepts

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.