How to install, configure and license Software in veHaaS
This guide applies to all veHaaS work environments connected to the Vector network.
Software Installation
Most Software on veHaaS Windows hosts is deployed via package management (Chocolatey) using Chocolatey package config files for Basic Software and additionally on veHaaS-Standard-VMs define Standard Software. We strongly recommend NOT no install Software manually and to use Chocolatey with package config file tailored to you project's needs.
Please create a new choco request if you are missing specific tools which are needed for your work in veHaaS.
Software Configuration
Most tools are already configured correctly via chocolatey. If you need to configure tools manually please be aware to commit any change to your project's repository or to save your configurations at an appropriate location. veHaaS is used by multiple users and we can not guarantee immutable setups.
Critical software updates will be deployed either by ADP or veHaaS responsibles.
Software Licensing
For better flexibility and maintenance most licenses are provided via license servers. veHaaS has access to all PES internal license resources.
Vector Software
We provide multiple license server hosting licenses for all relevant Vector Tools. NUL-NA, Floating and CITEL license types are supported. The current stable license servers are configured on all veHaaS VMs. All tech-user running on veHaaS VMs are allowed to retrieve at least one license seat of each type. Additionally special users, e.g. root/vector/pes/devcontainer/... for e.g. usage in docker containers etc. are configured to retrieve multiple license seats.
Please consult License Documentation for detailed information.
We recommend NOT to borrow licenses on veHaaS VMs.
Please contact us if you are missing a license.
3rd party Software
An overview of all available licenses can be found 3rd-Party Licensing for PES Documentation. Most tools, e.g. Tasking Compilers, are already configured if installed via Chocolatey. Please consult the documentation for further details.