Managing application models

You can manage the application models held in the BMC Discovery system using the Application modeling home page (Model > Applications).

Application modeling home page components

The Application modeling home page shows totals of applications models in the following states:

• Any State—A count of models in any state.
• Not published—Models that have been saved, but not published.

• Review suggested—Sometimes, automatic model updates would change a model a great deal, either in one single change or as a result of a gradual expansion over time. When BMC Discovery detects that an update would cause a large change, it suppresses most of the change, and sets the application model into a state of Review Suggested. When the model enters Review Suggested, only new nodes directly connected to nodes that were previously in the model are added – any nodes down-stream of those new nodes are suppressed. Once the model is in Review Suggested, Discovery no longer updates it during scanning. See Lifecycle of an application model for more details.

• Published—Models that have been published.

• Review suggested—Models that have been published, and require a user review in the same way as the user review described for unpublished models.

• CAM models—Models created using CAM.

• Other BAIs—Other BAIs.

The totals are links to list views or node pages showing the models or BAIs.

The totals content is displayed in tabs which enable you to view totals for:

• All—totals for the BMC Discovery system.

• Favorites—totals for those models marked as your favorites.

When you have saved a model, it is considered a favorite, which is denoted by a blue star under the workflow bar. Clicking the star toggles whether the model is a favorite or not. A blue star shows a favorite, a gray star shows a model that is not a favorite. You can also mark existing models or model definitions as favorites on their view pages.

The Application modeling home page also provides an activity stream which shows a list of modeling related activities for the system.

• Click a row in the activity stream to view the application model.
• Some rows have details links, for example for an operation where nodes were removed from a model. Click details to see an activity record of that operation. For example:
  

You can also see a compact view of application modeling home page on the UI home page.

Creating or importing application models

You can create or import application models from the Application modeling home page. To do this, click Create/Import.

To create an application model using search

When you have clicked Create/Import, the default tab shown is Create Using Search. This directs you to the search box. You can start application modeling anywhere in BMC Discovery.

To create an empty model

You can create an empty application model. When you have created it you can then add nodes to it by searching the data, visualizing, and then adding the data to the empty model using Model > Add to Existing. See Creating an application model for more information.

To do this:

1. Click Create Empty to create an empty model.
2. Enter a name in the name field, and click OK.
   The empty model is created.

To create a Legacy CAM model

You can also start to create a Legacy CAM model. The start point for Legacy CAM is to create a group.

To do this:

1. Click Create Legacy CAM to create an empty group.
2. Enter a name for the group and click Create.
   The empty group is created and the group page displays. See  Creating manual groups and in the Legacy CAM documentation, see Creating the prototype application map.

To import an application model

You can import any of the following:

• A model definition exported from the application editing view.
• A Legacy CAM application mapping definition.
• A zip file containing multiple items (of either or both types).

To do this:

1. Click Import.
2. Click Browse, and in your file browser, locate the name of the file to import.
3. Click OK.
4. Click Apply.
   A results page displays showing the completion of a successful import, or error messages if the import failed.

Related topics

• Creating manual groups
• Creating an application model