| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| what is the use of 2 agents on same machine ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| sebastia |
 Posted: Mon Feb 18, 2013 12:28 am Post subject: what is the use of 2 agents on same machine ? |
 |
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Good morning.
I have a question about MQFTE.
I read "Each agent uses its own uniquely identified queues that are separate from those used by other agents. Thus, an agent queue manager can validly host more than one agent."
As I understand it, a FTE Agent is the "entry point" for an Application to access the MQ network, so it cand send files to remore queue managers.
So, why should someone place 2 agents on same (input) machine ?
Well, if 1 agent is "local", this is "Server" and "N-1" are "remote" or "client",, then I understand the phrase ...
Can someone clarify my concepts, if wrong ? Sebastian. |
|
| Back to top |
|
 |
| nickla23 |
| Posted: Fri Feb 22, 2013 6:30 am Post subject: |
|
|
Novice
Joined: 06 Dec 2012
Posts: 12
|
There are a couple different reasons you could use more than 1 agent per queue manager.
The main one being that there are different types of agents, Transfer Agent(standard), Protocol Agent(FTP), Web Agent(Web Gateway), and Connect:Direct Agent. Also within each agent you can specify in the agent.properties, the particulars as far as how MQ will handle the transfer, chunk/block/window size as well as max transfers. One other reason, in cases where there are large number of transfers coming into a system, you can divide them up based off your needs so that there is less of an impact if you have a problem with one of the transfers or agents. |
|
| Back to top |
|
|
| sebastia |
| Posted: Sat Feb 23, 2013 12:14 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
| nickla23 wrote: |
There are a couple different reasons you could use more than 1 agent per queue manager.
The main one being that there are different types of agents, Transfer Agent(standard), Protocol Agent(FTP), Web Agent(Web Gateway), and Connect:Direct Agent. Also within each agent you can specify in the agent.properties, the particulars as far as how MQ will handle the transfer, chunk/block/window size as well as max transfers. One other reason, in cases where there are large number of transfers coming into a system, you can divide them up based off your needs so that there is less of an impact if you have a problem with one of the transfers or agents. |
THANKS A LOT, mr NICKLA - very good explanation ! |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Wed Apr 24, 2013 11:34 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
I think, this is the Redbook being discussed in the original question. I have a follow-up question.
About the client agents, on page 32, this is mentioned (emphasis mine) :
| Quote: |
| WebSphere MQ File Transfer Edition Client agents, which must run on a machine that does not have WebSphere MQ installed, can only associate with this queue manager in client mode. |
So, by design, the machine where Client agents are expected to run shouldn't have WMQ clients or the queue manager. Is this right ?
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Apr 25, 2013 11:23 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2602
Location: The Netherlands (Amsterdam)
|
another reason for multiple agents per machine can be access control...
suppose you have app A sending files to app B and
app C sending files to app D
suppose app A and C are on one machine and you use 1 agent, that means the id the agent is running under needs read/write (to delete the files you need write rights) access to both directories where app A and C are writing their files... you may not want that... as the agent can now technically send files from app A to app D ... and from app C to app B ...
having seperate agents with seperate access rights prevents that from happening.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 25, 2013 8:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| Cogito-Ergo-Sum wrote: |
I think, this is the Redbook being discussed in the original question. I have a follow-up question.
About the client agents, on page 32, this is mentioned (emphasis mine) :
| Quote: |
| WebSphere MQ File Transfer Edition Client agents, which must run on a machine that does not have WebSphere MQ installed, can only associate with this queue manager in client mode. |
So, by design, the machine where Client agents are expected to run shouldn't have WMQ clients or the queue manager. Is this right ? |
I believe you're reading into it more than there is. My interpretation is that there will be no MQ Server installation. Nothing said about MQ Client... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Thu Apr 25, 2013 10:07 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
Thanks !
| Quote: |
| I believe you're reading into it more than there is. |
Sometimes, I read like a lawyer. 
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| 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
|
|
|
|
