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.

Creating a requestable offering

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

However, the Service Request Designer does not support change policy. To implement change management, you cannot use Service Request Designer, and you must use the Requestable Offering Definition window.

This topic consists of the following sections:

Before you begin

  • Create a service with at least one service offering.
  • (Optional) Define the options and option choices.

Note

Request definitions and post-deploy actions must have unique names across all service offerings.

To create a request definition

 

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

To edit a request definition

  1. Select a service offering.

  2. Click Edit the request definition.edit_requestable_definition_window.png

    Tip

    For advanced editing, you can select the request definition, and then click Edit request definition with SRD Designer.edit_service_request_designer.png

  3. Take the SRD offline to edit the request definition, or online so that it is visible to end-users.
    OfflineSRD.gif
    • Offlinedisables the SRD so that it is no longer deployed and end-users cannot access it from the Service Catalog.

    • Onlineredeploys the SRD and users can once again access it.

      Note

      The Offline and Online options do not appear when you create a request definition; they are only available in edit mode.

  4. Click Next.
    EditSRD.gif
  5. Modify the navigational category or packages that are associated with the request definition.
  6. Click Finish.
  7. To take the SRD back online, edit the request defintion and click Online.
    OnlineSRD.gif

To create a post-deploy action

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

To edit a post-deploy action

Important

BMC Cloud Lifecycle Management allows you to change the CPU or memory values only if your operating system supports the hotplug capability. That is, you can change components such as CPU and memory without shutting down and rebooting the operating system.

If your operating system does not support the hotplug capability, you receive an error message. For example, the message "CPU hot plug not supported for this virtual machine" results from an attempt to change the CPU. The message "The operation is not supported on the object" results from an attempt to change the memory. The workaround is to manually shut down the impacted system before attempting to update the CPU or memory.

  1. If updating CPU or memory and the impacted operating system does not have hotplug capability, power down the system.
  2. Select a service offering.
  3. Select a post-deploy action.
  4. Click Edit a post-deployment action.edit_requestable_definition_window.png
  5. For advanced editing, select the post-deploy action, and click Edit post-deploy action with SR Designer. edit_service_request_designer.png
    The Service Request Designer appears.
  6. In the Requestable Offering Definition or Service Request Designer window, click Online to change it to Offline.
  7. Modify the post-deploy action.
  8. Click Offline to change it to Online.
  9. Click Save.
  10. Reboot the operating system if you shut it down in step 1.

Related topics

Creating-new-services-for-the-Service-Catalog
Creating-a-service-offering
Service-Catalog-options-and-option-choices
Integrating-with-BMC-Change-Management

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*