Difference between revisions of "Community Marketplace"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 15: | Line 15: | ||
#: {{TBD|The subdomain can be anything. The domain portion has to match doesn't it? Why don't we specify just the subdomain?}} | #: {{TBD|The subdomain can be anything. The domain portion has to match doesn't it? Why don't we specify just the subdomain?}} | ||
#: | #: | ||
# {{TBD|LJ Only: | # {{TBD|LJ Only:}} In the '''Catalog Configuration''' section above this one, remove the default URL from the '''Package Catalog URL''' field. (It's an older interface that provides reduced functionality). | ||
===Adding a Package to a Marketplace=== | ===Adding a Package to a Marketplace=== | ||
:--package approval process? | :--package approval process? | ||
Revision as of 01:56, 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 provide information for a catalog listing by clicking [Edit Catalog Info] after publishing a package.
- Service Providers approve a submitted package using Manage Catalog functionality.
Tip:
Service Providers will generally want to enable Tenant Subdomains, as they allow for 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?__
- __TBD: LJ Only:__ In the Catalog Configuration section above this one, remove the default URL from the Package Catalog URL field. (It's an older interface that provides reduced functionality).
Adding a Package to a Marketplace
- --package approval process?