Core Query API Usage

[Roger_Soares]

We are using Unity API in a customer for external access, and we're trying to use the Core Query API license for unlimited user access, without usage of concurrent client licenses.

We already registered the license in Workstation Registration, and we added the license in Unity API connection code too, but the concurrent client license continues to be in use by API.

Could someone help telling if there is something missing? The OnBase version is 18.

EDIT:

It was our mistake. There're 2 connection methods and 1 of them didn't have the LicenseType property.

Now, after the property inclusion, the connection is consuming the Core Query API license successfully.

Thanks to everyone!

[Scott_McLean · Accepted solution]

On your AuthenticationProperties object, set the LicenseType property to QueryMetering

If the system is licensed for them, this should use the metered queries instead of concurrent.

An exception to this would be if you access an API area that requires a separate concurrent license for the module (like workview), which would still consume that concurrent license.

[Roger_Soares]

Hello Scott!

We added the QueryMetering value on LicenseType property, and we're using the API only for archival in our tests. The system is also licensed for them.

Even including this information, the API still consumes the concurrent license.

[Scott_McLean]

Are you licensed for the "Archival API"?
I believe this is required in order to import new documents using query metering.

[Nevin_Steindam]

Are you licensed for the "Core Query API" or the "Client Query API"? You mention registering the license in Workstation Registration, and I think that step is only possible if you're using the Client Query API.

The Unity API can only use the Core Query API license. The Client Query API is specifically for solutions using our Thick Client API, which is probably NOT what you want to work with today.