Registering a new service

Register a service if you need to add a new service or if you unregistered a service that you need again. If the service is set up to be manually started, you may need to enable the registered service later.

1. From the cluster management console, select System & Services > EGO Services > Service Profiles.
2. In your consumer tree, navigate to the location where you want to register your service. You can only register a service to a leaf location. If your consumer has any sub-consumers, then it is not a leaf.
3. Select Global Actions > Register a new service.

   The Service Profile displays showing the minimum required and preferred attributes for a new service along with preconfigured default values.

4. Click Table Preferences select the boxes to add the corresponding information columns to the table.
5. For main sections in the service profile (for example, "sc:ServiceDefinition"), click Actions and then insert any desired optional service parameters.
6. For each parameter, click within the Value field to add or change the value.
   Note: The actual number of slots requested with MaxInstances/MaxInstancesPerSlot may be adjusted depending on the values of MaxInstancesPerSlot and MaxInstancesPerHost. For EGO service instances, the number of slots provided on each host is a fixed amount determined by MaxInstancesPerHost/MaxInstancesPerSlot. If the number of slots requested is not a multiple of the fixed amount, extra slots will be needed to fill the gap and thus be wasted. Take the following configuration as an example:

   <sc:MaxInstances>10</sc:MaxInstances>
   <sc:MaxInstancesPerSlot>1</sc:MaxInstancesPerSlot> 
   <sc:MaxInstancesPerHost>6</sc:MaxInstancesPerHost>
   

   Ideally 10 slots (MaxInstances/MaxInstancesPerSlot) are needed. However, the integer value of MaxInstancesPerHost/MaxInstancesPerSlot (fixed amount) is 6 and thus EGO will allocate 12 slots instead of 10, causing two slots to be wasted. To prevent slot wastage, ensure MaxInstances is a multiple of MaxInstancesPerHost/MaxInstancesPerSlot.

   The MaxInstancesPerHost/MaxInstancesPerSlot configuration is not compatible with exclusive slot allocation. If MaxInstancesPerHost/MaxInstancesPerSlot is configured in the EGO service profile, the service cannot use a resource group configured for the exclusive slot policy. If you continue to use both configurations together, the EGO service will fail to start.

7. Click Register and confirm that you want to modify your service.