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 » prob trying to access MQ Workflow server using portal client

Post new topic  Reply to topic Goto page 1, 2  Next
 prob trying to access MQ Workflow server using portal client « View previous topic :: View next topic » 
Author Message
zaklum
PostPosted: Mon May 02, 2005 11:10 am    Post subject: prob trying to access MQ Workflow server using portal client Reply with quote

Voyager

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

when trying to access workflow with portal client


2005-05-02 18:34:35.03 Servlet.Engine.Transports : 1: userID: WFADMIN
2005-05-02 18:34:35.03 Servlet.Engine.Transports : 1: mode: null
2005-05-02 18:34:35.03 Servlet.Engine.Transports : 1: Locating system '' in group ''.
2005-05-02 18:34:35.04 Servlet.Engine.Transports : 1: MQWFWorkflowCommunication conductLogon: Logging on
2005-05-02 18:34:35.20 Servlet.Engine.Transports : 1: BAD CONDITION while establishing the logon status
com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : /projects/fmc/drv2/lbld/v350/aix/src/fmcjcesv.cxx, line 2450
Error Message : FMC00013E Communication error - Failing Action: Connect_to_QM, Reason Code: 2058, Failing Object: FMCQM.
Nested Exception : None

I've changed access permission on MQWFCHL.TAB (on workflow server) and that is fine:

could someone please tell me where does this username "WFADMIN" which is complaining about shall exist? on the workflow server? on the database server?

please help.
Back to top
View user's profile Send private message
vennela
PostPosted: Mon May 02, 2005 11:56 am    Post subject: Reply with quote

Jedi Knight

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

Quote:
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : /projects/fmc/drv2/lbld/v350/aix/src/fmcjcesv.cxx, line 2450
Error Message : FMC00013E Communication error - Failing Action: Connect_to_QM, Reason Code: 2058, Failing Object: FMCQM.
Nested Exception : None

The problem is not with the userid. The problem is with MQ and communication. Tell us your setup? 2-tier, 3-tier etc.

Where is the portal server running on? Where is workflow server running on etc.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
zaklum
PostPosted: Mon May 02, 2005 12:09 pm    Post subject: Reply with quote

Voyager

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

Vennela,
As usual, thanks for taking the time to answer my questions:

I'm in a three -tier setup.

server1 --> portal server; MQ server/client; MQ Workflow client

server2 --> MQ Workflow Server; MQ Server

server3 --> Oracle DB


I'm trying to communicate from server1 to server2
Back to top
View user's profile Send private message
vennela
PostPosted: Mon May 02, 2005 12:12 pm    Post subject: Reply with quote

Jedi Knight

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

I also need the QMGR names on server1 and server2.
Also on server1 and server2 issue under runmqsc
runmqsc <QMGRNAME>

dis clusqmgr(*)

What is the output. Are the clussdr and clusrcvr channels running on both ends.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Ratan
PostPosted: Mon May 02, 2005 12:19 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

From your portal server try to connect to WF Server using fmcautil. If that is succesfull you dont have a problem with communication.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
zaklum
PostPosted: Mon May 02, 2005 12:35 pm    Post subject: Reply with quote

Voyager

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

server1:/home/fmc #> runmqsc FMCQM
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager FMCQM.


dis clusqmgr(*)
1 : dis clusqmgr(*)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCQM) CLUSTER(FMCGRP)
CHANNEL(TO.FMCQM.TCP)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCQM25) CLUSTER(FMCGRP)
CHANNEL(TO.FMCQM25.TCP)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCQM26) CLUSTER(FMCGRP)
CHANNEL(TO.FMCQM26.TCP)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(FMCQM29) CLUSTER(FMCGRP)
CHANNEL(TO.FMCQM29.TCP)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(PORTAL) CLUSTER(FMCGRP)
CHANNEL(TO.PORTAL)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(QUILLIX) CLUSTER(FMCGRP)
CHANNEL(SSOWF.QUILLIX)
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(SSOWF) CLUSTER(FMCGRP)
CHANNEL(TO.SSOWF)




