From the server infrastructure view, Creatio is a three-tier architectural system with modification as shown below.
The center of the infrastructure is the application server that runs under the Internet Information Services (IIS) version 7.0 or higher
Application server consists of two parts: WebAppLoader and WebApp.
The main purpose of WebAppLoader is authorization, authentication and redirect of users to the main application. The main functions of the WebAppLoader:
After incoming requests were processed in the loader they are redirected to the WebApp. This part is responsible for the business logic of the system. This is an application that implements specific configuration and workplace in the system.
Database stores a data necessary for user or for the operation of the system itself. All configuration settings that define functionality of the products are also stored in the database.
Systems that can be used as database server:
All requests to the server are performed via the web browser. Following web browsers are supported:
The Creatio mobile application is used to access the server with mobile devices.
In addition to the three main components, there are:
Redis main functions:
This is an optional component that is enabled only when you need to start the development of custom configuration on the platform in parallel with system operation. Server functions:
More information about the version control system can b e found in the “Create repository in SVN server” article.
This is an additional cloud services that can be accessed from the several Creatio applications.
There are two deployment options:
In On-site deployment, all costs associated with the organization of the server part (installation, configuration, maintenance, administration) are assigned to the customer.
One of the advantages of this deployment option is the simpler integration with the Active directory, since the domain controller is usually located in the enterprise LAN. Also, the on-site deployed application is better for development.
Disadvantages of this deployment options are that the customer bears constant costs to support this infrastructure (update, administration, maintenance costs).
How to deploy Creatio on-site is described in the "Deploying Creatio application on-site" article in the User Guide.
In the cloud deployment option, the application is deployed on the cloud servers (Amazon, Azure etc). All application server part is stored in the data centers and administrated by Creatio employees. All issues related to administration, speed, scalability are solved by the Creatio employees and client uses only the client part of the application.
Advantages of the Cloud deployment:
See "Deploying the Creatio cloud application" article for more on restrictions related to Creatio cloud.
Additional articles that provide an in-depth look at Creatio architecture: