Server Administration Application – Configuring FPL
Functions
See also: Server Administration Application Home Page, FPL Functions
FPL Functions can be maintained on the server using the Server Administration web application as shown below. The functions are saved in file userfunctions.xml in the ebaseConf folder of the web application e.g. UfsServer/tomcat/webapps/ufs/ebaseConf/userfunctions.xml. This file can be copied between servers if required. A file of the same name also exists in each Ebase Xi designer (in folder UfsClient/properties) where it is used to syntax check FPL scripts and to provide a dropdown list of available functions; if the file is changed on the server, it can be copied to the designer.
See FPL Functions for information on how to write the Java class required for each function.
The meaning of the various columns shown above is explained in the next section.
Function properties can be edited when either creating a new function using the icon or clicking on the name of an existing function.
Function Information tab:
Name |
The function name – this is the name used to access the function from an FPL script |
Java class |
Class name of the Java class that implements the function |
Description |
Optional description |
Return type |
Return type of the function. This field is for information only, it’s not used by the system. |
Function Parameters
tab:
These are the input parameters required by the function. These parameters are for information only, there are not used by the system.
Sequence |
Parameter position |
Type |
Parameter type |
Description |
Optional description |