Manual Application Services - Service Mapping View

[Alec Hanson]

I am trying to get my head around with the new "Application Service" Physical alignment in the CMDB in Paris (v3.0) which is:

I understand that Application Service is now (cmdb_ci_service_auto) and there are child Classes for a variety of  Population Methods.

This states that Manual Application Services are stored in cmdb_ci_service_discovered as previous but now called Mapped Application Service

However if I select the Manual Population Method I have to provide a CI at that point in time, and as this is in effect driving a discovery/service mapping model creates a "Manual Endpoint" CI.

A number of clients are either managing manual data (due to the small size) or using external discovery tools and the end user might not know any CIs at time of creation or it might be a SaaS application without an Infrastructure CI. If you do not enter a manual CI then the Application Service is created as a cmdb_ci_service_auto.

Questions:

1. What does the Manual Endpoint provide within the scope of a 'Manual' Application Service?

2. Is there anyway of creating a Manual Application Service now in Paris without an infrastructure CI within the cmdb_ci_service_discovered class?

3. Does this work with SaaS application services - a very common thing these days?

Any thoughts welcome.

[Barry Kant]

Hi Alec,

not 100% sure, but in the navigation searching for application service gives 2 options:

1 - Configuration / Application Services

2 - CSDM / Managed Technical Services / Application Service

The first selection is the one you describe here. It opens the discovered services view, and when adding a New one it shows the Entry Point form.

The second option is a new wizard like format, that is for better purpose for manual usage.

Why? I don't know. Confusing, yes I think so as well.

Enjoy the weekend,

Barry 

[Alec Hanson Bay]

Thanks Barry. Interestingly for me the new wizard format appears when using either of the navigator options.

[bdubz7]

1. Manual Endpoints are the infrastructure/applications you're manually adding to the manual service. It can be anything you would with Discovered App Services, with the downside of manually maintaining.

2. I believe you can create manual app services without any population methods (or empty). You can actually see this captured in the new Application Service Dashboard with the widget No Population Method Defined

3. Application Service mapping can happen with Cloud Resources - best approach would be to use tag based mapping

[Alec Hanson Bay]

Hi,

1. Thanks I get that, it was the extra CIs that are added that confused me -see picture where I added the Application and a Manual Endpoint was created. However I can see this is only visible on the Legacy CI Relations view (which is still OOTB on Business Services)

2. Yes you can indeed, however they are then created in cmdb_ci_service_auto and not cmdb_ci_service_discovered as the mapping above implies 'Manual' Application Services should be.

3. Yes, assuming you have linkage to the cloud platform in place at that point in time. This also will not support SaaS platforms where there is are no Cloud Resources you can Tag.