Microservice Settings - Event
The following groups contain Adeptia Connect microservices Event properties that can be configured by going to Account > Settings > Microservice Settings. For more details on properties configuration, refer to the page Configuring the application properties.
[+] Event
[-] Hide
| Property name | Description | Default value |
|---|---|---|
abpm.autoActivate.activeMigratedEvents.enable | Enable the property to auto activate the active migrated events. | false |
abpm.event.abort.retryCount | consecutive number of time event can poll if it fails, after this count the event will be de-activated. If the value given is -1 then it means infinite. | 3 |
abpm.event.parametersOverriding.enable | Enable the property to activate events with parameters defined in external JSON file. | false |
org.quartz.scheduler.bCalendar | Specifies list of holidays of year. Enter the value (date) in mm/dd/yyyy format. | 01/15/2007,02/19/2007,05/28/2007,07/4/2007, 09/3/2007,10/8/2007,11/22/2007,12/25/2007 |
[+] Event MetaData
[-] Hide
| Property name | Description | Default value |
|---|---|---|
abpm.eventMetadata.delete.chunks.delay | Delay time between consecutive chunk deletion (provide time in seconds). | 2 |
abpm.eventMetadata.delete.chunks.size | Number of rows that will delete from the table per chunk. For SQL-Server database server we should not keep chunk size value to more than 5000; otherwise it will do lock escalation i.e. it will exclusively lock the entire table. | 4500 |
abpm.eventMetadata.retryCount | Set the maximum number of times, a retry will perform in case of error in deleting event metadata. | 3 |
abpm.eventMetadata.retryInterval | The retry delay in milliseconds. | 3000 |
[+] Log Database Configuration
[-] Hide
| Property name | Description | Default value |
|---|---|---|
| abpm.log.connection.retryTimeInterval | Time interval in seconds after which the next retry for log database will be done | 30 |
[+] Logging
[-] Hide
| Property name | Description | Default value |
|---|---|---|
logging.includeLocation | Used by log4j to include the location in the appenders (Console, jdbc etc.). Possible values of this property is true or false. | true |
logging.level.audit | Audit logging level. For production server, it is recommended to use NOTICE log level. | INFO |
logging.level.root | Root Application logging level. For production server, it is recommended to use NOTICE log level. | INFO |
logging.level.system | System logging level. For production server, it is recommended to use NOTICE log level. | NOTICE |
logging.pattern.console | %d %-5p [%t] %5c %l - %m%n%ex |
[+] Mail Event
[-] Hide
| Property name | Description | Default value |
|---|---|---|
| abpm.mailEvent.mailProcessConcurrency | Defines the maximum number of concurrent emails that can be processed by a mail event at a time. Possible value- Any positive integer. It should be based on a number of concurrent connections that the mail server is using. | 0 |