Building service blueprints
Service blueprints define the software, hardware, and deployment options for a service in the Service Catalog. A service blueprint is required before you can create a service. For service blueprint overview information, see Service-blueprints-overview.
For more information about building service blueprints, see the following topics:
Before you begin
You must create and publish to the Product Catalog at least one Virtual Guest Package (VGP) and one System Package (SP) from BMC Server Automation, as described in Creating-objects-in-BMC-Server-Automation.
Service blueprints require a system package to be published to the Product Catalog even if your VGP already defines the OS. This allows the service blueprint's Service Definition to be decoupled and authored independently from the blueprint's Service Deployment Definition.
After the VGP and SP have been added to the Product Catalog, you then can select them as an Installable Resource when you create the service blueprint. For more information, see Creating-service-deployment-definitions-and-resource-sets.
To create a service blueprint
- Create a service blueprint, as described in Creating-or-modifying-a-service-blueprint.
- Define the component connections, as described in Creating-or-modifying-a-connection.
- Define the component operations, as described in Creating-or-modifying-an-operation.
- Define the service deployment definition and resource sets, as described in Creating-service-deployment-definitions-and-resource-sets.
After creating a service blueprint, you can use the blueprint when creating a service, as described in Creating-services.
Related topics