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 » - FMC00013E Communication error

Post new topic  Reply to topic
 - FMC00013E Communication error « View previous topic :: View next topic » 
Author Message
zaklum
PostPosted: Thu Dec 01, 2005 1:02 pm    Post subject: - FMC00013E Communication error Reply with quote

Voyager

Joined: 17 Mar 2005
Posts: 96
Location: Boca Raton

Here is the setup

2 MQ Workflow servers:
WFS1 - config details below:
Configuration/FMC/FMLConnectName=FMC.FMCGRP.FMCSYS,FMCQM


WFS2- config details below:
Configuration/FMC2/FMLConnectName=FMC.FMCGRP.FMCSYS2,FMCQM2

******************************************************
1 MQ Workflow client:
WFC1 - config details below:
Configuration/FMC/FMLConnectName=FMC.FMCGRP.DUMMY,PORTAL44


**********************************************************

My understanding is that the only diffence on the Configuration/FMC/FMLConnectName between WFS1 and WFS2 should be the system (FMCSYS, FMCSYS2) name and the configuration id (FMC, FMC2) which i've done.
Also, for the client to load balance the servers we must specify a different system name on the Configuration/FMC/FMLConnectName. If you notice I put "DUMMY" for this.

OS - AIX 5.2 on all boxes
MQ Workflow version - 3.5.0.4
MQSeries version - 5.3.10

each system is on a different box.

Please explain why am I getting the following error when trying to connect to the workflow servers from the workflow client:




/home/fmc #> fmcautil -yFMC -uADMIN -ppassword
- FMC16006I Administration Utility started.
System group name : [FMCGRP] FMCGRP
System name : [DUMMY] DUMMY
Userid : [ADMIN] ADMIN
Password : [********] ********
- FMC00013E Communication error - Failing Action: open, Reason Code: 2085, Failing Object: FMC.FMCGRP.DUMMY.ADM.
- FMC16302I Not connected to any system.
FMC15010I Main Menu:
s ... System Commands Menu
Back to top
View user's profile Send private message
vennela
PostPosted: Thu Dec 01, 2005 1:37 pm    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Quote:
Also, for the client to load balance the servers we must specify a different system name on the Configuration/FMC/FMLConnectName. If you notice I put "DUMMY" for this.

Where did you get this information from?
I don't think that is correct
Back to top
View user's profile Send private message Send e-mail Visit poster's website
zaklum
PostPosted: Thu Dec 01, 2005 2:43 pm    Post subject: Reply with quote

Voyager

Joined: 17 Mar 2005
Posts: 96
Location: Boca Raton

ok, I took away the "DUMMY" and it works for each system that we are specifying. Here is the new setup:

2 MQ Workflow servers:
WFS1 - config details below:
Configuration/FMC/FMLConnectName=FMC.FMCGRP.FMCSYS,FMCQM


WFS2- config details below:
Configuration/FMC2/FMLConnectName=FMC.FMCGRP.FMCSYS2,FMCQM2

******************************************************
1 MQ Workflow client:
WFC1 - config details below:
Configuration/FMC/FMLConnectName=FMC.FMCGRP.FMCSYS,PORTAL44
Configuration/FMC2/FMLConnectName=FMC.FMCGRP.FMCSYS2,PORTAL44


**********************************************************

My understanding is that the only diffence on the Configuration/FMC/FMLConnectName between WFS1 and WFS2 should be the system name, which i've done (FMCSYS, FMCSYS2) and the configuration id which i've done (FMC, FMC2).

For the client we now have 2 config ID FMC and FMC2. This correspond to each of the Workflow Servers.


Now the issue is the following:

when running the fmcautil, we have to specify the config id in which to connect. In other words, we can't randomly connect to any workflow server.

If we don't specify the config ID "FMC" or "FMC2" we are able to connect to the default "FMC".

If we shut down the default "FMC" and run the fmcautil, then we're not able to establish connection to any system.
Back to top
View user's profile Send private message
vennela
PostPosted: Thu Dec 01, 2005 6:10 pm    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Your answer is below:
http://www.mqseries.net/phpBB2/viewtopic.php?t=18564&highlight=admin+server+fmcautil

Just shutting down the workflow server will not stop MQ from sending the messages to the workflow server QMGR and that is the reason your attempt fails.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
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 » - FMC00013E Communication error
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.