Introduction to the tutorial environment

The script creates the following service model members and organizers to initialize the CRM service model in Service Impact. Use of these members and organizers is a recommended best practice.
  • Dashboard organizer; root-level organizer for service models as a whole. Initially, the organizer is empty.
  • Root-level CRM - Development organizer that contains additional organizers. Use a single root-level organizer to contain the subservices of each service model, and use standardized names (and contents) for sub-organizers.
  • CRM - Application Service and CRM - Compute Service service model members, children of the CRM - Development organizer.

    These members summarize the application and compute services that are associated with the CRM application. They are easily located without having to open the organizers in which their constituent subservices are located.

  • Members in the Network organizer that start with zfake represent the network connections between fake devices.

    Because these fake devices are not modeled, Resource Manager cannot discern their relationships, and Service Impact cannot create device or component members. Therefore, the script creates members to represent the connections.

    These members have neither contextual nor global policies, so the default policy applies. That is, the state of the worst condition that affects child members becomes the state of the zfake members, which is the correct policy for these connections.

  • DNS and interface names that follow a naming convention.
  • Subservice members in the Network organizer that start with tx, which contain redundant resources. Standardized, global availability policies are defined.

    These subservice members demonstrate the following best practices:

    • Each subservice member contains homogeneous child members. Global policies work best when child members are homogeneous.
    • Each subservice uses global policies. Global policies can be re-used across service model boundaries. Contextual policies are restricted to specific service models.
    • Each global policy contains the following, standardized availability state triggers: ATRISK if 50% or more child members are down; DOWN if 100% of child members are down. Use of percentage thresholds means that the policies do not need to be adjusted if additional resources are deployed later.

The remaining procedures in this tutorial demonstrate how to complete and test the CRM service model.