Lianja Cloud Server
The Lianja Cloud Server is a modern, fast, and flexible cross-platform cloud database Application Server that enables you to share Apps and Data in the Cloud or on premises running on either Linux, Windows or MacOS. Lianja Cloud Server provides an enterprise-class solution for both SMEs and large enterprises.
This article provides a functional overview of the Lianja Cloud Server.
- 1 Introduction
- 2 App Deployment Services
- 3 Data Services
- 4 Dynamic Page Services
- 5 Server side procedures
The "Lianja Platform" consists of the following products.
The Lianja Platform consists of:
The Lianja Cloud Server provides a variety of features that are grouped by functionality.
App Deployment Services
Lianja ODBC data access
Open Database Connectivity (ODBC) is an industry standard interface for accessing data in a heterogeneous environment of relational and non- relational database management systems. Based on the Call Level Interface specification of the SQL Access Group, ODBC provides an open, vendor- neutral way of accessing data. Using the Lianja ODBC Driver in conjunction with the Lianja SQL Server, third party ODBC-aware products have full CRUD (Create, Read, Update, and Delete) access to Lianja data no matter where it resides.
Lianja OData Server
OData is a standardized protocol for creating and consuming data APIs. OData builds on core protocols like HTTP and commonly accepted methodologies like REST. The result is a uniform way to expose full-featured data APIs. The Lianja Cloud Server has built-in support for OData. There is no need to write any custom code to use this functionality, you just point at an OData URI and the Cloud Server will perform the requested OData operation returning data in industry standard JSON format. See this article for details.
Lianja WebSockets Server
Dynamic Page Services
Server side procedures
Remember that when invoking server side procedures in the web/mobile client, the server knows nothing about the UI or the data state: it is "stateless". What this means is that any required UI information should be passed as arguments to the server side procedure and that the procedure should open the database and tables that it needs. When testing on the desktop, the situation is different as the desktop App is stateful: it has access to the UI, the database is open and the tables may be in an active state.
e.g. (Lianja/VFP example)
proc getBalance(database, table, args) local result = 0 if not isServer() push datasession endif open database &database use &table // Insert your code here to do what you need to do use close database if not isServer() pop datasession endif return result endproc
A function can be called directly if it is declared in exports.conf.
var result = myfunc();
The Lianja.evaluate() method can be used to call a Lianja/VFP function/procedure.
var result = Lianja.evaluate("myproc()");
To call a procedure in a library, prefix the procedure name with the library name and '::'.
var result = Lianja.evaluate("mylib::mylibproc()");
The file 'myfunc.js' should be in the app or library directory and contain a function with the same name as the file. If the 'myfunc.js' file does not exist in the app or library directory and the file 'server_functions.js' exists then the function 'myfunc' is assumed to be defined in the 'server_functions.js' file.
To call a function in a library, prefix the function name with the library name and '::'.
An alternative syntax using the Lianja.evaluate() method is also available:
Pages in category "Lianja Cloud Server"
The following 20 pages are in this category, out of 20 total.