You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, in the Technical Requirement for Data Provider wanting to use the gateway, it says:
. The GTS header CCCC code to be used for the bulletins published on their behalf.
. The list of GTS bulletins, and, where appropriate, their cut-off times, to be published by the Gateway on their behalf.
I don't really understand and I don't agree with the part I get...
Typically, the CCCC will be available in each notif message from the producer. So, there is no predefined list...
Then below in the same adoc:
. Add the CCCC code designated by the Member to the Gateway's publication whitelist.
. Complete configuration required in the MSS for each bulletin specified by the Member; e.g., set up the data import channel, set the cut-off time, etc.
@6a6d74 Can you explain (it seems you wrote that) ?
The text was updated successfully, but these errors were encountered:
I also want to add a question. The doc says "Subscribe to notifications on the topic: cache/a/wis2/{centre-id}/data/core/#". So we are not forwarding recommended data from WIS2 to GTS?
At the moment, in the Technical Requirement for Data Provider wanting to use the gateway, it says:
. The GTS header CCCC code to be used for the bulletins published on their behalf.
. The list of GTS bulletins, and, where appropriate, their cut-off times, to be published by the Gateway on their behalf.
I don't really understand and I don't agree with the part I get...
Typically, the CCCC will be available in each notif message from the producer. So, there is no predefined list...
Then below in the same adoc:
. Add the CCCC code designated by the Member to the Gateway's publication whitelist.
. Complete configuration required in the MSS for each bulletin specified by the Member; e.g., set up the data import channel, set the cut-off time, etc.
@6a6d74 Can you explain (it seems you wrote that) ?
The text was updated successfully, but these errors were encountered: