Manual creation of Application Services and Topology map

david_legrand
Kilo Sage

Hi Community,

 

One of my customer does the ITOM discovery/Service Mapping outside ServiceNow and provide the info via REST.

So I creates via transform map:

find_real_file.png

* Application Service (cmdb_ci_service_discovered)

* Relationship to Business Application (cmdb_rel_ci and cmdb_ci_business_app)

* Relationship to my "top CI" in the CMDB (cmdb_ci_endpoint_manual, sa_m2m_service_entry_point, cmdb_rel_ci and my technical top CI)

* Nota Bene: The kubernetes ojects are custom because it's apparently required to have ITOM to have the Vanilla classes.

* I added a link to Business Service Offering directly on the Application Service as I was thinking it could be important for the Topology map, without success.

 

I thought I had all the required objects created but the topology map (when we click view map from the application service record) remains empty. The Dependency View map is generated properly and I tell the customer to use that one on the case/incident so far. Do you see something missing?

find_real_file.png

1 ACCEPTED SOLUTION

Vishal Savajia1
Kilo Sage

Hi David, 

Please see below Steps for creation of  Entry point for One CI, Now as you are using Custom Integration, Kindly verify your Transform Maps, are they creating end points for respective CI. 

Procedure

  1. Navigate to Configuration > CI Class Manager.
  2. To create a standard entry point, right-click Endpoint from the Class Hierarchy pane and select Add Child Class.
  3. To create an entry point of the inclusion type, right-click Inclusion Endpoint from the Class Hierarchy pane and select Extend.
  4. Create an entry point type using the following parameters.
    See Create a table.
    New table form
    FieldDescription
    LabelEntry point type name. For example, HTTP entry point.
    NameThe table name. For example, cmdb_ci_endpoint_http.
    Extends tableThe table name of the parent CI type is automatically filled by the system:
    • cmdb_ci_endpoint - for entry points
    • cmdb_ci_endpoint_inclusion - for entry points of the inclusion type
  5. Add entry point attributes on the Columns tab at the bottom of the page.
    By default the new entry point derives attributes from its parent CI, but you can modify the attributes as necessary.
  6. Click Submit.

 

Please see this too.

Manually add CIs to an application service | ServiceNow Docs

Warm Regards, 

 

Vishal Savajiani

 

View solution in original post

2 REPLIES 2

Vishal Savajia1
Kilo Sage

Hi David, 

Please see below Steps for creation of  Entry point for One CI, Now as you are using Custom Integration, Kindly verify your Transform Maps, are they creating end points for respective CI. 

Procedure

  1. Navigate to Configuration > CI Class Manager.
  2. To create a standard entry point, right-click Endpoint from the Class Hierarchy pane and select Add Child Class.
  3. To create an entry point of the inclusion type, right-click Inclusion Endpoint from the Class Hierarchy pane and select Extend.
  4. Create an entry point type using the following parameters.
    See Create a table.
    New table form
    FieldDescription
    LabelEntry point type name. For example, HTTP entry point.
    NameThe table name. For example, cmdb_ci_endpoint_http.
    Extends tableThe table name of the parent CI type is automatically filled by the system:
    • cmdb_ci_endpoint - for entry points
    • cmdb_ci_endpoint_inclusion - for entry points of the inclusion type
  5. Add entry point attributes on the Columns tab at the bottom of the page.
    By default the new entry point derives attributes from its parent CI, but you can modify the attributes as necessary.
  6. Click Submit.

 

Please see this too.

Manually add CIs to an application service | ServiceNow Docs

Warm Regards, 

 

Vishal Savajiani

 

Ouch, so I still miss some records in this schema, thanks mate, I'm trying to do that.

Maybe I'll have to check if there is an online class on that stuff before the CMDB is way more complex than what I used to have.