1. Home
  2. Environments & Release Management
  3. System Administration Configuration

System Administration Configuration

Introduction

Key administrative tasks are managed under Configuration Management.

Default Enterprise Locations: Configuration Management / Add Data

Default Enterprise Locations: Configuration Management / Systems Administration

Note: You will probably use the “Add Data” area when you initially get started i.e. so you have necessary underlying organizational structure and later on you will probably want to use “Systems Administration” as you advance to automation / integration.

Add Data

Access Management

The “Access Management” area is the key place for adding and managing Users & User Groups

Default Enterprise Location: Configuration Management / Add Data

There are two sections to this dashboard:

  1. Executive Banner Buttons
  2. Table to view Selected Type (Active Users, Inactive Users, Active User Groups, Inactive User Groups).

Usage

  • Select “List” in a Banner Button to list objects
  • Select “Add” in a Banner Button to add a new object
  • View Object Information with the Editor (“View” Button).

Organizational Management

 Important! Adding Organizational details is an essential “Getting Started” (Administration) Task. Complete this task before you commence your journey into other areas like Environments Management and Portfolio Release Management.

Default Enterprise Location: Configuration Management / Add Data

Before we get started on Environments or Release, EcoSystem needs to know a little bit about your organization. Simply navigate to the Organizational Management area and add:

  • Your Organization e.g. ACME Ltd
  • Your Business Units e.g. Technology, Accounts, Sales
  • Your Business Teams e.g. Applications, Data, Infrastructure, Test Environments
  • Your Business Processes (Optional, you can add these later)
  • Your Business Functions (Optional, you can add these later)

 Tip: It need not be perfect, and you can always come back and refine this later.

There are two sections to this dashboard:

  1. Executive Banner Buttons for each Organizational Object.
  2. Table to view Selected “Organizational Objects”

Usage

  • Select “List” in a Banner Button to list objects
  • Select “Add” in a Banner Button to add a new object
  • Use Green (My) Button to only show what belongs to you
  • Add/View Object with the Editor.

Warning – EcoSystem visibility (e.g. visibility of business units and systems etc) is controlled at the organization level. So don’t create multiple organizations unless you have reason to restrict visibility.

Location Management

An area to manage Physical Location information.

Default Enterprise Location: Configuration Management / Add Data

There are two sections to this dashboard:

  • Executive Banner Buttons for Business Addresses, Locations & Rack Space.
  • Table to view Selected “Location Objects”

Terminology Note:

  • Business Address is basically a postal address.
  • Business Location is more granular. It depicts a room at the Business Address.
  • Rack space is more granular. It can be a rack within the Business Location.

Usage

  • Select “List” in a Banner Button to list objects
  • Select “Add” in a Banner Button to add a new object
  • Use Green (My) Button to only show what belongs to you
  • Add/View Object with the Editor.

CMDB Management

The “Configure Environments” area inside the “Environments Management” module is the key place for adding and managing your Environment data.

Default Enterprise Location: Configuration Management / Add Data

There are two sections to this dashboard:

  1. Executive Banner Buttons for key EcoSystem Environment Objects. This is made up of: Environment (Lanes), Systems (Platforms), Instance, Components, Interfaces, Packages, Labs & Lab Devices.
  2. Table to view Selected Object Type

Usage

  • Select “List” (1) in a Banner Button to list objects in Grid (2).
  • Select “Add” in a Banner Button to add a new object
  • Add/View Object Information with the Editor (refer Editor Guidelines).
  • If you only want to see environments belonging to you then use the “Green Button” (My Environments) to filter.

Tip: An alternative to adding data “one-by-one” is to use Bulk Upload. Refer Bulk Upload Section.

Bulk Data Upload

A useful feature to upload “existing” data quickly and bypass the editors.

Default Enterprise Location: Configuration Management / Add Data / Bulk Data Upload

 Important! Please take a backup of your model before doing an upload. Please also make sure data being uploaded doesn’t already exist. Duplicate data will be created if same file or data is uploaded again. 

Usage:

  1. Select the Organization (you usually only have one)
  2. Select Object Name (the type of objects you want to upload e.g. System).
  3. Download a Sample i.e. CSV for the selected object

Note: Each Object Type (like Systems) has its own CSV.

Example:

Populate your CSV

4.  Upload your CSV  (note it must follow the correct format)

5. Press Submit.

Important! Information can also be added to EcoSystem Automatically via the Open API. This is particularly useful for data that is "fast moving" e.g. Status or Version details. Learn More 

Systems Administration

Droplist Management

An area to configure EcoSystem Combo Values i.e. Types, Categories & Status..

Usage:

  • Select Drop List Type e.g. Release Type (refer example)
  • Add  (or Delete) a New Combo Value

API Management

An area to add, edit or delete an Application ID & Key.

Usage:

  • Select Add Key
  • Type in Application ID (Application Name)
  • Type in Application Key (password), or Generate a Random Key

Note: You can edit existing key in bottom section by clicking on cell or bin (delete) button.

Webhook Management

On an event e.g. Object Create, Delete or Update send message to Webhook Listener.

Usage:

  • Enter name e.g. Jira Listener
  • Enter  Object Class e.g. Project
  • Enter Action Type e.g. Create, Update, Delete
  • Provide URL that EcoSystem is to send JSON payload to.

Permission Management

Control which User Groups can see/use which EcoSystem items.

This section has four areas:

(1) Module Permission Details

This allows you to control which users in a group can see which EcoSystem Modules.

For example: Who can see the “Booking Management” module.

(2) Report Permission Details

This allows you to control who can see what Reports or Forms.

For example: Who can see/use the “Booking Form”.

(3) Class Permission Details.

This allows you to control who can add what information (Objects) to Ecosystem.

For example: Who can add an “Environment”.

(4) Class Definitions

This details the structure (properties) of a class and underlying rules. For example: Is property Mandatory, How many values can it have etc. And also outlines which groups can edit the property.

Workflow Management

Control how system workflows behave.

For example: Booking Status has 3 overarching paths to closure:

  1. Submit – Confirmed – Completed
  2. Submit – Cancelled – Confirmed – Completed
  3. Submitted – Unconfirmed – Deleted

Basic Usage:

Workflow is controlled by identifying what transitions are allows.

For example: In a LeanSR I can move from Approved to Assigned, or Closed, or Rejected.

Note: Use the status column on right to set whether Transitions is “Active” or “Inactive”.

Advanced

In addition to adding transitions you can also have a transition send communication (email) or activate a webhook. The use of webhooks may be useful if you want to integrate with other tools e.g. CICD tools, ITSM tools etc.

Updated on October 11, 2019

Was this article helpful?

Related Articles