WebSphere brand IBM WebSphere IP Multimedia Subsystem Connector, Version 6.2

Diameter Enabler configuration files

Use the Diameter_Rf.properties, Diameter_Ro.properties, and Diameter_Sh.properties files to configure which Diameter peers Diameter Enabler will communicate with, and what characteristics the associated connections will have.

The Diameter_Rf.properties, Diameter_Ro.properties, and Diameter_Sh.properties files are located in the properties directory:
  • AIXLinuxSolaris was_profile_root/properties
Note: was_profile_root is the directory for a WebSphere® Application Server Network Deployment profile called profile_name. By default, this directory is:
  • AIX /usr/IBM/WebSphere/AppServer/profiles/profile_name
  • Linux /opt/IBM/WebSphere/AppServer/profiles/profile_name
  • Solaris /opt/IBM/WebSphere/AppServer/profiles/profile_name
For example, AppSrv01 in a standalone environment, or Custom01 as the name of a federated node profile in a clustered environment.

After making changes to these files you will need to restart the associated enterprise application using the Integrated Solutions Console.

In the following table every connection property that begins with the prefix conx is associated with the same connection and with naming the route that is using that connection. Replace the x in conx with the number of the connection that your are configuring. The value of x can any integer between 1 through 20.

Table 1. Property information for the Diameter_Rf.properties, Diameter_Ro.properties and Diameter_Sh.properties files
Property Value
OriginHostName Used to identify this Diameter node to those Diameter peers it shares connections with.
  • The OriginHostName is required and should be a fully-qualified domain name.
    Note: In a vertical cluster, you may have only one IP address and fully-qualified domain name. In this case, create a unique OriginHostName for each server in the vertical cluster. For example, add diam1 to the FQDN to create diam1.yourcompany.com for the first instance, diam2 to the FQDN to create diam2.yourcompany.com for the second instance, and so on.
  • The OriginHostName can be the same as the DNS hostname.
  • The OriginHostName must be unique for each Diameter client instance.
  • Only one Diameter client instance can be running on a given server instance.
  • Recommended value: use the same hostname as the DNS hostname.
  • Example: OriginHostName = server.test.yourcompany.com
OriginRealmName The realm the Diameter client resides in.
  • The OriginRealmName is required and should be a fully-qualified domain name.
  • The OriginRealmName is only used as information exchanged in the Capabilities Exchange (CER/CEA) transaction.
  • Recommended value: use your current realm name.
  • Example: OriginRealmName = yourcompany.com
HostIpAddress The IP address of this Diameter client instance.
  • The HostIpAddress is required and the value will be verified against the valid IP addresses for this host server.
  • If the Diameter client is running on a multi-honed server, the HostIpAddress may be any of the IP addresses listed for that host.
  • This value is used as information exchanged in the Capabilities Exchange (CER/CEA) transaction. and is verified for correctness.
  • Recommended value: use your current host IP address.
  • Example: HostIpAddress = 9.3.4.6.
ProxySupport A Boolean value that indicates whether this Diameter client will allow requests made from it to potentially be passed through a proxy agent in the Diameter network.
  • True: if set to true, packets may have the P bit set depending on the command code in use.
  • False: if set to false, no packets originating from the Diameter client will have the P bit set.
  • Default value: True.
  • Example: ProxySupport = true
conx.remotePeerOriginHostName The Origin-Host name of the peer that Diameter will setup the TCP connection to.
  • The remotePeerOriginHostName is required for the connection "conx", and must be a fully-qualified domain name.
  • The remotePeerOriginHostName must match exactly with the configuration value on the peer as the Diameter client will only allow connections with a peer whose origin-host name matches this configured property.
  • Recommended value: use the host name of the remote server you are connecting to
  • Example: con1.remotePeerOriginHostName = shserver.yourcompany.com
conx.remotePeerIpAddress IP address of the peer.
  • If the remotePeerIpAddress is not configured, a name resolution will be performed on the remotePeerOriginHostName.
  • If the name resolution is successful, the received IP address will be used to set up the connection.
  • Recommended value: use the host IP address of the remote server you are connecting to.
  • Example: con1.remotePeerIpAddress = 1.2.3.4
