Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Options overview

Inside the Service Catalog, the primary purpose of configuring Option Choices is that the cloud administrator allows end users to modify the services they are requesting to meet their specifications. For example, you decide to set up three variations of the Apache server service offering with 0GB, 2GB or 4GB of additional disk space. By using Option Choices, you only need to specify one Service Offering and one Blueprint Deployment model (DM). You then configure three option choices — 0GB, 2GB, and 4GB.


You can also open the Option Choices editor from inside a service offering by clicking the Options tab.

As a result, when end users request a service for a new Apache server, their options are not constrained by the underlying service blueprint. Instead, they can modify the request to specify a Web NIC or additional disk capacity.

If you did not use Option Choices, you would need to specify three Service Offerings and three Blueprint DMs — one each for each GB disk space. If you included a 1 CPU, 2 CPU, or 4 CPU configuration, the number of configurations then increases to nine. The immediate benefit for the cloud administrator is that Option Choices reduce the proliferation of Service Offerings and Service Blueprints that you would need to configure in typical cloud environments.

In the Service Catalog, you can create options for service offerings (request definitions), requestable offerings (post-deploy actions), or any request. An option has one or more choices, each of which has cost and price information. These options and their choices are used when end users make a request in a request console, such as Service Request Management. They are managed separately from offerings because they do not rely on a specific offering. You can reuse options across offerings. You can use any number of options in an offering.

You can also group options into categories visible to end users. For example, a Hardware category might include options for CPU and memory.

Finally, you can set an icon to display the option when a user requests it in the Service Catalog request portal (under Service Instances).

You can use the Blueprint Configuration Editor of the Service Catalog to map options to service blueprints, enabling users to override the original value defined in the service deployment definition. For example, when mapped to the related deployment mode, a memory option choice of 4GB can enable the user to request more memory than originally defined for that deployment definition.

Fulfillment options include:

  • A change to a service blueprint's service definition, such as adding software packages, and tagging service definitions to assist with policy-based placement.
  • A change to a service blueprint's service deployment definition, such as a resource-set change for memory or CPU, and tagging deployment definitions to assist with policy-based placement.

Related topics

Service offerings overview
Requestable offerings overview
Entitlement packages overview
Service Catalog overview
Service blueprints overview

Was this page helpful? Yes No Submitting... Thank you