08-04-2015 09:13 AM
Hello,
Whenever we try to access Unity API through some webservices and connect to On Base our concurrent license is being used.
If we directly login to onbase using the thick client, it consumes enterprise Concurrent license. See screenshot of Currently logged in users from unity client.
3 users logged in(2 of them are using Enterprise Concurrent license and 1 concurrent license). The concurrent license call is being made from our application. . Our application it calls the web service and the service is what actually connects to onbase.
This is a problem because the next time someone connects to onbase using our application, we are getting Maximum concurrent license exception.
Did we have unlimited concurrent licenses before and now something has changed. We have been having this problem since 1 week.
I added a line of code to specify the license type in while making a connecting using API.
var authenticationProperties = Application.CreateOnBaseAuthenticationProperties(ObWebServiceUrl, userName, password, ObWebDataSource);
authenticationProperties.LicenseType = LicenseType.EnterpriseCoreAPI;
error occurred within the Unity API: License type 'EnterpriseCoreAPI' for client type 'Hyland.Core.License.ConcurrentLicenseStrategy' is not properly licensed
Thank you
08-04-2015 10:44 AM
Hi Smitha,
EnterpriseCoreAPI is a different license than Enterprise Concurrent Client, which is why you recieved an error when specifying that LicenseType off of AuthenticationProperties.
Regarding the API consuming a concurrent license instead of an enterprise license, I'd recommend contacting your first line of support. They'll be able to look at your specific licensing configuration, which will help in diagnosing the issue.
Chris
08-04-2015 10:44 AM
Hi Smitha,
EnterpriseCoreAPI is a different license than Enterprise Concurrent Client, which is why you recieved an error when specifying that LicenseType off of AuthenticationProperties.
Regarding the API consuming a concurrent license instead of an enterprise license, I'd recommend contacting your first line of support. They'll be able to look at your specific licensing configuration, which will help in diagnosing the issue.
Chris
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.