Infrastructure blueprints

BMC Helix AIOps offers several out-of-the-box blueprints that are ready to use and consist of rule-based templates for creating services or applications. Find the details of the default application blueprints in the following sections:

The out-of-the-box blueprints that apply to the SaaS (Cloud) infrastructure are:

The out-of-the-box blueprints that apply to an on-prem infrastructure are:

Related topics

Creating-service-blueprints

Defining-a-service

FAQ



Default Blueprint for Cloud Region

Use this default blueprint to create a technical service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Cloud Region
  • Traversal path and connected nodes: Cloud Service, Cloud Provider, Cloud Resource, and Administrative Collection nodes, as shown in the following image:
    cloud_region_1.0_244.png
  • Default filter rules: The start node has a set filter criterion, as shown in the image. When creating the service model, the service designer must select the names of Cloud Region deployments as input.
    cloud_region_1.0_filter_part1_244.png


Default Blueprint for Cloud Service

Use this default blueprint to create a technical service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Cloud Service
  • Traversal path and connected nodes: Administrative Collection, Load Balancer Service, Virtual Machine, and so on, as shown in the following image:
    cloud_service_1.0_244.png
  • Default filter rules: The start node has a set filter criterion, as shown in the image. When creating the service model, the service designer must select the names of Cloud Region deployments as input.
    cloud_service_1.0_filter_part1_244.png


Default Blueprint for Virtual Host With Cloud Associations

Use this default blueprint to create a technical service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Virtual Machine
  • Traversal path and connected nodes: Host, Load Balancer Member nodes, Cloud Service, Cloud Provider, Cloud Resource, and Administrative Collection nodes, as shown in the following image:
    virtual_host_cloud_associations_244.png
  • Default filter rules: The start node has a set filter criteria, as shown in the image. The criteria automatically filter any matching cloud-hosted instances, such as AWS, Google, Microsoft Azure, Alibaba, IBM, or OCI. Additionally, when creating the service model, the service designer must select the names of Cloud Hosted Virtual Machine Instances as input.
    virtual_host_cloud_associations_filter01_244.png


Default Blueprint for Control-M Enterprise Manager

Use this default blueprint to create a business application or business service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Software Instance
  • Traversal path and connected nodes: Software Instance, Host, Database, Virtual Machine, Host, Network Interfaces, Network Device, and so on, as shown in the following image:
    control_m_enterprise_mgr_1.0_244.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. The criteria automatically filter the Oracle WebLogic Server Clusters. Additionally, when creating the service model, the service designer must select the names of the Oracle WebLogic Server Cluster as input.
      control_m_enterprise_mgr_1.0_filter01_244.png

    • The default filter rule that applies to all instances of the Software Instance node where it appears immediately after a Host node is as shown in the following image:
      control_m_enterprise_mgr_1.0_filter02_244.png

    • The filter rule that applies to the Software Instance node with the Software Instance as its parent and grandparent nodes is as shown in the following image:
      control_m_enterprise_mgr_1.0_filter03_244.png

    • The default Filter by Kind link rule is enabled between all instances of the Virtual Machine and Host node connections, as shown in the following image:
      vm_vcluster_2.0_filter_part3.png


Default Blueprint for Microsoft Cluster

Use this default blueprint to create a business application or business service.

Important

If this blueprint has multiple versions, the version is added to the Description field, for example, Using Microsoft Cluster Name, v2.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Cluster of type Microsoft Cluster
  • Traversal path and connected nodes: Clusters, Load Balancer member nodes, Deployments, Virtual Machine, Administrative Collection, Storage nodes, and so on as shown in the following image:
    MS_cluster_2.0_244.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. The criteria automatically filter Microsoft Clusters. Additionally, when creating the service model, the service designer must select the name of Microsoft Cluster as input.
      MS_cluster_2.0_filter_part1_244.png

    • The default Filter by Kind link rule is enabled between the Virtual Machine and Host node connection, as shown in the following image:
      MS_cluster_2.0_filter_part2.png

Earlier version of the blueprint

Click here to expand.

Discontinued versionStarting with version 24.1.01, BMC has released version 2.0 of this out-of-the-box blueprint and no longer supports version 1.0. However, if you want to continue using version 1.0, export the blueprint from the earlier version of BMC Helix AIOps and import it into the current version of BMC Helix AIOps.

Version 1.0 nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Cluster of type Microsoft Cluster
  • Traversal path and connected nodes: Associated Cluster, Software Instance, Database, Host, Network Interfaces, and Network Device as shown in the following image:
    MS_cluster_1.0.png
  • Default filter rules: The start node has a set filter criteria, as shown in the image. The criteria automatically filter Microsoft Clusters. Additionally, when creating the service model, the service designer must select the name of Microsoft Cluster as input.
    MS_cluster_1.0_filter_part1.png


Default Blueprint for Oracle WebLogic Cluster

Use this default blueprint to create a business application or business service.

Important

