Index Changes

Difference between version and version     

Back to Scheduler SE, or Scheduler SE Info


At line 23 removed 1 line.
* Graphical editor to define/maintain triggers.
At line 52 changed 1 line.
;__Step 2__:Key in Project name. The name forms part of the Scheduler consumer endpoint name so choose one that's meaningful yet succinct (no spaces or other unsavory characters for now), for example schedules related to a particular demo, such as __{{SchedulerDemo}}__.
;__Step 2__:Key in Project name. The name forms the first half of the Scheduler consumer endpoint name so choose one that's meaningful yet succinct (no spaces or other unsavory characters for now), for example schedules related to a particular demo, such as __{{SchedulerDemo}}__.
At line 56 changed 2 lines.
;__Step 3__:Right-click the project's __{{src}}__ folder and choose __{{New | Schedule File...}}__
[{Image src='SchedulerSE/NewSchedFileMenu.png' align='center' }]
;__Step 3__:Right-click the project's __{{Process Files}}__ folder and choose __{{New | Schedule File...}}__
[{Image src='SchedulerSE/NewSchedFile.png' align='center' }]
At line 59 changed 1 line.
;__Step 4__:Key in Schedule file name. The name forms the latter part of the Scheduler consumer endpoint name so again, choose one that's meaningful yet succinct (no spaces or other unsavory characters for now), for example what this particular schedule will trigger, such as __{{KickOffBPEL}}__ (don't prvoide any extensions in the name for a standard __{{.sched}}__ extension is always used).
;__Step 4__:Key in Schedule file name. The name forms the latter half of the Scheduler consumer endpoint name so again, choose one that's meaningful yet succinct (no spaces or other unsavory characters for now), for example what this particular schedule will trigger, such as __{{KickOffBPEL}}__ (don't prvoide any extensions in the name for a standard __{{.sched}}__ extension is always used).
At line 62 changed 1 line.
;__Step 5__:Fill in by hand (for now) the desired trigger element as illustrated below under __Scheduler XML File Syntax__.
;__Step 5__:In the ensuing Schedule editor, click the __{{Add Simple Trigger}}__ toolbar button and a new trigger row will appear in the table below.
[{Image src='SchedulerSE/SchedTableEditorAdd.png' align='center' }]
At line 64 changed 1 line.
;__Step 6__:Save your work and build the Scheduler project.
;__Step 6__:With the respective trigger table row highlighted (note, the __{{Selected}}__ checkbox is used for indicating triggers selected for deletion), you can specify the various parameters for that trigger. Changes to a field are registered when either focus is lost or an __{{Enter}}__ key is pressed (except for the __{{Message}}__ text area since it will accept newlines as part of the data).
At line 66 changed 1 line.
;__Step 7__:Use the generated WSDL files as appropriate to set up the provider endpoints to be triggered.
* The __{{Starting}}__ and __{{Ending Date & Time}}__ entries delineate when this trigger will be active. Until a date/time chooser is implemented (very soon; or please donate if you have a good free open-source one), you'll need to enter one manually in the default locale format (Java [SimpleDateFormat|http://java.sun.com/j2se/1.5.0/docs/api/java/text/SimpleDateFormat.html] is used); the first item in the __{{Job Date Format}}__ exemplifies the default locale format. Alternatively, if you want the trigger to be active immediately after the Composite Application has been deployed, choose __{{Now}}__ and similarly select __{{Never}}__ if the active period has no end.
* A simple trigger basically repeats after a certain time interval so specify the __{{Repeat Count}}__ or __{{Indefinite}}__ and the various time units that comprise the overall time interval.
* Finally, the __{{Job}}__ section pertains to the __{{Message}}__ that will be sent when the trigger fires and will contain a metadata part that details the appointed date and time the trigger was configured to fire (note, this may precede the actual time the message is received due to network latency) in the specified __{{Date Format}}__. Moreover, the metadata will also contain the trigger's name and group to which it belongs.
[{Image src='SchedulerSE/SchedTableEditorPopulate.png' align='center' }]
;__Step 7__:Save your work and build the Scheduler project.
;__Step 8__:Use the generated WSDL files as appropriate to set up the provider endpoints to be triggered.
At line 69 changed 1 line.
;__Step 8__:Create a JBI project that provisions the desired endpoints to be triggered, for example in the following BPEL project.
;__Step 9__:Create a JBI project that provisions the desired endpoints to be triggered, for example in the following BPEL project.
At line 74 changed 1 line.
;__Step 9__:Add this Scheduler project and other required ones into a Composite Application project.
;__Step 10__:Add this Scheduler project and other required ones into a Composite Application project.
At line 76 changed 1 line.
;__Step 10__:Connect the various Scheduler consumer endpoints with their respective provider endpoints to be triggered.
;__Step 11__:Connect the various Scheduler consumer endpoints with their respective provider endpoints to be triggered.
At line 79 changed 1 line.
;__Step 11__:Save Composite Application project, build, and deploy into running instance of GlassFish Application Server.
;__Step 12__:Save Composite Application project, build, and deploy into running instance of GlassFish Application Server.
At line 85 changed 4 lines.
<schedule name="everyMinute" group="SchedulerDemo-KickOffBPEL"
xmlns="http://schemas.sun.com/jbi/engines/scheduler">
<trigger name="everyMinuteSched" enabled="true"
description="Triggering the BPEL usecase every minute">
<schedule name="kickOffBPEL" group="SchedulerDemo"
xmlns="http://schemas.sun.com/jbi/engines/scheduler"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.sun.com/jbi/engines/scheduler schedule.xsd">
<trigger name="everyMinute" enabled="true" description="Triggering the BPEL usecase every minute">
At line 91 removed 5 lines.
<!-- date value can be "now" (case-insensitive and in which case format is
ignored, of course) or value corresponding to specified format
(http://java.sun.com/j2se/1.5.0/docs/api/java/text/SimpleDateFormat.html);
if none specified, format defaults to locale's default pattern.
-->
At line 99 changed 6 lines.
<!-- date value can be "never" (case-insensitive and in which case format is
ignored, of course) or value corresponding to specified format
(http://java.sun.com/j2se/1.5.0/docs/api/java/text/SimpleDateFormat.html);
if none specified, format defaults to locale's default pattern.
-->
<date format="MM/dd/yyyy-kk:mm:ss" value="08/30/2008-12:13:14"/>
<date value="9/30/08 11:59 PM"/>
At line 106 removed 1 line.
<!-- count can be "indefinite" (case-insensitive) or an int value -->
At line 108 changed 1 line.
<interval weeks="0" days="0" hours="0" minutes="0" seconds="60" millisecs="0"/>
<interval minutes="1"/>
At line 111 changed 3 lines.
<message date-format="yyyy-MM-dd&apos;T&apos;HH:mm:ss.SSSZ">
Send status email to loan applicant!
</message>
<message date-format="M/d/yy h:mm a">Send status to loan applicant!</message>
At line 135 changed 1 line.
<xsd:documentation>This name, when prefixed by the Scheduler project's name, is the latter part of the group name for the schedule element. </xsd:documentation>
<xsd:documentation>Name for the set of triggers in this schedule. Note, this name forms the latter half of the prefix for the resultant Scheduler SE Consumer Endpoint name.</xsd:documentation>
At line 140 changed 1 line.
<xsd:documentation>Typically should be the combination of the Scheduler project's name, a dash, and schedule element's name. Note, this is used as the Quartz group name for all the triggers defined here.</xsd:documentation>
<xsd:documentation>Group name for the set of triggers in this schedule. Note, this name forms the first half of the prefix for the resultant Scheduler SE Consumer Endpoint name.</xsd:documentation>
At line 278 changed 3 lines.
<xsd:sequence minOccurs="0" maxOccurs="unbounded">
<xsd:any processContents="lax"/>
</xsd:sequence>
<xsd:choice minOccurs="0" maxOccurs="unbounded">
<xsd:any processContents="skip"/>
</xsd:choice>
At line 308 changed 1 line.
* NetBeans 6.1 or greater
* NetBeans 6.1 with Patch 3 (available via NetBeans Update Center after installing standard NetBeans 6.1, or simply use the OpenESB Installer)
At line 308 added 2 lines.
/ojc/schedulerse.jar]
* Standalone Scheduler UI NetBeans plug-in available [[not yet]
At line 314 changed 3 lines.
! Unofficial A La Carte Binaries
** [NetBeans Plugin|SchedulerSE/org-netbeans-modules-scheduler-ui.nbm]
** [OJC Runtime|SchedulerSE/schedulerse-installer-2.3-SNAPSHOT.jar]
! A La Carte Binaries
** [Scheduler SE runtime|http://download.java.net/jbi/binaries/open-jbi-components/main/nightly/latest/ojc/schedulerse.jar]
** [Scheduler UI NetBeans Plugin|http://download.java.net/jbi/binaries/open-esb-full-install/nbm/latest/org-netbeans-modules-scheduler-ui.nbm]
** Unofficial [Scheduler UI NetBeans Plugin|SchedulerSE/org-netbeans-modules-scheduler-ui.nbm]
At line 316 added 1 line.

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-30) was last changed on 20-Jan-09 09:30 AM, -0800 by EdWong