Flosum Architecture overview

Above: This diagram provides a high-level overview of how each architecture layer is configured.

Application layer

The application layer consists of two major elements:

1. A workstation running on macOS or Windows with a full Automation installation. We recommend that you always use the latest version of Automation, especially when running your test cases via continuous integration and continuous delivery (CI/CD).
2. A version control system (VCS) setup to contain your Provar test project(s). This can be Git, Subversion(SVN), Team Foundation Server(TFS), etc.

Note: To learn more about integrating Automation with your version control system of choice, please refer to Version Control and Devops.

Once you have made your initial check-in to your VCS, the next phase is implementing the environment layer.

Environment layer

The environment layer consists of two major elements:

1. A full package installation of Flosum in your Salesforce org.
2. A Jenkins server accessible from the internet.

Note: The installation of Flosum will not be covered in this guide and must be managed/supported by your Flosum representative/consultant.

Once you have this package installed and correct access has been provisioned, you must also setup your Jenkins server to be publicly accessible from the internet. That configuration will be covered in a later section.

Platform layer

The platform layer consists of two major elements:

1.  Your Salesforce org.
2.  Amazon Elastic Compute Cloud (EC2) instance or Azure Virtual Machine (VM).

1. • This guide will be configuring the integration using an Amazon EC2 instance.
   • Setup for the Azure VM would be similar. More documentation can be found here.
   • These instances should have at least 8 GB RAM, 50 GB of storage space, and a high-speed internet connection.
   • If you use something other than an AWS EC2 instance or an Azure VM, then just ensure that your server can be accessed from your Salesforce Org. This generally means opening up your server to outside access on all Salesforce IP ranges (which are A LOT).

Note: In both cases we recommend that you use a Linux distribution as your base since these are generally more secure and have a better performance.