I have been working on a CPBM connector that provides applications through a CPBM product bundle. A user is able to subscribe to an application and provision it; this works as expected.
The applications I offer through the connector can have several configuration options. At the point where a user starts a subscription, I would like to ask the user several questions. Currently this screen only asks for a name to give the application; I would like to ask many more questions (e.g. domain names, SLA option, choice of Windows/Linux...)
I see that the MetadataRegistry interface has several methods that return ResourceComponents, and ResourceComponents contain attributes and display attributes. I'm assuming that these what I am needing to use to create configuration entries, but I'm not certain that: (1) this is the right place, and (2) how these attributes/display attributes maps should be filled in.
Can anyone describe how these attributes are supposed to work, maybe point me at the right documentation for the API? And confirm that what I am wanting to do with configuration questions is possible?
So it seems that ResourceComponents attributes are not the right place to add configuration information - it becomes part of the application, but does not appear to be user-configurable.
See screenshot attached.
I would like to write my connector so that all of the options "OS stack", "DNS domain", etc. appear in the "Configure and Subscribe" section where the user can edit them.
The resource component is used to describe any attributes of the resource type that has an impact on the price definition of the resource itsef.
For additional properties, you can find the property tag within resource types that will be just additional information that will be collected in the "Configure and Subscribe" screen and passed on to the connector SubscriptionLifecycleHandler.
Thanks Palani - I've got a step further. I've been able to modify serviceDefinition.xml and define the new properties there.
Unfortunately it's not quite what I was looking for. This file is set at compile time. The connector I'm writing is dynamic in its behaviour, and the applications and their configurations will actually be discovered at runtime.
Therefore I need a way to be able to change the properties for a particular application in a product bundle from code, not from static resources. Is there a way to do this?