If this blueprint has multiple versions, the version is added to the Description field, for example, Using Oracle WebLogic Cluster Name, v2.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Software Cluster of type Oracle WebLogic Server Cluster
  • Traversal path and connected nodes: Cluster, Host, Virtual Machine, Host, Network Interfaces, Network Device, and so on, as shown in the following image:
    oracle_weblogic_cluster_2.0_244.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. The criteria automatically filter Oracle WebLogic Server Clusters. Additionally, when creating the service model, the service designer must select the name of the Oracle WebLogic Server Cluster as input.
      oracle_weblogic_1.0_filter_part1_244.png

    • The default Filter by Kind link rule is enabled between the Software Cluster and Database node connection, as shown in the following image:
      oracle_weblogic_1.0_filter_part2.png

    • The default Filter by Kind link rule is enabled between the Virtual Machine and Host nodes connection, as shown in the following image:
      oracle_weblogic_1.0_filter_part8.png

Earlier version of the blueprint

Click here to expand.

Discontinued version

Starting with version 24.1.02, BMC has released version 2.0 and no longer supports version 1.0 of this out-of-the-box blueprint. However, if you want to continue using version 1.0, export the blueprint from the earlier version and import it into the current version of BMC Helix AIOps.

Version 1.0 nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Software Cluster of type Oracle WebLogic Server Cluster
  • Traversal path and connected nodes: Cluster, Host, Virtual Machine, Host, Network Interfaces, Network Device, and so on as shown in the following image:
    oracle_weblogic_1.0.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. The criteria automatically filter Oracle WebLogic Server Clusters. Additionally, when creating the service model, the service designer must select the name of the Oracle WebLogic Server Cluster as input.
      oracle_weblogic_1.0_filter_part1.png

    • The default Filter by Kind link rule is enabled between the Software Cluster and Database nodes, as shown in the following image:
      oracle_weblogic_1.0_filter_part2.png

    • The default Filter by Kind link rule is enabled between the Software Cluster and Software Component nodes, as shown in the following image:
      oracle_weblogic_1.0_filter_part3.png

    • The default Filter by Kind link rule is enabled between the Software Instance and Software Instance nodes, as shown in the following image:
      oracle_weblogic_1.0_filter_part4.png

    • The default Filter by Kind link rule is enabled between the Software Instance and Software Instance nodes, as shown in the following image:
      oracle_weblogic_1.0_filter_part5.png

    • The default Filter by Kind link rule is enabled between all the Software Instance and Software Component nodes, as shown in the following image:
      oracle_weblogic_1.0_filter_part6.png

    • The default Filter by Kind link rule is enabled between the Software Instance and Database nodes, as shown in the following image:
      oracle_weblogic_1.0_filter_part7.png

    • The default Filter by Kind link rule is enabled between the Software Instance and Host nodes, as shown in the following image:
      oracle_weblogic_1.0_filter_part8.png

    • The default Filter by Kind link rule is enabled between the Load Balancer Service and Load Balancer Pool and between the Load Balancer Pool and Load Balancer Member nodes, as shown in the following image:
      oracle_weblogic_1.0_filter_part9.png

    • The default Filter by Kind link rule is enabled between the Load Balancer Member and Software Instance nodes, as shown in the following image:
      oracle_weblogic_1.0_filter_part10.png


Default Blueprint for vCenter Cluster

Use this default blueprint to create a business application or technical service.

Important

If this blueprint has multiple versions, the version is added to the Description field, for example, Using Blueprint for VCenter Cluster Name, v2.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Cluster of type VMware vCenter Cluster
  • Traversal path and connected nodes: Associated Cluster, Software Instance, Host, Virtual Machine, Storage nodes, and so on, as shown in the following image:
    vm_vcluster_2.0_244.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. The criteria automatically filter VMware vCenter Clusters. Additionally, when creating the service model, the service designer must select the name of the VMware vCenter Cluster as input. 
      vm_vcluster_2.0_filter_part1_244.png

    • The filter criterion in the Software Instance node, which is the immediate child of the start node, is shown in the following image. This criterion automatically filters applications of type VMware vCenter Server.
      vm_vcluster_2.0_filter_part2_244.png

    • The default Filter by Kind link rule is enabled between the Virtual Machine and Host node connection, as shown in the following image:
      vm_vcluster_2.0_filter_part3.png

Earlier version of the blueprint

Click here to expand.

Discontinued versionStarting with version 24.1.01, BMC has released version 2.0 of this out-of-the-box blueprint and no longer supports version 1.0. However, if you want to continue using version 1.0, export the blueprint from the earlier version of BMC Helix AIOps and import it into the current version of BMC Helix AIOps.

Version 1.0 nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

  • Start node: Cluster of type VMware vCenter Cluster
  • Traversal path and connected nodes: Cluster, Host, Virtual Machine, Host, Network Interfaces, Network Device, and so on, as shown in the following image:
    vm_vcluster_1.0.1.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. The criteria automatically filter VMware vCenter Clusters. Additionally, when creating the service model, the service designer must select the name of the VMware vCenter Cluster as input. 
      vm_vcluster_1.0.1_filter_part1.png

    • The default Filter by Kind link rule is enabled between the Virtual Machine and Host node connection, as shown in the following image:
      vm_vcluster_1.0.1_filter_part2.png

Where to go from here

Creating-service-models

 

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