Author |
Message
|
DragonFist |
Posted: Tue Feb 10, 2004 8:17 am Post subject: workflow session |
|
|
 Acolyte
Joined: 11 Nov 2003 Posts: 52
|
Hello all
we have an ejb application that establishes a connection with appserver. when ever a user logs on and establishes a connection with appserver, he should be able to establish connection with workflow server too, so that he can check his workitems. My question is how to establish the connection with workflow in sync with appserver. Any pointers on this would be appreciated.
thx in advance _________________ DragonFist |
|
Back to top |
|
 |
satboppana |
Posted: Tue Feb 10, 2004 9:34 am Post subject: |
|
|
Acolyte
Joined: 20 Dec 2001 Posts: 64
|
I havent looked at the session management of workflow which was introduced recently. But i think you should be able to store the session id for the user and go from there.
We have implemented using java threads.
WE keep the user thread alive after he has logged in for that day.
The threads are recycled by the end of the day. _________________ Sb |
|
Back to top |
|
 |
kriersd |
Posted: Tue Feb 10, 2004 11:50 am Post subject: |
|
|
 Master
Joined: 22 Jul 2002 Posts: 209 Location: IA, USA
|
DraggonFist
Just a word of CAUTIOIN! I have NEVER had good luck with EJB's and the Workflow API set. Due to an issue with sharring the connection in the underlying Workflow C code, you will need to run your EJB in a isolated appserver. When I tried to do this I could not put the EJB within the same appserver as my web client because only one object can have a connection to workflow at a given time. Once you logon (Agent.setconfig) in either the EJB or the Webclient the other component CAN NOT logon.
I ended up having to build a new appserver for the sole purpose of housing my EJB. YUCK... In the long run your better off not even waisting your time with an EJB.
Just my 0.02
If anyone has gotten this to actually work I would love to hear about it.
dk _________________ Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
Back to top |
|
 |
DragonFist |
Posted: Wed Feb 18, 2004 9:41 am Post subject: |
|
|
 Acolyte
Joined: 11 Nov 2003 Posts: 52
|
My Scenario is like this. When ever a user logs in, he will call an EJB and in turn EJB should call workflow to access workitems. Between EJB and workflow should there be a session established to access workitems ( i think yes) or is it possible to query work items without establishing a session with workflow for that particular user. If a session has to be established must and should, then how to do it in sync with workflow. I read somewhere that Authentication exit can be used for that. Does anybody know how to do it. Also it might just create a lot of network traffic becos of the no of users trying to access workflow at a time. This thing is just eating my head. Any help would be appreciated...
thanx _________________ DragonFist |
|
Back to top |
|
 |
Ratan |
Posted: Wed Feb 18, 2004 11:09 am Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
when the user logs in to you app server, log him on to Workflow and pass the sessionID and UserID to your EJB. You will be able to establish the session with Workflow with this Info and query for Workitems. _________________ -Ratan |
|
Back to top |
|
 |
DragonFist |
Posted: Wed Feb 18, 2004 11:23 am Post subject: |
|
|
 Acolyte
Joined: 11 Nov 2003 Posts: 52
|
Ok that means when a user logs on to appserver, then i should passon the userid and password for that user to login into workflow again. this would create a lot of network traffic. Instead of this, is there a centralized mechanism , like once the user longs into the appserver, it should also establish the connection with workflow, instead of again establishing a connection with workflow separately. Hope I am clear. _________________ DragonFist |
|
Back to top |
|
 |
vennela |
Posted: Wed Feb 18, 2004 12:22 pm Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Quote: |
Instead of this, is there a centralized mechanism , like once the user longs into the appserver, it should also establish the connection with workflow, instead of again establishing a connection with workflow separately. |
NO |
|
Back to top |
|
 |
|