best grammar app

Understanding Savvion Session Objects and Types

Submitted by Abhishek on Wed, 2011-09-07 18:34

Savvion Business Manager architecture being multi tiered allows for a number of sessions. Often developers get confused which session errors. This article aims to explain the different sessions and the role they play in overall workflow orchestration.


Essentially three kinds of sessions work together in Savvion. They are explained below but before that a word of caution. Each of these sessions have a timeout.  Progress has optimized the timeouts for best performance and least not of timeout errors while you are using it. If you are changing these make sure you match all three otherwise you could end up with a lot of errors


HTTP Session

HTTP session is the standard web session that you use. This is what the java guys call “Session” in their JSP pages. It can keep track of who is logged into the portal. When you logout this session is destroyed. Things normally stored in this are  who is logged in, which process you are currently using and so on. Certain Implicit Savvion objects depending on page could also be stored in this.


If you want to change the session timeout you will need to check the Web server specific c files.


BizSite Session

This is the Session on page which you use to fetch process related data. If you are using BizSite/BPMPortal API you would need to create a BizSite Session before you can access the available templates/task. BizSIte API has huge list of method calls which are very useful.


The newer versions of Savvion have BPMportal instead of BizSite. This applies to the BPM Portal session.


BizLogic Session

This is the backend session of workflow engine. Whenever you are connecting with BizLogic API or web services then this is the only session you deal with. When you log in to the BPM portal, the BizSite API’s take care of setting up this session for you.


The session timeout can be changed from Bizlogic.conf file in your Savvion home.


A Word on Session beans

Session Beans (EJB) are used to manage the access to the workflow engine. Sometimes if you are using a large volume of data processing you might need to tweek it a bit. This means the number of beans in the pool and their timeout.


Once again, unless it is absolutely do not modify these settings. Your users might crib about increasing the session timeout because they don’t want to see the login box but do explain to them that lower the session timeout healthier the server would be.

Questions are welcome

Abhishek Mishra
Good experience in working with BPM technologies like Savvion, JBPM. Founder and Chief Editor of Founder of Savvion Business Manager Mobility Framework Savmobify| View my BPMGeek Profile
best grammar app

About BPMGeek

BPMGeek is an initiative to collaborate and communicate with the growing Business process management community out there. The goal is to help developers connect with experts, ask questions, post their learning and get understanding of BPM Concepts. Often tool specific knowledge of niche areas end up developers perplexed and confused - especially when there are very less number of resources available. We will be coming up several several new features. Have a look at our Roadmap here

BPMGeek is an independent entity not associated with any Product. All BPM product professionals are invited to contribute. The Logos and Names used across the site belong to their respective owners. The viewpoints mentioned by Individual contributors are their own. BPMgeek cannot be held liable for any issues arising out of it.

BPMgeek is promoting the Nounshoun English Grammar App - developed by Constellation Software.