Top-Down Service Mapping

[abhijee]

Hello Team,

I have a Top-Down Service Mapping requirement for an OpenText application hosted on AWS IaaS (Infrastructure as a Service). Based on my basic understanding, to get started we would need the application entry point and the required credentials/access.

Apart from that, I would like to understand what other information or prerequisites we should request from the client before starting the Service Mapping implementation.

For example, should we ask the client for:

Application entry point/URL Application servers and hostnames AWS account/VPC/subnet details Load balancer details Database and other backend dependencies Application ports and protocols AWS tags used to identify the OpenText application Application architecture/dependency diagram Any external integrations or dependencies Also, since the application is hosted on AWS, can we use Tag-Based Service Mapping along with Pattern-Based Discovery, if feasible?

If anyone has real-world experience implementing Service Mapping for an application like OpenText hosted on AWS, I would really appreciate your guidance on the recommended approach.

I’m new to Top-Down Service Mapping, so any practical guidance on where to start, what client information to collect, what needs to be discovered, and how to combine tag-based mapping with pattern-based discovery would be very helpful.

Thank you in advance!