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 » What's new in MQWF 3.4

Post new topic  Reply to topic
 What's new in MQWF 3.4 « View previous topic :: View next topic » 
Author Message
vennela
PostPosted: Fri May 02, 2003 11:27 am    Post subject: What's new in MQWF 3.4 Reply with quote

Jedi Knight

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

If you notice anything different in MQWF 3.4 from the older versions please post them here.

-------
Venny
Back to top
View user's profile Send private message Send e-mail Visit poster's website
leongor
PostPosted: Sun May 04, 2003 12:08 am    Post subject: Reply with quote

Master

Joined: 13 May 2002
Posts: 264
Location: Israel

Changes to MQ Workflow Version 3.4 are:

v LDAP support has been added to MQ Workflow.
v The execution service exposes new API calls that allow an administrator to close the PEA or active sessions of the specified user.
v The process instance exposes a new API call to change the process administrator.
v Global container members can be compared with the currently logged-on user.
v Compilers supported in terms of MQ Workflow maintenance are updated.
v Support for Windows 98 and ME is removed.
v Support for Windows XP Professional is added.
v A description has been added that shows how to customize the Web Client.
v FlowMark Version 2 compatibility mode is no longer supported.
v The COS, OSA, RMI, and IOR policies in the Java API are no longer supported. Supported are the LOC and JNDI locator policies.
v Support for configuring the Web client and Java agents using the MQ Workflow Configuration Utility. These tasks no longer require fmczutil.
_________________
Regards.
Leonid.

IBM Certified MQSeries Specialist.
Back to top
View user's profile Send private message
sshaker
PostPosted: Mon May 05, 2003 6:08 am    Post subject: Reply with quote

Disciple

Joined: 20 Sep 2002
Posts: 185

One obvious thing is WAS5 support... we are running wf3.4 on was5 with ease.. i found one curious thing when i complete tasks without entering any data in the data structure field the tasks are not removed automatically on completion. instead i am forced to delete them manually, but when i enter data during testing and complete the task the task is removed from the client. the same applies for the process instance. i can even restart the process instance. when i complete a process with with data the activities and the process instance are completed. anybody elese encountered this?

regards
shaker
_________________
shaker
Back to top
View user's profile Send private message
vennela
PostPosted: Tue May 06, 2003 9:09 am    Post subject: Reply with quote

Jedi Knight

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

These are a few that I observed:
1. When a standard client is invoked, PEA doesn't start in foreground or in another command window anymore.
2. The Web-clients default port is not 9081 anymore (on WAS5). It is 9080.
3. There are a few more jar files added (like xerces xml parsers)
4. Some portal client stuff (haven't done anything on this yet to know what it does)

Though they are significant, I am paranoid enough to wonder 'why pea doesn't show up when standard client is started'

-------
Venny
Back to top
View user's profile Send private message Send e-mail Visit poster's website
jmac
PostPosted: Tue May 06, 2003 10:03 am    Post subject: Reply with quote

Jedi Knight

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

Vennela:

I have wanted the PEA to be a hidden window since the beginning of MQWF.

These days we don't have too many fat client implementations, but when we did, there was always the training issue of getting the user to NOT shut down their pea.

I think this was a good change, although its a little late now.
_________________
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
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 » What's new in MQWF 3.4
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.