Create a new use case for ICO Content Pack
One of the most salient features of IBM® Cloud Orchestrator (ICO) is the ability to extend, customise, or create a new use case with ease. This is where BPM comes into picture. Most, or we can say, almost all the use cases of ICO are part of one or the other toolkits (Content Packs). ICO Content Pack is designed and implemented in such a way that a set of use cases pertaining to a component are all in one toolkit. For example, all the volume management/cinder related use cases are part of SCOrchestrator OpenstackBlockStorage Toolkit. While implementing the use cases, many building blocks are created so that they can be reused. Instead of having the entire operations code in a single flow, specific independent code snippets are added as integration services and then used so that they are reusable.
There are many blogs/videos/forums/documents on how to build a simple scenario using BPM. Apart from them, creating a new use case using BPM in ICO has some conventions/best practices. Let us look into these best practices in detail. Terms ‘use case’ and ‘offering’ are used interchangeably in the document.