VISULOX layout of a node

Overview

A VISULOX Node owns a layout. The layout has serveral fields.

Some of the fields are for information, some of them are controlling the behaviour of the node.

Usage

Fields	Description	Comment
layout.<node>.feature.sc	Each node can handle VISULOX Session Controller (recorder). This parameter defines how many can be provided by this node.	Can be configured to adapt the node to customer needs.
layout.<node>.fileexchange	Enable / disable File Echange (true, false)	Default setting is false
layout.<node>.ftpd	Enable / disable FTP Service (true, false)	Default setting is false
layout.<node>.location	This is a name tag for the location. Nodes with the same location are grouped. This field has the same meaning as in the VISULOX PORTAL.	Can be configured to adapt the node to customer needs.
layout.<node>.logname	Logical name of the node.	Set during installation, fixed,
layout.<node>.replication	Replication mode of the node.(default, all, ftonly, false)	Replication service has special replication behavior on tables "session,files,events".
layout.<node>.runlevel	The current runlevel of the node.	Operation.
layout.<node>.shortinfo	A description field.	Information, can be configured to adapt the node to customer needs. The shortinfo is displayed with visulox status and on the cluster page in the Cockpit.
layout.<node>.webservice	Enable / disable webservice (true, false)	Default setting is false
layout.<node>.zone	This is a name tag for the zone. Nodes with the same zone are grouped.	Firewall ports must be configured between nodes in the same zone.

Replication mode

The replcation mode after setup is default, witch means, that each node with a VISULOX PORTAL Service and VISULOX Archive has all data, any other node has no session, files, events from other nodes.

There are different reasons to have more data:

If the node is envolved with VISULOX File Transfer, the replication mode has to be to ftonly
If the node runs the VISULOX Cockpit (and is not on the VISULOX Access Node), the repication mode has to be set to all

Setting

Setting	Description
default	If the node is a VISULOX PORTAL or VISULOX Archive - sessions, files, events are replicated from other nodes. On standalone servers default will lead to a warning in integrity. On standalone servers the replication mode can be set to false.
all	Independent wether VISULOX PORTAL or other node - session, files, events are replicated from other nodes.
ftonly	Only the File Transfer entries are replicated from other node. ftonly is necessary for VISULOX PORTAL Nodes and application nodes, if no other information is needed and Cockpit is on an extra server.
false	Replication service is disabled (recommended setting for standalone servers). If there is more than one node, this setting will lead to an error.

When an application is started on a node without replication, the files in the vlxtransit directory can't be seen.

If the assigned host is in the VISULOX PORTAL Array, then everything is fine (default replication is ok!).

If the assigned host is not in the VISULOX PORTAL Array, then ftonly or all has to be used.

Example: disabling session controllers on a node

The following example shows how the session controller feature on a VISULOX Access Node set to 0. This node the will not provide any session controller and so it will not be used for recording.

Displaying the layout entries

CODE

visulox config -name layout
    -------------------------------------------------------------------
    | changed | key                                   | value         |
    -------------------------------------------------------------------
    |         | layout.<logical server name>.banner       |           |
    |         | layout.<logical server name>.connection   |           |
    |         | layout.<logical server name>.feature.sc   | 400       |
    | changed | layout.<logical server name>.fileexchange | true      |
    |         | layout.<logical server name>.ftpd         | false     |
    |         | layout.<logical server name>.location     | STANDARD  |
    |         | layout.<logical server name>.replication  | default   |
    |         | layout.<logical server name>.runlevel     | accepting |
    |         | layout.<logical server name>.shortinfo    | STANDARD  |
    |         | layout.<logical server name>.webservice   | false     |
    |         | layout.<logical server name>.zone         | STANDARD  |
    -------------------------------------------------------------------

Setting session controller to 0