Technical data

Documentation Additions, Changes, and Corrections
BEA WebLogic Integration Release Notes 63
url = URL of the server that the TimeProcessor is deployed on
user = the wlpisystem user
pwd = wlpisystem user's password
connectionFactory = JNDI name of the WLPI connection factory
queue = JNDI name of the Timer queue
Also, note the addition of
FailureIsfatal="true".
Information for Application Designers
Users designing applications should note that since the instance ID is used as the
message selector for the MDBs, it is possible that time actions could all get sent to the
same TimeListenerBean. This occurs in situations where the instance containing the
time action is always a factor of the number of deployed TimeListenerBeans.
For example, if 3 TimeListenerBeans are deployed and the application has the
following template definitions:
Parent
→Child→Grandchild
where the Grandchild template definition performs a time action such as Task Due
Date, and then starts another instance of the Parent. This results in the instance of
Grandchild always going to the same MDB because the result of the following
calculation:
<
instance#>%3 (the remainder of <instance>/3)
will always be the same, assuming these are the only workflows running).
Time-Based Processing and WebLogic Time Services
BPM time-based processing is now coupled more closely with WebLogic Time
Services. This affects the trigger time of time-based actions in a BPM workflow. The
accuracy of timers is dependent on that of the underlying WebLogic Server timers,
with a resolution of milliseconds but an accuracy of plus or minus roughly one second.
This means that time based actions may fire up to one second prematurely. Time-based
actions should, therefore, not be used for timing-critical designs needing extreme
accuracy.