| Author |
Message
|
| ivanachukapawn |
 Posted: Wed Sep 15, 2010 5:13 am Post subject: M071 missing amqzsaic.dll - MQ6.0.2.9 on Win2k |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| M071 can't find amqzsaic.dll on this server. I have MQ6.0.2.9 installed with rootDir = e:\IBM\WebSphere MQ\ - and this DLL is not in the bin. I tried to install MQ7 client for Windows but setup could not continue because SP1 was not installed. I don't see any MQ6 client installation media in Support Pacs. Questions: Should I install MQ client to solve this problem? If so, where is there a download link to the MQ client installer for this environment? |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Sep 15, 2010 5:31 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
It's normally bundled with the Server installation. If at install time the selection did not include Client, then fire up the installer again and select it. You may have to roll out any FixPacks before you can install (not sure on that point, it's been a while).
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Wed Sep 15, 2010 5:58 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| The installation was done silently via MQParms (for 6.0.2) and by running the FP 9 .exe for 6.0.2.9 - apparently the silent install does not install client. I am now taking steps to install MQC6 (Windows MQ6.0.2.9 client). Hopefully this will fix it. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Sep 15, 2010 6:03 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
The silent install will whatever is in its input file  ...
You are now learning the efficacy of future-proofing by installing all components, and if you have MO71 on the server why are you using client-mode to connect? Why not use bindings mode?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 15, 2010 6:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ivanachukapawn wrote: |
| apparently the silent install does not install client. |
It does (or should) if you have both Server & Client in the ADDLOCAL parameter but not otherwise; see here.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Wed Sep 15, 2010 6:41 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| Exerk - you wrote, "why not use bindings mode". I want to tighten up security on these Win2K MQ6.0.2.9 servers. Currently everybody and their uncle are in the local administrators group. I want to remedy that by getting MQ admins into the Domain\domain mqm group and then pairing down the administrators group to bona fide administrators. My plan is to allow MQ admin client access (even though its on server) via SSL encrypted SVRCONN. Do you know of a better way to go about it? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Sep 15, 2010 8:54 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| ivanachukapawn wrote: |
| The installation was done silently via MQParms (for 6.0.2) and by running the FP 9 .exe for 6.0.2.9 - apparently the silent install does not install client. I am now taking steps to install MQC6 (Windows MQ6.0.2.9 client). Hopefully this will fix it. |
If you installed MQ Server on a machine, then you have to use that media to add the client. You cannot apply the MQ Client Support Pack in this scenario. Or at least you were never able to in the past, at least up to MQ 5.3.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Sep 15, 2010 10:59 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| ivanachukapawn wrote: |
| Exerk - you wrote, "why not use bindings mode". I want to tighten up security on these Win2K MQ6.0.2.9 servers. Currently everybody and their uncle are in the local administrators group. I want to remedy that by getting MQ admins into the Domain\domain mqm group and then pairing down the administrators group to bona fide administrators. My plan is to allow MQ admin client access (even though its on server) via SSL encrypted SVRCONN. Do you know of a better way to go about it? |
If you cannot install client you can still lock down access with OAM, even with bindings mode, or tunnel through another queue manager that you have client-only restricted-access to.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| zonko |
| Posted: Wed Sep 15, 2010 10:04 pm Post subject: |
|
|
Voyager
Joined: 04 Nov 2009
Posts: 78
|
I don't see any point in using SSL, since you already know the machine the client is running on.
You need to authenticate the user, not the connection. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Sep 16, 2010 2:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| zonko wrote: |
I don't see any point in using SSL, since you already know the machine the client is running on.
You need to authenticate the user, not the connection. |
You can't, as a rule, trust the UserID that is passed in on a client connection. Regardless of whether or not you know the machine the program is running on. There are simply too many ways this can be overridden by the application, and thus expose you to mqm access from unintended sources.
SSL allows you to determine if a given cert is able to connect to a given channel using SSLPEER. You can then use MCAUSER to enforce the role that holders of that cert should act in. |
|
| Back to top |
|
|
|
|
