Multiple Environment Business Applications

[Dan74]

Can you have Production and Non Production Business Applications?

I am aware these would usually stand at the application service level but is there any reason not to do it, to separate the environments further for a clearer picture for our users?

The relationship we are currently looking at using are:

Service Offering [Depends on] Business Application [Consumes] Application Services [Depends on] Configuration Items.

Or would we have 2 separate relationships?

Service Offering [Depends on] Application Service

Business Application [Consumes] Application Service

Thank you in advance for your assistance.

Dan

[Daniel Carvalho · Accepted solution]

Hi

The way I do the interpretation on the CSDM diagram, we should not expect a direct relationship from the (green) Service "layer/domain" to the Business Application record (on the blue layer/domain).

Library reference does point to direct connection from service layer to the (yellow domain) of more infrastructure-level items, where we find instances/tenants/deployments of applications (Aka.: Application Services).

I, personally, have always looked to Business Application table (blue domain) as "the concept of a App": E.g. There is a concept of a CRM system. In that sense looking into environment would spoil the broader perception of a "concept".

My take is that it is not recommended to onboard environment into cmdb_ci_business_app.

Cordial

Daniel

[Daniel Carvalho]

From a reporting perspective, I suggest creating a DB view:

DB View idealized to query  2x cmdb_rel_ci joining over itself.

Initial requirement business capabilities x business process x serviceCI.

No filters applied to dbview, therefore it runs on any parent CI class and any children CI class.