To open the HTTP/2 Server agent configuration dialog from a workflow configuration, you can do either one of the following:
...
Setting | Description |
|---|---|
Enable Overload Protection | Select this option if you want enable overload protection. |
Number of Requests | If you have selected enable overload protection, enter the maximum number of requests that are allowed to be sent during the time specified in Average Period (sec). When this number of requests has been reached, further requests will be blocked until the time specified in Wait Duration (sec) has passed, then a retry will be attempted. |
Period (sec) | Enter the time period in seconds for which the number of requests should be counted. |
Wait Before Retry (sec) | Enter the number of seconds to wait before attempting to retry a request. |
OpenAPI Tab
...
HTTP/2 Server Agent Configuration - OpenAPI tab
...
Setting | Description | ||
|---|---|---|---|
5G | |||
Use 5G Profile | Select this option if you want the agent to use a 5G profile. | ||
5G Profile | Browse and select the profile to be used. This field is enabled when the Use 5G Profile option is selected. | ||
NRF Address (Primary) | Enter one or more primary NRF (NF Repository Function) address in this list.
| ||
Additional NRF Address Settings (Secondary) | |||
Enable Fall Back (Reconnect to primary address when it is available) | Select this option to have the agent reconnect to the primary NRF address from the secondary address. The agent will constantly send a registration request heartbeat repeatedly to the primary NRF address at every heartbeat interval. The heartbeat interval will be based off of the value that you have configured in the 5G profile.to determine its availability. | ||
NRF Address (Secondary) | Enter one or more secondary NRF (NF Repository Function) address in this list, this is to allow for alternative connections when the heartbeat with the primary NRF Address is not established. | ||
Examples of Configuring Multiple Primary NRF Addresses
| Info |
|---|
Use the primary and secondary addresses below as reference to the following examples.
|
Example 1 - Successful connection to all primary addresses
Address | P1 | S1 | P2 |
|---|---|---|---|
Availability | |
|
|
Result | Connected | Connected |
Example 2 - Connect to secondary address when primary address is unavailable
Address | P1 | S1 | P2 |
|---|---|---|---|
Availability |
|
|
|
Result | Connected | Connected |
Example 3 - Connect to all remaining primary addresses when any of the primary and secondary addresses are unavailable
Address | P1 | S1 | P2 |
|---|---|---|---|
Availability |
|
|
|
Result | Connected |
When the primary (P1) and secondary (S1) addresses are unavailable, the system will not attempt to reconnect. Users are required to re-initiate the workflow to reconnect.
Example 4 - All primary and secondary addresses are unavailable upon starting up the workflow
Address | P1 | S1 | P2 |
|---|---|---|---|
Availability |
|
|
|
Result | The workflow is aborted. | ||
Proxy Support
If a proxy server is needed to reach NRF servers please look at HTTP Proxy Support in order to configure the proxy.
...