The HTTP header action code of update is normally correct for sending Fledge readings to OMF since old PI data values will be updated and new data values will be properly compressed by the PI Data Archive. However, if the PI Buffer Subsystem is used, it converts the OMF update action code into the PI Data Archive's internal replace storage mode which causes the PI Server's compression algorithm to be bypassed. The published AVEVA workaround of disabling the PI Buffer Subsystem is not an option for PI Collectives since Collectives must use the PI Buffer Subsystem.
This change allows the system manager to specify the create action code instead. Documentation has been updated.
The HTTP header action code of update is normally correct for sending Fledge readings to OMF since old PI data values will be updated and new data values will be properly compressed by the PI Data Archive. However, if the PI Buffer Subsystem is used, it converts the OMF update action code into the PI Data Archive's internal replace storage mode which causes the PI Server's compression algorithm to be bypassed. The published AVEVA workaround of disabling the PI Buffer Subsystem is not an option for PI Collectives since Collectives must use the PI Buffer Subsystem.
This change allows the system manager to specify the create action code instead. Documentation has been updated.