An Application is an element that describes a program that the system can deploy. As such, every program you want to deploy must be defined by an Application element. You can specify the application type, whether it has a management protocol (only applies to application type Game), give it a name, a website, description, etc.
An Application can be one of four types:
- a game server (type: Game)
- a utility / sidecar (type: Utility)
- a dependency installer (type: DependencyInstaller)
- a dependency un-installer (type: DependencyUninstaller)
|Unique identifier of this element
|The type of application:
1: Game server
|The management protocol supported by the application (only applies when Application Type is Game server):
|The name of the application
|A description of the application
|A website URL for the application
|The developer of the application
|The publisher of the application
|The default operating system group being used for the stop method, WINDOWS = 1, LINUX = 2. If you have a Windows and Linux ApplicationBuild you can overwrite on the AplicationBuild level. The default operating system is Linux
|The stop method that will be used on restart or destroy of an application instance. The default is hard kill
|The timeout that will be used on restart or destroy of an application instance. The default is 0 (no timeout)
|A unix timestamp of when this element was created
|If the application currently in use or not
Every program we deploy with the platform will be defined by an Application element. The Application element is at the top of the application related hierarchy. It gives everything related to an Application an identity:
Additional application specific properties are provided through the ApplicationProperty element. An Application can have zero or more ApplicationProperty elements.
You can define any number of Applications for your account. There is no limit.