Application Service Configuration

The Application Manager (the component that implements the Application Service) will look for an XML file (specified with the -c option) containing the configuration to be used.

Application Service configuration items

Element	Description
PingInterval	When the Application Service is not busy with other tasks it will ping all started applications to see that they are still alive. The interval between the pings (or rather the timeout waiting for other tasks) is defined by the PingInterval. The unit is seconds.
StopTimeout	StopTimeout is used to define the maximum time to wait for applications to die when they are stopped. When the timeout occurs the Application Service will try to kill the application with the SIGKILL signal instead of the SIGTERM signal. The unit is seconds.
ServiceCallbackTimeout	The ServiceCallbackTimeout is the maximum time to wait for internal services to callback when they are informed about applications that are about to start or applications that have stopped. If the timeout occurs the platform is considered to have failed and the whole platform and all applications have to be restarted. The unit is seconds.
Application	Each application should be defined with an Application element. The propertyfile attribute is used to point out the property file of the application and the startup attribute is used to tell whether the application started immediately when the platform is started. Applications that have been started can be activated faster, but they will consume resources like memory and CPU power. The infront attribute tells which of the initially started applications that should be in the visible and active states (infront means that the application will show on the screen fully or partially). Of course the infront attribute should only be true if startup attribute is true. When the platform starts there has to be a full-screen application in the visible or active state so one full-screen application has to be started and infront. Optionally a pop-up application can be active (the infront full-screen application will then be visible) having the infront attribute set to true. At least one and no more than two applications can be infront. One of the infront applications must be full-screen and if there is another it has to be a pop-up application.

A typical configuration file could look like this:

<?xml version="1.0"?>
<AppmanConfig>
  <PingInterval>20</PingInterval>
  <StopTimeout>2</StopTimeout>
  <ServiceCallbackTimeout>3</ServiceCallbackTimeout>
  <Application propertyfile="/etc/navigator_properties.xml"
               startup="true" infront="true"/>
  <Application propertyfile="/etc/web_properties.xml"
               startup="true" infront="true"/>
  <Application propertyfile="/etc/portal_properties.xml"
               startup="true" infront="false"/>
  <Application propertyfile="/etc/game_properties.xml"
               startup="false" infront="false"/>
</AppmanConfig>