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 » J2EE/EJBs and MQWF 3.6?

Post new topic  Reply to topic
 J2EE/EJBs and MQWF 3.6? « View previous topic :: View next topic » 
Author Message
GNaschenweng
PostPosted: Fri Mar 10, 2006 6:20 am    Post subject: J2EE/EJBs and MQWF 3.6? Reply with quote

Newbie

Joined: 10 Mar 2006
Posts: 1

Hi all,

We are kicking off a project, where we would like to use EJBs (a SessionFacade) as a service to communicate with workflow. When reading through the EJB example in WA03 I have a few questions:

- What is the purpose of carrying the session-id back and forth (i.e. between Application Server and presentation tier)? Isn't the OID sufficient or does the session-id provide any caching?
- Once the EJB has instantiated an Agent and retrieved a session-id via the ExecutionService (through logon2), will a connection to WF ever time out and how is this managed?
- Using a stateless-session bean, are there any limitations to number of connections to WF? i.e. the J2EE-container will start as many SLSB as required - doesn't this create a potential problem by running out of WF-connections on the server?
- How does clustering/work-load management work? i.e. if a portlet gets a session-id from a business-service in a clustered Websphere environment, and WLM delegates subsequent calls to another WAS-instance (not the same where the session-id was created before) - how is this non-session-affinity managed between client/server?
- How is transactional support management? The pure-Java APIs do not really provide XA-connectors to support 2-phase commits. So the only option would be for the SLSB to participate in a user-defined transaction.
- As part of the MQWF Java APIs I am missing features such as a J2C/JCA connector in order to reap the J2EE container benefits (transaction support, resource management, security etc) and it would have been nice to do a JNDI lookup to a MQWF-factory providing this functionality (similar
to a QueueConnectionFactory for MQ or a datasource for databases).

Has anyone got practical experience on how to do this according to best-practice? IBMs documentation is not very specific for custom J2EE applications?

I believe XML-messages are out of the question, since from the Programming Manual I gather that XML-messages are not supported for WorkItem/WorkList functionality, but only for ProcessInstance interaction.
_________________
Gerd W. contact admin
Architect, Vodacom Business Solutions
1st Floor, Corporate Park, Midrand
Email: GerdWolfgang.contact admin@vcontractor.co.za
Cell: +27 83 271 5677, http://gerd.ibscon.com
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 » J2EE/EJBs and MQWF 3.6?
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.