All configuration is performed through the use of Java properties file(s) stored in pre-defined locations that are specific to the underlying operating system. Refer to the Release Notes for specific details.
The Calling AE Titles of the local application are configurable in the preferences file. The mapping of the logical name by which remote AE’s are described in the user interface to Called AE Titles as well as presentation address (hostname or IP address and port number) is configurable in the preferences file.
Table G.4.4-1Configuration Parameters Table
|Time-out waiting for acceptance or rejection Response to an Association Open Request. (Application Level timeout)||No||None|
|General DIMSE level time-out values||No||None|
|Time-out waiting for response to TCP/IP connect() request. (Low-level timeout)||No||None|
|Time-out waiting for acceptance of a TCP/IP message over the network. (Low-level timeout)||No||None|
|Time-out for waiting for data between TCP/IP packets. (Low-level timeout)||No||None|
|Any changes to default TCP/IP settings, such as configurable stack parameters.||No||None|
|AE Specific Parameters (all AE’s)|
|Size constraint in maximum object size||No||None|
|Maximum PDU size the AE can receive (see note 1)||No||Unlimited|
|Maximum PDU size the AE can send||No||Unlimited|
|AE specific DIMSE level time-out values||No||None|
|Number of simultaneous Associations by Service and/or SOP Class||No||Unlimited|
|SOP Class support||No||All supported SOP Classes always proposed and accepted|
|Transfer Syntax support||No||All supported Transfer Syntaxes always proposed and accepted|
|Other parameters that are configurable||No||None|
Notes: 1. Though the application can support unlimited PDU sizes, it will never offer a Maximum Received PDU Length of zero (unlimited) since this triggers a bug in some older systems.