Setting up Instance Types

FS (Frontend Server)

This is preferred in cases where the platform operations are handled on the front-end.

E.g. simple excel download, upload on the client side.

If the instance type is set as "FS" at the io.properties or ra.properties level, the functionality which is controlled by the following profile options will be disabled. This is for making sure that all these services are not enabled when you are creating a Dev/UAT servers.

• IS_BULK_IMPORT_ENABLE : Enables the BulkImportJobManager Job

• ENABLE_GOOGLE_DRIVE_FAIL_OVER_PROCESSOR : Enables the transition of files from RA_FILES to Google drive

• ENABLE_EMAIL_PROCESSOR : Enables the EmailRequestJob which will get all the pending requests from email_request table and and process the emails

• ENABLE_INBOUND_EMAIL_PROCESSOR : Enable Inbound Email Processor

• ENABLE_FILE_UPLOAD_PROCESSOR : Enable File Upload Processor

• ENABLE_OFFLINE_STORAGE_SCHEDULER : Turn on/off backend scheduler for processing all the offline data transactions

• IS_GOOGLE_CALENDAR_ENABLE : Enable the Google Calendar Job to have all the meeting scheduled google calendar

• ENABLE_SCHEDULE_PROCESSOR : Enable ScheduleServiceManager which gets all the scheduled jobs(snippets) and executes the jobs

• ENABLE_EXPORT_JOB : Will add Export excels as an asynchronous job

By default when you are setting up a new instance , instance type will not be set and it is defaulted to "BS" and all these services will be enabled.

BS (Backend Server)

Mostly preferred in cases of asynchronous operations like Asynchronous upload and download. And actions like send email notifications, Code snippet executions and workflow operations.

Advantages

In case of BS, these asynchronous operations are queued to get executed from the backend (from server) there by lessening the load on the client side.

Recommendation

Always recommended to configure one BS and the rest as FS type.