Page tree
Skip to end of metadata
Go to start of metadata

The following steps provide the summary of creating discrete and distributed service models. The steps to create discrete and distributed service models are the same except for the Yes and Propagate setting. See To specify attributes for configuration items.

  1. Create a service model by using BMC Impact Model Designer on a TrueSight Infrastructure Management Server. For information, see Designing a service model.

    Notes

    1. If you are creating a distributed service model, ensure that the TrueSight Infrastructure Management Servers on which the model is to be distributed contain Publishing Server details of all the servers in their respective <installationDirectory>/pw/server/etc/pserver.conf files. For example, if a service model is distributed across Infrastructure Management Server 1,2, and 3 respectively, then the pserver.conf file of all these servers must have the following entries:
      • Infrastructure Management Server 1 - pserver.conf file: EnterpriseNodes=<Publishing Server 1>, <Publishing Server 2>, <Publishing Server 3>
      • Infrastructure Management Server 2 - pserver.conf fileEnterpriseNodes=<Publishing Server 1>, <Publishing Server 2>, <Publishing Server 3>
      • Infrastructure Management Server 3 - pserver.conf fileEnterpriseNodes=<Publishing Server 1>, <Publishing Server 2>, <Publishing Server 3>
    2. When specifying the properties of the CIs in the model, in the Edit Component Properties dialog box, ensure that you select the Yes and Propagate option for Publish to Infrastructure Management Performance Management for the cell of the top-level CI. Also, set Enterprise=Tin the pserver.conf file. (See pserver.conf file.) These two settings are mandatory to set up discrete or distributed service models.

    3. If you are creating a distributed service model, ensure that the TrueSight Infrastructure Management Servers on which the model is to be distributed contain cell details of one another in their respective installationDirectory/pw/server/etc/mcell.dir files. For example, if a service model is distributed across TrueSight Infrastructure Management Server 1,2, and 3 respectively, then the mcell.dir file of all the three servers must have the following entries:
      • cell tsim_cell1 mc tsimserver_host1:<port number>

      • cell tsim_cell2 mc tsimserver_host2:<port number>

      • cell tsim_cell3 mc tsimserver_host3:<port number>

  2. If you edit pserver.conf and mcell.dir files of the Infrastructure Management servers to update the distributed service model details, restart all the servers before you proceed to the next step.
  3. Promote and publish the service model to the TrueSight Infrastructure Management Server. For information, see Promoting the service model.
  4. View the service model by using the Administration Console of the TrueSight Infrastructure Management Server. For information, see administration console Services Editor tab.

Recommendations for creating distributed service models

  • The CIs associated the with top-level CI must have the home cell specified and the Yes and Propagate: Publish Me and My Providers option selected.
  • All other CIs must have the Default option selected for the home cell and the Inherit: Publication is dictated by the value set in this CI's consumers option selected.
  • For a graph view of a service model that has more than 500 CIs, BMC recommends a shallow and very wide service model.

Related topics