TCPIP Inbound Settings - Inbound Connection
Management — TCP/IP HL7 V2 Inbound Adapter
The following table lists and describes the properties that
appear on the Inbound Connection Management page of the Properties
Editor accessed from the Connectivity Map. These properties manage
the connection to inbound systems. For example, these properties include
the connection pool and the life cycle of the accepted connection.
Table 6 Connectivity Map - TCPIP Inbound Settings
- Inbound Connection Management
Name
|
Description
|
Max Connection Pool Size
|
The maximum number of concurrent connections allowed for the
specific listener or monitor that is listening or monitoring the specified
TCP/IP port. 0 (zero) indicates
that there is no limit.
This value indicates the capability or availability of this
server’s services. Each connection request from a client gains
one concurrent connection. This value also indicates the maximum number
of clients that can concurrently connect to this server’s services
and can be served by the specific listener or monitor at the same
time.
|
Scope Of
Connection
|
The scope of the accepted connection that is used by the adapter.
Select one of the following options:
-
Resource Adapter Level –
The resource adapter closes the connection upon request (by way of ClosureCommandMessage) so the connection may “keep
alive” during multiple executions of the Collaboration.
-
Collaboration Level –
The resource adapter closes the connection once the Collaboration
has been executed so the connection has the same life cycle as the
Collaboration.
|
Close Notification
|
A String indicating the trigger value that notifies the server
to close the connection. When the server receives a notification with
content that matches this parameter’s value, the server safely
closes the connection and cancels any corresponding schedules.
The default value is QUIT.
|
Idle Timeout
|
The length of time (in milliseconds) for inactivity of the requestor
(client). The adapter attempts to detect in/out activity from the
client. If there is no client activity for a specified time period,
then the connection is closed from the server side to release the
resource. To disable idle timeout checking, specify 0 (zero) for this parameter.
|