Defining Your Application Baseline

Using the Application List View for Adding or Deleting

Use the Application List View accessible from the left hand Application menu option. This will take you to a list of all Application Base Versions and Application Versions to which you have access. There is a row for every Environment to which the Application Base Version or Application Version has been deployed. For this reason, there will be multiple entries for the same Application if it has been deployed to multiple Environments.

The list view is organized on the following columns:

List Column	Description
Version	The Application Base Version or Application Version number.
Domain	The Domain to which the Application belongs.
Parent	The Application Base Version from which the Application Version was created. This will be empty for the Application Base Version.
Environment	The Environment to which the Application has been deployed. Each Environment will represent a different row in the List View table.
Last Deployment to Environment	The Deployment Log number.
Completed	The date and time of the last deployment to the listed Environment.
Results	Success or Fail.

You can also use the Filter bar, represented by a funnel icon, to reorder your Application List View by:

• Domain
• Environment
• Last Deployment
• Parent
• Result
• Version

Double click on an item to see the Dashboard view.

Additional Tabs from the Application List View

The Application List View has the following Tabs.

Tab	Description
Refresh	Refreshes the browser.
Add Base	Allows you to Add a new Application Base Version.
Add Version	Creates a copy of the selected Application in the list, creating a new Application Version.
Delete	Deletes the selected item. However, you must delete the Applications starting from the newest to the oldest. The Application Base Version would be deleted last. Sorting by “Version” gives you the order.
Tasks	Displays all Application Tasks available for the selected item based on the Tasks defined to the Application Domain. See Tasks for more information.
List	Displays the List View.
Map	Displays a global Map of all versions of the Application with Components.

Viewing and Editing with the Application Dashboard

The Dashboard view displays all information related to a specific Application Base Version or Application Version. The Dashboard view has two additional tab options - Package Components and Versions. Below are the Details for an Application.

Details	Description
Full Domain	The fully qualified path of the Domain that the Application is to be associated with, showing all parent Domains.
Name	The Name of your Application.
Owner Type	Owned by a User or Group.
Owner	Name of User or Group.
Summary	Description of the Application.
Created	The date the Application was added.
Modified	The date the Application was updated.

Application Dependencies

The Dependency list shows all of your Package Components. This will remain empty until you assign Components to your Application. You can manually assign Package Components by using the Package Components tab at the top of your Application Dashboard. Alternatively, the recommended method is to automate the collection of this data via a CI/CD Command Line Interface (CLI).

Vulnerabilities

Your Application’s vulnerabilities are derived by aggregating all of your Package Component’s vulnerabilities to the ’logical’ Application level. Vulnerabilities are displayed based on each Component’s SBOM. This data is automatically populated when one or more of your Package Components have an SBOM that produced vulnerability data.

Note - This list may be incomplete if one or more of your Package Components do not have an associated SBOM that can be used to gather vulnerability data.

SBOM

Your Application’s SBOM is derived by aggregating all of your Package Component’s SBOMs to the ’logical’ Application level.

Note - This list may be incomplete if one or more of your Package Components do not have an associated SBOM.

Log History

Applications can be deployed many times, to the same or different locations (Environments). For every Deployment, the Log History will show all deployments based on “Result” and “Date”.

Key Value Configurations

Key Value Configurations are Value Pairs for managing associative arrays assigned to the Object.

Key Value Pairs can be assigned at multiple levels, from the Global Domain down to an individual Component and have a “scope.” Lower level Objects can override a higher level Object. Below is the order in which Key Value Pairs can be overridden:

Object	Description
Global	Contains all Environment variables and any “additional Key Value Pairs” set by the user when running that task.
Environment	Overrides any Global Key Value Pairs during a deployment.
Application	Overrides the Environment Key Value Pairsduring a deployment.
Endpoint	Overrides the Application Key Value Pairs during a deployment.
Component	Overrides the Application Key Value Pairs during a deployed.

Key Value Pairs can be given any Name and a Value. Use +Add to add Key Value Pairs to the table. Use Save to confirm. Use the checkbox to Delete or Edit a Key Value Pair.

Trends

The Trends graph shows the success or failure rates overtime as well at the time required for the last 10 deployments. If an Application deployment takes longer than previous deployments, there is an issue with the deployment logic.

Deployed Environments

When you record deployments via the Ortelius CLI, you can capture deployment data showing which Application Versions have been deployed an Environment.

Last Deployment Difference Based on Environment

When tracking versions, the Difference Graph shows what changed in the last deployment between the previous deployment.

Audit Trail

The Audit Trail displays audit entries for any changes or deployments that impact this object. It includes all changes in the object including User date and time, and deployments with unique numbers.

For deployment audits, select a deployment number to see the details including:

Access	Description
Log	The output of the deployment.
Files	Any files or objects deployed.
Step Duration	Deployment Steps with time required to execute.
Feedback Loop	Shows what was updated starting from Component.

You can also Subscribe or Comment to an Audit Entry.

• Subscribe: Allows you to receive information about the selected deployment.

• Comment: Click on ‘Comment’ to add information. There is a field above the list labeled “Say something about this Application” that can have comments placed into it, and files can be attached to the comment as well. Entering text into this field activates the Add Message button. Click to save the comment as a line in the list.

• Add Files to Comments: Click on the paperclip icon to add a file to the message. Once done, click on the “Add Message” button. These attachments can later be retrieved by clicking on the paperclip icon which then displays the name of the file within a list. Choose the file to download it into the your default Download directory on your local computer.

Access

Users within designated Groups can update or view the Application. To add a Group to one of the access lists, drag and drop the Group from the Available Groups list onto desired access list. All Users who belong to a Group within an Access lists will be granted access to the Application:

Access	Description
View	Any User in any Group within this list can see the selected Component in the List View.
Change	Any User in any Group within this list can make changes to the Component.
Deploy	Any User in any Group within this list can deploy the Application. Restrictions are based on the Access defined at the Environment level.

Package Components Tab

This tab contains all the Components that make up an Application, linked together in order of deployment if needed using a blueprint designer. Click on the Component Selector on the right side to see the available Components based on Domains and Categories. A Category acts as a tag or label assigned at the Component level and are not specific to Domains. Domains are identified with a sitemap icon. A Category is identified with a Tag icon. Selecting either expands the options to show all available Components.

Click and drag a Component from the list on the far right side and drop it into the Assigned Components area. It will appear in the area as a box containing the name of the Component. It automatically links to the last Component. Right click on the connecting line, select “Delete this Connection”.Create by Click on the anchor (the green dot at the bottom of the Component) to create a new connector. Then drag and drop it onto another Component. This determines the order in which the Components will be deployed. Each Component contains Component Items also linked together in the order to be executed. For a microservice implementation, they can all be linked to the “start point”. This means they will be deployed in parallel.

NOTE: At least one Component must be connected to the “start point” or the deployment will fail.

How to Publish New Application Versions Automatically via Continuous Delivery

Configure a continuous delivery system to automatically update new Application versions each time a new GitCommit triggers a new Component to be consumed by your Application. Ortelius in the workflow performs this continuous versioning of new Components and their consuming Applications. For more information, see Using Ortelius with CI/CD.