The ASTM TCP Server communication point enables messages to be sent and received using ASTM 1381.
Supported Operational Modes: All.
In order to make this server communication point more tolerant to connection failures from clients or misconfigured clients, we recommend that its connection retry count be set to infinite. Refer to Connection Retries for details.
Configuration Properties
Property |
Description |
---|---|
Local Port |
The local port to which to listen for connections. |
Local Address |
The local interface to which to listen for connections (all interfaces if empty). |
Listen Backlog |
The maximum number of connections that the OS kernel queues for the underlying TCP socket. TCP connections which have been established after completing a three-way TCP handshake are queued on this queue until a Rhapsody server communication point accept them A Rhapsody communication point can only accept a number of connections equal to its maximum configured connections. Any additional connections will remain on the kernel queue and will not be processed by Rhapsody - client applications will be unaware that their connection is not being processed and may continue to send data. As such, it is imperative that Rhapsody TCP server communication points have the number of connections configured to adequately service all client connections. The listen backlog parameter is only intended to serve as a temporary queue for client connections prior to being accepted by the server communication point. The specified backlog parameter must be a positive number greater than |
Use SSL |
Options: It is strongly recommended that SSL be enabled for ASTM TCP Server communication points. Refer to TLS/SSL Support in Rhapsody for details. |
SSL Protocol Mode |
Refer to SSL Protocol Versions for details. |
SSL Cipher Suites |
Refer to SSL Cipher Suites for details. |
Use SSL Client Mode |
Options: |
Secure Keys |
The list of private keys to choose from when selecting a private key to use in the communication with the client. If the Secure Keys configuration property is not configured with the SSL server's private key, then this SSL server operates in anonymous server authentication mode, and so enables the appropriate anonymous cipher suites. However, it is highly recommended that the server's private key always be provided here to allow server authentication to be performed. If the server does not have a private key, then one can be generated from Rhapsody's certificate manager. Refer to Server Authentication for details. |
Trusted Certificates |
Identifies the trusted certificates used at the non-Rhapsody end of the SSL connection. If it is configured with one or more certificates, then the SSL server requires client authentication as part of the SSL protocol negotiation, and will reject clients that do not present either the configured certificate, or a certificate directly or indirectly issued by the configured certificate. It is highly recommended that client authentication be enabled whenever possible. Refer to Client Authentication for details. |
Drop on Collision |
Options: One of the two devices involved in a connection must be configured to drop on collision. |
Debug Mode |
Options: |
Log Connections |
Log the establishing and dropping of all connections. |
Log Data |
Options: |
Log Data as Hex |
Options: |
Connection Log File |
The file to which connection information is logged. |
Extra Information |
Options: |
Bidirectional, In->Out and Out->In Mode
The configuration properties for the Directory communication point in Bidirectional, In->Out and Out->In modes is a combination of the properties described above.
Refer to Out->In and In->Out Properties for general details on a communication point's In->Out and Out->In modes.