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 » Sessions Management

Post new topic  Reply to topic
 Sessions Management « View previous topic :: View next topic » 
Author Message
pedmartins
PostPosted: Tue Mar 21, 2006 3:11 pm    Post subject: Sessions Management Reply with quote

Newbie

Joined: 29 Apr 2005
Posts: 5
I have this situation for my next question about Sessions Management in MQWF:

Our client has an arquitecture wich is:

- a presentation platform that connects to

- front-end (Windows platform) farm composed by several Websphere Application Servers, hosts MQ Workflow API client stateless webservices - connects via MQ Series (server - server connection) to

- back-end (Windows platform) cluster that holds MQ Workflow system plus DB2.

We want to improve performance in logon and we are considering session reuse by caching sessionid in presentation platform.

The front-end platform machines have no affinity with the users who perform the requests. Services are selected for each request by round-robin method.

The sessions in workflow should be "present".

We are using MQWF Java Native API in front-end -> back-end interactions.

The questions:

- is this the best / only scenario to enhance performance in logon, since we have many concurrent threads "attacking" administration server?

- since front-end has no affinity with end-users and I know that setSessionContext() doesn't need administration server online to perform, where does the API caches sessionids and objectids?

- are there any additional issues to take care in this scenario?

Thanks.
_________________
Best regards,

Pedro Martins
Back to top
View user's profile Send private message Send e-mail
hos
PostPosted: Wed Mar 22, 2006 3:53 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470
Hi,

pooling of MQWF sessions in the front-end seems to be a reasonable approach. You must take care that sessions are not used concurrently, i.e. your session provider must be synchronized. I do not understand why you want to use 'Present' session mode, as your users do not have an affinity to the session. I would suggest 'Default'.

MQWF sessions are alive until Logoff() is called or until the session_expiration_time (server setting) is reached.
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 » Sessions Management
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.