Apama 10.7.2 | Connecting Apama Applications to External Components | Working with Connectivity Plug-ins | Getting Started with Connectivity Plug-ins | Specifying the settings for the connectivity chains in the YAML file
 
Specifying the settings for the connectivity chains in the YAML file
The configuration file for a connectivity plug-in describes both the chains and the plug-ins making up each chain. It is written in the YAML markup language. See also Using YAML configuration files.
Edit the YAML configuration file (with the file extension .yaml) which comes with the connectivity bundle and specify all required information for creating the connectivity chains.
Find out from the documentation for the standard connectivity plug-ins how connectivity chains are created for the transport you are using. See Standard Connectivity Plug-ins.
*If the transport provides a dynamic chain manager, then the chains are created by the transport. In this case, you have to provide one or more dynamicChains definitions in the YAML configuration file so that the chains are then created from these definitions.
*If the transport does not provide a dynamic chain manager, you have to choose between
*defining the chains statically in your YAML configuration file using startChains, or
*creating the chains dynamically from EPL using dynamicChains definitions in the YAML configuration file.
Your decision on which transport to use affects which sections of the YAML configuration file you have to edit. See also Static and dynamic connectivity chains.
Sometimes it is necessary to make more changes in the YAML configuration file. For example:
*You can add custom connectivity transport plug-ins or codec plug-ins that you have built yourself in Java or C++, or have downloaded from the Apama community. See also Configuration file for connectivity plug-ins.
*You can change the configuration settings for the transport. This depends on whether your transport has a dynamic chain manager that will be either in the dynamicChainManager section and/or under the transport's name in the startChains or dynamicChains sections of the YAML configuration file. For an example, see Configuring the HTTP server transport.
Note:
The Digital Event Services connectivity plug-in is an exception. In this case, the YAML configuration file should not be modified by the user. All of the required configuration is to be done in the properties file.