Thinking it is useful for an IPM repo to provide different "visibility" of "available" deployed modules, depending on the account used to access the IPM server.
This avoids having a separate repo per customer. So one common repo service, where account-permissions to access different modules (and versions) is configured.
Can this work for a subscription business model ie: Once installed the software runs forever. Maybe this is limited to some extent with byte-code being published per IRIS version. So a "subscription" is on the IPM repo by security configuration continuing to enable access to module updates.
In that case the listing / search of modules, might give hints on whether subscription is enabled.
Speculating then a "10 seat / process" license would translate to a specific module byte-code build? To upgrade the "license capacity" is installing a different module version? This has potential to cause service disruption, if only interested in a change in capacity behavior.
Maybe a product would be split into two parts, an IPM "license module" that changes, and an IPM "main software module" that remains unaffected.
- Log in to post comments
.png)
.png)
.png)
.png)
.png)
.png)