server2:/var/fmc #> runmqsc FMCQM
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager FMCQM.


AMQ8118: WebSphere MQ queue manager does not exist.

No MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
mqm@wt00005:/var/fmc #> dspmq
QMNAME(WAS_COEXIST) STATUS(Ended normally)
QMNAME(TEST_QUEUEMNG) STATUS(Running)
QMNAME(PORTAL) STATUS(Ended immediately)
QMNAME(PORTAL2) STATUS(Quiescing)
QMNAME(SSOWF) STATUS(Running)
Back to top
View user's profile Send private message
vennela
PostPosted: Mon May 02, 2005 12:38 pm    Post subject: Reply with quote

Jedi Knight

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

On server2:

Start the QMGR.
Code:

strmqm PORTAL


The as fmc, issue fmcautil and try to login to workflow server and see if you can login. If you can, then you should be able to login to portal client. But based on your setting, I am guessing fmcautil will also fail because your connect names might be wrong.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
zaklum
PostPosted: Mon May 02, 2005 12:39 pm    Post subject: Reply with quote

Voyager

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

Ratan,
Where do you specify ther servername in which you're trying to
connect to?
fmcauti -u username -ppassword; what about servername? how does it know to which server to go to?
server1:/var/fmc #> fmcautil -?
Usage: fmcautil [-option [argument] ... ]

The following options are valid:

-y string configuration identifier
-g string system group name
-s string system name
-u string userid
-p string password
-f force here
-r [string] record file
-b [string] playback file
-l [string] log file
-k keep
Back to top
View user's profile Send private message
zaklum
PostPosted: Mon May 02, 2005 12:53 pm    Post subject: Reply with quote

Voyager

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

where do you specify there Workflow server when using the fmcautil

portalserver:/var/fmc #> fmcautil -y FMC -uWFADMIN -ppassword
- FMC16006I Administration Utility started.
System group name : [FMCGRP] FMCGRP
System name : [FMCSYS] FMCSYS
Userid : [WFADMIN] WFADMIN
Password : [********] ********
- FMC00013E Communication error - Failing Action: Connect_to_QM, Reason Code: 2058, Failing Object: FMCQM.
- FMC16302I Not connected to any system.
FMC15010I Main Menu:
s ... System Commands Menu
x ... Exit Main Menu
Back to top
View user's profile Send private message
Ratan
PostPosted: Mon May 02, 2005 1:01 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

you do not specify the server name with fmcautil. you specify the configuration ID using the '-y' option.

The server connect names should be specified when you do the configuration.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
Ratan
PostPosted: Mon May 02, 2005 1:05 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

how did you configure the WF Client on your portal server. If you have the settings, post them.


Is the QM on your Portal Server shared in the cluster of WF Server QM?
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
zaklum
PostPosted: Mon May 02, 2005 1:07 pm    Post subject: Reply with quote

Voyager

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

well, there you go. I couldn't establish any connection from the portal box on AIX
Back to top
View user's profile Send private message
vennela
PostPosted: Mon May 02, 2005 1:38 pm    Post subject: Reply with quote

Jedi Knight

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

The connect names are wrong.
Issue fmczutil and select the configuration, then
Code:

s
     Configuration identifier : [FMC] FMC
   FMC33202I Selected Configuration Commands Menu:
             Selected configuration : FMC (Default configuration)
     c ... Configuration Settings Menu
     r ... Runtime Database Commands Menu
     q ... Queue Manager Commands Menu
     x ... Exit Selected Configuration Commands Menu
c
   FMC33212I Configuration Settings Menu:
             Selected configuration : FMC
     c ... Client Settings Menu
     x ... Exit Configuration Settings Menu
c
   FMC33216I Client Settings Menu:
             Selected configuration : FMC
     c ... Connect Name Commands Menu
     x ... Exit Client Settings Menu
