License Management System Upgrade and Development Overview

This project focuses on upgrading and enhancing the license management system at the Joint Institute for Nuclear Research in Dubna. It addresses challenges related to optimizing license usage through different types of licenses and monitoring systems. The system architecture includes components like Network Licensing System, Databases, Web Services, and Network Monitoring, with a special emphasis on the Personal Account for managing license distribution. Various technologies like PostgreSQL, Apache Tomcat, Java, and more are utilized for effective audit and analysis of license usage. Roles are defined within the system based on functional requirements, with the User role being default.

• License Management
• Upgrade
• Development
• Network Licensing
• System Architecture

auly864 Follow

Uploaded on Oct 06, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. LIT License management system. Upgrade and further development. E. Alexandrov, I. Alexandrov, D. Belyakov, N. Davydova, L. Kalmykova, M. Lyubimova, T. Sapozhnikova, T. Syresina, A. Yakovlev, P. Zrelov Joint Institute for Nuclear Research (Dubna) 06.10.2024 GRID'2023 JINR, Dubna

2. Purpose of the work There are various aspects of work related to optimizing the use of licenses. The variety of types of purchased licenses creates a potential difficulty in considering and choosing the optimal licensing conditions for the specific needs of the Laboratory. (There are many types of licenses, such as personal, local, pre-installed software, full package product, volume licensing, group, network, etc.) Additional difficulties arise when solving the problem of collecting dynamic information on the use of network licenses. (License managers are third-party products from which it is not always possible to obtain license usage information.) 06.10.2024 2 GRID'2023 JINR, Dubna

3. Architecture of the LMS The LMS consists of three parts: Network Licensing System (NLS) Databases Web Services Network Licensing System Network Monitoring Personal Account Put Data PostgreSQL Log analyzation InfluxDB Get log Get Data Get Data Pool of Virtual Machines Grafana Server Web Server Get Monitoring Get free network license Get Personal Account 06.10.2024 3 GRID'2023 JINR, Dubna

4. Personal Account Main goals: - managing the distribution of licenses Basic technologies: - PostgreSQL - Apache Tomcat - JAVA - JQuery - HTML / CSS / JAVA-script - WALT* - audit and analysis of the effectiveness of the use of licenses. PostgreSQL - making decisions on the purchase of licensed software Web server Main functionality ( Java servlets) *Web Application Lego Toolkit (Developer Sergey Kunyaev from JINR) Client (Web-browser) 06.10.2024 4 GRID'2023 JINR, Dubna

5. Personal Account view The JINR single sign-on (SSO) is used to authenticate the user and his role when entering the personal account of the LMS. The personal account view depends on the role of the client. user personal account view admin personal account view 06.10.2024 5 GRID'2023 JINR, Dubna

6. Roles The LMS defines different roles depending on the functional requirements The User role is assigned by default to all users of the LMS. Other roles must be assigned explicitly. 06.10.2024 6 GRID'2023 JINR, Dubna

7. User role The User can see information about all public licenses, any information about own licenses and their expiration period, as well as receive notifications about new licenses. The User can request a new license from the list of existing licenses or a renewal of the old one. * The User may request that a new license be added to the catalog of available software for purchasing licenses. * * Requests involve approvals in several instances. 06.10.2024 7 GRID'2023 JINR, Dubna

8. Roles : Entering data into the DB The Operator (and some another roles) has all user rights and can additionally enter into the DB all data concerning licenses, their owners and other information that should be presented in the LMS database. 06.10.2024 8 GRID'2023 JINR, Dubna

9. Database filling and data verification New All data on licenses in LIT, which were purchased and assigned to users starting from 2018, were entered and verified into the LMS database. Now the LMS contains: - 114 LIT users; - 54 items in the software catalog; - 128 purchased licenses (different types, for different software, for a different number of users, etc.); - 354 license instances assigned to users; 06.10.2024 9 GRID'2023 JINR, Dubna

10. Providing statistics New The LMS provides statistical information on the effectiveness of the use of purchased licenses. The interface provides the ability to filter the output of information by various parameters (by type of software, by license validity period, etc.). The interface also provides for varying degrees of information detail. 06.10.2024 10

11. Approval of requests (workflow) New The approval mechanism for requests (workflow): - was imported from the "EDMS Dubna"; - was adapted to the specifics of the architecture (PostgreSQL); - all key features of the approval of applications (workflow) from the "EDMS Dubna" are supported (forwarding to another user, delegation of approval, etc.). 06.10.2024 11 GRID'2023 JINR, Dubna

12. User request for a new license New The User can request a new license from the list of existing licenses: request editing form workflow 06.10.2024 12 GRID'2023 JINR, Dubna

13. All requests New list of all requests related to the given user: drafts, in the process of approval, came for approval (just like in EDMS "Dubna") 06.10.2024 13 GRID'2023 JINR, Dubna

14. List of user requests for the specialist New Approved user requests are grouped in a specific interface for the specialist. In the future, based on these data, the specialist creates an application for the purchase of additional licenses. 06.10.2024 14 GRID'2023 JINR, Dubna

15. Specialist's request for the purchase of additional licenses Purpose of this request: preparation of a purchase request in the EDMS "Dubna" Fields related to the purchase of licenses are filled in the LMS: software, technical task, supplier, etc. New Then, based on the data from our request (in the LMS), a purchase request is created in the EDMS "Dubna". 06.10.2024 15 GRID'2023 JINR, Dubna

16. JINR Digital Eco System New The LMS is one of the services of the JINR Digital Eco System Science => Scientific software => License management system 06.10.2024 16 GRID'2023 JINR, Dubna

17. Conclusion The architecture and object model of the LMS database were developed. The design of the Web interface of the system was completed. The release of the LMS was implemented. New Work has been carried out to fill the LMS database. The LMS provides various statistical information. The mechanism for approving requests has been implemented. Work has been carried out to integrate the LMS with other services within the JINR Digital Eco System. 06.10.2024 17 GRID'2023 JINR, Dubna

18. Thanks for attention ! 06.10.2024 18 GRID'2023 JINR, Dubna