Application 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:

Related topics

Creating-service-blueprints

Defining-a-service

FAQ

Default Blueprint for Apache Tomcat Application Server

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 of type Apache Tomcat application server
  • Traversal path and connected nodes: Associated Software Instances, Hosts,  Databases, Load Balancer member nodes, Network interface, and so on, as shown in the following image:
    default_apache_tomcat_blueprint.png
  • Default filter rule:

    • The start node has a set filter criteria, as shown in the image. This criteria automatically filters Apache Tomcat Server applications. Additionally, when creating the service model, the service designer must select the name of the Apache Tomcat Application Server as input.
      apache_blueprint_startnode_filter.png

      Tip

      You can add more filters based on the environment, such as for the additional Software Instance node or the link connecting the Software Instance with the Software Instance.

Default Blueprint for Red Hat JBoss and its connections

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 of type Red Hat JBoss application server
  • Traversal path and connected nodes: Associated Software Instances, Hosts,  Databases, Load Balancer member nodes, Network interface, and so on, as shown in the following image:
    redhat_jboss_bp_v1.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. This criteria automatically filters Red Hat JBoss Application Server applications. Additionally, when creating the service model, the service designer must select the name of Red Hat JBoss Application Server as input.
      redhat_jboss_bp_v1_filter01.png

    • A filter criterion is set on the Software Instance node interconnecting with the Software Instance node. This criterion automatically filters for type Oracle Database Server, Microsoft SQL Server, MYSQL, MYSQL Database Server, PostgreSQL Database Server, or IBM DB2 Database Server applications, as shown in the following image:
      redhat_jboss_bp_v1_filter03.png

    • A filter criterion is set on the Software Instance node interconnecting with the Database node. This criterion automatically filters for type PostgreSQL Database, Oracle Database Server, or SQL Server Database applications, as shown in the following image:
      redhat_jboss_bp_v1_filter02.png

    • A filter criterion is set on the Software Instance node interconnecting with the Host node.
      redhat_jboss_bp_v1_filter04.png

    • A filter criterion is set on the Software Instance node interconnecting with the Software Instance node. This criterion automatically filters for type Apache Webserver applications, as shown in the following image:
      redhat_jboss_bp_v1_filter05.png

Default Blueprint for Microsoft IIS Webserver

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 IIS Webserver 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 Instance of type Microsoft IIS Webserver
  • Traversal path and connected nodes: Associated Software Clusters, Software Instances, Software Components, Hosts,  Databases, Load Balancer member nodes, Storage, and so on, as shown in the following image:
    MS_IIS_WS_2.0.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. This criteria automatically filters Microsoft IIS Webserver applications. Additionally, when creating the service model, the service designer must select the name of IIS Webserver as input.
      MS_IIS_WS_2.0_filter_rules_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:
      MS_IIS_WS_2.0_filter_rules_part2.png

Earlier version of this blueprint 

Click here to expand.

Use this application blueprint to create business services by using Microsoft IIS Webserver.

Discontinued version

Starting 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: Software Instance
  • Traversal path and connected nodes: Software Component, Host, Network Interfaces, and Network Device, as shown in the following image:
    MS_IIS_WS_1.0.png
  • Default filter rules: The start node has a set filter criteria, as shown in the image. This criteria automatically filters Microsoft IIS Webserver applications. Additionally, when creating the service model, the service designer must select the name of IIS Webserver as input.
    MS_IIS_WS_2.0_filter_rules_part1.png

Default Blueprint for Microsoft SharePoint Server

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 of type Microsoft SharePoint Server
  • Traversal path and connected nodes: Associated Software Instances, Software Clusters, Software Components, Hosts, Load Balancer member nodes, and so on, as shown in the following image:
    Ms_sharepoint_2.0.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. This criteria automatically filters Microsoft SharePoint Server applications. Additionally, when creating the service model, the service designer must select the name of Microsoft SharePoint Server as input.
      Ms_sharepoint_2.0_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:
      Ms_sharepoint_2.0_filter_part2.png

Default Blueprint for Microsoft Skype for Business Site

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 Cluster of type Microsoft Skype for Business
  • Traversal path and connected nodes: Associated Software Cluster, Software Instances, Software Component, Hosts, Database, Load Balancer member nodes, Network Interfaces, and Network Devices, as shown in the following image:
    MS_skype_2.0.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. This criteria automatically filters Microsoft Skype for Business Cluster. Additionally, when creating the service model, the service designer must select the name of the Start CI node as input.
      MS_skype_2.0_filter_part1.png

    • A filter criterion is set on the Software Instance node that interconnects with the Database and Host nodes. This criterion automatically filters Microsoft SQL Server applications, as shown in the following image:
      MS_skype_2.0_filter_part2.png


Default Blueprint for SAP

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 SAP System ID, 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 instance of type SAP Java Server Process
  • Connected nodes: Associated Software Instances, Hosts, Databases, Virtual Machine, Storage member nodes, Hardware Containers, Network Interfaces, and so on, as shown in the following image:
    SAP_2.0.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. This criteria automatically filters SAP Java Server Processes. Additionally, when creating the service model, the service designer must select the name of SAP System Id as input.
      SAP_2.0_filter_part1.png

    • A filter criterion is set on the Software Instance node interconnecting with the Host node. This criterion automatically filters the SAP Enqueue Server or SAP Enqueue Replication Server applications, as shown in the following image:
      SAP_2.0_filter_part2.png

    • A filter criterion is set on the Software Instance node interconnecting with Cluster, Database, and Host nodes. This criterion automatically filters the Oracle Database Server applications, as shown in the following image:
      SAP_2.0_filter_part3.png

    • The default Filter by Kind link rule is enabled between both instances of Virtual Machine and Host node connections, as shown in the following image:
      SAP_2.0_filter_part4.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: Software instance of type SAP Java Server Process
  • Traversal path and connected nodes: Associated Software Instances, Hosts, Database, Cluster, and so on, as shown in the following image:
    SAP_1.0.png
  • Default filter rules:
    • The start node has a set filter criteria, as shown in the image. This criteria automatically filters SAP Java Server Processes. Additionally, when creating the service model, the service designer must select the name of SAP Java Server Process as input.
      SAP_1.0_filter_part1.png

    • A filter criterion is set on the Software Instance node interconnecting with the Host node. This criterion automatically filters the SAP Enqueue Server or SAP Enqueue Replication Server applications, as shown in the following image:
      SAP_1.0_filter_part2.png

    • A filter criterion is set on the Software Instance node interconnecting with the Cluster, Database, and Host nodes. This criterion automatically filters the Oracle Database Server applications, as shown in the following image:
      SAP_1.0_filter_part3.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*