Before users can select different component states while creating/provisioning environments, the available states need to be defined as component instances.
In order for a component can be used, at least one component instance must be defined. You can define several component instances and use them in instances of your environments. An instance describes a particular state that the component can be set to (in terms of proxies, virtual assets, data source usage, performance profiles, etc.). An instance can determine:
- What message proxy is used—and with what settings (e.g., whether it records traffic, directs traffic to a real asset, directs traffic to a virtual asset).
- What JDBC controller is used—and with what mode (e.g., virtualize, record, passthrough, etc.) and what logging.
- Which virtual asset is deployed—and with what settings (data sets, performance profiles, etc.).
- Which test scenarios are used to check the health of this component.
- Which real endpoints are checked in determining online or offline status.
- Which provisioning action is performed (e.g., to configure a real endpoint in a certain manner, etc.).
...