| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [SOLVED]PEA vs. UPES |
« View previous topic :: View next topic » |
| Author |
Message
|
| DJGoodrich |
 Posted: Thu Mar 06, 2003 4:28 pm Post subject: [SOLVED]PEA vs. UPES |
 |
|
Apprentice
Joined: 12 Dec 2001
Posts: 30
Location: SW Florida
|
Does anyone have documented information about when to use PEA vs. when to use a UPES? I have read the supplied documention, but I am not seeing the specific answer I am looking for.
The customer scenario is an application will be generating numerous XML messages. Each message will become a worklist items detined to be managed by a specific role. A number of individual users will be defined to each unique role. A second, web-based application will then be coded to select the specific worklist item and upon completion of its unit of work, mark it as complete/finished. WorkFlow is being implemented due to the time requirement/notification functionality. each item must be processed by the end user within a specified period of time.
In terms of the roles, there are presently estimated to approximately 1500 unique 'roles', and numerous individual users within each role.
When & what messages need be placed in the FMC.FMCGRP.FMCSYS.EXE.XML queue and when would messages be sent to the UPES defined queue? Are both ever used in conjunction with one another, or would the recomendation be to always keep them separate?
Last edited by DJGoodrich on Tue Mar 11, 2003 9:47 am; edited 2 times in total |
|
| Back to top |
|
 |
| Ratan |
| Posted: Thu Mar 06, 2003 5:07 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Read the thread:
http://www.mqseries.net/phpBB2/viewtopic.php?t=6468
the thread talk about JHPB VS UPES, but essentially JHPB is a PEA.
FMC.FMCGRP.FMCSYS.EXE.XML is an alias to EXEXMLINPUTQ which workflow read from. If you re using XML interface you have to always put your messages to EXEXMLINPUTQ (FMC.FMCGRP.FMCSYS.EXE.XML). Workflow inturn puts the message to the UPES inputQ if it determines that the activity needs to be executed by the specified UPES. Your UPES should inturn reply back to (<ActivityImplInvokeResponse>messages) EXEXMLINPUTQ.
-Laze |
|
| Back to top |
|
|
| clindsey |
| Posted: Thu Mar 06, 2003 8:07 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
As a general rule, if you are using a non-browser based client and the activity implementation requires user interface or need to launch an executable on the client machine, then a pea is the correct tool, otherwise employee a upes.
A pea is especially undesirable for high volume batch throughput.
This criteria is not currently documented, but based on conversations I have had with developerment, I believe it soon will be.
Charlie |
|
| 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
|
|
|
|
