- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2020 01:11 PM
Just starting my crawl... can I directly relate my Application Service (i.e. "Sales - Prod") to my Infrastructure CIs (i.e. "Unix Server ABC" and "Oracle DB XYZ") or must I include Application in-between: Application Services --> Application --> Infrastructure CIs?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2020 02:17 PM
Hi -- close, but typically the application CI is the installation of a running process (although other ways exist, this is very common). i.e. Discovery finds XYZ windows process running, and therefore create an application CI that represents the running proc. With disco, this happens automatically for things like SQL, Apache, etc... each found running process becomes an application CI.
So the relationship is like: Service > Application CI (running proc) > server its hosted upon.
Hope this helps?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2020 06:52 PM
Remember what your Application Service is :: it is the "entry point" into your application ... meaning ... this is where Service Mapping takes over. So [when] you are mapping a Business Service / Application the Application Service is where you start and then let Mapping take over. Now ... if you don't have Service Mapping ... then this part is still a manual process and remains a manual process until you get to the infrastructure CI's where Discovery takes over. I have been on a few engagements where we have went from Application Service directly to infrastructure CI's. Not 'best practice', however does occur in more than a few occasions. I think it is a learning process to understand what the difference is between an Application Service and an Application in terms of CSDM but it is necessary in that this is the model that we are driving to.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2020 06:55 AM
Thank you, very helpful.
So best practice is the Server CI is associated to an Application CI (with a "Runs On" relationship) and the Application CI is associated to an Application Service (with a "Depends On" relationship). But this depends on our Service Mapping and Discovery capabilities and SN will support server CI association directly to an Application Service (I assume this will be with a "Runs On" relationship).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2020 04:23 AM
Although the correct solution for CSDM is App Service -> Application -> Infrastructure, I have also been in a engagements where it is App Service -> Infrastructure.
I would say that this is a maturity PoV. The company might not be adopting Discovery / Service Mapping, might have their own Discovery and/or App service -> Infrastructure might be mature and maintainable via appropriate processes.
However I agree that the maturity should be to move from App service -> Infrastructure to App Service -> Application -> Infrastructure by rolling out appropriate automation/discovery to the above to get the correct level of granularity and Verification of App Service coverage.
