ISV Tech Talk: License Management App Manishi Singh Principal Technical Evangelist Salesforce.com in/manishisingh

Safe Harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

What will we cover today? • What is License Management Application (LMA) • Pre-requisites for LMA • How to get the LMA •  Installing the LMA • Partner Business Org / License Management Org (LMO) • Associating your managed package to LMO •  Inside the LMA • Best Practices

What is License Management App • An app to manage your AppExchange app

• Control licensing and access for your app installed on a customer’s org

• Creates a lead and a license record for every new installation of your app

• Allows you to support your customers through the subscriber console

Pre-requisites for LMA • Be an eligible and registered AppExchange partner –  For partner models visit us here

• Use a managed release package for your app

• Clear the Salesforce Security Review process for AppExchange apps

Getting the LMA • The LMA is installed to your business / CRM Org –  New partners get it pre-installed on the enterprise

orgs provided

•  If you meet the pre-requisites and do not have the LMA –  Log a case on the partner community with your

login –  Support will provide you a link to install the LMA

Installing the LMA • LMA should be installed to a business org

–  Install it on your CRM org (recommended) •  We will add 2 EE Salesforce licenses to this CRM org

OR

–  Install it to the business org provided through the ISV program •  Partner business orgs come with 2 EE Salesforce licenses

• Follow the steps outlined in the ISVForce guide for installation steps –  Read through the LMA specific sections to understand how to configure and use the LMA

• Setup access permissions for people who would use the LMA

Important Installation notes • LMA only works with managed packages

–  You cannot track installs of unmanaged or beta packages through LMA

• LMA on the business org –  This is the org where your sales team logs in to to run their business (track leads, opportunities

etc.) –  Leads created through LMA will help them keep track of new prospects

Partner Business Org • What is the business org?

–  Partner Business Org / License Management Org (LMO) / AppExchange Publishing Org (APO)

–  This is also your CRM org, which you use to: •  Run your sales •  Support your customers •  Run operations i.e. submit orders to Salesforce, track

licenses, track customer org expirations etc.

Contacts

Analytics

Campaigns

Leads

Accounts

Licenses (LMA)

Orders (COA)

Cases

Opportunities

Environment Hub

Subscriber Support (LMA)

Associating your managed package to the LMO • Why should you do this?

–  To get package installation information into your partner business org •  Leads •  Licenses •  Subscriber

• How should I do it? –  Go to AppExchange.Salesforce.com –  Login –  Go to Publishing Console –  Follow these instructions

• This is a one time activity

•  http://www.salesforce.com/us/developer/docs/packagingGuide/Content/lma_associate_package_lmo.htm

Inside the LMA • What’s in the LMA?

–  Leads –  Licenses –  Packages –  Package Versions –  Subscribers (Support Console)

Leads • When a customer installs your package, a lead is created in the LMO

• The lead contains the installer’s name, company name and email address

• This information links the license to a Salesforce user

• The lead source defaults to “Package Installation”

Lead Record

Lead Data Lead Source

Licenses • Upon package installation, a license record is also created in the LMO

• License record contains additional information like the –  Installer’s org ID –  Installed package version –  License status –  Install date –  Org Status* –  Instance* –  Org Edition*

• License settings can be modified to reflect changes on the customer’s org

* Winter15 release

License Record

Packages • Package records lists the packages created on the orgs linked to AppExchange

• Package record contains additional details about the package like –  Package ID –  Latest Version –  Packaging Org ID

•  In addition all past versions of the package are listed on a related list

Package Record

Package Versions • Lists all versions of your managed package

• A package version contains details about the specific version like –  Version ID –  Version name –  Version number –  Release date

•  In addition all license records tied to this package version are listed on a related list

Package Version Record

Subscribers (Subscriber Console) • Real-time information about your installed packages –  Installed Org ID –  Installed instance –  Installer’s company name –  API consumption on the org* –  Data space consumed on the org* –  File space consumed on the org*

• Link to login** to the installed org if customer access has been granted

• All your packages installed on the org are also listed (in case you have multiple packages) *Org level info, not package level

** Post Winter’15, License record will have this link

Subscriber record

Best Practices • On the license record create formula fields to track trial expiration date, package expiration date

• Create reports to see all orgs statuses and expirations • Schedule these reports to run weekly • Enable time based workflows to generate notifications when customer’s orgs are close to expiry

• Pull info out of LMA (Org ID) to automate order submission through Channel Order App (blog post)

• Usage Metrics based on license data, requires environment hub (blog post)