TIBCO's TIB/IntegrationManager1.0. Great built-in UML editor - let's one
define message and process flow diagram using UML. Also, one can define the
whole messaging data model using the UML editor. Supports EJB, Corba, etc.

-----Original Message-----
From: Zerbe John W [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 12, 2000 1:53 PM
To: [EMAIL PROTECTED]
Subject: Re: Workflow products


MQ Workflow is the latest name for their old Flowmark (not sure of spelling)
product. It's a workflow engine that uses MQSeries as the transport layer.

John Zerbe - Mellon Bank
Information Technology Solutions - Middleware Team
Phone:  412-234-1048   E-Mail:[EMAIL PROTECTED]


> -----Original Message-----
> From: David Regan [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, May 12, 2000 1:16 PM
> To:   [EMAIL PROTECTED]
> Subject:      Re: Workflow products
>
> Er..is this something new? MQSeries (the part I worked with in the past)
> is just a messaging system with  multi-platform support, noteably a lot
> of mainframe/mini support. I wasn't aware of workflow support in
> Forte either. I guess all of this stuff really depends on your definition
> of what workflow means.
>
> -David
>
>  -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Javier Borrajo
> Sent: Friday, May 12, 2000 4:20 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Workflow products
>
>
>
>       We are begining to use Sun Fort� as the workflow development&runtime
> component
>       for a Java application. We used Staffware in the past but were not
> happy with it
>       since for instance you needed an special applet to build the UI.
>
>       Another interesting tool you may want to check is IBM MQSeries
> Workflow.
>
>       + Fort� supports an IIOP Gateway and we plan to use this to
> communicate the
>       workflow engine and the Java applicaction logic. The IBM tool also
> supports IIOP.
>       + Both support an XML interface for activity automation.
>       + IBM has more sophisticated exception modeling features.
>       + IBM uses MQSeries while Forte will use JMQ in a future release, it
> now uses HTTP
>       which is nice but not reliable enough.
>       + Forte is database neutral while IBM requires DB2 for workflow
> data, though you
>       may use any other database for applicaction data.
>
>       Best regards
>
>           Javier Borrajo
>           www.tid.es <http://www.tid.es>
>
>               -----Original Message-----
>               From: Randy Stafford < [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>
>               To: [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]> < [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>>
>               Date: viernes 12 de mayo de 2000 0:08
>               Subject: Re: Workflow products
>
>
>               Proneel-
>
>               GemStone/J integrates Verve in the Commerce Automation
> edition (in fact,
>               Verve stores its data in GemStone).  Thus we offer the
> workflow/J2EE
>               integration you mention - see <http://www.gemstone.com> for
> more info.
>
>               Best Regards,
>               Randy
>
>               > -----Original Message-----
>               > From: Proneel Guptan [ SMTP:[EMAIL PROTECTED]
> <mailto:SMTP:[EMAIL PROTECTED]>]
>               > Sent: Thursday, May 11, 2000 12:05 PM
>               > To:   [EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>
>               > Subject:      Workflow products
>               >
>               > Hi,
>               >
>               > We are looking to use workflow technologies to manage long
> running
>               > business processes. However, a significant portion of our
> application
>               > would still run in an EJB/JMS environment; we expect that
> workflow
>               > activities would call into our session beans as part of
> the processing
>               > of tasks and our beans would also call into the workflow
> to complete
>               > or release tasks in a specific business process.
>               >
>               > The main criteria for us is (as expected) scalability and
> performance.
>               > We would naturally be interested only in Java based
> workflow engines
>               > preferably with a strong integration into EJB or JMS
> technologies.
>               >
>               > We are in the process of evaluating 2 products, Verve and
> jFlow
>               > (a company that BEA recently purchased).
>               >
>               > We would be very interested to know of other java based
> workflow
>               > products; we would like to hear from vendors and from
> users too,
>               > if possible. Any user experiences on Verve and jFlow would
> also
>               > be greatly appreciated.
>               >
>               > Thanks!
>               > Proneel.
>
>

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to