| Author |
Message
|
| kayoumt |
 Posted: Tue Oct 23, 2007 11:21 pm Post subject: |
 |
|
Voyager
Joined: 18 Sep 2007
Posts: 81
|
Yeap !
-- C# .NET
The MQIC32.DLL is installed. But seems it is not used for local connections to local queue manager. MQM.DLL is probably the library called by applications.
-- C++
I worked on C++ MQ applications yesterday night and found out something very strange. My full MQ installation (Client + Server) does not contain CLIENT CONNECTION DLLs (they are not installed). So far, so logical ; since applications could not bypass the local queue manager. But ; If have somewhere on my hard disk an MQ Client directory containing MQ CLIENT CONNECTION libraries (and add that directory to my PATH environment variable) MQ applications can make use of those libraries and bypass the local queue manager. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Oct 23, 2007 11:32 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Ok, this may be an obvious point but are you aware that a server installation does not, by default, include a client installation? Hence doing a "full" install does a full install of the server?
So if when the server installation was done, the client libraries were not deliberately selected as part of the install process they will not be present?
Just dotting the i's and crossing the t's on what you mean by a full install.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Oct 24, 2007 4:06 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
and if this the case and you want to install the MQ Client on a server that has MQ Server already, you have to install the MQ Client from the MQ Server install package. In this case you cannot install the MQ Client Support Pack, it just won't work.
I have VB.NET apps acting as clients from my laptop and I have a full Queue Manager running locally. I use the hashtable method to set the client variables like hostname, port #, etc. FYI amqmdnet.dll is indeed the only thing you need to link into your MQ Client app, but that dll requires a local install of the full MQ Client.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| kayoumt |
| Posted: Wed Oct 24, 2007 5:09 am Post subject: |
|
|
Voyager
Joined: 18 Sep 2007
Posts: 81
|
PeterPotkay,
Have couple of questions for you :
1) What value of MQC.TRANSPORT_PROPERTY you use for connecting to queue manager ?
2) Do you applications sometimes bypass the local queue manager and connect to a remote queue manager (via network) ?
3) What do you mean by MQ Client Support Pac ?
FYI.
Let me tell you how I did MQ installation on my labtop for being able both to connect to a local queue manager and to a remote queue manager with the labtop.
- I downloaded something called WMQv600Trial-x86_win.zip (size = 478 383 Ko) and install it by asking the installer to "install all features" of Server, Client, MQ Explorer, Development Tool Kit, SOAP, ...
- I downloaded also something called 6.0.2-WS-MQ-WinIA32-FP0002-EnUs.zip (size = 231 581 Ko) and installed on top of the already installed 6.0.0.
This is what I'm calling full installation. But, this kind of installation semms to omit installing client libraries for certain languages or to not allow certain olanguages to connect to remote queue managers. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Oct 24, 2007 8:02 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| kayoumt wrote: |
PeterPotkay,
Have couple of questions for you :
1) What value of MQC.TRANSPORT_PROPERTY you use for connecting to queue manager ?
|
I don't code it.
| Code: |
Dim myHashTable As New Hashtable
myHashTable.Add(IBM.WMQ.MQC.PORT_PROPERTY, MyPortNumber)
myHashTable.Add(IBM.WMQ.MQC.CHANNEL_PROPERTY, MyClientChannel)
myHashTable.Add(IBM.WMQ.MQC.HOST_NAME_PROPERTY, MyHostname)
myQM = New MQQueueManager(MyQMName, myHashTable)
|
| kayoumt wrote: |
2) Do you applications sometimes bypass the local queue manager and connect to a remote queue manager (via network) ?
|
Yes.
| kayoumt wrote: |
3) What do you mean by MQ Client Support Pac ?
|
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24009961&loc=en_US&cs=utf-8&lang=en
You can't install this support to get MQ Client on a macine that you installed full MQ Server on. In those cases you need the full MQ CLient from the MQ Server install.
| kayoumt wrote: |
I downloaded something called WMQv600Trial-x86_win.zip (size = 478 383 Ko) and install it by asking the installer to "install all features" of Server, Client, MQ Explorer, Development Tool Kit, SOAP, ...
|
That seems to say you should have everything you need. BUT, I have never played with a trial version. Maybe the trial version restricts that functionality I don't know.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| kayoumt |
| Posted: Wed Oct 24, 2007 1:21 pm Post subject: |
|
|
Voyager
Joined: 18 Sep 2007
Posts: 81
|
1)
Ok ! Ok ! I see. The directory I discovered on my hard disk which made my C++ code run anywhere is an unzipped MQ Client directory.
2)
Your application is probably running with the default value of MQC.TRANSPORT_PROPERTY (MQC.TRANSPORT_MQSERIES).
3)
Of course ! A commercial license, with support deal with IBM could maybe make life better for me. So far ; this forum helped me a lot ; I really appreciate the patience of its members. I have all stuff I need for terminating the development, testing and demos of my software. |
|
| Back to top |
|
|
| kayoumt |
| Posted: Thu Nov 08, 2007 10:12 am Post subject: |
|
|
Voyager
Joined: 18 Sep 2007
Posts: 81
|
MQNOREMPOOL ? Could someone explain me in very simple words what is the meaning of that MQ environment variable ?
After having lot of trouble with MQ connection and network errors, I found out that setting "MQNOREMPOOL=1" is, so far, the solution for compiling (once) C++/C# MQ applications and having them work with a standalone local MQ Server on a labtop or with a remote one. |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Nov 08, 2007 4:10 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Setting NOREMPOOL changes the way the listener handles TCP/IP sockets. It's designed to fix a very specific problem, that can be identified by the TCP/IP return codes on the connection failures.
If you can start a single channel, or a single Client connection to a Queue Manager, without NOREMPOOL, then you do not need it. It's not an intermittent issue.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| kayoumt |
| Posted: Thu Nov 08, 2007 8:49 pm Post subject: |
|
|
Voyager
Joined: 18 Sep 2007
Posts: 81
|
| I do not want to "worry" about how many channels are running or how many clients are connected to my queue manager. Then ; I think I need to have NOREMPOOL=1 on my standalone labtop ??? |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Nov 09, 2007 8:57 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
NOREMPOOL is only applicable for Windows Queue Managers that exhibit the issues for what it's designed to circumvent. And if you can make a single connection to that QM, either from a 2nd QM, or a client, both of which can be on the same machine, then you do not have the issues that warrant NOREMPOOL.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
