You are viewing limited content. For full access, please sign in.

Question

Question

Admin license connections for high availability/high workload systems

asked on June 10, 2015

Hi,

I have a client that is concerned about the possibility of bottlenecks when using the admin license (2 connections) with multiple modules.  They are currently using a named user license on their workflow user, forms user, and admin user.  They're looking to free up these named user licenses for employees to use.

Their concern is that they may run into bottlenecks with only 2 available connections.  For example, they have public portal and they're concerned that multiple users submitting forms simultaneously, while workflows are running, will cause bottlenecks and/or failures between each other.  They also have the potential for workflows to be running at any given moment.

Could this be a potential issue, or are there safeguards in place to keep these issues from arising?  Or are they simply in a situation where applying named user licenses to these accounts would be the best option to avoid issues and keep business moving?

Thanks.

0 0

Answer

SELECTED ANSWER
replied on June 10, 2015

The default "ADMIN" user in the repository should not be a named user and reserved for performing administrative tasks in the Laserfiche system. For other applications that connect to the server/repository with an account, please refer to the individual help documentation regarding what type of user is needed.

The account you have configured in the Workflow Connection Profile (i.e. Workflow user) does not need to be a named user.

The WebLink Public Portal account should not be a named user and should be marked as read-only.

The account configured for Forms should be a named user.

3 0
replied on June 15, 2015

Thanks Alexander.  I do have a follow-up question on this.  I've seen mentioned in other threads that Forms does not need a named user license to store forms in the repository.  What is the purpose of having a Named User License on the Forms user?

0 0
replied on June 15, 2015

Please refer to this help page. Forms requires a named user account with the "Manage Trustees" privilege to perform the initial user list retrieval as well as initializing the FORMSUSER$ account which will be used thereafter. Note that this user is who you will need to log into the Forms site as initially to set up all other users. At this point you wouldn't need to reserve a named user license for that initial Forms user anymore.

1 0
replied on June 15, 2015

Ah, that makes sense.  That's how I thought it worked, but I thought you meant we would need to keep a named user license on the Forms user indefinitely.  Thanks for the clarification!

0 0

Replies

replied on June 10, 2015

In my system I have a non-named user for each service that connects to Laserfiche. IE, Quick Fields, Import Agent, Workflow and so on. This makes it so easy for tracking when you are trying to figure out how a document was created, moved and such. 

3 0
replied on June 10, 2015

Workflow does not require a named user license for the connection profile user. The connections made by Workflow and Forms to the repository during their normal operations are not subject to the 2/4 concurrent connection limits.

2 0
replied on June 10, 2015

Hi Eric,

The admin connection is not intended for usage in situations where bottlenecks would occur. It is intended such that you are able to log in and configure named users without having to somehow already have logged in and configure named users. 

Note that the public portal user does not require - and indeed should not have - a named user account. If public portal is set up to use a named user account, or the admin account, you are not actually making any use of your public portal connections. The public portal connection is in place to account for this exact type of concern. 

Also, as noted https://answers.laserfiche.com/questions/78628/Laserfiche-Licensing-Details-for-Laserfiche-Products, the workflow user does not require a named user license. 

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.