IBM Sterling Intelligent Promising custom resources and service groups
The Operators creates custom resources for each service in your cluster. The five types
of custom resources are
SIPEnvironment, IVServiceGroup, PromisingServiceGroup, UtilityServiceGroup, and OptimizerServiceGroup.
Types of custom resources
- SIPEnvironment
- The primary custom resource that manages all the other custom resources that are created by the IBM® Sterling Intelligent Promising Operator.
- IVServiceGroup
- A custom resource that manages number of deployments, replica counts, thread counts and more, for Inventory Visibility service resources.
- PromisingServiceGroup
- A custom resource that manages number of deployments, replica counts, thread counts and more, for Promising service resources.
- UtilityServiceGroup
- A custom resource that manages number of deployments, replica counts, thread counts, and more, for all the shared utility services- audit, carrier, catalog, rules, and search.
- OptimizerServiceGroup
- A custom resource that manages number of deployments, replica counts, thread counts and more,
for
provisioningService,kpiProcessorService,optimizationService,configurationService,requestOrganizerService,dataCaptureService,elasticSearchDataProcessor, anderrorProcessorService.
For more information about configuring SIPEnvironment, see Configuring SIPEnvironment custom resource.
Service groups
For IBM Sterling Intelligent Promising to function smoothly, a set of defined microservices should be run. These microservices are run in multiple deployments with different services added to them so that API calls are fulfilled for a specific end point. The service groups offer you the flexibility to group the deployments.
For example, you can choose to deploy service1, service2, and service3 into one deployment and service4 and service5 into another deployment. Alternatively, you can choose to run all the services in a single deployment.
Note: Deploying the services are mandatory. By creating a service group CR, you are defining a
structure for all the required services.
Service group topologies
You can deploy service groups in the following three modes:
- Development Mode
- All the required services can be deployed into a single deployment.
- Production Mode
- Each required service can be deployed into a single deployment.
- Flexible Mode
- You can activate or deactivate a server or a group of servers. You can create the flexible mode deployment by providing any name other than dev or production.
Methods to deploy service groups
You can deploy service groups for Inventory, Promising, and Utility services by using any of the
following two modes:
- Integrated mode
- A service group is defined in the
SIPEnvironmentcustom resource, and the IBM Sterling Intelligent Promising operator automatically activates the service group. For more information, see Configuring SIPEnvironment custom resource. - Independent mode
- A service group is defined in the specific custom resource of the service-
IVServiceGroup,PromisingServiceGroup,UtilityServiceGroup, orOptimizerServiceGroup. When you create a service group independently, you must activate it manually by setting theactiveproperty to true. For more information, see