Naming conventions and acronyms
What
FileWave Knowledge Base articles will sometimes use acronyms, and occasionally we may miss giving detail or context, but we try to always use the full name once or explain the term.
When/Why
This will be a list of terms you can refer to when unsure.
How
Alphabetical list of terms:
A
ABM - Apple Business Manager is a web-based portal designed for businesses and organizations to manage Apple devices and services. It provides tools for device deployment, app distribution, and configuration management. ABM allows businesses to streamline device procurement, deploy custom apps, enforce security policies, and centrally manage Apple devices for improved efficiency and productivity.
ADE - Apple Device Enrollment is a program that simplifies the deployment and management of Apple devices within organizations. It allows for easy enrollment of devices into a mobile device management solution, automating configuration and saving time in the setup process. Admin - When you see FileWave Admin used it is frequently referring to FileWave Central and FileWave Anywhere, but some older documentation may only be referring to FileWave Central. Administrator - A user that may log into the FileWave Server via the Admin application. Anywhere API (v2) - The second RESTful API that is used by FileWave Anywhere and usually commands are on TCP 443 unless you have changed the port that FileWave Anywhere operates on.AppleSeed - AppleSeed is an invitation-only program offered by Apple that allows selected users to test pre-release software and provide feedback to Apple's engineering teams. Participants in the AppleSeed program get early access to upcoming software updates and can help identify and report bugs, ensuring a more stable and polished user experience before the software is released to the general public.
Archive - To archive a device is to remove it from active monitoring. The device remains in the database with its last reporting information intact; but the device is no longer counted as an active Client. Archiving a Client frees up one Client license.ASM - Apple School Manager is a web-based portal provided by Apple for educational institutions to manage Apple devices and services. It allows schools to easily deploy and manage Apple devices, distribute apps and books, create Apple IDs for students and staff, and configure settings for a seamless educational experience.
Associations - An Association is made between a Fileset and a Client or Client Group and represents the link between the two objects. Time-based attributes can be assigned to the Association. Associations are how distributions are made. You can also make associations between images and clients, licenses and Filesets, and VPP users and devices. Attributes - Properties of files that specify how the files are treated once the FileWave Client activates them.B
- Booster - A Linux, macOS, or Windows system running software that caches software deployments for macOS and Windows clients.
C
Command Line API (v1) - The initial RESTful API for FileWave. Commands happen on TCP 20443 and 20445.
F
- File - A File in a Fileset represents a file that will be delivered to a specific location for a FileWave Client. Files have attributes and permissions.
H
- Hosted Customer - Any customer where FileWave runs the server itself in either our Cloudv1 or Cloudv2 infrastructure.
I
- IVS - Imaging Virtual Server - A Linux Linux-based used for Windows imaging. The server sits on your network to capture and deploy images.
K
M
O
- On-Premise - The term used to refer to running a FileWave Server on your own network.
P
- Payload - A term for the item in FileWave that is a bundle of content that can contain files, policies, and profiles. In FileWave Central it is called Fileset and in FileWave Anywhere it is called a Payload. The two terms Fileset and Payload are really the same item type.
R
- RESTful API - Another name for the Command Line API (v1) and you may hear it referred to as either name because originally there was a single API and it was RESTful. Now there are 2 different APIs and both are RESTful so it makes more sense to not call it the RESTful API.