Application blueprints

Default Blueprint for Microsoft IIS Webserver

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

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:
  
  
• 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 Microsoft IIS Webserver as input.
    
    
    
  • The default Filter by Kind link rule is enabled between the Virtual Machine and Host node connection, as shown in the following image:
    

Earlier version of this blueprint 

Default Blueprint for Microsoft SharePoint Server

Use this application blueprint to create business services by using Microsoft SharePoint Server applications.

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:
  
• 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.
    
    
    
  • The default Filter by Kind link rule is enabled between the Virtual Machine and Host node connection, as shown in the following image:
    

Default Blueprint for Microsoft Skype for Business

Use this application blueprint to create business services by using Microsoft Skype for Business applications.

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:
  
  
• Default filter rules:
  • The start node has a set filter criteria, as shown in the image. This criteria automatically filters Microsoft Skype for Business applications. Additionally, when creating the service model, the service designer must select the name of Microsoft Skype for Business as input.
    
    
    
  • 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:
    

Default Blueprint for SAP

Use this application blueprint to create business services by using SAP.

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:
  
  
• 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.
    
    
    
  • 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:
    
    
    
  • 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:
    
    
    
  • 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:
    

Earlier version of the blueprint

Where to go from here

Creating-service-models