| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DCOM and MQ Series 5.3 (CSD07) for Windows |
« View previous topic :: View next topic » |
| Author |
Message
|
| mikeHT |
 Posted: Fri Oct 07, 2005 6:38 am Post subject: DCOM and MQ Series 5.3 (CSD07) for Windows |
 |
|
Voyager
Joined: 01 Jul 2005
Posts: 82
|
| What would be the impact on running of MQ Series 5.3 by disabling DCOM on Windows 2003? Any experience or inputs welcome. Thankyou. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Oct 07, 2005 4:32 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
DCOM is used by the IBM MQSeries service to start and stop queue managers, as far as I know.
I wouldn't recommend doing this. If you're concerned about security problems, then put the server behind a firewall that only allows communications on MQ listener ports.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| hopsala |
| Posted: Fri Oct 07, 2005 4:51 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
From the System Administration manual:
| Quote: |
The WebSphere MQ Services snap-in uses Component Object Model (COM) and Distributed Component Object Model (DCOM) technology to communicate between servers and between processes on a server.
The COM server application, AMQMSRVN, is shared between any client processes that need to use the WebSphere MQ Services snap-in components (for example, the WebSphere MQ Services snap-in, the alert monitor task bar, and the WebSphere MQ service). |
In other words - change at your own risk, with a healthy chance for problems  |
|
| Back to top |
|
|
| hguapluas |
| Posted: Wed Oct 19, 2005 11:05 am Post subject: |
|
|
Centurion
Joined: 05 Aug 2004
Posts: 105
Location: San Diego
|
Even though it's been a while since last post on this topic,
doing so is bad. If you do, your MQ will fail as noted in prior posts. When you manually go back in and start it, the service will run fine until the next refresh of the policy and kill MQ again.
The only way to stop this is to make a policy exception for that server(s) in your policies so that DCOM is not disabled and then you will be able to run fine while killing DCOM for all other servers/services in your domain. This works as I've been through this much to my frustration with our security folks.
Cheers, |
|
| 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
|
|
|
|
