TCPIP Inbound Schedules - Listener Schedule —
TCP/IP HL7 V2 Inbound Adapter
The following table lists and describes the properties that
appear on the Listener Schedule page of the Properties Editor accessed
from the Connectivity Map. These properties configure the scheduler
used by the inbound TCP/IP server. The server waits for a new client
connection establishment request. These parameters are used to configure
the listener.
Two Java EE schedulers are available, both of which provide
the functionality required by the inbound TCP/IP Server.
-
Timer Service –
Available for Java EE, this scheduler is configured using the At
Fixed Rate, Delay, and Period properties.
-
Work Manager –
Available for Java EE (JCA 1.5 and above), this scheduler is configured
using the Delay and Period properties.
Table 7 Connectivity Map - TCPIP Inbound Schedules
- Listener Schedule
|
Name
|
Description
|
|
Scheduler
|
The scheduler type for this inbound communication. Select one
of the following options:
-
Timer Service –
The task is scheduled through the Java EE Timer Service. Timer Service
is supported by Java EE.
-
Work Manager –
The task is scheduled through the Java EE Work Manager. Work Manager
is supported by Java EE (JCA 1.5 and above).
If your container doesn’t support JCA Work Manager, select Timer Service.
|
|
Schedule Type
|
This property, though visible from the Properties Editor, is
disabled. The only available schedule type is Repeated, indicating
that the task is scheduled for repeated execution at regular intervals
defined by the Period property.
|
|
Delay
|
An integer indicating the length of time (in milliseconds) before
the task is executed. This property applies to both the Timer Service
and the Work Manager.
|
|
Period
|
An integer indicating the length of time (in milliseconds) between
successive task executions. This property applies to both the Timer
Service and the Work Manager.
|
|
At Fixed Rate
|
An indicator of whether a fixed-rate execution or fixed-delay
execution is used. This property applies to the Timer Service configuration
only. Select true to indicate fixed-rate; select false to indicate fixed-delay.
-
Fixed-Rate –
Each execution is scheduled relative to the scheduled time of the
initial execution. If an execution is delayed for any reason (such
as garbage collection or other background activity), two or more executions
occur in rapid succession to “catch up.” In the long run,
the frequency of execution is exactly the reciprocal of the specified
period, assuming the system clock underlying Object.wait(long) is accurate.
-
Fixed-Delay –
Each execution is scheduled relative to the actual time of the previous
execution. If an execution is delayed for any reason (such as garbage
collection or other background activity), subsequent executions are
delayed as well. As a result, the frequency of execution is generally
slightly lower than the reciprocal of the specified period, assuming
the system clock underlying Object.wait(long) is
accurate.
|
