Server Configuration > Server Properties for Workflow > PTC RV&S Server Configuration Properties > Updated Properties for PTC RV&S 13.3.0.3 and Later Versions
Updated Properties for PTC RV&S 13.3.0.3 and Later Versions
In addition to the server configuration properties listed in the Server Configuration Properties in the Database topic the following Server Configuration properties are applicable to PTC RV&S 13.3.0.3 and later versions:
Server Configuration Properties
mksis.incomingRMIconnections.rate
This is a new property for PTC RV&S 13.3.0.3 and later versions.
Sets the maximum number of concurrent incoming RMI connections the server accepts per minute.
Default value 600
Minimum value is 0
Maximum value is 1500
Set the value of the policy to 0 to disable it. A server restart is required for any changes to the policy to take effect.
In addition to the is.properties listed in the PTC RV&S Server Properties in is.properties topic the following is.properties are applicable to PTC RV&S 13.3.0.3 and later versions:
is.properties
Property
Description
mksis.rmi.minExecutorThreads=
This is a new property for PTC RV&S 13.3.0.3 and later versions.
The minimum number of executor threads that the RMI subsystem may use. The system starts with this minimal number of threads. The value of the property should not exceed the value set for the property mksis.rmi.maxExecutorThreads.
The default value of the property is 25% of the mksis.rmi.maxExecutorThreads. Minimum value of the property is 10, whereas the maximum value can be anything less than or equal to the value set for the mksis.rmi.maxExecutorThreads property.
mksis.throttle.list=<alias1>,<alias2>,...
This property has been upgraded in PTC RV&S 13.3.0.3 and later versions.
Throttle list enables throttling for outgoing traffic to one or more remote clients and servers.
Throttling is defined by using aliases where you compose aliases using only uppercase letters (A…Z), lowercase letters (a…z), numbers (0…9), and hyphens (-). Throttling aliases are specified using a comma separated list.
For each throttle alias, you must configure the iprange, max, or lowPriorityMax , and optionally configure maxRTT (maximum round trip time).
For example, mksis.throttle.list=fsa1, directRemoteUsers, localTeam
* 
You must define only one alias per IP address range.
mksis.throttle.<alias>.IPrange=
This property has been upgraded in PTC RV&S 13.3.0.3 and later versions.
Indicates the range of IP address of remote hosts.
For example,
mksis.throttle.fsa1.iprange=10.1.0.123.
This indicates throttling is done to the specified IP range, which is 10.1.0.123
mksis.throttle.fsa2.iprange=10.1.0.124,10.1.0.125
This indicates throttling is done to the specified IP range, which is 10.1.0.124, 10.1.0.125.
mksis.throttle.directRemoteUsers.iprange=10.2.0.*
This indicates data transfer scheduling is done for the specified IP range, which is 10.2.0.1, 10.2.0.2, and so on in this case.
* 
The property cannot take both comma-separated values as well as a value with wildcard.
For example, mksis.throttle.directRemoteUsers.iprange= 10.0.0.124, 10.2.* is an invalid combination.
mksis.throttle.<alias>.max=
This is a deprecated property and may be removed in a future release.
Indicates the maximum limit of data that can continuously be sent per second. The default unit is bytes/second. Can also be specified in kilobytes/second(K) or megabytes/second(M).as displayed by an external transfer. By default, data transfer is unlimited in a throttling. Therefore, is not recommended to limit the data transfer at the application level.
For example,
mksis.throttle.fsa1.max=12000000
Indicates a maximum of 12MBps bulk data transfer.
* 
Ensure to take into account traffic in both directions when planning for throttling limits.
mksis.throttle.<alias>.lowPriorityMax=
This is a deprecated parameter and may be removed in a future release. Use the mksis.throttle.<alias>.lowPriorityMaxRatio= parameter instead.
Indicates the maximum amount of data that can be sent for low priority operations such as bulk data file transfers where values are displayed by default in bytes/second. Can also be specified in kilobytes/second(K) or megabytes/second(M).
For example,
mksis.throttle.fsa1.lowPriorityMax=10000000
Indicates a maximum of 10MBps bulk data transfer.
* 
The lowPriorityMax value would be set to 80% of the max value if it is not specified.
PTC recommends following these best practices when transferring data for low priority operations:
Check the amount of network bandwidth available with the server machine.
Typically, avoid setting max or lowPriorityMax values. However, if you need to limit data transfer, adjust these values according to the server's network bandwidth.
Ensure that no more than 80% of maximum bandwidth is allocated to low priority operations and the remaining bandwidth is reserved for non-low priority operation.
During bandwidth allocation, consider all aliases defined in the mksis.throttle.list parameter as the mksis.throttle <alias> max parameters will be applied to individual lists.
* 
PTC RV&S attempts to match the values set in the throttling parameters.
mksis.throttle.<alias>.lowPriorityMaxRatio=
This is a new property for PTC RV&S 13.3.0.3 and later versions.
Indicates the fraction of max reserved for the bytes that can be transferred per second for low priority or bulk data.
* 
lowPriorityMaxRatio depends on a deprecated parameter and may be removed in a future release.
mksis.throttle.<alias>.maxconnections=
This is a new property for PTC RV&S 13.3.0.3 and later versions.
Maximum number of client connections that can be accommodated in a throttling.
Default value of the parameter is unlimited, which means by default there can be unlimited client connections in a throttling.
Once the number of connections made exceeds the maxconnections value, a new throttle having the identical profile is created automatically.
* 
The property is applicable only for the defined alias and not for the default throttling.
mksis.throttle.default.buffersize=
This is a new property for PTC RV&S 13.3.0.3 and later versions.
Buffer size represents the amount of data that can be sent but not received by the remote end without interrupting the data transfer.
Default unit used for buffer size is bytes. It can also be specified in megabytes(M) or kilobytes(K).
Values must be positive integer greater than zero. Default buffer size if the throttling profile is not selected is mksis.throttle.default.buffersize=512K.
PTC recommends to not change the buffer size values unless advised to do so by PTC Technical Support.
Was this helpful?