1 of 1 people found this helpful
For application modelling you can have 4 approaches.
4) Pattern Based application model
Static Model approach : In this approach, though it does not create BAI in Discovery, it create application CI in CMDB when sync happens. Sync mapping patterns looks at your defined static group and creates appropriate CI in CMDB. Once application CI is created rest of the eco system can use this information like any other approach.
Unpublish model approach (SAAM) : This is not a approach but a state in SAAM. When you unpublish the model then Discovery deletes the BAI which it has created in Discovery and same gets deleted in CMDB after successful sync. When you will publish the model again that time it will create BAI again based on what is currently present in Discovery.
Please note : Model definition of your model stay as it is but BAI gets deleted when you unpublish the model.
Saurabh, thanks for the above.
I have another query, say when we do SAAM modelling and to avoid the addition of too many nodes to the existing model to gain static nature and avoiding maintenance.
Can we keep those model in an" UNPUBLISHED" State.
what are the pros and cons.
As soon as you unpublish the model then your BAI gets deleted. i.e. you do not have model left in Discovery. As model itself has deleted there is no question on avoiding too many updates.
You will only have model definition referring to nodes and from that definition you can again create a model based on new criteria.