Setting up Scheduled Task Adapter

After I published a post to get the scheduled task adapter to work (by gacing the assemblies) I had someone ask me if I had a tutorial on setting up the properties for the adapter.  So here it is.
This is based on the previous version of the adapter not the lastest one.

Step 1: Create a receive location by creating a receive port or defining an existing receive port and choose the type to be “ScheduledTask” adapter

Step 2: Click on the configure button and click the Task Tab

Step 3: Click the FindTask button and then the browse to the location of the scheduled task dlls

Step 4: Select the Task Component dll

Step 5: Choose “XmlStringStreamProvide” and double click to populate “Assembly Qualified Type Name”

Step 6:Hit OK and “…” to bring up the XMLText Editor

Step 7: Type in the message that you want the adapter to put in the message box.  To generate this message, (if you have followed the solution architecture as outlined in Dan R’s book) you can generate an instance of the internal schema.  Hit ok..

Step 8: Click the schedule tab to specify the schedule.  There are various options, and in this example, I would be using weekly so that I can drop the message every day at 4:55 pm

Step 9: Choose XML Transmit pipeline and thats basically it.

 

 

Advertisements
    • Shabbir Hussain
    • February 6th, 2013

    It looks just fine but another concerning thing which I am thinking of is “If the orchestration doesn’t complete its cycle during the scheduled time then what will happen?”

  1. Good post, but i have not seen any post on really the deep end of usage. One of the question is. does the adapter work in conjuction to the native “Schedule” items in the adapter dialog ? and how it will behave if both the Schedule settings and the adapters built in settings are set to something. I have not tried this but i have to use this adapter now and i may run a test to find that out but just throwing this question out there hoping i may save some effort and time 🙂

    • The Native schedule is at port level where as this adapter schedule is at the adapter level. Hence, when the port is disabled using the native scheduled, it will hold all the messages. The schedule task adapter will continue routing messages based on its schedule. That means all the messages sent from the scheduled task will be held at the port level and routed when the port is enable again via its schedule. Does this make sense?

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: