Here is the sitrep:
I have two servers. ServerA is running Windows NT and has MQSeries Server version 5.1 installed. ServerB is a Windows 2000 Web server that is hosting my web application and has MQSeries Client version 5.2 installed. I am attempting to connect to a queue manager on ServerA from an ASP page on ServerB using MQSeries ActiveX components (found in the MQAX200.dll). I have a server connection channel defined on ServerA (named "ABC.MQ.CLIENT"
and I have modified the autoexec.bat on ServerB to utilize this channel with this line of code:
------------
SET MQSERVER=ABC.MQ.CLIENT/TCP/12.34.56.78(9999)
------------
Here is the VBScript code I have written (contained in an ASP file on ServerB) to connect to the queue manager (named "NewQueueManager" that is hosted on a ServerA:
--------------------
Dim MQAXSession
Dim qm ' get at the queue manager
set MQAXSession = Server.CreateObject ("MQAX200.MQSession"
Set qm = MQAXSession.AccessQueueManager("NewQueueManager"
--------------------
This code works up until the line where I try to run the AccessQueueManager function. I get a 2058 error message which is MQRC_Q_MGR_NAME_ERROR or "queue manager name not valid or not known". I have run the example files that come with the MQSeries ActiveX components and they all work fine on ServerB using the MQ Client to get to the MQ Server. I did notice that all of the example files that IBM sent with the MQSeries ActiveX component run using client-side processing and not server-side processing. I cannot use client side processing due to development constraints. Does anyone know how to get MQSeries ActiveX components to work using the scenario I have described above?
Thanks...
I have two servers. ServerA is running Windows NT and has MQSeries Server version 5.1 installed. ServerB is a Windows 2000 Web server that is hosting my web application and has MQSeries Client version 5.2 installed. I am attempting to connect to a queue manager on ServerA from an ASP page on ServerB using MQSeries ActiveX components (found in the MQAX200.dll). I have a server connection channel defined on ServerA (named "ABC.MQ.CLIENT"
and I have modified the autoexec.bat on ServerB to utilize this channel with this line of code:------------
SET MQSERVER=ABC.MQ.CLIENT/TCP/12.34.56.78(9999)
------------
Here is the VBScript code I have written (contained in an ASP file on ServerB) to connect to the queue manager (named "NewQueueManager"
that is hosted on a ServerA:--------------------
Dim MQAXSession
Dim qm ' get at the queue manager
set MQAXSession = Server.CreateObject ("MQAX200.MQSession"
Set qm = MQAXSession.AccessQueueManager("NewQueueManager"
--------------------
This code works up until the line where I try to run the AccessQueueManager function. I get a 2058 error message which is MQRC_Q_MGR_NAME_ERROR or "queue manager name not valid or not known". I have run the example files that come with the MQSeries ActiveX components and they all work fine on ServerB using the MQ Client to get to the MQ Server. I did notice that all of the example files that IBM sent with the MQSeries ActiveX component run using client-side processing and not server-side processing. I cannot use client side processing due to development constraints. Does anyone know how to get MQSeries ActiveX components to work using the scenario I have described above?
Thanks...