|
 |
|
|
 |
|
| |
|
|
|
|
| |
 Server Side Logic |
| |
|
Defines business logic to be executed on server. The business logics such as modifying/selecting records in a database, email, workflow or triggering a business process in the BPM engine can be defined. Server side logic definition is stored as XML in two formats — executable and downloadable. The executable XML is used by the interpret engine to execute the logic. The downloadable XML stores the business logic independent of technology, i.e. independent of language (such as C#, JAVA) and database (such as SQL server, Oracle). This XML is used for code download in different technologies. The downloadable XML protects the IT assets irrespective of technology or environment change. As logic is stored as XML, it can be parsed in future for Impact Analysis. These XMLs form the metadata for server side logic. Server side logic is invoked using AJAX (for file submission form submit is used). The AJAX code is automatically generated by the tool. |
 Webservices |
| |
All server side logic are exposed as REST-based webservices by default. Security can be applied to restrict the usage of these webservices, which can be invoked using HTTP GET/POST request. The service returns back the XML that contains the response. Advantages are: effort not required to expose business logic, existing web server is enough, other software stack is not required. Clients such as JavaFX, AIR can use this to invoke business logic. |
| Security |
| |
Security is user/role based. Roles must be assigned to users. A user can have more than one role. Rights (Authorization) are assigned to roles. Username/Password authentication is available by default. Developers can build their own authentication process. Security is automatically applied in the Server side logic. All security definitions are stored in XMLs, which are the metadata for security. Security is defined at different levels as follows: |
|
|
|
|
|
|
|
