test 24781785-BEA-WebLogic | Page 62

Conf ig ur in g Di amet er Cli ent Nod es an d Re lay Ag ent s Table 4-2 Diameter Node General Configuration Properties Property Name Description Dynamic Peers Allowed Select this option to allow dynamic discovery of Diameter peer nodes. Dynamic peer support is disabled by default. BEA recommends enabling dynamic peers only when using the TLS transport, because no access control mechanism is available to restrict hosts from becoming peers. Peer Retry Delay Enter the amount of time, in seconds, this node waits before retrying a request to a Diameter peer. The default value is 30 seconds. Request Timeout Enter the amount of time, in milliseconds, this node waits for an answer message before timing out. Watchdog Timeout Enter the number of seconds this node uses for the value of the Diameter Tw watchdog timer interval. Targets Enter one or more target engine tier server names. The Diameter node configuration only applies to servers listed in this field. Default Route Action Specify an action type that describes the role of this Diameter node when using a default route. The value of this element can be one of the following: Default Route Servers • none • local • relay • proxy • redirect Specifies one or more target servers for the default route. Any server you include in this element must also be defined as a peer to this Diameter node, or dynamic peer support must be enabled. 6. Click Activate Changes to apply the configuration to target servers. After creating a general node configuration, the configuration name appears in the list of Diameter nodes. You can select the node to configure Diameter applications, peers, and routes, as described in the sections that follow. Configuring Diameter Applications Each Diameter node can deploy one or more applications. You configure Diameter applications in the Administration Console using the Configuration->Applications page for a selected Diameter node. Follow these steps: 4-12 Configuring Network Resources