This section describes the different properties that you can use in the STR to configure EC/ECSAs.
...
Database Properties
| Property | Description | |||||
|---|---|---|---|---|---|---|
| max.cached.prepared.statements | Default value: If you have want to change the number of preparedStatements that are cached between connections, you can use this property to specify a different number than default.
|
...
| Property | Description |
|---|---|
mz.dx200.acceptsequentiallost | Default value: The default behavior for the FTP/DX200 collection agent is to skip files if the sequential order of the files has been lost. Add this property and set it to true if you want continue collecting files even if the sequential order has been lost. |
mz.dx200.acceptoverwritten | Default value: The default behavior for the FTP/DX200 collection agent is to not collect files that have been in FULL state before being set to OPEN, and untransferred data has been overwritten. Add this property and set it to true if you want to collect files that have been overwritten. |
Rest Client Properties
rest.client.max.chunk.size | Default value: "8m" This property specifies the maximum chunk size of the HTTP response that the REST Client agent should receive from the server. The agent will reject data with sizes that are larger than the value defined by this property. You can also set this property on the container level, where the value is only applied to all EC's under a particular container. You can refer to 2.6.2 Container Properties for more information. |
rest.client.max.content.length | Default value: "64m" This property specifies the maximum length of the HTTP content received by the REST Client agent. The agent will reject content that is longer than the specified value defined by this property. Although it is also possible to set the value of this property to infinite, there will be a possibility where the EC will crash from an out of memory error. So do consider setting the memory size of the EC to be higher than the expected size of the HTTP content that the agent will be receiving. You can also set this property on the container level, where the value is only applied to all EC's under a particular container. You can refer to 2.6.2 Container Properties for more information. |
Inter Workflow Properties
...
| Property | Description | ||
|---|---|---|---|
ec.backlog.dir | Default value: This property is applicable for ECs and determines whether you want events and error messages occurring when the contact is lost to be logged in a backlog or not. If the property is not present, events and messages will not be logged. The value of this property specifies where the backlog resides. | ||
ecsa.backlog.dir | Default value: This property is applicable for ECSAs. All events and error messages occurring when the contact is lost will be logged in a backlog. The value of this property specifies where the backlog resides. | ec.shutdown.time | Default value: This property specifies the maximum time (in milliseconds) the EC will wait before a real-time workflow stops after a shutdown has been initiated. This is to enable the workflow to stop all input and drain all UDRs in the workflow before shutting down. The wait time is initially set to 60 seconds. If this value is set to 0 all draining is ignored and the workflow will stop immediately. |
| ec.excel.dateformat | Default value: "dd/MM/yyyy" This property will define the format of the date to be decoded for the ExcelCellUDR. For the date to be parsed successfully, you will have to provide the format of the date received by the ExcelCellUDR. The values in this property conforms to the standards of the SimpleDateFormat java class. If the date is not parsed successfully, the data type of the date field will be treated as a string. | ||
ec.shutdown.time | Default value: This property specifies the maximum time (in milliseconds) the EC will wait before a real-time workflow stops after a shutdown has been initiated. This is to enable the workflow to stop all input and drain all UDRs in the workflow before shutting down. The wait time is initially set to 60 seconds. If this value is set to 0 all draining is ignored and the workflow will stop immediately. | ||
pico.bootstrapclass | Default value: This property specifies the bootstrap classes that are required by some components. | ||
| pico.ec.do_graceful_shutdown | Default value: true This property determines the behavior of the mzsh command shutdown. When you have set the value of this property to | ||
pico.rcp.server.port | Default value: This property specifies the port that is used for EC to EC communication. If no port is set, a dynamic port will be used and the port number will change each time an EC is restarted. | ||
| mz.use.drdateformat | Default value: The date syntax used in the APL functions Even though the syntax conforms to You can enable date format handling based on the | ||
mz.use.date.timezone | Default value: Setting this property to In most cases, the property should be set in the pico configuration of EC/ECSAs . However, in case of audit processing, the property should also be set in the pico configuration of the Platform. Note that if the mz.use.date.timezone property is used for setting dates with another time zone, there will be no way of keeping track of the actual time zone in the database, and you may have to manually convert the date during selection. To keep track of the time zone in an Oracle database, use the data type TIMESTAMP WITH TIME ZONE. | ||
pico.type | Default value: "" This property specifies the type of pico instance used for the EC. The possible values are EC and ECSA. |
...