ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » WebClient and Reason Code: 2103

Post new topic  Reply to topic
 WebClient and Reason Code: 2103 « View previous topic :: View next topic » 
Author Message
ramires
PostPosted: Wed Jun 29, 2005 5:36 pm    Post subject: WebClient and Reason Code: 2103 Reply with quote

Knight

Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa

Hello,
I'm configuring WebClient to access two diferent systems. In one machine "server macinhe" I have to WF servers and the names are:
.
SysGrp-- System-- QueueMgr Prefix--
FMCGRP WFMC111A QM111A FMC
FMCGRP WFMC222A QM222A FMC
.
In my "client machine", where WAS is, I create two WebClient configurations, and then I add to one of this created configurations the connect names of the other, in the end I have under "Connect Name Commands Menu" this
.
SysGrp-- System-- QueueMgr Prefix--
FMCGRP WFMC111A WQM111A FMC
FMCGRP WFMC222A WQM222A FMC
.
Then I create the ear file and deploy it within WAS. Next I edit Logon.jsp and uncomment the lines regarding "System".
Go to logon page and it works ok for the first system I logon. When I try the second I receive the 2103 meaning MQRC_ANOTHER_Q_MGR_CONNECTED.
.
Is there a bypass to this ? Maybe create a third qmgr belonging to the two MQ clusters. ?

Thanks!
Joao Ramires
Back to top
View user's profile Send private message
hos
PostPosted: Thu Jun 30, 2005 12:30 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

Joao,

you should try to setup you scenario with the native Java API. I do not say that it is an easy task but it overcomes such problems and it is well suited for future requirements.

With MQWF 3.5 and WA0C you need to run two WebClients with different configurationIDs, one for each system. With MQWF 3.6 and built-in NJAPI you can have a single WebClient that supports multiple configurationIDs.

Note that the native Java API does NOT support multiple connectNames in a single configuration. Therefore you'll need multiple configurationIDs.

Good luck.
Back to top
View user's profile Send private message
ramires
PostPosted: Thu Jun 30, 2005 2:07 am    Post subject: Reply with quote

Knight

Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa

Thanks hos,

Meanwhile I found solution! Having a MQ cluster shared by 3 qmgrs. The ones belonging to WF configurations and one belonging to WebClient. I'm not sure of the implications having 2 wf groups sharing the same MQ cluster. This is what I have now in Webclient machine

FMC.GRP777.WFMC777,MQ7788
FMC.GRP888.WFMC888,MQ7788

1st WF configuration has:
FMC.GRP777.WFMC777,QM777

2nd WF configuration has:
FMC.GRP888.WFMC888,QM888

QM888 QM777 and MQ7788 are queue managers in a MQ cluster BIG777

From the logon page I can chose GRP888 ot GRP777 and connect to the rigth WF server.

But I'll follow your suggestion and I'll try the NJAPI.
Regards,
ramires
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » WebClient and Reason Code: 2103
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.