Author |
Message
|
Hari |
Posted: Sun Apr 25, 2004 11:41 pm Post subject: Workflow XML -- Initiating WF Instance doesnt work. [Solved] |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
Hi all,
This query infact cud have gone both in the WF and the WBIMB forums.
I have been converting this XMLNS msg to this WF XML msg to "Create and Start Process Instance".
But when this Output Node puts this msg in the "EXEXMLINPUTQ" though the msg is consumed but no Process instance is created & started.
Moreover there are no errors being shown in the Event Viewer as well.
*********************************************************8
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<WfMessage>
<WfMessageHeader>
<ResponseRequired>NO</ResponseRequired>
</WfMessageHeader>
<ProcessTemplateCreateAndStartInstance>
<ProcTemplName>ProcTemp1</ProcTemplName>
<ProcInstName>HARI1</ProcInstName>
<KeepName>TRUE</KeepName>
<ProcInstInputData>
<MYUPDTSTATONLY>
<EntyTyp>CUST</EntyTyp>
<UpdtDesc>Customer Updated</UpdtDesc>
<UpdtStat>COMPLETE</UpdtStat>
</MYUPDTSTATONLY>
</ProcInstInputData>
</ProcessTemplateCreateAndStartInstance>
</WfMessage>
*********************************************************
I thought that may be it may not be able to recognise the Format of the msg.
So tried all setting diff options in ESQL for the format, like :
SET OutputRoot.MQMD.Format = 'XML';
SET OutputRoot.MQMD.Format = 'MQSTR';
but no avail
Pls advice.
Regards,
Hari
Last edited by Hari on Mon Apr 26, 2004 9:25 am; edited 1 time in total |
|
Back to top |
|
 |
Hari |
Posted: Sun Apr 25, 2004 11:52 pm Post subject: |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
Also i have set :
SET OutputRoot.MQMD.UserIdentifier = 'ADMIN';
The process instance is created under the "ADMIN" user id. |
|
Back to top |
|
 |
CHF |
Posted: Mon Apr 26, 2004 4:35 am Post subject: |
|
|
 Master
Joined: 16 Dec 2003 Posts: 297
|
Put a Reply2Q and look for the error. The response gives you detail information on why it failed.
CHF |
|
Back to top |
|
 |
CHF |
Posted: Mon Apr 26, 2004 4:40 am Post subject: |
|
|
 Master
Joined: 16 Dec 2003 Posts: 297
|
Double check for the following:
1) Is template "ProcTemp1" exists already?
2) Is there any instance with name "HARI1" ? If so WF will not create any instance as you are specifying <KeepName>TRUE</KeepName>
The best way to solve problems like this is to specify a Reply2Q. Make suere to change "<ResponseRequired>" value to "Yes". Post the errors here.
CHF  |
|
Back to top |
|
 |
Ratan |
Posted: Mon Apr 26, 2004 6:33 am Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
CHF, Are you sure about this? I dont think so (too lazy to test it).
Quote: |
2) Is there any instance with name "HARI1" ? If so WF will not create any instance as you are specifying <KeepName>TRUE</KeepName> |
_________________ -Ratan |
|
Back to top |
|
 |
CHF |
Posted: Mon Apr 26, 2004 7:09 am Post subject: |
|
|
 Master
Joined: 16 Dec 2003 Posts: 297
|
Yes Ratan. It wont start the instance.
This is the response message you will get to Reply2Q:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- This document is generated by a MQSeries Workflow Version 3.4.0 server -->
<WfMessage>
<WfMessageHeader>
<ResponseRequired>No</ResponseRequired>
</WfMessageheader>
<ProcessTemplateCreateAndStartInstanceResponse>
<Exception>
<RC>121</RC>
<Parameters>
</Parameters>
<MessageText>FMC0121E Name is not unique</MessageText>
<Origin>d:\v340\src\fmcmctnm.c.............</Origin>
</Exception>
<RequestAsHexString>...content omitted...</RequestAsHexString>
</ProcessTemplateCreateAndStartInstanceResponse>
<WfMessage> |
|
Back to top |
|
 |
Hari |
Posted: Mon Apr 26, 2004 7:22 am Post subject: |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
Infact i just added this ReplyToQ and found one surprising thing, WF is giving the following error:
<MessageText>FMC00010E Unknown user ID </MessageText>
Though i have set the user id as "ADMIN" as said before, still it is not able to authorize the user.
Regards,
Hari |
|
Back to top |
|
 |
Ratan |
Posted: Mon Apr 26, 2004 7:27 am Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
The userID in your MQMD should be the user with which you want to start the Process. In your case ADMIN. _________________ -Ratan |
|
Back to top |
|
 |
Ratan |
Posted: Mon Apr 26, 2004 7:35 am Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
CHF, Thnx for the info. _________________ -Ratan |
|
Back to top |
|
 |
Hari |
Posted: Mon Apr 26, 2004 7:38 am Post subject: |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
What i did is i stopped WF service, to check what is the userid is being passed in the MQMD, to my surprise it is taking my NT login id.
I will need to chk why Message Broker is not able to set the "ADMIN" id.
Will need to chk my ESQL again.
Thanx all u guys for replies.
Regards,
Hari |
|
Back to top |
|
 |
Hari |
Posted: Mon Apr 26, 2004 8:10 am Post subject: |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
Thanks guys for all ur help.
Changing some parameters in the Output Node did the trick.
Now the UserIdentifier is being set to the "ADMIN" user.
Regards,
Hari |
|
Back to top |
|
 |
CHF |
Posted: Mon Apr 26, 2004 10:00 am Post subject: |
|
|
 Master
Joined: 16 Dec 2003 Posts: 297
|
You are Welcome Ratan.
Hari FYI:
If you put a message to EXEXMLINPUTQ thru a Windows box, the default user id WF takes is your Windows NT Login id.
If you are using any application (like WMQI, Java) to put a message to EXEXMLINPUTQ, make sure the user identifier value that you are setting in MQMD is setting correctly. |
|
Back to top |
|
 |
Hari |
Posted: Mon Apr 26, 2004 11:19 am Post subject: |
|
|
 Centurion
Joined: 21 Nov 2002 Posts: 117 Location: USA
|
Infact i had set the "UserIdentifier" as can be seen from my prev post.
Well i had to change the Message Context in the MQOutput Node from "Pass All" to "Set Identity", to properly set the User Identifier.
And bingo it works fine..
But thanks very much all of you for your quick responses. |
|
Back to top |
|
 |
|