ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED]asynchronous UPES- i/p Container fields

Post new topic  Reply to topic
 [SOLVED]asynchronous UPES- i/p Container fields « View previous topic :: View next topic » 
Author Message
kotha
PostPosted: Wed May 18, 2005 7:20 am    Post subject: [SOLVED]asynchronous UPES- i/p Container fields Reply with quote

Partisan

Joined: 12 Mar 2005
Posts: 333

The Process:

A-------->B--------->C

Data structures: Output of A, Input and Output of B and Input and Output of C are same.

B is UPES, UPES mode: asynchronous and B has a data loop connector.

When the activity A finishes B automatically finishes and puts the XML in a QUEUE and C is now in active state. but the input container of C values are NULL (means the output of B is not set.). Even without dataloop connector for B, the I/p container not filled.

Do i need to put the Data Structure values back to Queue by a java program?.

Question: How should I fill the output container of B??

any suggestions greatly appriciated. Thx


Last edited by kotha on Thu May 19, 2005 3:38 pm; edited 1 time in total
Back to top
View user's profile Send private message
jmac
PostPosted: Wed May 18, 2005 8:38 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

I believe what you need is a data connector from A to C.
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
kotha
PostPosted: Wed May 18, 2005 8:58 am    Post subject: Reply with quote

Partisan

Joined: 12 Mar 2005
Posts: 333

Thx Jmac. i tried other way n its working.

A-------->B
A--------->C

But what happens to the O/P container of asynchronous UPES activity when it is executed besides putting a message in a QUEUE?. program has fmcnshow.exe at the path and file name.
Back to top
View user's profile Send private message
vennela
PostPosted: Wed May 18, 2005 9:15 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Kotha:

From I/P container to O/P container of the same activity you should use Data Default Connector.
From O/P container to I/P container, of the same activity you should use Data Loop connector.

Hope this information will help you understand what happened in your case
Back to top
View user's profile Send private message Send e-mail Visit poster's website
jmac
PostPosted: Wed May 18, 2005 9:28 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

kotha wrote:
But what happens to the O/P container of asynchronous UPES activity when it is executed besides putting a message in a QUEUE?. program has fmcnshow.exe at the path and file name.


It is my opinion that after an Asynchronous UPES activity MQWF ignores the content of the Output container.... Note that this is just a guess, based on what you reported earlier. I wouldn't bet the ranch on this without doing some testing to be sure.
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
kotha
PostPosted: Wed May 18, 2005 9:57 am    Post subject: Reply with quote

Partisan

Joined: 12 Mar 2005
Posts: 333

vennela wrote:
Kotha:

From I/P container to O/P container of the same activity you should use Data Default Connector.
From O/P container to I/P container, of the same activity you should use Data Loop connector.

Hope this information will help you understand what happened in your case


Yes. I tried with Data Default Connector. It is working!!!.

So no matter what kind of activity it is, if we use the connectors properly, we can get the desired results!!!.

Thank you both for sharing your views.
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Thu May 19, 2005 1:07 am    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi vennela,

I have been using the Data default connector for all my activities....

I wanted to know what is the difference if i do not give any type of data connector (neither data default nor the data loop connector)....what would happen???

Also i can understand someone wanting to copy the I'P container to the O/P, but where and when do we need to copy the O/P to the I/P container ??
Back to top
View user's profile Send private message Send e-mail
mqmhr
PostPosted: Thu May 19, 2005 3:03 am    Post subject: Reply with quote

Centurion

Joined: 28 Dec 2004
Posts: 105

If you do not use a default data connector, when the task executes, its input container values will not be copied to its output container, even if the input and output container structures are the same.

Data loop connector could be used in a situation where we need to perform the same task repeatedly until its exit condition is satisfied. One or more ouput container field values (for e.g, a counter that is incremented by the task implementation when it executes) could be used in the exit condition. I have not done any such implementation but just put down my understanding of it.

Also, if a task does not have an exit condition, I believe there is no use in having a data loop connector, as the task will not be executed again and the values copied from the o/p container to its i/p container would not serve any purpose.
Back to top
View user's profile Send private message
kotha
PostPosted: Thu May 19, 2005 5:17 am    Post subject: Reply with quote

Partisan

Joined: 12 Mar 2005
Posts: 333

elvis_gn wrote:

Also i can understand someone wanting to copy the I'P container to the O/P, but where and when do we need to copy the O/P to the I/P container ??


With data connector, the data structure values can be copied from O/P container of the present activity to I/P container of next activity. It depends on you application/activity. If the next activity need some of the datastructure values, then you should transfer the datastructure values to next activity.

This is very common. But when you use asynchronous UPES activity...it appears that the I/P container is not automatically transfferred to O/P. That's the TOPIC issue. The solution we find is to implement the asynchronous UPES with Data Default Connector.
I hope you understand.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED]asynchronous UPES- i/p Container fields
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.