Not logged in | Login
The Scheduler Binding Component (BC), powered by OpenSymphony Quartz, affords scheduling capability to kick off (consume) other JBI component providers, for example a BPEL Service Engine.
Like other Binding Components such as File or JMS, in order to use Scheduler BC one has to first create a WSDL Document defining the Scheduler binding and then use it to construct a BPEL service to act as a provider endpoint. When the scheduler triggers, a message will be sent to the Business Process and it'll be incumbent on the business logic implemented there to perform an appropriate task.
|M1||09/17/08||Complete||Introduction of Scheduler in Service Engine form|
|M2||09/18/08||10/17/08||Complete||Scheduler refactored as Binding Component|
|M3||10/20/08||11/12/08||Complete||Quartz Cron Trigger functionality added|
|M4||11/13/08||12/05/08||Complete||Implementation of pivotal Systemic Qualities|
|M5||12/08/08||12/19/08||Complete||SchedulerBC Fuji/IFL enabling|
|M6||01/05/09||01/23/09||Complete||Monitoring for Scheduler|
|M7||01/27/09||03/06/09||Complete||Adding Hybrid Trigger capability|
|FEATURE FREEZE||03/06/09||Feature freeze targeting GlassFish ESB 2.1|
|M8||03/07/09||04/03/09||Planned||Database persistency for Quartz Trigger jobs|
|M9||04/06/09||05/15/09||Planned||Dynamic definition of Triggers|
|M10||05/18/09||06/19/09||Planned||Monitoring/Managing MBean for Scheduler dynamic triggers|
The Scheduler BC works pretty much the same as any other, such as File BC. However, with the recent WSDL Binding Wizard changes across the board for all BC's, it's worth mentioning how to create a deployment for a Scheduler BC triggering a BPEL to write to a File BC.
12 November 2008 at 3:47:31 PM: Do you need more money Joe? 12 November 2008 at 3:48:00 PM: Top of the Minute to you Hank Paulson, please send more money! 12 November 2008 at 3:48:31 PM: Do you need more money Joe? 12 November 2008 at 3:49:00 PM: Top of the Minute to you Hank Paulson, please send more money! 12 November 2008 at 3:49:31 PM: Do you need more money Joe? 12 November 2008 at 3:50:00 PM: Top of the Minute to you Hank Paulson, please send more money!
<?xml version="1.0" encoding="UTF-8"?> <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sched="http://schemas.sun.com/jbi/wsdl-extensions/scheduler/" name="schedEZLoans" targetNamespace="http://j2ee.netbeans.org/wsdl/bpelSubPrimeOrBust/schedEZLoans" xmlns:tns="http://j2ee.netbeans.org/wsdl/bpelSubPrimeOrBust/schedEZLoans" xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"> <wsdl:types/> <wsdl:message name="TriggerEventMessage"> <wsdl:part name="schedPart" type="xsd:string"/> </wsdl:message> <wsdl:portType name="TriggerPortType"> <wsdl:operation name="FireTriggerOperation"> <wsdl:input name="inMsg" message="tns:TriggerEventMessage"/> </wsdl:operation> </wsdl:portType> <wsdl:binding name="TriggerBinding" type="tns:TriggerPortType"> <sched:binding group="schedEZLoans" date-format="dd MMMM yyyy 'at' h:mm:ss a"/> <wsdl:operation name="FireTriggerOperation"> <sched:operation mode="static"/> <wsdl:input name="inMsg"> <sched:trigger name="SendLoanApplicationStatus" type="simple" enabled="true" description="Trigger sending loan application status to Joe The Plumber" repeat="indefinite" interval="60000" message="Do you need more money Joe?"/> <sched:trigger name="AskForBailoutMoney" type="cron" enabled="true" description="Trigger requesting more bailout billions from Feds" cron-expr="0 * * * * ?" message="Top of the Minute to you Hank Paulson, please send more money!"/> <sched:trigger name="VoteTheScoundrelOut" type="cron" enabled="true" description="Remind Americans to vote to save the economy" cron-expr="0 0 8 ? 11 3#1 2008/4" message="Back away from the remote, get up and go vote!"/> </wsdl:input> </wsdl:operation> </wsdl:binding> <wsdl:service name="TriggerService"> <wsdl:port name="schedEZLoans_TriggerPort" binding="tns:TriggerBinding"> <sched:active-period starting="now" ending="never" timezone="America/Los_Angeles"/> </wsdl:port> </wsdl:service> <plnk:partnerLinkType name="schedEZLoans"> <!-- A partner link type is automatically generated when a new port type is added. Partner link types are used by BPEL processes. In a BPEL process, a partner link represents the interaction between the BPEL process and a partner service. Each partner link is associated with a partner link type. A partner link type characterizes the conversational relationship between two services. The partner link type can have one or two roles.--> <plnk:role name="TriggerPortTypeRole" portType="tns:TriggerPortType"/> </plnk:partnerLinkType> </wsdl:definitions>
In order to try out the Scheduler BC:
Number of visits: 6