|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
problem invoking the process list at run time |
« View previous topic :: View next topic » |
Author |
Message
|
prabhu_chn |
Posted: Sun Jul 11, 2004 7:16 am Post subject: problem invoking the process list at run time |
|
|
Newbie
Joined: 20 May 2004 Posts: 7
|
hello all,
I created a workflow process model on build time. When I tried invoking process list on the runtime , the run time window is not responding.Then, I used this command fzmczrdb -0=b -d=FMCDB for binding with db. I tried invoking it again I got a message 'FMC_API_ALREADY_LOGGED_ON:USER 'ADMIN' is already logon. Iam unable to see the the tree view , again the client windoew is not respoding. Could anyone help me solve this problem..
thanks
prabhu |
|
Back to top |
|
 |
vennela |
Posted: Sun Jul 11, 2004 8:20 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Quote: |
I created a workflow process model on build time. |
Did you export the FDL of the process from buildtime and export it?
Quote: |
When I tried invoking process list on the runtime , the run time window is not responding. |
Do you mean the process template
Quote: |
I used this command fzmczrdb -0=b -d=FMCDB for binding with db. |
You are supposed to do this by shutting down tghe workflow server. It might work leaving the server running but is not the recommended thing.
Quote: |
I tried invoking it again I got a message 'FMC_API_ALREADY_LOGGED_ON:USER 'ADMIN' is already logon |
You can use force option while you logon and it will log you in even if you are aklready logged in.
Try shutting down the workflow server and restarting it again |
|
Back to top |
|
 |
prabhu_chn |
Posted: Sun Jul 11, 2004 11:52 am Post subject: same problem again! |
|
|
Newbie
Joined: 20 May 2004 Posts: 7
|
hi,
thanks for your reply . This is what exactly happening .As you said I created an FDL file using build time and tried importing that file at run time, I got this message code FMC31050E and server was not responding. Then I tried reconfiguring once again . I opened the Websphere MQ Worflow client and gave the user name and password as ADMIN and password , as written in installation manual. Again the window was not resonding..When I checked with fmcsys.log file I got the following message...
-----------------------------
7/11/2004 3:25:11 PM FMC10100I Administration server starting.
7/11/2004 3:25:11 PM FMC10110I Administration server for system FMCSYS started.
7/11/2004 3:27:12 PM FMC12290E The execution server for system FMCSYS is not responding to control requests.
could u help me solving this please.
thanks
prabhu |
|
Back to top |
|
 |
jmac |
Posted: Sun Jul 11, 2004 3:29 pm Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Check to make sure your trigger monitor is running. Also we will be better able to help if you tell us what is in the fmcsys.log (I think you showed us this), the fmcerror.log, the db2diag.log, and the Mq series error log. _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
amittalekar |
Posted: Mon Jul 12, 2004 5:24 am Post subject: |
|
|
 Disciple
Joined: 03 Apr 2002 Posts: 166 Location: VA, USA
|
On your windows WF server check following
1)Go to MQServices console. Go to listener properties, go to 'parameters' tab and verify whether port number & protocol are defined there. If not then do it manually
2) Go to the triggerMonitor properties. then go to parameters tab and verify whether queuename is 'FMCTRIGGER'.
I observed that 3.4 WF configuration on windows do not do these settings. you need to manually do that. Then start all and try. |
|
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
|
|
|
|