Use > Functionalities > Service Modeling > Service Modeling Setup

Service Modeling Setup

This section describes the necessary setup before running Service Modeling.

ClosedSet up the Data Flow Probes

  • Verify that the Data Flow Probe is installed on a Windows machine

    Note The Data Flow Probe installed on a Linux platform is intended for the CMS Sync integration only, but not for discovery.

  • Determine the network range of the network to be discovered

    Note  

    • You must configure the probe's IP address in the probe range.
    • A Service Discovery activity will only try to connect to those IP addresses that may potentially be relevant for the discovered services, not to every IP address in the range. Make sure the network range is wide enough and contains all the IP addresses for your discovered services.

  • Set the relevant credentials

    To enable the Data Flow Probes to connect to servers or applications using specific protocols, you must set the relevant credentials. Make sure the credentials have enough privilege; the root or root-equivalent privilege is highly recommended.

    Note The Data Flow Probe tries to connect to a node by using each credential in turn. Universal Discovery then saves the successful credential. The next time the Data Flow Probe connects to this node, it first tries to connect using the successful credential.

ClosedPrerequisites
  • The UCMDB Server has been upgraded to 10.22 (or later) with Content Pack 18 (or later).
  • The related credentials (NTCMD, SSH, and Universal Discovery Protocol) have been imported and verified.

  • The load balancers are discovered.

    If the services to be discovered contain a load balancer, run the load balancer discovery before you discover any services.

  • The lsof utility is installed on UNIX machines.

    The lsof utility can capture the TCP traffics between the discovered UNIX machines, and can check which process is listening on which port.

  • The credentials have sudo permissions on UNIX machines.

  • The web access management products are discovered.

    If the services to be discovered contain web access management products (such as WebSEAL), run the discovery jobs for them before you discover any services.

  • The services are not deployed on Solaris Local Zone.

    Solaris Local Zone is not supported by ASM.

  • The IIS Web Server should be IIS 7.0 (or later) on Microsoft Windows Server 2008 (or later).