Source data for lower environment urls

[Karen_K]

Our security team wants to know urls for instances of our business applications in all environments as we have exposure through both prod and non-prod instances. During service mapping exercises, our clients provided production urls which are stored in the HTTPS Endpoint table. I am looking for the following guidance around non-prod urls.

1) Is there a table and/or process in ServiceNow for retaining lower environment urls?

2) Are there any SNOW clients that track non-prod urls in SNOW that would be willing to share their experiences?

[Niklas Peterson]

Hi,

Application Services are the logical representation of an installation of a Business Application. If you have the need to represent the non-prod instances of the Business Application, you should create Application Services for those environments as well. There is really no difference if an Application Service is prod och non-prod, they are setup the same. There is an attribute called Environment to describe the type of environment.

Regards,
Niklas

[Karen_K]

Thanks for responding Niklas! I have been out of the office and am just now digesting the information you shared. 

I understand that non-prod and prod urls should be part of the appropriate Application Service. Can you help me understand in more detail?

• Is the url manually entered into the Application Service?
• Our prod urls are stored in the HTTPS Endpoint table. What table holds the non-prod url information?
• Is it necessary to create a custom field need to accommodate the environment?

[VigorousRefiner]

Thanks for your response, Niklas! I've been out of the office, so I'm just now catching up on the information you shared.

I understand that the non-prod and prod URLs should be part of the appropriate Application Service, but could you explain that in a bit more detail?

Is the URL manually added to the Application Service? For our setup, we store prod URLs in the HTTPS Endpoint table—where would the non-prod URLs be stored? Also, do we need to create a custom field to differentiate between environments?

Appreciate your help!

[Niklas Peterson]

Hi,

Configuration items are classified based on what they are, not how they are being used. Which means you should used the same class regardless of if they are production CIs or non-production CIs. The Environment attribute is available on cmdb_ci table so no need to create a custom attribute to differentiate between environments.

Regards,
Niklas