| Author |
Message
|
| Prahasith |
 Posted: Wed May 28, 2003 2:34 pm Post subject: upes |
 |
|
Disciple
Joined: 16 May 2003
Posts: 184
Location: Kansas City
|
The upes is responsible for processing of the container data, that is, to:
1) Copy the initial values of the output container into the output container(ProgramOutputData XML element) that is passed back to MQ Workflow.
MQ Workflow only takes the values passed back in the ActivityImplInvokeResponse as output data: this allows values to be unset
(to be set to null)
The above lines are from MQ workflow programming guide
can anyone explain me the above lines. |
|
| Back to top |
|
 |
| jmac |
| Posted: Wed May 28, 2003 2:48 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Prahasith:
When your UPES gets control it has (among other things) ProgramInputData and ProgramOutputDataDefaults.
If you wish those Defaults to be in the output container, you must move them there.
Basically, when your program responds it is the contents of the ProgramOutputData that determine the contents of the Output container.
Hope this helps
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Wed May 28, 2003 4:25 pm Post subject: Re: upes |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Hi Prahasith,
)
| Quote: |
| Copy the initial values of the output container into the output container |
As for as I know once the UPES takes over it retrieves the data from the input container of the UPES activity and builds the XML. If the upes is of type synchronous then once the response comes to the queue it updates the output container. If my assumption is wrong some one could correct me
Thanks,
Mahesh
IBM Certified Solution Expert - MQWorkflow |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed May 28, 2003 5:02 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Mahesh,
| Quote: |
| As for as I know once the UPES takes over it retrieves the data from the input container of the UPES activity and builds the XML. |
UPES doenot build any XML from input container. UPES gets the inputcontainer in the ActvityImplInvoke message sent by Workflow. Once it gets it UPES parses it out executes the appropriate program gets the output from the program and builds the appropriate <ActivityImplInvokeResponse> message and sends it back to workflow.
_________________
-Ratan |
|
| Back to top |
|
|
| Prahasith |
| Posted: Wed May 28, 2003 5:14 pm Post subject: Re: upes |
|
|
Disciple
Joined: 16 May 2003
Posts: 184
Location: Kansas City
|
" this allows values to be unset
(to be set to null)"
some one explain this line |
|
| Back to top |
|
|
| jmac |
| Posted: Thu May 29, 2003 4:05 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
UNSET = FMC_ERROR_MEMBER_NOT_FOUND (rc 113) in response to a Get Member API call.
THIS IS NOT NULL or Zero Length String this is NOT SET, Ie the member has never been valued.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
