Planning Service Models › Planning Service Models › Resource Collection

Resource Collection

As you define the services in your enterprise, you also define the specific resources that compose those services. Services can contain everything from applications and databases to servers and network devices. If some resources are omitted from a service model, you cannot ensure that the model is an accurate representation of the service health and availability.

Consider the following as you collect the resources that comprise your services:

• Find out where all required resources are currently managed. Verify that all resources in domain managers for which CA SOI provides connectors are actively managed, so that you can include the resources in service models. Consider a scenario where an application for which CA SOI does not provide a connector manages the resources. In this case, you can build a custom integration with the application using various tools provided.

  Note: For more information about implementing provided connectors and building custom integrations, see the CA Catalyst Implementation Guide or Connector Guide for each specific connector.

• Organize the resources that make up a service into logical subcomponents. Most complex services are sets of subservices or groups. If you can define these sets before modeling the service, you can improve the presentation and performance of your service. You can also reuse these modular components across multiple services.
• Consider the relationships among resources within subcomponents and the service at large. Try to separate subcomponents based on the following high-level relationship types:
  • Resources where the only concern is if a component is providing functionality
  • Resources that are critical to the functioning of a service
  • Resources that have some association or form a group, where the resources in the group can be operated on collectively
  • Resources that are intrinsically dependent on each other

  Note: For more information about relationships and how impact is propagated for each relationship, see Relationships and Propagation Types.

• For basic collections of resources or for areas of your enterprise with a high level of volatility, organize resources and note the criteria by which you can group them. Resources that fall into these categories can be good candidates for service discovery policies that automatically create services and relationships based on policy criteria.

  Note: For more information, see Service Discovery.