Skip to Content
Information
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.

Service blueprint enhancements

With BMC Cloud Lifecycle Management 3.0.00, the following changes have been made to service blueprints.

Adding application parameters to service blueprints

Service blueprint parameters benefits both end-users and cloud administrators.

Task

Example

Prompt end-users for data during the service request

Configure specific application settings, like DB Instance ID or Web Server Port

Pass values from either the end-user or the cloud administrator into BMC BladeLogic Server Automation jobs, NSH scripts, and Atrium Orchestrator workflows.

Create one parameterized BSA package for an application instead managing multiple permutations for each settings

The business value for BMC customers is that application parameters deliver more complete services with less post-deployment configuration. Benefits include:

  • More agile business with faster full service delivery
  • Reduced cost of service delivery through increase automation
  • Improved consistency through well defined service delivery processes

Enhancements to the Service Blueprint Definition editor

In the 3.0 release, BMC made the following enhancements to the Service Blueprint Definition editor.

Component

Enhancement description

Can easily navigate between components, connections, operations, and parameters

Can choose protocols and ports
Note: Starting with the 3.0 release, connections between components are unidirectional.

Can define Package Installation Parameters, Post Deployment Actions, and Network Paths (all new to 3.0)

Can define additional virtual system disks and post-deployment actions

Can define NICs and virtual load-balancer (VLB) pools more precisely :

  • NICS — Can assign private IP and NAT address. Can use network labels or tags to select networks.
  • VLB pools — Can assign NAT address. Can use network labels or tags to define client network.

Can add parameters to the Service Definition at the functional model level, or the Service Deployment Definition (SDD) at the deployment model level.

Can select BMC Atrium Orchestrator workflow that runs a particular action after the SDD is provisioned

Can define new or pending network paths between resource sets

Can export or import two versions of service blueprint .json files (1.0 and 2.0) as needed.

 

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

BMC Cloud Lifecycle Management 3.0