0

So I am new to the packaging and testing of the applications.

I tried earlier today to create my first (ISV - managed) package and install it on a different environment and that worked perfect.

My question here is how can I create an OEM package(the one that's a stand alone salesforce + the application I'm building)

One extra question: how can I make my content of the package in ISV not counted towards the users limits?

2

An OEM package is basically the same thing as a normal managed package; OEM vs. ISV is about who's providing licensing. With the OEM licensing model, you create contracts with salesforce.com for the licenses, and your clients create contracts with you. With the ISV model, users already have a salesforce.com contract, and form a separate licensing agreement with you. OEM installations have additional restrictions in place, so you'll want to read more about OEM User License Comparison.

To get started, you'll need to sign up as a partner in order to get it "blessed" as an OEM package. Once your application has completed the partner process (including getting a security review), your package will no longer count towards configuration limits. The Partner team will help you with the process and give you additional information, including how to set up Trialforce, which gives you the ability to create trials that are already pre-configured with your package.

You can use a normal managed package, but you'll probably want to upgrade your developer org. Once you're approved for the partner program, you can request that your developer account get upgraded to a partner developer account, which has more storage, more licenses, and higher limits, or you can create a new org from the portal and then create your package there. Once that you can't use the namespace you already used if you follow this path.

| improve this answer | |
  • Thank you for the detailed response. So in the mean time(while waiting to complete the partnership process) I can assume that the OEM package is the same thing as the ISV package, but Salesforce will allow me to install that package as a stand alone once I have the proper OEM license? – raym0nd Nov 6 '15 at 20:24
  • 1
    That's my understanding. I worked at a place that had an OEM package, but I wasn't involved in the original negotiation. They'll let you know how it works. – sfdcfox Nov 6 '15 at 21:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.