| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| regarding application program invoking MQ Workflow |
« View previous topic :: View next topic » |
| Author |
Message
|
| venkatesh1976 |
 Posted: Thu Dec 12, 2002 2:04 am Post subject: regarding application program invoking MQ Workflow |
 |
|
Apprentice
Joined: 11 Nov 2002
Posts: 26
|
Hi,
I have a java servlet running on websphere App Server 3.5.
This calls an instance of a class which issues workflow related calls.
I get this error in the logs of WAS :
"FMC38000E Could not locate Agent for Domain SAMPLEWF "
where SAMPLEWF is the Agent and using JNDI_LOCATOR.
If I run a simple Java Client as a standalone connecting to the Workflow
directly (ie without any App Server) it runs fine.
Please enlighten on this.
[/b] |
|
| Back to top |
|
 |
| marcioalcantara |
| Posted: Thu Dec 12, 2002 9:29 am Post subject: |
|
|
Novice
Joined: 25 Jun 2001
Posts: 23
|
I have the same problem...
Anyone have any idea?
Thanks. |
|
| Back to top |
|
|
| Ratan |
| Posted: Thu Dec 12, 2002 10:01 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
From your WebSphere machine use LOC_LOCATOR policy to connect to workflow. To connect using JNDI_Locator policy, You need to have the agent running. I have no Idea using JNDI Locator policy, but it is easy and better to use LOC_LOCATOR.
-Laze |
|
| Back to top |
|
|
| educos |
| Posted: Fri Jan 03, 2003 1:37 pm Post subject: |
|
|
Apprentice
Joined: 18 Jul 2001
Posts: 34
Location: Salt Lake City, UT
|
The JNDI_LOCATOR policy works fine in a WebSphere environment, and it doesn't under WebLogic - go figure. By "works fine" I mean the API calls execute as expected, but _substantially_ more slowly than using LOC_LOCATOR.
If at all possible, configure a queue manager on your app server as part of your MQWF queue manager cluster, and use the LOC_LOCATOR policy, that way, only your action calls go over the wire. With JNDI_LOCATOR, even non action calls go over the wire, which can degrade your performance to the point of making it non-viable in a high transaction volume environment.
When a queue manager local to the app server is not an option, then you may want to consider wrapping your code into coarse grained methods, callable through RMI-IIOP or as a Web Service and have the actual service object run local to your MQWF queue manager. That way, you only have one remote call, and all MQWF API calls are done local to the queue manager. At that point, I would assume that even action calls are cheaper since they're done locally.
If you think your RMI-IIOP object or Web Service will be called so frequently as to seriously impact your WF server performance, then you may want to install a physically separate MQWF execution server and run your RMI-IIOP object or Web Service on that box.
_________________
Eric Ducos
EmeriCon, LLC.
Phone: (801) 789-4348
e-Mail: Eric.Ducos@EmeriCon.com
Website: www.EmeriCon.com |
|
| 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
|
|
|
|
