OCI Application Listings, Artifacts, and Private Offer Entitlements for SaaS and PaaS
When a publisher creates a private offer, one or more OCI application listings must be attached. Whether the publisher’s solution is delivered by SaaS or PaaS, the publisher must have an artifact that is deployable to a customer’s tenancy to create an OCI application listing.
An artifact is a deployable software package. The simplest artifact is an OCI Compute image. For example:
- A gateway VM that enables access to a customer's environment for the publisher's SaaS or PaaS.
- A VM that contains developer tooling such as scripts that make API calls, SDKs, or CLIs related to the publisher's SaaS or PaaS.
When a publisher attaches listings to a private offer, they must identify a unit of measure and quantity for the listings. The unit of measure is defined when the publisher enables the listing for private offers. The quantity in the unit of measure for the listings defines the entitlement under the private offer. Monitoring the consumption of the entitlement is the responsibility of the publisher.