Can't manage to map a service
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2018 08:22 AM
Hi!
I've been training myself on my sandbox instance on ServiceNow (especially with Service Mapping) and I've decided to create a "Web Application", it's pretty basic honestly. I've coded several PHP Websites on my Virtual Ubuntu Machine on my Apache Web Server.
This Web Application is very basic, it's a sign-up form from which the data put in is transfered to a database on a MySQL instance. Everything works, no issue with either the Web Server, the Web App or the Database.
With Discovery, both Web Server and the MySQL instance are detected. Good.
With Service Mapping, the Web Server is mapped, that's good. But only the Web Server. Isn't Service Mapping supposed to connect the Web Server with the instance?
If so, why doesn't it appear?
P.S : The Tomcat server is my Apache GUI, I thought I'd try service mapping from there but it didn't work as well.
Thank you in advance for your help,
Fares K.
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2018 12:48 AM
Hi Dave,
Thanks for your answer. What I don't understand is that I thought that SM was supposed to automatically create those connections using specific patterns?
Or am I creating a connection because this particular pattern is unknown to ServiceNow?
Once again, thank you for your answer, it's been helpful.
P.S : Where do I find the "CREATE CONNECTION" option?
Fares K
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-06-2018 06:18 AM
That's correct Fares - there are many connection options we provide out of the box, but there may not be one to the technology you are looking for. If you open the discovery log once the mapping completes, you will see all the things it tries to connect to and may then need to open the pattern, add a connection section at the bottom, and from there you will get an operation option to 'create connection'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2018 03:05 AM
Hi Nick!
I tried doing that and I don't know whether that changed anything but I know have a new issue : my Service Mapping either :
1 - tell me that my host at that specific address isn't accessible and that it doesn't exist in my CMDB even though :
and
and/or
2 - Service Mapping goes fetching in a totally different address :
Why does it go fetching in a totally different address? I checked whether I may have incorrectly typed the IP Address but I don't seem to see where. I checked the Pattern Designer where I created a specific connection pattern and all the information seems to be from the CMDB.
Thanks in advance for your help.
Fares K.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2018 06:33 AM
Hi Fares - are there multiple interfaces on that system? Your URL shows the 172.19.49.86 address, then the terminal shows 172.19.49.95, then the second error shows 176.19.49.86, so not sure if that is a configured interface on the server that is part of a configuration file we're reading to gather the connection information... which is how it should be operating.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2018 06:45 AM
Hi Nick
The "172.19.49.95" is the broadcast IP Address and when you ping that one, nothing returns.
And about the 176.19.49.86 address, I tried to read the Discovery Logs:
"Endpoint Details: Endpoint Type: HTTP(S) Endpoint IP Address: 176.19.49.86 Target Name: Apache server@fares-virtual-machine URL: http://176.19.49.86/create.php"
Even though I do admit that throughout the trials I may have mistyped 176 instead of 172, what I don't know is why it stayed that way. I keep using "Add Management IP Address" to try to correct it but it doesn't work.