| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XML message interface |
« View previous topic :: View next topic » |
| Author |
Message
|
| RJoubert |
 Posted: Wed Jul 03, 2002 5:03 am Post subject: XML message interface |
 |
|
Apprentice
Joined: 30 May 2002
Posts: 43
Location: Buffalo, NY
|
We have a step in our workflow process where work items are in a "holding pattern" waiting for an update to the data container. These work items are introduced into our workflow via the XML message interface (using ProcessTemplateCreateAndStartInstance).
Is there anyway, using similar XML, to update the data container and introduce these work items back into the workflow process?
Thanks,
_________________
Rich Joubert
Computer Systems Engineer
Univera HealthCare, an Excellus Company |
|
| Back to top |
|
 |
| steinra |
| Posted: Wed Jul 03, 2002 10:06 am Post subject: |
|
|
Apprentice
Joined: 23 May 2002
Posts: 28
Location: USA
|
Rich,
The items that are in a holding pattern, are they at an activity point?
Randy |
|
| Back to top |
|
|
| RJoubert |
| Posted: Mon Jul 08, 2002 11:34 am Post subject: |
|
|
Apprentice
Joined: 30 May 2002
Posts: 43
Location: Buffalo, NY
|
Yes.
To generalize the question...is there a way to update the data container for an existing workflow instance via XML? To create these workflow instances, I used XML with the <ProcessTemplateCreateAndStartInstance>. Is there a similar tag for updating an instance, or overwriting an instance?
Thanks,
_________________
Rich Joubert
Computer Systems Engineer
Univera HealthCare, an Excellus Company |
|
| Back to top |
|
|
| steinra |
| Posted: Mon Jul 08, 2002 9:36 pm Post subject: |
|
|
Apprentice
Joined: 23 May 2002
Posts: 28
Location: USA
|
I am not familiar with all of the new XML interfaces in 3.3.2, haven't had a chance to play with it yet. So someone else may have to reply to if it is possible in that version.
To do what you are asking for in 3.3, the only way I can think of is like this.
Have the activity be a UPES activity. When the XML UPES message comes in write that message to the database. I am assuming you have a unique identifier in the data structure so you can tie your update back to this workflow item. With the primary key entered into the row then store the original XML message in the record. I found it easier to encode the data (UUEncode, Base64, or YEnc) prior to putting it into a database character type. That way you don't need to worry about escaping the ' that may appear in the data.
When your update comes in, select the record with the matching criteria and then update the XML data contatiner and send it back to workflow. You could also set an expiration time on the item to take another path in the process map if the external update does not arrive in a timely fashion.
If you have MQSI you might be able to do all these steps in there.
I know it now requires a database resource and some supporting code. I had to do something similar to integrate a system that didn't understand XML. Plus the sytem I was integrating could hold the work item for days.
There might be another way with the newer version, but I am not aware of one if there is.
Hope that helps.
Randy |
|
| Back to top |
|
|
| RJoubert |
| Posted: Tue Jul 09, 2002 2:47 am Post subject: |
|
|
Apprentice
Joined: 30 May 2002
Posts: 43
Location: Buffalo, NY
|
Thanks for the suggestion. I'm trying to use the XML message interface to avoid unneccessary coding, but I may have to bite the bullet here.
I'm starting to look into storing all of the container data in a separate database and only carrying a "pointer" through workflow. Any experience in that area?
Thanks again for your help,
_________________
Rich Joubert
Computer Systems Engineer
Univera HealthCare, an Excellus Company |
|
| Back to top |
|
|
| webstream |
| Posted: Tue Jul 09, 2002 8:21 am Post subject: |
|
|
Newbie
Joined: 03 Jul 2002
Posts: 5
|
hi,
I have used the approach of carrying a pointer through the workflow.However i also have a corresponding status with the pointer so that at every activity point in the workflow we can determine which path(Success OR Error) to pursue.At every activity point the data required is read from the database.
The only caveat on using this approach is that you have to ensure that an optimistic locking is set on the record being used.
The following link is the best example for XML interface with Workflow
http://www-3.ibm.com/software/ts/mqseries/txppacs/wa05.html
Hope this helps,
WebStream |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
