corda/network-management/network-parameters.conf

notaries : [{
    notaryNodeInfoFile: "/Path/To/NodeInfo/File1"
    validating: true
}, {
    notaryNodeInfoFile: "/Path/To/NodeInfo/File2"
    validating: false
}]
minimumPlatformVersion = 1
maxMessageSize = 10485760
maxTransactionSize = 10485760
eventHorizonDays = 30 # Duration in days
ENT-990 Make doorman read an initial set of Network parameters from d… (#96) ENT-990 Make doorman read an initial set of Network parameters from disk at start-up time 2017-11-13 15:40:44 +00:00			`notaries : [{`
Changing network parameters to use node info files instead of by hand… (#288) * Changing network parameters to use node info files instead of by hand specification of notary * Addressing review comments * Different names for notaries * Updating README 2018-01-05 15:10:34 +00:00			`notaryNodeInfoFile: "/Path/To/NodeInfo/File1"`
ENT-990 Make doorman read an initial set of Network parameters from d… (#96) ENT-990 Make doorman read an initial set of Network parameters from disk at start-up time 2017-11-13 15:40:44 +00:00			`validating: true`
			`}, {`
Changing network parameters to use node info files instead of by hand… (#288) * Changing network parameters to use node info files instead of by hand specification of notary * Addressing review comments * Different names for notaries * Updating README 2018-01-05 15:10:34 +00:00			`notaryNodeInfoFile: "/Path/To/NodeInfo/File2"`
ENT-990 Make doorman read an initial set of Network parameters from d… (#96) ENT-990 Make doorman read an initial set of Network parameters from disk at start-up time 2017-11-13 15:40:44 +00:00			`validating: false`
			`}]`
			`minimumPlatformVersion = 1`
Add correct value of maxMessageSize For network-parameters.conf in network management 2018-01-08 11:25:57 +00:00			`maxMessageSize = 10485760`
ENT-1433: Implementation of NetworkParameters updates (#477) * Implementation of NetworkParameters updates Implementation of NetworkParameters updates for network-management server side of the process. Change the way network parameters are read up on network-management startup. Introduced 3 flags to clearly communicate intentions: initial-network-parameters, update-network-parameters and flag-day. * Address Shams comments * Address comments * NetworkMapStorage refactor getLatestNetworkParameters returns NetworkParametersEntity * TODO Exit after parameters update Started implementing feature requested by devops. TODO: Fix NodeRegistrationTest * Code cleanup * Merged the two cmd line flags into one --set-network-parameters. The idea being to simply check if there are any active network parameters to determine if it's an update or not. Applying network parameters causes the server to exit once done (ENT-1559). * Merge fixes * Minor cleanup * Small fixes * Merge fixes and cleanup * TODO Implementation of cancelUpdate flag Will slightly change after more manual testing * Small cleanup * Address comments Add OneToOne relation between ParametersUpdate and NetworkParameters. * Address comments fix tests 2018-03-21 12:29:27 +00:00			`maxTransactionSize = 10485760`
CORDA-866: Implement removal of stale nodes from network (#774) * Implement removal of stale nodes from network Add eventHorizon to NetworkParameters structure. Add republishing of node info on 1 day intervals - it is treated by network map as heartbeat from node indicating if it's alive or not. Add removal of old node infos on network map signing. * Add copy method to NetworkParameters data class Add JvmOverloads annotation to the constructor, because it's data class exposed in API 2018-05-11 17:11:56 +01:00			`eventHorizonDays = 30 # Duration in days`