Technical data

62 BEA WebLogic Integration Release Notes
Time Services Changes in BPM
This section includes information on changes to time services in BPM. This
information will be added to the BPM documentation in a future release.
The BPM time services now allow multiple workflow instances to be processed
simultaneously when started by a time trigger. Previously, all time actions were
processed sequentially by a single instance of the Message-Driven Bean (MDB)
TimeListenerBean. Now, instead of being a singleton, TimeListenerBean is initially
deployed with 5 instances. It uses the
wlpiOrderKey = <instance id> message
header for message selection to ensure that timer actions are processed sequentially for
any given instance and different instances are processed by a different bean.
Information for Deployers
Users deploying applications should note that a prime number of TimeListenerBeans
must be deployed to ensure that any one instance’s time actions are processed by the
same MDB. This preserves the sequence of time actions within an instance.
Information for Administrators
Administrators should update the WebLogic Server configuration file, config.xml,
with the required arguments for the
com.bea.wlpi.server.timeprocessor.TimeProcessor startup class. A sample
follows:
<StartupClass
Arguments="url=t3://localhost:7001,user=wlpisystem,
pwd=wlpisystem,
connectionFactory=com.bea.wlpi.QueueConnectionFactory,
queue=com.bea.wlpi.Timer"
ClassName="com.bea.wlpi.server.timeprocessor.TimeProcessor"
FailureIsFatal="true" Name="TimeProcessor"
Targets="myserver"/>
where: