| Author |
Message
|
| AmolArch |
 Posted: Mon Mar 21, 2005 7:59 pm Post subject: Broker application on AIX |
 |
|
Newbie
Joined: 19 Jan 2005
Posts: 7
|
Hi,
Our requirement is to deploy the final message flow application in AIX system.
Currently we have knowledge of broker on Windows XP.
Can we develop message flows, message sets in Windows and then port to AIX system.
If yes what will the efforts.
 |
|
| Back to top |
|
 |
| vennela |
| Posted: Mon Mar 21, 2005 9:15 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
You don't deploy directly to a physical broker.
You deploy to the configmgr and tell the configmgr which broker and execution group to deploy to. The configmgr will deploy to the respective broker.
It doesn't matter whether the broker is on Windows or AIX or HP-UX. |
|
| Back to top |
|
|
| AmolArch |
| Posted: Mon Mar 21, 2005 10:06 pm Post subject: |
|
|
Newbie
Joined: 19 Jan 2005
Posts: 7
|
Actually the scenario is like this.
There are two machines, Windows xp and AIX.
Requirement is that,we need to develop the message flows on windows system(contains only message broker toolkit) and deploy that flows on AIX system (AIX system will have broker,configmgr,DB2,MQ)
If this configuration is correct then how we can deploy these flow on remote AIX system ?
It will be thankfull if you share remote deployment procedure in details.
Thanks
Amol |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Mar 21, 2005 10:38 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| Requirement is that,we need to develop the message flows on windows system(contains only message broker toolkit) and deploy that flows on AIX system (AIX system will have broker,configmgr,DB2,MQ) |
Well, I 'll try one last time.
ConfigMgr is only on Windows. You cannot have it on AIX or any other platforms.
Having said that:
MachineA: ToolKit
MachineB: ConfigMgr
MachineC: Broker
MachineA, B, C can all be different or same or any combination.
Now ToolKit talks to ConfigMgr using MQ Java Client.
ConfigMgr talks to broker using MQ Channels (or if using the same QMGR then you will not have channels).
Toolkit always connects to configmgr. It never directly talks to broker. Any messages (like deployment) will be routed through configmgr.
You want to deploy a message flow, you will deploy it to the configmgr and the configmgr deploys to the broker. It doesn't matter whether the broker is local or remote.
Read the doc. |
|
| Back to top |
|
|
| vedantpatil |
| Posted: Tue Mar 22, 2005 12:08 am Post subject: |
|
|
Novice
Joined: 10 Mar 2005
Posts: 19
|
Hi vanella,
We are having similar situation.
We have two machines. One for development(windows) and other having broker (AIX)
It will be very much helpfull if you can tell me, which softwares/components i need to install on windows machine and AIX machine.
It will be very nice if you could give some documentation related to this.
Thanks in advance.
Vedant |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Mar 22, 2005 12:23 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Documentation link:
http://www.mqseries.net/phpBB2/viewtopic.php?t=17795
I am not too much of a WBIMB person.
Basically:
You install configmgr on a windows box. Broker on the AIX box. Setup DMQ (Distibuted Message Queueing) between the broker QMGR and configmgr QMGR.
Usually for development, the toolkits will be installed on the developers' machines. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 22, 2005 5:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Actually, you really need at least three machines.
You need one Windows machine for development purposes. This machine should have a full broker and configuration manager set up, with DB2 and MQ and everything. In fact, the WBIMB licensing, the last I knew, allowed for as many of these machines (with full setup) as you want, as long as they don't do production work and external machines don't use the broker that are installed on them. But all licensing questions should be addressed to your IBM sales representative.
Then you need a second Windows machine to act as the production Configuration Manager.
Then the production broker is on AIX.
The development machines can make additional Domain connections to the production configuration manager when needed, and can do all development and testing using the local development configmgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
