By creating a server class, you are telling the deployment server that a specific set of clients should receive configuration updates in the form of a specific set of apps.
This diagram provides a conceptual overview of the relationship between a deployment server and its set of deployment clients and server classes: In this example, each deployment client is a Splunk Enterprise forwarder that belongs to two server classes, one for its OS and the other for its geographical location.
Deployment clients can be universal forwarders, heavy forwarders, indexers, or search heads.
Each deployment client belongs to one or more server classes.
Also refers to the overall configuration update facility comprising deployment server, clients, and apps.
The deployment server maintains the list of server classes and uses those server classes to determine what content to distribute to each client.
For an example of how to implement this type of arrangement to govern the flow of content to clients, see "Deploy configurations to several forwarders".
NET MVC from Azure, Ruby hosted with a 3rd party ISV, etc).
The important point is that in all cases, the app’s code runs outside of the Share Point site collection that is consuming it.
Note: The term "app" has a somewhat different meaning in the context of the deployment server from its meaning in the general Splunk Enterprise context.