PPM License Types
PPM offers you two types of user licenses: named licenses and concurrent licenses. You can install the license type that can best support your business.
A named license is individualized. Only the user named can access specific features of PPM. And the user can access PPM anytime and anywhere.
What features can named licenses cover
- User Administration
- Application Portfolio Analyst
- Application Portfolio User
- Demand Management
- Deployment Management
- Portfolio Management
- Program Management
- Project Management
- Time Management
Named license capacity check
PPM checks the capacity of named licenses when you assign them to users. If a named license limit is reached, you cannot assign that license to users.
Concurrent licenses enable a pool of licenses to be shared across a group of potential users, ensuring that at no point in time is the maximum concurrent number of licenses exceeded.
For example, in a four-user concurrent user license setup, four users, regardless of who they are, can simultaneously access PPM, but another user is unable to log in until one of the four users logs out.
Typically, concurrent licenses are purchased for the maximum number of people who will be using PPM.
What features can concurrent licenses cover
- Foundation - Over 25 Users
- Concurrent Configuration
- Concurrent User Administration
- Concurrent Demand Management
- Concurrent Project Management
- Concurrent Portfolio Management
- Concurrent Program Management
- Concurrent Time Management
Concurrent license capacity check
PPM does not check the capacity of concurrent licenses when you assign them to users: You can assign installed concurrent licenses to as many users as possible.
PPM checks the capacity when the users that are assigned the concurrent license log into PPM. If the concurrent license limit is reached, a warning message pops up when another user tries to log into PPM:
Cannot login. The limit for concurrent online users has been reached. Try again later.
Compatibility with Portfolio Optimization and Mobility licenses
If you have installed the Portfolio Optimization or the Mobility license, they can both work with the related concurrent licenses.
- If Portfolio Optimization is enabled, all users that have the concurrent Portfolio Management licenses can access the feature.
- If PPM Mobility Access is enabled, all users that have the concurrent Demand Management licenses can access the feature.
Known issue for new users
Known issue: If you use instance-on or Eval licenses and assign such licenses to some users in the trial period, after you install the concurrent licenses, the PPM Server cannot be started.
Cause: The instance-on and Eval licenses are named licenses. They are disabled once you install the concurrent licenses. When the PPM Server starts, PPM will check whether the number of the users that are assigned named licenses exceeds the license number. Since no named license exists in PPM, PPM cannot be started.
Solution: A script is provided to help you transform the named-licensed users to concurrent-licensed users.
You have installed 5 concurrent licenses. The total capacity of the concurrent licenses are:
- 5 Foundation - Over 25 Users
- 5 Configuration licenses
- 5 User Administration licenses
- 5 Demand Management licenses
- 5 Project Management licenses
- 5 Portfolio Management licenses
- 5 Program Management licenses
If 5 users with only the concurrent Portfolio Management licenses are currently accessing PPM, then a user with the concurrent Portfolio Management license cannot log into PPM, unless at least one of the 5 previous users logs out. However, if a user with the concurrent Time Management license tries to log into PPM, the user can log in: because none of the concurrent Time Management licenses is consumed.
Concurrent license FAQs
A: When you log into PPM, one concurrent license is consumed for each feature assigned to you. When you log out from the last session, all the concurrent licenses are returned.
A: If you close a session without explicitly logging out, the concurrent licenses will be returned after the session times out.
A: Concurrent licenses are consumed on a per-user basis. When you log into PPM, one concurrent license is consumed for each feature assigned to you, regardless of how many sessions you open.
A: By default, a PPM session times out after 120 minutes. You can modify the timeout setting using the
KINTANA_SESSION_TIMEOUT parameter in the
A: When SSO is enabled, you will automatically log into PPM if the SSO session is longer than the PPM session. If the SSO session is shorter than the PPM session, you need to log into IDP again. In both cases, PPM session is logged in and the concurrent license is consumed.
A: If you open the PPM Workbench, there is heart-beat communication between the workbench and PPM. Therefore, PPM session is logged in and the concurrent license is consumed. Make sure you close the workbench after use.
A: Each SOAP request will automatically log into and out of PPM. Therefore, the concurrent license is consumed and returned automatically.
A: Yes. Each REST API call creates a PPM session. The concurrent license is consumed until all the sessions are closed. You can call logoff API to actively end the session. Or, wait until the session times out.