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 » EAI Bus and workflow

Post new topic  Reply to topic Goto page Previous  1, 2
 EAI Bus and workflow « View previous topic :: View next topic » 
Author Message
vennela
PostPosted: Tue Nov 18, 2003 11:26 am    Post subject: Reply with quote

Jedi Knight

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

I think I know what you are talking about.

It shouldn't look like this:
Quote:
<Mq message>
<Header>
<MQMD Filelds>
<Enterprise Header Values>

</header>
<Body or PayLoad>
<CDATA>
<Wfmessage>
<Wfheader>
</wfheader>
<ProcessTemplatecreateandstartinstance>
<ProcInputdata>

</wfmessaage>
</CDATA>
</Body>
</Message>


It should look like this

<Mq message>
<Header>
<MQMD Filelds>
<Enterprise Header Values>

</header>
<Body or PayLoad>
<Wfmessage>
<Wfheader>
</wfheader>
<ProcessTemplatecreateandstartinstance>
<ProcInputdata>

</wfmessaage>
</Body>
</Message>
Notice no CDATAs.

Whenevr you are ready to put an XML message to workflow it should conform to the DTD (it is published in MQWF Programming guide chapter 35)

From where you get the data... client side... server... or from wherever it is upto you.

Quote:
I think it doesn't support wf-xml tags)

What do you mean by this. What doesn't support workflow tags. You should confirm this from the source where you got this information from.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Ramgathy
PostPosted: Tue Nov 18, 2003 11:43 am    Post subject: Reply with quote

Apprentice

Joined: 31 Oct 2003
Posts: 49

Ratan,

It's my understanding that we cannot put xml tags inside an XML.I just assumed it.No source as such..thanks for correcting

Correct me if my understanding is wrong.I get the data embed the wfxml message inside the body of other message.
ur message

It should look like this

<Mq message>
<Header>
<MQMD Filelds>
<Enterprise Header Values>

</header>
<Body or PayLoad>
<Wfmessage>
<Wfheader>
</wfheader>
<ProcessTemplatecreateandstartinstance>
<ProcInputdata>

</wfmessaage>
</Body>
</Message>


Can i put this message directly onto EXEXXLINPUTQ

will the WF be able to parse the data and start instance or do I need to parse the overall XML and get the WFXML and send it to inputQ

Thanks ratan i will gothrough the dtd in manual
Regards,
Back to top
View user's profile Send private message
vennela
PostPosted: Tue Nov 18, 2003 11:50 am    Post subject: Reply with quote

Jedi Knight

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

Quote:
Can i put this message directly onto EXEXXLINPUTQ

I think "Yes" but
Code:
<Enterprise Header Values>

</header>


What are these?
Back to top
View user's profile Send private message Send e-mail Visit poster's website
jmac
PostPosted: Tue Nov 18, 2003 12:02 pm    Post subject: Reply with quote

Jedi Knight

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

Ramgathy wrote:
<Wfmessage>
<Wfheader>
</wfheader>
<ProcessTemplatecreateandstartinstance>
<ProcInputdata>

</wfmessaage>


This portion of the message can be put to EXEXMLINPUTQ. Be sure that everthing is valid for MQWF.
_________________
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
Ramgathy
PostPosted: Tue Nov 18, 2003 1:11 pm    Post subject: Reply with quote

Apprentice

Joined: 31 Oct 2003
Posts: 49

Hi All,
I am enclosing the kind of message inneed to send from client side and receive on the serverside.
Businessservice,contol and error portion of the headers are used for logging auditing and commonservices across enterprise.
This is common across enterprise.How do we use this in workflow scenario.

I get a feeling that we need to put wf-xml in payload(Body) of the message

Venny-This is the enterprise header values-Mapped values to MQMD

<?xml version = "1.0" encoding = "UTF-8"?>
<Message>
<CompanyNameHeader>
<BusinessService>
<ServiceSource>
<domainName>USA</domainName>
<queueName/>
<session/>
</ServiceSource>
<ServiceTarget>
<domainName/>
<queueName/>
<session/>
</ServiceTarget>
<serviceName>GetMember</serviceName>
<serviceVersion>1</serviceVersion>
<serviceTransport>1</serviceTransport>
<encryption>N</encryption>
<messageFormat>1(XML)</messageFormat>
<messageSize/>
<transformMessage>0(No)</transformMessage>
<priority>1</priority>
<persistence>1</persistence>
<expiry/>
<loggingLevel>1</loggingLevel>
<auditLevel>1</auditLevel>
<environment>DEV</environment>
</BusinessService>
<ControlHeader>
<CompanyNameMessageId>ABC0123456</CompanyNameMessageId>
<systemSignatureType>WFCLNT_ADT</systemSignatureType>
<componentTimestamp>2003-06-17 22:41:27.630</componentTimestamp>
<softwareReleaseLevel>WF_EAI_REV1</softwareReleaseLevel>
<sourceQueueManagerName>QM</sourceQueueManagerName>
<sourceReplyToQueueName>WFCLNT.RECVQ</sourceReplyToQueueName>
<destinationBusinessServiceId>ALIGNDEX</destinationBusinessServiceId>
<destQMgrName/>
<destQueueName/>
<originalMessageId/>
</ControlHeader>
<ErrorInformation>
<systemSignatureType>EMPICLNT_ADPT</systemSignatureType>
<errorTimestamp>2003-06-17 23:41:27.630</errorTimestamp>
<exceptionObjectLabel>WGS2_0REV1</exceptionObjectLabel>
<errorMessageText>Name not found</errorMessageText>
<errorServerity>serve</errorServerity>
<errorMessageDescription>Name not found</errorMessageDescription>
</ErrorInformation>
</CompanyNameHeader>
<Payload>
<GetMemberRequest>
<MemberNumber>24680</MemberNumber>
</GetMemberRequest>
</Payload>
</Message>
Back to top
View user's profile Send private message
Ratan
PostPosted: Tue Nov 18, 2003 1:23 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

Only this XML can be put into EXEXMLINPUTQ to start a PI:
<Wfmessage>
<Wfheader>
</wfheader>
<ProcessTemplatecreateandstartinstance>
<ProcInputdata>

</wfmessaage>

You cant have this enclosed in any other XML and put it to EXEXMLINPUTQ.

If you have this XML as a part of some other XML, make sure you parse this portion out before putting to EXEXMLINPUTQ.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
Ramgathy
PostPosted: Tue Nov 18, 2003 2:44 pm    Post subject: Reply with quote

Apprentice

Joined: 31 Oct 2003
Posts: 49

Thanks ratan..
Can you please tell me the pros and cons of
passing data as wf-xml in the payload and parsing and sending that chunk into workflow
2.get data in the EAI bus format and parse payload and build a wf-xml on the server side and send to wf.

Regards,
Back to top
View user's profile Send private message
Ratan
PostPosted: Tue Nov 18, 2003 2:50 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

Both look same to me. How you get your XML is beyond the scope of this forum. If you have doubts about the actual message that is put into EXEXMLINPUTQ we can help.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
Ramgathy
PostPosted: Tue Nov 18, 2003 4:20 pm    Post subject: Reply with quote

Apprentice

Joined: 31 Oct 2003
Posts: 49

Thanks Ratan
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » EAI Bus and workflow
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.