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
| Property name | Description | Default value | Possible value |
|---|
abpm.autoActivate.activeMigratedEvents.enable | Enable the property to auto activate the active migrated events. |
|
|
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. |
|
|
abpm.event.parametersOverriding.enable | Enable the property to activate events with parameters defined in external JSON file. |
|
|
org.quartz.scheduler.bCalendar | Specifies list of holidays of year. | 01/15/2007,02/19/2007,05/28/2007,07/4/2007,09/3/2007,10/8/2007,11/22/2007,12/25/2007NA | Any date in mm/dd/yyyy format |
Event MetaData
| Property name | Description |
|---|
abpm.eventMetadata.delete.chunks.delay | Delay time between consecutive chunk deletion (provide time in seconds). |
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. |
abpm.eventMetadata.retryCount | Set the maximum number of times, a retry will perform in case of error in deleting event metadata. |
abpm.eventMetadata.retryInterval | The retry delay in milliseconds. |
Logging
| Property name | Description |
|---|
logging.includeLocation | Used by log4j to include the location in the appenders (Console, jdbc etc.). Possible values of this property is true or false. |
logging.level.audit | Audit logging level. For production server, it is recommended to use NOTICE log level. |
logging.level.root | Root Application logging level. For production server, it is recommended to use NOTICE log level. |
logging.level.system | System logging level. For production server, it is recommended to use NOTICE log level. |
logging.pattern.console |
|
Mail Event
| Property name | Description | Default value | Possible value |
|---|
| abpm.mailEvent.mailProcessConcurrency | Defines the maximum number of concurrent emails that can be processed by a mail event at a time. | 0 | Any positive integer. It should be based on a number of concurrent connections that the mail server is using. |
