+ Start a Discussion
Jerry HeJerry He 

What's the license Agreement and License management in force.com?

Can anyone tell me what is the license agreement and license management in force.com?

What's the difference between them?

I know that force.com has four edition, group/professional/enterprise/unlimited, are these four edition is license agreement?

Thanks for your reply.

:)

Best Answer chosen by Admin (Salesforce Developers) 
Navatar_DbSupNavatar_DbSup

License Management


License Management starts with the Licenses Management App (LMA). The LMA is developed by Salesforce and is available to eligible partners. For more information on the Partner Program, including eligibility requirements, please visit us at www.salesforce.com/partners.
With the LMA, partners can:
• Set up trial defaults
• Track installations and used licenses
• Extend, activate, suspend or expire licenses
The LMA should be installed in a production org. The org needs to be Enterprise or Unlimited Edition because of the features required to use the app. Partners who do not have a compatible production org are eligible for a 2-user Enterprise Edition org. Details can be found here. Once you install LMA into your production org, this org will be known as your License Management Org (LMO). The LMO will store the licenses, leads, packages and package versions associate to your Managed Package. It is important to note that the LMA cannot be uninstalled, so be sure to review the org before installing. If you decide to release multiple managed package apps, you can use one LMO to manage all of these packages. This will ensure all of your prospects and customers are all in one org.
To associate your Managed Package to your LMO, you need to use the AppExchange. You can only associate a released Managed Package to your LMO. You cannot associate a beta Managed Package or an Unmanaged Package. After you have successfully uploaded your released Managed Package, you will need to login to the AppExchange. Follow these steps to complete the associate:
1. Visit AppExchange and click the Publishing tab.
2. Login with your DE credentials - if you have a different publisher profile you'd like to use, you can change this later by following this guide.
3. Next you must navigate to the Default License Settings page to setup the LMO association.
4. To access the Default License Settings page, click Manage Licenses link next to the managed package in the Your Uploaded Packages section of the Publishing Home page.
5. The first time you associate the managed package to the LMO, you will be required to register the package. When the Register Your Uploaded Package page appears, click Register to register your uploaded package.
6. Specify the username and password of your LMO. After you set this, all subsequent versions of your managed package will automatically be associated to the same LMO and the LMO name and org id will be displayed.
7. Select whether your default license is a free trial or active. If your app is free, then select active.
8. If you selected a free trial license, enter the length of the trial in number of whole days, up to 90. A trial cannot last more than 90 days, even if you try to extend this in the LMO. If you selected an active license, enter the license length in number of days. If your license is free or does not expire, select License does not expire.
9. Enter the number of seats associated with your default license, or select License is site-wide to offer the license to all users in the installer's organization. If you select site-wide, the customer will not need to setup licensing when installing.
10. Click Save to submit your changes.
Note: If a previous version of your package is associated with an LMO, when you register your uploaded package, the package is associated with the same LMO and the default license settings are initially set to the previous version’s settings. You can override the default license settings, but you cannot change the LMO.

License Assignment


Depending on how you setup your license defaults, the customer experience will vary. If you decide to define a default number of seats, this means the admin will need to assign licenses to any user interested in using the app including him/her. After install, the admin will need to assign licenses for the install managed package.
An alternative path that is recommended is to set your license default to site-wide (Figure 3). The benefit is that the installation process will be even easier for the customer since they will not need to assign licenses initially. Instead, licenses will be automatically assigned to all your users and the ability to manage licenses will not available. Your users will have instant access to your app as long as they have the appropriate profile and permissions.

 

Did this answer your question? If not, let me know what didn't work, or if so, please mark it solved. 

 

All Answers

Navatar_DbSupNavatar_DbSup

License Management


License Management starts with the Licenses Management App (LMA). The LMA is developed by Salesforce and is available to eligible partners. For more information on the Partner Program, including eligibility requirements, please visit us at www.salesforce.com/partners.
With the LMA, partners can:
• Set up trial defaults
• Track installations and used licenses
• Extend, activate, suspend or expire licenses
The LMA should be installed in a production org. The org needs to be Enterprise or Unlimited Edition because of the features required to use the app. Partners who do not have a compatible production org are eligible for a 2-user Enterprise Edition org. Details can be found here. Once you install LMA into your production org, this org will be known as your License Management Org (LMO). The LMO will store the licenses, leads, packages and package versions associate to your Managed Package. It is important to note that the LMA cannot be uninstalled, so be sure to review the org before installing. If you decide to release multiple managed package apps, you can use one LMO to manage all of these packages. This will ensure all of your prospects and customers are all in one org.
To associate your Managed Package to your LMO, you need to use the AppExchange. You can only associate a released Managed Package to your LMO. You cannot associate a beta Managed Package or an Unmanaged Package. After you have successfully uploaded your released Managed Package, you will need to login to the AppExchange. Follow these steps to complete the associate:
1. Visit AppExchange and click the Publishing tab.
2. Login with your DE credentials - if you have a different publisher profile you'd like to use, you can change this later by following this guide.
3. Next you must navigate to the Default License Settings page to setup the LMO association.
4. To access the Default License Settings page, click Manage Licenses link next to the managed package in the Your Uploaded Packages section of the Publishing Home page.
5. The first time you associate the managed package to the LMO, you will be required to register the package. When the Register Your Uploaded Package page appears, click Register to register your uploaded package.
6. Specify the username and password of your LMO. After you set this, all subsequent versions of your managed package will automatically be associated to the same LMO and the LMO name and org id will be displayed.
7. Select whether your default license is a free trial or active. If your app is free, then select active.
8. If you selected a free trial license, enter the length of the trial in number of whole days, up to 90. A trial cannot last more than 90 days, even if you try to extend this in the LMO. If you selected an active license, enter the license length in number of days. If your license is free or does not expire, select License does not expire.
9. Enter the number of seats associated with your default license, or select License is site-wide to offer the license to all users in the installer's organization. If you select site-wide, the customer will not need to setup licensing when installing.
10. Click Save to submit your changes.
Note: If a previous version of your package is associated with an LMO, when you register your uploaded package, the package is associated with the same LMO and the default license settings are initially set to the previous version’s settings. You can override the default license settings, but you cannot change the LMO.

License Assignment


Depending on how you setup your license defaults, the customer experience will vary. If you decide to define a default number of seats, this means the admin will need to assign licenses to any user interested in using the app including him/her. After install, the admin will need to assign licenses for the install managed package.
An alternative path that is recommended is to set your license default to site-wide (Figure 3). The benefit is that the installation process will be even easier for the customer since they will not need to assign licenses initially. Instead, licenses will be automatically assigned to all your users and the ability to manage licenses will not available. Your users will have instant access to your app as long as they have the appropriate profile and permissions.

 

Did this answer your question? If not, let me know what didn't work, or if so, please mark it solved. 

 

This was selected as the best answer
Jerry HeJerry He

thanks, :)