License Management
Overview
IBM DevOps Solution Workbench supports floating, perpetual and wmu token licensing through the IBM Common License Key Server. This licensing model allows you to share a pool of licenses across multiple users, providing flexibility in license allocation and cost optimization.
License management
During the installation process, you need to set the information for the IBM License Server.
License Types
IBM DevOps Solution Workbench offers two main license types and regarding editions:
DSWProfessionalFL / DSWProfessional
- Available in product edition: Professional
DSWArchitectFL / DSWArchitect
- Available in product edition: Architect
Community Edition
only available when installed within the Loop platform.
The following restrictions apply when running in Community Edition:
- The overall number of model elements in a branch is 25 maximum
- An implementation project can contain only 1 API, 1 domain and 1 integration namespace.
- 3 items of each kind are allowed (e.g. Entities, Services) in implementation projects
When the limit is reached, the creation of additional elements is not possible any more. After upgrading the license, the project can be further edited and viewed. When a project exceeds the limits, it can only be opened by users with a non community-license.
Community Edition does not include any product support or warranty.
All product features display the availability in each edition (professional / architect) in the product documentation.
Requirements for functional licensing
Before using the IBM DevOps Solution Workbench ensure that:
- IBM Common License Key Server is installed
- You have valid license keys for Professional and/or Architect
- The IBM Common License Key Server is accessible from your IBM DevOps Solution Workbench installation
Troubleshooting
Common Issues
Issue: License service is not accessible.
- Solution: Verify the license service URL and network connectivity
- Check: Ensure the service is running and accessible from your cluster and namespace
Issue: Your user does not have a valid license associated, or the license check failed.
- Solution: Verify license key format, validity and available licenses
- Check: Ensure keys are properly configured in the license service and enough licenses are available
Issue: The associated license (Architect) to doesn't allow this action.
- Solution: Check current license usage and assign a professional license
- Check: Verify license allocation and type of assigned license
Helpful command to check licenses in IBM Common License Key Server
cd /opt/IBM/LKS
bin/lmutil lmstat -a
User License Service Logs
To troubleshoot license-related issues:
kubectl logs -n <devops-solution-workbench> deployment/k5-user-license-service