<img height="1" width="1" src="https://www.facebook.com/tr?id=241894266379435&amp;ev=PageView &amp;noscript=1">

Creatio Application Architecture & Deployment

Overview:

From the server infrastructure view, Creatio is a three-tier architectural system with modification as shown below.

creatio_application_architecture

The center of the infrastructure is the application server that runs under the Internet Information Services (IIS) version 7.0 or higher

APPLICATION SERVER

Application server consists of two parts: WebAppLoader and WebApp.

WEBAPPLOADER

The main purpose of WebAppLoader is authorization, authentication and redirect of users to the main application. The main functions of the WebAppLoader:

  • user authorization
  • user licensing and authentication
  • starting the scheduler.

WEBAPP

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.

Get Started with Success with CRM


Learning Academy

About Creatio 

Creatio_Integrator

Creatio Free Trial
 

THE DATABASE SERVER

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:

  • MS SQL Server 2012 SP3 or higher (on-premise)
  • MS SQL Server 2016 is used in the Creatio cloud infrastructure.
  • Oracle DBMS 11 g Release 2 and up (when deploying on-site)

CLIENT

All requests to the server are performed via the web browser. Following web browsers are supported:

  • Internet Explorer 11.0+,
  • Firefox, the last official version on the Creatio release date
  • Chrome, the last official version on the Creatio release date
  • Safari, the last official version on the Creatio release date.

The Creatio mobile application is used to access the server with mobile devices.


In addition to the three main components, there are:

  • database session server (Redis)
  • version control server (optional)
  • cloud web services.

THE SESSION STORAGE SERVER (REDIS)

Redis main functions:

  • storing the data of user sessions
  • storing cached data
  • Data exchange between web farm nodes.

Redis advantages:

  • data is stored in RAM, it provides high performance of the system
  • server can work under Unix OS

VERSION CONTROL SYSTEM SERVER (SVN).

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:

  • Transition of modifications between applications. Modifications are transferred with the packages.
  • Storing the status of the configurations as a packages of specific version. Everything that is developed in the packages is stored in the version control system.

More information about the version control system can b e found in the “Create repository in SVN server” article.

WEB SERVICES

This is an additional cloud services that can be accessed from the several Creatio applications.

  • Global Search Service - is created for integration of the ElasticSearch with Creatio.
  • Bulk Email Service - used for integration of Creation and bulk email services and transnational email (immediate delivery to one recipient)
  • Website Event Tracking Service - enables to track events from one on the client site and pass them to Creatio.
  • The Database Enrichment Service - for account enrichment to find information about account and their communications and contact enrichment to find information and their communications from emails. 

DEPLOYMENT OPTIONS

There are two deployment options:

1.On-site

2.Cloud.

ON-SITE DEPLOYMENT

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.

CLOUD DEPLOYMENT

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:

  • timely updates
  • maximal performance
  • compliance with industry standards on data availability and security.

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: