Based on the following Answers post: https://answers.laserfiche.com/questions/68792/concurrent-sessions, I learned that for any repository (in this case our repository associated with WebLink), there is a maximum of four concurrent connections per Named User. Now, we have set WebLink up to have a Laserfiche user automatically login, so as to minimize efforts to people connecting from "the outside". Without having to make the site so external clients would have to log in (so as to split up connections among multiple users), is there any other way we might be able to increase the number of concurrent connections?
Also, in the past I've compared connection sessions with the repository sessions in the Laserfiche Administration Console. Recently, I was experiencing the "maximum connections exceeded" message, but didn't even see four connections total. Am I looking in the right place, or should I be looking for something, say, in the Event Viewer?
Thanks, as always, to anyone who can help. :)
Marty Gaffney - Network Technician
Town of Okotoks
@ablfguy
Question
Question
Increasing number of concurrent connections to WebLink
Answer
Please confirm that after you regenerated the license file, you replaced it in the Laserfiche Server installation directory (by default C:\Program Files\Laserfiche\Server) and then restarted the Laserfiche Server service. Also confirm that the new license is the only *.licx file in that directory prior to restarting the service.
As for the user that you've configured in WebLink to be used as the Public Portal user, make sure that it is not configured in the Laserfiche Administration Console to be a repository named user, i.e. the Named User option for that user should be "False". Also make sure that the "read only user" option has been checked and that the user does not have the "Manage Trustees" privilege. Make sure that the user is also not a member of a group that has said privilege.
After you've configured WebLink to automatically log in using that repository user, if you are still unable to have users log into WebLink using the Public Portal licenses, then please contact your Laserfiche reseller to open a case with Laserfiche Support so we can investigate the matter further.
Regards
Replies
WebLink connections for public profiles are not subject to that limitation since their point is to allow an unlimited number of public users to log in without specifying a username and password.
Interesting...so if that's the case, what else do you think might be causing the "maximum connections exceeded" message?
(And thank you for your quick reply!)
Hi Marty,
So to confirm, your Laserfiche Server has been allocated the 25 public portal users and WebLink is configured to use a single LF user to automatically log in with? Is this LF repository user configured to be read-only, does not have the Manage Trustees privilege, and also is not using a repository named user license?
Regards
Hey Marty,
We actually have a licensing scheme called 'Public Portal' for exactly this reason. Public portal allows your to set up a LF account for auto login with Laserfiche and pull from a pool of concurrent connections. As long as that account is marked 'read-only' in the admin console and doesn't have any other privileges that would override that read-only designation (Manage Trustees, for instance), that user will use the concurrent connections from public portal and will not require a named user license.
Note that the 4 session max limit you mention only applies to named user licenses, so you'd avoid that limit with public portal.
Looking at your page in our internal customer portal, it appears you have public portal already. You can talk to your reseller/regional manager for more info on what you have and price sheet for other options.
As for the admin console not reflecting the number of sessions accurately, not sure what's going on here. You made sure you refreshed the connection listing?
I think that's probably what the problem is. I'm hoping to migrate my existing licensing scheme from Licence Manager to Directory Server tonight anyways, so I'll probably re-generate the licence for our main Laserfiche Server at the same time (as our existing instance doesn't have the Public Portal users as you specified).
I'll let you know how it goes - thanks again!
Marty
Hi Alex:
Sorry for the delay getting back to you, there were a few things I wanted to walk through first:
1) I have re-generated the licence associated with our main Laserfiche server to have 25 public portal users allocated.
2) I have attempted to configure WebLink to use a single Laserfiche user. Even though I only have four Laserfiche Named Users set up (across all my repositories), and the server has five Laserfiche Named Users allocated, I can't seem to add a new Named User due to licensing limitations. Now, I have a few Laserfiche users, through all of my repositories, that are not Named; would this be interfering with me being able to add new Named Users?
Please let me know if I'm on the right track with getting this set up properly - thanks much.
The User(s) for use with WebLink should not be set as a named user. If they are a named user, then they will not pull a license from the 25 concurrent Public Portal read only licenses.
Also, make sure to set the check for Read Only on the user(s) profile.
In Rio, the default way of assigning Named licenses is through the License Manager (now Directory Service). If you wish to assign named licenses through a repository user profile, first you must assign the license to the server through LM/DS and then it will be available to assign to at the repository level. This is not a recommended practice for regular users as when you assign a license to a server, that license can then only be used to access 1 repository. If the license is assigned to an AD user from the LM/DS, the user can be granted access to any repository on your system.
As an example, lets say (for simplicity) you have a 10 user Rio (I know, it does not exist).
Server A has 3 Named Licenses assigned
Server B has 2 Named Licenses assigned
In LM/DS you now only have 5 license left to assign to AD users
Now if Server A has 2 repositories, the 3 Named Licenses available to Server A can only be assigned in 1 repository each. Assume that Repository 1 (Ar1) gets 2 of those licenses and Repository 2 (Ar2) gets the remaining 1. Then lets say that Server B has 2 repositories and assume that Repository 1 (Br1) gets both of the assigned Named Licenses and Repository 2 (Br2) then gets none of the server assigned Named Licenses. Below shows your log in limits.
Ar1 = 5 AD users from LM/DS and 2 users from Repository assignment for a total of 7 users
Ar2 = 5 AD users from LM/DS and 1 users from Repository assignment for a total of 6 users
Br1 = 5 AD users from LM/DS and 2 users from Repository assignment for a total of 7 users
Br2 = 5 AD users from LM/DS and 0 users from Repository assignment for a total of 5 users
Currently, we have 88 Named User licences, 83 which are assigned to Windows accounts, and 5 for Named (non-Windows) Users. I've tried moving away from having Named Users assigned anywhere, except when absolutely necessary, to avoid using multiple licenses across multiple repositories. I was wanting to set up another Named User with Full access to the repository associated with WebLink, however even though I have 4 Named Users defined, I can't seem to add another. I have users defined across my repositories, however they're not Named per se, so I'm not sure why I can't add another Named User, unless all users in all repositories count toward, the 5 Full Repository user limit we currently have in place?
In LM/DS, did you assign all 5 licenses to the same LF server and then generate and apply the Server license?
I'll have to check again tonight, as I was pretty sure this was the case - I'll let you know tomorrow. :)
Okay, sorry about the delays, here's what I've done:
1) My Laserfiche Server has been allocated the 25 public portal users, and I've regenerated the licence key and restarted the Laserfiche Server service to apply this change to my existing licensing scheme.
2) WebLink has now been configured to use a single, full repository user, logging in automatically.
3) The WebLink user has been set with read-only privileges on the repository, and the Manage Trustees privilege has been removed (but not set as a retrieval only user, as it appears our existing licensing doesn't appear to have this).
I have experimented with using a Windows account as well, but this didn't seem to work either. Might there be something else I might need to do to get the public portal licenses associated with this user? Or have I maybe set this user incorrectly?
Thanks again to everyone for all of your assistance!
Marty
Please confirm that after you regenerated the license file, you replaced it in the Laserfiche Server installation directory (by default C:\Program Files\Laserfiche\Server) and then restarted the Laserfiche Server service. Also confirm that the new license is the only *.licx file in that directory prior to restarting the service.
As for the user that you've configured in WebLink to be used as the Public Portal user, make sure that it is not configured in the Laserfiche Administration Console to be a repository named user, i.e. the Named User option for that user should be "False". Also make sure that the "read only user" option has been checked and that the user does not have the "Manage Trustees" privilege. Make sure that the user is also not a member of a group that has said privilege.
After you've configured WebLink to automatically log in using that repository user, if you are still unable to have users log into WebLink using the Public Portal licenses, then please contact your Laserfiche reseller to open a case with Laserfiche Support so we can investigate the matter further.
Regards
Okay, I think I finally got it (including this to anyone who has the same sorts of problems):
1) I had a Repository Named User tied to a Windows account, and I removed this association.
2) The Repository Named User was a member of the Admin group, so I removed this.
3) I ensured the Repository Named User was NOT a Full Repository Named User.
4) I changed the Repository Named User to Retrieval Only (I couldn't do this previously, this might be tied to the fact that I hadn't tried since after I changed the Server licence to have 25 Public Portal licences).
5) I ensured this same user had read-only access to the entire repository specified in the WebLink Administration Console.
Before this, I also re-generated the licence key, and restarted the Laserfiche Server service. Having a look at everyone connecting, I could see the new connection instances showing up as Retrieval users, and the number of people connecting was definitely more than two.
Thanks a bunch for your help - much appreciated as always!
Marty Gaffney - Town of Okotoks