Database software embedded in 3rd party app solution

[caldwellb]

We've all seen these where you have a turn key application installed only to find it has embedded with it say a licensable edition of SQL, Oracle DB, etc.   What are best practices folks use here to track compliance of the Database or what ever app is embedded (assuming of course their contracts offers the entitlement as pro bono from the original publisher?

We want to ensure the embedded app which has not purchased license record will not consume against the pool of those that do.  Approaches that come to mind are set "Exemptions" and maintain in notes or documents those exempted devices when the product shows up.  

How do others accomplish this in large scale enterprises?

[mfranz]

Hi,

Assuming FNMS on-prem here. If you can define a rule set around your problem and all needed inputs were available in FNMS, you could certainly automate allocations with a business import. Examples:

• Your own SQL servers follow a  specific name schema
• Your own SQL servers are hosted on specific hosts/in specific clusters
• Your own SQL servers run in a specific subnet
• Your own SQL servers run on specific operating systems
• Your own SQL servers are accompanied by specific other applications
• Your own SQL servers are managed by a 3rd party solution

You could then use one or many of these to identify and allocate your own databases or exempt 3rd party ones.

Best regards,

Markward

[caldwellb]

mfranz,

Love having these other options.  Thank you for yet another approach

Cheers!

[caldwellb]

Solution B from kclausen from inital testing seems to be working nicely.  More testing to do to be 100%

Much appreciate the response offering options for us.

[kclausen · Accepted solution]

@caldwellb - Here is the scenario:

You have entitlements and installation for Product A.  Product B is installed and "bundled" in with Product A.  When Product B when installed on its own it is commercial software that requires an entitlement.

You can manage this scenario in a couple of ways:

Solution A - Exemptions

If you have a low volume of installs of Product A, then you can find the installs of Product B that are associated with an installation of Product A and set a License Exemption on your Product B license.

Solution B - Create a Product Bundle License

When you create the software license for Product A, go to the Applications tab of the license and add Product B.  Go to the Use Rights tab of the license and make sure that Product A is Primary and Product B is supplemental.  Set the appropriate Upgrade/Downgrade rights for each product.

During a License Reconcile, if you have a Server where both Product A and Product B are installed, the Product B installation will automatically get consumed against your product bundle license.

If an install of Product B that is bundled with an instance of Product A is installed on a separate server, you need to "Allocate" the server where Product B is installed against the Product Bundle license.  That stand-alone install of Product B will then get consumed against the Product Bundle license.

[caldwellb]

kclausin,

Solution A was to be our initial go to solution. However Solution B sounds interesting having used this in different methods. I'll give some exploration with this.  

Appreciate the feedback will update how this turns out

Cheers