Mainframe 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 Mainframe LPAR to connected Softwares

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: Mainframe (MF) Part 
  • Traversal path and connected nodes: Associated Mainframe, Software Instances, and Clusters interconnected with other Software Instances and Databases, as shown in the following image:
    mainframe_lpar_2.0_244.png
  • Default filter rules: The filter criteria are set in the start node, as shown in the following image. The service designer needs to select the name of a Start CI as input when creating the service model. 
    mainframe_lpar_2.0_filter_part1_244.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 includes information of all the interconnected nodes, their relationships, and the default filter criteria as follows:

  • Start node: Mainframe (MF) Part 
  • Traversal path and connected nodes: MF Part interconnected with Software Instance and Cluster, as shown in the following image:
    mainframe_lpar_1.0.png
  • Default filter rules:
    • The filter criteria are set in the start node, as shown in the following image. The service designer needs to select the name of a Start CI as input when creating the service mode.
      mainframe_lpar_1.0_filter_part1.png

    • The default link rule Filter by Kind is enabled between the MF Part and Software Instance node connection, as shown in the following image:
      mainframe_lpar_1.0_filter_part2.png

    • The default link rule Filter by Kind is enabled between the MF Part and Cluster node connection, as shown in the following image:
      mainframe_lpar_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*