Difference between revisions of "Community Marketplace"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
==About Marketplaces== | ==About Marketplaces== | ||
A ''marketplace'' is a catalog of application packages. | A ''marketplace'' is a catalog of application packages. | ||
:* Users browse the available packages by clicking '''[Go to Marketplace]''' in the [[Applications]] page. | |||
:* Developers submit a package for inclusion in the catalog by clicking '''[Edit Catalog Info]''' after publishing a package. | |||
:* Service Providers approve a submitted package using [[Manage Catalog]] functionality. | |||
{{Note|[[Tenant Subdomains]] are recommended. They let you create different marketplace destinations, with different kinds of packages.}} | |||
==Working with Marketplaces== | ==Working with Marketplaces== | ||
Revision as of 00:35, 8 April 2014
About Marketplaces
A marketplace is a catalog of application packages.
- Users browse the available packages by clicking [Go to Marketplace] in the Applications page.
- Developers submit a package for inclusion in the catalog by clicking [Edit Catalog Info] after publishing a package.
- Service Providers approve a submitted package using Manage Catalog functionality.
Note: Tenant Subdomains are recommended. They let you create different marketplace destinations, with different kinds of packages.
Working with Marketplaces
Creating a Marketplace
- If you haven't already done so, create a Community Tenant.
- In Service Provider Settings#Community Site Configuration, specify a domain that will be used to access the marketplace page. For example: applicationCatalog.ourServices.com
- __TBD: The subdomain can be anything. The domain portion has to match doesn't it? Why don't we specify just the subdomain?__
Adding a Package to a Marketplace
- --package approval process?