Rules and considerations for creating business service definitions

When defining business service definitions in the service.data.template file, keep the following rules and considerations in mind:

• Each business element to be included must start with the class name (for example, ServiceOffering, ServiceSubscriber).

• You can combine ServiceOffering data with group data (HierarchicalGroups) in the service.data.template file.

• When defining members or subscribers in a separate input file, <file_name> is a file that will contain one member or subscriber name per line, as an alternative to listing members in the service.data.template file. For members, the <class_name>::<instance> syntax is required.

• Each relationship must be defined on a separate line.

• The same business element can appear in multiple lines (so you do not have to list all of the related elements on a single line).

• Because a service is created as a ServiceOffering of a subscriber, it does not need to be defined separately if it does not have any other subscribers or any members of its own. Similarly, when a subscriber appears in a line where an offering is listed, it is automatically created. You do not have to define it individually.

• The system name of an element does not need to be a fully qualified domain name. The truncated system name will be searched for and matched.