FOGL-9164: Allow the Action code in OMF North to be configurable #1470
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Ray Verhoeff <ray@dianomic.com>
Add description of new configuration item "Action Code for Data Messages." Signed-off-by: Ray Verhoeff <ray@dianomic.com>
Added Action Code for Data Messages Signed-off-by: Ray Verhoeff <ray@dianomic.com>
MarkRiddoch
approved these changes
Oct 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.