Business Application Instance node

Business Application Instance node

A Business Application Instance (BAI) node is a datastore node which represents a running instance of a known business application running in the environment. This node type is composed of a number of Software Instances and/or other Business Application Instances.

Business Application Instance lifecycle

Business Application Instance nodes are created, maintained and destroyed by patterns. Business Application Instance nodes always have a relationship to the Pattern node corresponding to their maintaining pattern.

If a pattern is deleted, any Business Application Instance nodes it is maintaining are immediately destroyed (as are all other nodes it might be maintaining).

Creation/update

When a pattern declares the existence of a Business Application Instance node, it must provide a key for it. If the key matches the key of an existing BAI node, the node is updated, otherwise a new BAI node is created.

Removal

Business Application Instance node can be destroyed either manually or automatically.

To remove a Business Application Instance node manually, find the necessary Business Application Instance, select it in the list and pick Destroy from the Actions list.

Automatic removal happens according to the following scenario

Business Application Instance node patterns normally trigger on the creation or modification of Software Instance or Business Application Instance nodes. In this case, the Business Application Instance nodes are removed using the Cascade removal type; when the triggering Software Instance node or Business Application Instance node is destroyed, the destruction is cascaded to the Business Application Instance. See Cascade Removal.

The situation where the primary data provenance (triggering) SI ages out, that is, not discovered for seven scans and ten days is unlikely as another SI would become primary. The same situation might occur through manual deletion, though this is considered unlikely in a production system.

If a Business Application Instance node is created by a pattern triggered on a node kind other than a Software Instance node or Business Application Instance node, BMC Discovery has no automatic removal behavior. Patterns must be used to explicitly destroy any such Business Application Instance node.

Business Application Instance attributes

The attributes on a Business Application Instance node are as described in the following table:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.

Business Application Instance relationships

The relationships on a Business Application Instance node are as described in the following table:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.

Business Application Instance expressions

The expressions on a Business Application Instance node are as described in the following table:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.