- 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-07-2020 01:26 PM
Do you mean Application as in class 'is' application or class 'is a' application? because if you mean application parent class, then application services could be mapped directly to application class components and not necessarily application CIs. In fact, we are planning on reclassing our applications as application services so that the existing IPC task associations are retained.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2020 02:01 PM
Interesting. Do you think you'll be able to maintain the incident, problem, change, etc. history that way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2020 02:08 PM
yes we tested and found that the history is maintained regarding any related incidents, problems, changes, etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2020 01:31 PM
Hi -- since you posted this in the CSDM forum, I assume you also want best practices... so...
A) via automation (discovery/service mapping), the app service is related to apps (running procs) and then to the infrastructure CI. Disco+SM can do this thru automation (very preferred)
but manually:
B) you could create relationships as you depicted. I wouldn't bother if your environment is very big at all.. all this manual hardwiring will get stale soon.. a huge burden to try to keep up to date (read: impossible in large ecosystems). long story short: manually created relationships are typically only feasible in small IT shops. Any big enterprise and manual relationships are a losing effort. Lastly, this approach isn't really adhering to the spirit/intention of CSDM I believe -- but theoretically, AS-->infrastructure is do-able.
Hope this helps?
