Home
Categories
Dictionary

Server configuration properties


    1  Configuration properties format
    2  Common configuration properties
       2.1  Mandatory properties
       2.2  Optional properties
          2.2.1  Strict / Loose ARINC 661 Schema
          2.2.2  Warnings for undefined attributes
    3  Setting specific properties for extensions
    4  Specific server configuration properties
       4.1  Mandatory properties
       4.2  Optional properties
          4.2.1  General properties
          4.2.2  Performance properties
          4.2.3  Graphic properties
          4.2.4  Activation properties
          4.2.5  Windowing properties
          4.2.6  Maps properties
    5  Layers cyclic activation
       5.1  Examples
          5.1.1  OnProcessed
          5.1.2  OnCycle
          5.1.3  Mixed usage
    6  Debug buffer
       6.1  Example
    7  WindowManager activationBehavior
    8  Server Event processor configuration
    9  Server Container Swing Offset behavior
    10  Showing a Server console Window
    11  Examples
       11.1  Basic properties−based configuration
       11.2  The same configuration using the XML format
    12  See also

The Server configuration properties allows to specify the configuration of the Server at start. This file is specified through the −config launch argument. The properties are the same as for the Client so the same properties File can be used for both Client and Server in standalone mode.

Configuration properties format

See Configuration properties format.

Common configuration properties

The Common configuration properties are configuration properties used by both the Server and the Client.

Mandatory properties


Note that if the "network" property is not defined, the following properties must also be defined:

Optional properties

Strict / Loose ARINC 661 Schema

The ARINC 661 supplement 6 enforce the use of an XML Schema for the XML Definition File.

The ARINC 661 supplement 6 enforce the use of an XML Schema for the XML Definition File. Prior to supplement 6, the ARINC 661 standard did only define a DTD, but J661 already used a Schema which was a little more loose the the standard supplement 6 schema. Note that the DTD which was defined before in the standard was even more loose than the "loose" schema.
Differences between the loose schema and the strict schema:

See also the Definition File article.

Warnings for undefined attributes

All the widgets and extensions attributes are defined in the Binary Definition Files, but some of the attributes might not be defined in the XML Definition File. The warnForUndefAttrs attribute allows to emit a warning if one of the attributes defined for a widget or extension is not found in the XML Definition File.

Setting specific properties for extensions

By default only properties which are defined for the Client or Server are taken into account. However it is possible to define specific properties for J661 extensions. See See Extensions manifest properties for more informations on how to define these properties.

Specific server configuration properties

These properties are configuration properties specifically used by the Server .

Mandatory properties


Note that if the
"network" property is not defined, the following properties must also be defined:

Optional properties

General properties

Performance properties

Graphic properties

Activation properties

Windowing properties

Maps properties

Layers cyclic activation

The "server.autoActivated propertyallows to specify how the cyclic activation is working (default value is false). Note that the exact behavior of the Server notification is implementation dependent. The behaviors supported by the J661 Server are:

The two onProcessed and onCycle notifications types can both be supported by using the following syntax: onProcessed;onCycle:<value>. The first boolean sent after the notification ID will be set to:

Examples

OnProcessed

      server.cyclicActivation=onProcessed
Will send a A661_NOTE_CYCLIC_ACTIVATION notification for all Layers of a Buffer after the Buffer is processed. Note that no notification will be sent if the Buffer is discarded (usually because the Server did not have time to process it). Each notification comes with a boolean value set to true.

OnCycle

      server.cyclicActivation=onCycle:1000
Will send a A661_NOTE_CYCLIC_ACTIVATION notification for all active Layers each second. Each notification comes with a boolean value set to false. The first notification will be sent 1 second after the connection.
      server.cyclicActivation=onCycle:10000−1000
Will send a A661_NOTE_CYCLIC_ACTIVATION notification for all active Layers each second. Each notification comes with a boolean value set to false. The first notification will be sent 10 seconds after the connection.

Mixed usage

      server.cyclicActivation=onProcessed;onCycle:1000
Will send a A661_NOTE_CYCLIC_ACTIVATION notification:

Debug buffer

The property name to specify an XML Debug Buffer file which is able to define a list of widgets whose renderer will not be updated. This can be used for debugging to identify the cause of a performance problem.

Example

   <debugBuffer>
      <layer appliID="1" layerID="10" setInactive="true" />
      <layer appliID="1" layerID="12" >
         <widget widgetID="51" />
         <widget widgetID="234" recurse="true" />
     </layer>
   </debugBuffer>
This debugBuffer XML file defines that:

WindowManager activationBehavior

The property "windowManager activationBehavior" specifies the Server behavior for the Layer activation and inactivation notifications when the Cockpit Layout changes.

Server Event processor configuration

The
"server.evtProcessorQueueSize" property is the maximum size of the Queue of events sent to the User Applications. The default value is 5 (which means that at maximum 5 events will be stored before they are sent for the associated Channel). Note that: The associated "server.evtProcessorYield" property specifies the time to wait in ms between two sending. This protects against cases where several output messages sent in very short succession are overridden in the User Application reception. This can happen in some protocols, for example UDP. Note that the wait itself will be performed in a background Thread which manage the sending, thus not stealing CPU time to the main Thread of the Server.

Server Container Swing Offset behavior

By default, containers children in Swing are clipped in the size of their parent, which would cause a problem for unsized containers as A661_BASIC_CONTAINER. The J661 Server Swing implementation uses a trick to be able to draw children widgets inside container parents without clipping the children in the limits of the parent size. This behavior can only be performed by setting the value of a JComponent private flag, which is not possible in secured environments like Applets.
Applets use anoterh way to paint containers, by setting the size of unsized container widgets to the size of their parent, and offset the position of all the containers children. This is usable in Applets.
Note That this does not correspond to a Server flag, because it is never necessary to perform the Offset behavior except in Applets. However, it is still possible to set it directly in the Editor.

Showing a Server console Window

The following configuration properties will show a Server console Window allowing to:
      logServerArea=true
      server.menus=true
      server.uiCombo=true
      logMaximumLines=10

Examples

Basic properties−based configuration

      graphics=DefGraphics.xml
      pictures=DefPictures.xml
      ui=LookAndFeel.xml
      lf=JavaFX
      supplement=6
      serverInputPort=8080
      serverOutputPort=8081
      serverInputSize=50000
      serverOutputSize=200
      server.autoVisible=true
      logServerArea=true
      server.menus=true
      server.uiCombo=true
      logMaximumLines=10

The same configuration using the XML format

      <properties>
         <property key="graphics" value="DefGraphics.xml" />
         <property key="pictures" value="DefPictures.xml" />
         <property key="lf" value="JavaFX" />
         <property key="supplement" value="6" />
         <property key="serverInputPort" value="8080" />
         <property key="serverOutputPort" value="8081" />
         <property key="serverInputSize" value="50000" />
         <property key="serverOutputSize" value="200" />
         <property key="server.autoVisible" value="true" />
         <property key="logServerArea" value="true" />
         <property key="server.menus" value="true" />
         <property key="server.uiCombo" value="true" />
         <property key="logMaximumLines" value="10" />
      </properties>

See Also


Category:server Category:dev Category:conf Category:user

Copyright 2016 Dassault Aviation. All Rights Reserved. Documentation and source under the GPL v2 licence

Project Web Hosted by SourceForge.net Copyright 1999-2010 - Geeknet, Inc., All Rights Reserved About - Legal - Help