setting release time of web component server 1

[jpicks]

I read a thread (149-488986) a while back about changing the session timeout of the Crystal Web Component Server in order to prevent licenses from being used up for 20 minutes every time a report is viewed. The thread referred me to a knowledge base article at crystal

http://support.crystaldecisions.com/library/kbase/articles/c2012077.asp

I followed the suggestions and changed the default timeout from 20 minutes to 5 minutes. I changed the setting back to the default setting and now I get locked out the second time that I try to access a report. Has anyone else ran inot this?

Now I've gone from trying to figure out how far I can stretch the five user licenses that we have to only being able to use one of the five licenses at a time.

Any ideas or suggestions?

 

[SurfingGecko]

Make sure that the "Minutes Before Idle..." settings in the Page and Cache Servers are the same. 20 minutes is good for this.

Also make sure you add the command line switch -DefaultSessionTimeout X for the WCS in the Configuration Manager.

Do not set this too low or you will be doing yourself a disservice. 5 licenses should be able to support about 20 users.

cheers,

SurfingGecko
SurfingGeckoSoftware.com

 

[jpicks]

Thanks for the reply. After a reboot, everything worked fine. I'll check that the settings are the same.

I set the DefaultSession Timeout to 5 minutes. Does this seem like a reasonable amount of time?

Thanks again,

Jim

 

[SurfingGecko]

Sounds like the Servers needed to be re-initialized with the name server is all.

The 5 minute setting should be fine if you are confident that the users coming into the system viewing reports are in and out in less than 5 minutes.

One thing that could happen is a users comes in to the system views a report, goes to the water cooler, and their session times out, then when they return to view another page in the already open report they may be asked to re-log in or the system is out of licenses.

You will simply need to keep an eye on the system and have users report to you if they are running into this.. You can alway bumpt it if need be.



Cheers,

SurfingGecko

http://www.surfinggeckosoftware.com