Effector 6.3 developer manual

XML reference 6.3

Effector Studio 6.3 summary

Effector Studio 6.3 manual

Effector 6.2 developer manual

XML reference 6.0

Effector Studio 3.2 summary

Effector Studio 3.2 manual


The authentication and management of the users and the licenses issued to clients are all done by a central service. Multiple application instances can be operated with the same user base.

The LicenseHandlerServer is a special application instance (Effector).

For every application instance there is an instanceName file in the App_Data directory, that contains the unique identifier of the application.

Files necessary for the operation of the LicenseHandlerServer:

  • App_Data\LicenseHandlerServer.key: The server key file provided for the client. There is a key file allowing for a Demo operation, that contains a user valid for 30 days from the first login.

  • DBConnections\ConnectionLicenseHandlerServer.xml: A DBConnection file that describes which database fulfills the role of the license-server in relation to the application instance.

On the screens provided by the LicenseHandlerServer, it is possible to:

  • Create a user
  • Assign a license to a user
  • Make setting pertaining to the login procedure of the application
  • Import license package and new server key files

Maintenance notifications

It is possible to create a maintenance notification. Before the start of maintenance events, a message in the current language will be displayed on the login screen. During maintenance events, users who are not members of the Maintenance, Admin, or SuperAdmin groups are automatically logged out and cannot log in during the maintenance event. During maintenance, only users in the above three groups are allowed to log in.

Creating maintenance notification

It is possible to record a maintenance event on the Maintenance screen of the License Manager (Server) menu after selecting the appropriate application instance. By clicking on Add new item button on the Maintenance panel a form will be displayed, where the fields Start and End are mandatory. By default, maintenance events are created as inactive.

When you add a new maintenance event, the Maintenance messages panel displays the default maintenance messages in as many languages ​​as are set in the ofn_getLanguages function and in the FSYS_LHS_ApplicationInstanceMaintenanceMessage table with a value of '-1' in the ApplicationInstanceMaintenance field. These messages can be redefined by adding, or modified when already defined. The language is required in the form, and the message field must contain %1 and %2 to replace the maintenance interval.

The osp_wrk_BO_AS_FSYS_LHS_ApplicationInstanceMaintenance stored procedure is executed when a maintenance event is saved.

  • Last update: 32 weeks 6 days ago
  • Effector