cancel
Showing results for 
Search instead for 
Did you mean: 

Licenses got stuck while testing API

Israel_Cordero1
Confirmed Champ
Confirmed Champ

Hello, so I'm an OnBase Dev and I'm working on a webservice that uploads documents to OnBase. I was doing some testing uploading documents without using the app.disconnect() after each upload to check how many licenses would get stuck. my issue is that the dev environment is managed by a third party and to do an IIS reset would take up to 4 days. Other than scheduling an IIS reset to release all the concurrent licenses, is there some way that from either the client or config I could do that?

 

PS: all the concurrent licenses appear active even tho no one is logged in

2 REPLIES 2

James_Perry
Elite Collaborator
Elite Collaborator

Israel, what version of OnBase are you using? There is an option in the Diagnostic Console to review and end Application Server Sessions. This requires some configuration on the Application Server to set up the permissions to allow you to do this. Once done thought it is quite simple to use.

Configure Users or Groups Allowed to Review and Disconnect Sessions

  1. Navigate to C:\inetpub\wwwroot\AppServer\Admin
  2. Open the sessionAdminSecurity.config in Notepad
  3. Edit the "allow users" or "allow roles" lines to add authorized users or groups (see EXAMPLE)
  4. Save the sessionAdminSecurity.config
EXAMPLE sessionAdminSecurity.config
<sessionAdminSecurityConfiguration>
  <allow users="USERNAME"/>
  <allow roles="MANAGER,ADMIN GROUP"/>
</sessionAdminSecurityConfiguration>

Review Active OnBase Sessions

  1. Launch Diagnostics Console
  2. Set the ServerUrl to http://bcobweb:8989
  3. Click the OK button
  4. Click the Tools menu
  5. Click the View Application Server Sessions menu option
  6. Set the Application Server URL to http://onbaseWebServer/AppServer
  7. Click the Go button to refresh the Sessions list

Disconnect Active OnBase Sessions

  1. Click the User Name column header to sort the list
  2. Select the user in the list
  3. Click the Disconnect button
  4. Click the Yes button to Confirm Session Disconnect

Note: Sessions should not be disconnected unless the user is notified or if there is an emergency reason to free up a session

No one person needs to know everything—they simply need to know who knows it.

we are running OnBase 16.0.2.71. My issue with this is that the Server is handled by a third party and the config is on the server, so to achieve this it will take 4 to 5 days.