conx.remotePeerPort The TCP port number of the Peer. The default port number for the TCP connection can be overridden with a different port number.
  • Default value (port number): 3868.
  • Example: con1.remotePeerPort = 3868

conx.inbandSecurityPolicy Identifies if TLS is required for all transactions.
  • Valid values are 0 or 1. 0 = PROHIBIT_TLS will not allow TLS to be used for this connection. 1 = REQUIRE_TLS requires that TLS is used for this connection.
  • Default value: 0.
  • Example: con1.inbandSecurityPolicy = 1
conx.watchDogTimeout Number of seconds that can occur on an unused connection before a WatchDog packet (DWR) is sent to the peer.
  • Valid values are 0 and any value between 6 to 2147483647.
  • If set to zero, there will be no DWR sent to the peer.
  • Default value: 30 seconds.
  • Example: con1.watchDogTimeout = 40
conx.maxWatchDogExpirations Number of consecutive watchdog timeouts that can occur before declaring this connection suspect and failing over to another available route.
  • Valid values are 0 and any value between 2 to 2147483647.
  • For a setting of 2 the DWR packet will be sent when the first watchDogTimeout occurs. When the second watchDogTimeout occurs this connection and the associated routes will start failover processing.
  • If set to zero the failure monitoring is suspended and failover will not occur on this connection.
  • Default value: 2 periods.
  • Example: con1.maxWatchDogExpirations = 2
conx.includeOriginStateId Indicates whether or not the Origin-State-Id AVP should be transmitted in Base packets (CER/CEA).
  • True: indicates the Origin-State-Id AVP should be transmitted.
  • False: indicates the Origin-State-Id AVP should not be transmitted.
  • Default value: false.
  • Example: con1.includeOriginStateId = false.
conx.includeFirmwareRevision Indicates whether or not the Firmware-Revision AVP should be transmitted in Base packets (CER/CEA).
  • True: indicates that the Firmware-Revision AVP information will be sent.
  • False: indicates that the Firmware-Revision AVP information will not be sent.
  • Default value: false.
  • Example: con1.includeFirmwareRevision = false
conx.maxPendingQueueLength Maximum number of requests to be stored on the pending queue. If the pending queue is full, any new requests will be rejected until room becomes available on the queue.
  • Default value: 30.
  • Example: con1.maxPendingQueueLength = 100
conx.sourcePort Source port used when initiating a connection to the Diameter peer. If zero (0) is specified, an ephemeral source port is used.
  • Valid values are zero (0) and any integer from 1 to 65535 that is not already in use.
  • Default value: 0.
  • Example: con1.sourcePort = 4444
conx.reconnectInterval Number of seconds the connection will wait before attempting to reconnect with a peer.
  • Valid values are any integer between 30 and 2147483647.
  • Default value (seconds): 30.
  • Example: con1.reconnectInterval = 30

conx.packetTimeout Number of seconds that a request packet will remain on the pending queue waiting for a response packet before it is removed and the application is notified of a timeout.
  • Default value (seconds): 30.
  • Example: con1.packetTimeout = 30.

routex Defines routes used in the configuration file to link a realm to the next-hop connection.
  • Each route property value contains three fields separated by a colon (:). All three fields are required for a valid route.
  • For each realm there should be one primary route. There can be any number of secondary routes up to the maximum total of 20. The maximum number of primary routes is 10.
  • The first field is the realm name this route represents.
  • The second field is the connection that the packet to be sent to this realm should go through. The connection identifier must match the conx identifier that you used to configure the associated connection.
  • The third field is an indication this route will be either a primary or a secondary route. A secondary route will only be used for forwarding traffic if no primary route can be reached.
  • Example:
    route1 = DEFAULT:con1:PRIMARY
    route2 = example.com:con2:PRIMARY
    route3 = example.com:con3:SECONDARY
subscriptionPurgingInterval This property only applies to Ro.

In a clustered installation, this property should only be enabled on a single application server.

Defines the interval in which expired subscriptions to receive Reauthorization Requests are purged from the database. The minimum value is 30 seconds, and the maximum value is 32,000,000 seconds.

If the property is missing or commented out (default), purging will not occur.
  • Default value: Purging is suspended
  • Example: subscriptionPurgingInterval = 30.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.