We have created dedicated installation and configuration guides for each type of deployment option, as part of the complete documentation set for Pulse Secure Virtual Traffic Manager (vTM). You can choose from a number of different deployment options, depending on whether you want to install vTM in a Docker container, as a virtual appliance, as a cloud service, on a bare-metal hardware appliance, or on a private server using a software installation. Choose your target platform from the list here, and follow the link to the dedicated "Getting Started" guide:
Install Pulse vTM from Docker Hub - no need to register, giving quick, easy access for container and microservices deployment. For a detailed guide, see
Pulse Virtual Traffic Manager: Docker Deployment Guide
Looking to run a trial on Microsoft Hyper-V, VMware, Xen, QVM/KEMU, or Oracle VM? See
Pulse Secure Virtual Traffic Manager 20.1: Virtual Appliance Installation and Getting Started Guide
For information on installing in Google Cloud Platform, Amazon EC2, or Microsoft Azure, see
Pulse Secure Virtual Traffic Manager 20.1: Cloud Services Installation and Getting Started Guide
To deploy the Pulse vTM appliance image on an approved server hardware platform, see
Pulse Secure Virtual Traffic Manager 20.1: Appliance Image Installation and Getting Started Guide
For hardware compatibility information, see the Pulse vTM Hardware Compatibility List.
If you are installing onto a private server, or inside a VM running Linux, see
Pulse Secure Virtual Traffic Manager 20.1: Software Installation and Getting Started Guide
Note that these links are valid for the Pulse Secure vTM 20.1 software release. The most recent set of user documentation can always be found on https://www.pulsesecure.net/techpubs/ under the "Pulse vADC Solutions" section. This includes detailed configuration, REST API and TrafficScript programming guides.
(Copies of the "Getting Started" guides are attached to this article)