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 » Java Activity Program Implementation requirements

Post new topic  Reply to topic
 Java Activity Program Implementation requirements « View previous topic :: View next topic » 
Author Message
rgucci
PostPosted: Mon Nov 29, 2004 2:37 am    Post subject: Java Activity Program Implementation requirements Reply with quote

Newbie

Joined: 29 Nov 2004
Posts: 3

Is the Runtime Client required to be able to run an Activity Program written in Java? (similar to ActImpl.java)
Back to top
View user's profile Send private message
jmac
PostPosted: Mon Nov 29, 2004 5:04 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

Assuming that you are talking about the Fat client the answer is yes, but it is somewhat rare these days to use the fat client. You need to give a little more information about what you are trying to do
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
rgucci
PostPosted: Mon Nov 29, 2004 8:34 pm    Post subject: Reply with quote

Newbie

Joined: 29 Nov 2004
Posts: 3

I am asking the question because I have two MQWF servers running on windows NT. In one, everything works fine. I have an FDL with an automatic activity1 that invokes an activity program written in Java. Everything works fine. I can do the usual check-outs and check-ins, and when the flow gets to the automatic activity1, the java program is executed in the MQ server machine.

Now when we deploy the same FDL to another MQ workflow server running on the same configuration, the automatic activity1 is shown as running, but the java program never gets executed. I have checked the command line and classpath and working directory to be correct. The only difference between the two MQ workflow servers is that in the first one, the Runtime Client is checked (as viewed from the configuration program). In the second server, the Runtime Client option is not checked.
Back to top
View user's profile Send private message
rgucci
PostPosted: Mon Nov 29, 2004 8:36 pm    Post subject: Reply with quote

Newbie

Joined: 29 Nov 2004
Posts: 3

By the way, we are not using the Runtime Client (windows fat client) to check out/check in work items. We are using the web client, plus a custom client running on remote machines calling the Java API.
Back to top
View user's profile Send private message
jmac
PostPosted: Tue Nov 30, 2004 4:49 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

Are you sure that the activity is in a running state? If it is truly automatic, and it is not A UPES activity then I would suspect it would be in the InError state.

One thing to check, is java in your path on the 2nd configuration?
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
hos
PostPosted: Tue Nov 30, 2004 7:54 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

Hi,
you are on the right track with your first append. In order to invoke a program implementation activity you need a Program Execution Agent. The Standard Runtime Client automatically starts a PEA for the same UserID (and stops it when the client terminates). Without a PEA started for the UserID that 'owns' the automatic activity the activity remains in state 'RUNNING' until a PEA is started.

You can start and stop a PEA without the Standard Runtime Client by using the fmcxspea and fmcxpeasd utilities. However using a PEA is not recommended in a production environment. Use an UPES activity instead and write your own UPES implementation.
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 » Java Activity Program Implementation requirements
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.