c
   FMC33229I Connect Name Commands Menu:
             Selected configuration : FMC
     l ... List
     s ... Select
     a ... Add
     x ... Exit Connect Name Commands Menu
l
   SysGrp-- System-- QueueMgr Prefix--
-  FMCGRP   FMCSYS   FMCQM    FMC     

   FMC33229I Connect Name Commands Menu:
             Selected configuration : FMC
     l ... List
     s ... Select
     a ... Add


The connect names on the portal server box should be

Code:


   SysGrp-- System-- QueueMgr Prefix--
-  FMCGRP   FMCSYS   PORTAL    FMC     
Back to top
View user's profile Send private message Send e-mail Visit poster's website
zaklum
PostPosted: Tue May 03, 2005 4:18 am    Post subject: Reply with quote

Voyager

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

Vennela,
I notice that the only difference that I have is the QUEUE manager. This pointing at a non-existing one on the portal box, but it exist in the workflow box. Isn't this the way it suppose to be? we are trying to connect to workflow server, which contains FMCQM queue manager. The portal box does not contain an FMCQM, but my understanding was that it wasn't necessary, since we are establishing communication with the Workflow queuemanager (FMCQM).

If this is not so, please let me know how to change this FMCQM to PORTAL. Do I need to log in as root and run fmcautil? please help?

Regards,
Back to top
View user's profile Send private message
zaklum
PostPosted: Tue May 03, 2005 5:47 am    Post subject: Reply with quote

Voyager

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

here is what I did to set the queu manager as PORTAL, let me know if it looks good.

wt00005:/root >fmczutil

FMC33899I libfmczdfnc.a(share.o) was not loaded.

FMC33201I Configuration Commands Menu:

l ... List

s ... Select

c ... Create

x ... Exit Configuration Commands Menu

l

- FMC33611I The following configurations are defined:

FMC

- FMC33622W Currently there is no default configuration specified.

FMC33201I Configuration Commands Menu:

l ... List

s ... Select

c ... Create

x ... Exit Configuration Commands Menu

s

Configuration identifier : [FMC] FMC

FMC33201I Configuration Commands Menu:

l ... List

s ... Select

c ... Create

x ... Exit Configuration Commands Menu

c

Configuration identifier : [FMC1] FM^Croot@wt00005:/root >

root@wt00005:/root >fmczutil

FMC33899I libfmczdfnc.a(share.o) was not loaded.

FMC33201I Configuration Commands Menu:

l ... List

s ... Select

c ... Create

x ... Exit Configuration Commands Menu

s

Configuration identifier : [FMC]

FMC33201I Configuration Commands Menu:

l ... List

s ... Select

c ... Create

x ... Exit Configuration Commands Menu

c

Configuration identifier : [FMC1]

Configuration administrator : [fmc]

FMC33210I Select Category Menu:

s ... ( ) Server

i ... ( ) Runtime Database Utilities

c ... ( ) Client with queue manager

j ... ( ) Java Agent

a ... all

n ... none

x ... Exit Select Category Menu

c

FMC33210I Select Category Menu:

s ... ( ) Server

i ... ( ) Runtime Database Utilities

c ... (X) Client with queue manager

j ... ( ) Java Agent

a ... all

n ... none

x ... Exit Select Category Menu

j

FMC33210I Select Category Menu:

s ... ( ) Server

i ... ( ) Runtime Database Utilities

c ... (X) Client with queue manager

j ... (X) Java Agent

a ... all

n ... none

x ... Exit Select Category Menu

x

FMC33593I Configuration of client ...:

FMC33608I Select the Workflow System to connect to ...:

System group name : [FMCGRP1]

System name : [FMCSYS1] FMCSYS

Queue prefix : [FMC]

FMC33591I Configuration of the new queue manager ...:

Queue manager name : [FMCQM1] PORTAL

FMC33513I Select log type ...:

c ... (X) Circular log

