Try OpenEdge Now
skip to main content
Messaging and ESB
Implementing Messaging : Externally managed connections : Using serialized connection objects : Connection file parameters
 
Connection file parameters
A connection file allows you to configure a set of connection parameters. The following table lists the connection parameters that can be set for each connection type.
Table 19. Connection file parameters (Continued)
Parameter
Connection type
Broker-side selectors
All1
Client ID
All
Connection URL
All
Connect ID
All
Default password
All
Default user name
All
Durable message order
All
Flow to disk
All
Load Balancing
All
Max delivery count
All
Persistent delivery mode
All
Ping interval
All
Prefetch count
All
Prefetch threshold
All
Sequential
All
Client transaction buffer size
Client-connect, Server-connect
Enable fault tolerant
Client-connect, Server-connect
Enable local store
Client-connect, Server-connect
Fault tolerant reconnect timeout
Client-connect, Server-connect
Initial connect timeout
Client-connect, Server-connect
Local store directory
Client-connect, Server-connect
Local store size
Client-connect, Server-connect
Reconnect interval
Client-connect, Server-connect
Reconnect timeout
Client-connect, Server-connect
1 All connections include Broker-connect, Client-connect, Server-connect

Note: The combined length of the Client ID, Default password, and other connection file parameters listed in the table above must not exceed 30,000 non-Unicode characters when connecting to an AppServer.
Parameter values are fixed when the beginSessionprocedure is called. When the beginSessionprocedure is called, the following process takes place for each parameter to determine its value:
1. If the parameter value was set by a call to the corresponding set<parameter>routine, the values set in the call is used. If the same set<parameter>routine is called more than once, the last setting is used.
2. If the parameter value was not set by a set<parameter>routine, and a parameter file is specified, and the parameter is set in the connection file, then the value in the connection file is used.
3. If the parameter is not set by a set<parameter>routine, and it is not set in a specified connection file, then the default value is used.
The following figure depicts the process for determining the parameter value for each parameter during execution of the beginSessionprocedure .
Figure 2. Connection parameter value decision flow
All connection parameters must be set prior to calling beginSession.