| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [SOLVED]Connecting to remote MQWF instance from WebClient |
« View previous topic :: View next topic » |
| Author |
Message
|
| Thérèse |
 Posted: Thu Jan 12, 2006 6:29 am Post subject: [SOLVED]Connecting to remote MQWF instance from WebClient |
 |
|
Newbie
Joined: 12 Jan 2006
Posts: 3
|
Hi all,
We have an application that connects to a remote MQ WF instance and performs the following operations (among others):
1. Instantiate the Agent
2. Locate the Agent
3. ExecutionService.logon4 with credentials
5. ExecutionService.persistentPerson
6. Person.refresh
We're getting the following error all the time (sorry for the mispellings if any, I translate the log messages from spanish to english):
FMC38009E Error API MQSeries Workflow :
API Return code : 106
Error origin : FmcSession.java:405
Error message : FMC00106E Not connected
We have a fmcrc file in our WEB-INF/classes folder of our web application that looks like the following:
Configuration/DefaultConfigurationID=FMC
Configuration/FMC/FMLConnectName=FMC.FMCGRP.FMCSYS,FMCQM
Configuration/FMC/MQCommunicationAddress=s1128s51
Configuration/FMC/MQPort=5010
Configuration/FMC/MQQueueManager=FMCQM
Configuration/FMC/MQConnectionType=MQClient
Configuration/FMC/SystemGroup=FMCGRP
Can anyone help with the problem? We have no idea why this is happening, apparently the configuration is correct.
Thx |
|
| Back to top |
|
 |
| hos |
| Posted: Fri Jan 13, 2006 12:10 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
I would say your logon4() call failed. Are you successful with logon2()?
If yes check your implementation of the authentication exit. |
|
| Back to top |
|
|
| Thérèse |
| Posted: Fri Jan 13, 2006 12:17 am Post subject: |
|
|
Newbie
Joined: 12 Jan 2006
Posts: 3
|
Yes, certainly logon4 failed.
The implementation for the authentication exit must be ok because we have been using it from other systems.
The difference with those web application that worked with the same auth. exit was that MQ Workflow was actually installed in the same box as the application server running the webapps, so no use of the fmcrc file was needed. |
|
| Back to top |
|
|
| Thérèse |
| Posted: Fri Jan 13, 2006 3:07 am Post subject: |
|
|
Newbie
Joined: 12 Jan 2006
Posts: 3
|
Well, we found what the problem was: apparently the mq installation in the application server machine corresponded to an old version without fixes and the classpath jar files for mq and jms needed to be the newer ones for everything to work OK.
Copying the correct jar files and changing the classpath solved the problem. |
|
| 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
|
|
|
|