l ... ( ) Linear log (prerequisite for backup)

c

- FMC33749I Selected Log type : Circular log

Queue manager log files location (leave empty to use the MQSeries default path) : []

Channel definition table file : [/var/fmc/chltabs/MQWFCHL.TAB]

FMC33044I Specify address information used to connect to this Queue Manager:

TCP/IP address : [wt00005.tyco.net]

TCP/IP port number : [14000]

MQ principal userid to connect to this Queuemanager (PORTAL) : [fmc]

MQ Cluster name : [FMCGRP1] FMCGRP

FMC33537I Select repository type ...:

f ... ( ) 'PORTAL' is the first queue manager in cluster 'FMCGRP'

a ... (X) 'PORTAL' is an additional queue manager in cluster 'FMCGRP'

f

- FMC33749I Selected Repository type : 'PORTAL' is the first queue manager in cluster 'FMCGRP'

FMC33594I Configuration of Java Agent ...:

FMC33509I Select locator policy ...:

l ... (X) Local bindings

j ... ( ) Java Naming and Directory Interface (deprecated)

l

- FMC33749I Selected Locator Policy : Local bindings

JDK/JRE Installation Directory : [/usr/java14/jre]

c ... Create configuration profile for 'FMC1' now

s ... Save input to file

r ... Review/change input

x ... Exit (input for configuration 'FMC1' will be lost)

r

Configuration administrator : [fmc]

FMC33210I Select Category Menu:

s ... ( ) Server

i ... ( ) Runtime Database Utilities

c ... (X) Client with queue manager

j ... (X) Java Agent

a ... all

n ... none

x ... Exit Select Category Menu

x

FMC33593I Configuration of client ...:

FMC33608I Select the Workflow System to connect to ...:

System group name : [FMCGRP1] FMCGRP

System name : [FMCSYS]

- FMC33760I A queue manager has been found that is already configured for WebSphere MQ Workflow. Do you want to use this queue man?

On your machine, the following queue managers are configured for the MQ Workflow system group 'FMCGRP':

FMCQM

- FMC33717I Do you want to reuse one of these queue managers ?

y ... Yes

n ... No

n

Queue manager name : [PORTAL]

Queue prefix : [FMC]

FMC33591I Configuration of the new queue manager ...:

FMC33513I Select log type ...:

c ... (X) Circular log

l ... ( ) Linear log (prerequisite for backup)

c

- FMC33749I Selected Log type : Circular log

Queue manager log files location (leave empty to use the MQSeries default path) : []

Channel definition table file : [/var/fmc/chltabs/MQWFCHL.TAB]

FMC33044I Specify address information used to connect to this Queue Manager:

TCP/IP address : [wt00005.tyco.net]

TCP/IP port number : [14000]

MQ principal userid to connect to this Queuemanager (PORTAL) : [fmc]

MQ Cluster name : [FMCGRP]

FMC33537I Select repository type ...:

f ... (X) 'PORTAL' is the first queue manager in cluster 'FMCGRP'

a ... ( ) 'PORTAL' is an additional queue manager in cluster 'FMCGRP'

f

- FMC33749I Selected Repository type : 'PORTAL' is the first queue manager in cluster 'FMCGRP'

FMC33594I Configuration of Java Agent ...:



FMC33509I Select locator policy ...:

l ... (X) Local bindings

j ... ( ) Java Naming and Directory Interface (deprecated)

l

- FMC33749I Selected Locator Policy : Local bindings



JDK/JRE Installation Directory : [/usr/java14/jre]





c ... Create configuration profile for 'FMC1' now

s ... Save input to file

r ... Review/change input

x ... Exit (input for configuration 'FMC1' will be lost)

s

Enter file name : [fmczkcfg.dat]



FMC33201I Configuration Commands Menu:

l ... List

s ... Select

c ... Create

x ... Exit Configuration Commands Menu

x
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » prob trying to access MQ Workflow server using portal client
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.