Welcome to your Appgate SDP system!
This chapter provides step-by-step instructions to help you set-up and configure your first Appgate SDP Collective. A Collective is a group of one or more appliances comprising Controllers, Gateways, etc. Appliances can operate as physical machines, virtual machines (VMware/HyperV/VirtualBox) or Cloud instances.
Installing the first appliance (Controller) requires a different process from any additional appliances which can subsequently be created and activated from the Controller's admin UI.
To set up the first appliance:
The steps below guide you through the process and provide links to relevant pages where you will find more details
Step 1: |
Pre-installation checklist: Before you start to deploy Appgate SDP it's important that you have a good grasp of your current network topology. You should then make sure you understand the 8 key concepts that underpin Appgate SDP as these will help you understand how to place Controllers and Gateways throughout your network. To help streamline installation and configuration, our Pre-installation checklist covers things you need to consider prior to starting the process. |
||||||||
Step 2: |
Appliance / instance creation: The process for creating your first (and subsequent) appliance can vary depending on which appliance option is being used:
|
||||||||
Step 3: |
Create the first Controller: The first Controller topic takes you through the process of creating a Controller using a choice of appliance options. Some options may mean the Controller is available automagically (after Step 2). Whichever option you choose, you will end up with a network-connected Controller with access to the admin UI from where you will be able to get on with adding other appliance functions and provisioning secure access for users. |
Next steps:
As well as creating your first Controller there are some other important "getting started" tasks you should attend to such as: provisioning redundant administrative access, adding logging services to help monitor the deployment of Appgate SDP and installing a production license.
Step 4: |
Provisioning redundant admin access: It is recommended that you provision access for other system administrators before configuring other aspects of the system. Our system admin guide provides step-by-step instructions on setting up admin accounts, admin roles and admin policies: |
Step 5: |
Deploying a LogServer: Logs are collected locally by each appliance and are accessible using the journalctl command. Initially you might want to add a LogServer to your Collective which will act as a collector for all the appliances. To add a LogServer: Option 1: Add LogServer functionality to an existing appliance (eg. your Controller). In the admin UI, open System>Appliances and click on the name of the appropriate appliance and under the Functions tab check the LogServer option and save. Option 2: Configuring a new appliance and enable the LogServer. |
Step 6: |
Install a license: Once the Controller has been configured it is possible to request and add a license to the system. |
Step 7: |
Deploying a Gateway: Now you need to deploy a Gateway - there are two approaches to this: Option 1: Add Gateway functionality to your Controller appliance. Option 2: Configuring a new appliance and enable a Gateway. |
Now you are ready to configure other aspects of your system.
Help at hand
The Troubleshooting guide will direct you to the right chapter in the manual to solve any problems you might encounter.
For guidance on managing the system and provisioning user access, go to the General Administration chapter.
The admin UI chapter will help you use the forms to configure the system and settings.
On each form in the admin UI, there is relevant help in the right-hand panel. Each form also provides a link to take you to right section of the admin guide should you need any more detail.
