| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Setting up a clustering solution |
« View previous topic :: View next topic » |
| Author |
Message
|
| glen |
 Posted: Tue Oct 22, 2002 7:03 am Post subject: Setting up a clustering solution |
 |
|
Novice
Joined: 05 Jun 2002
Posts: 13
Location: Dublin, Ireland.
|
Hi
I currently have MQS 5.2.1 on NT4-enterprise: Several qm's have been setup and running for some time now.
the install was not straightforward as MQS is in a DMZ - with clients in our (internal) domain, and an external company with clients which connect to the MQS over a leased line. Trusting their domain is not an option. The long and short of it is that this works. I can get and put to queues successfully.
I have this working as user accounts are created locally on the MQS and are added to the mqadmin local group. If there is a way of restricting client access - I would prefer not to give admin access, I would appreciate any advice (slightly off topic, but read on :)
1. I am planning to install an additional server and hardware cluster, using MSCS / NT4E, unless someone can convince me to use a Win2k solution.
If I need to reinstall everything from scratch, then so be it. However, if I can get away with adding to my existing solution, I would love to know how to achieve this.
2. Due to the security relationships with Win2k, I have been steering away from this - again, unless someone can convince me that I can get Win2k/ MQS to work - given my current setup - are there any advantages to doing this?
thanks
G. |
|
| Back to top |
|
 |
| Bill57 |
| Posted: Tue Oct 22, 2002 9:19 am Post subject: |
|
|
Apprentice
Joined: 26 Jul 2002
Posts: 35
Location: Atlanta, GA
|
As far as the client access goes, you can specify a user id in the MCAUSER parameter of the serverconn definition. Lets say you make it "client". Then create a user id on the system called client, and a group named client. Use the setmqaut utility to give client access privileges to the queues your customers use. Now they can put and get to their queues, but they have no admin permissions to reek havoc on your queue manager.
This is not the most robust solution, but requires little admin, and offers you some protection.
There is a security white paper on the IBM web site that goes into great detail on how all this works. Its very dry reading, but good info.
Good Luck
_________________
Bill Anderson
MQSeries Developer |
|
| 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
|
|
|
|
