Apama 10.15.3 | Using Apama with Software AG Designer | Working with Projects | Specifying an adapter configuration in a launch configuration
 
Specifying an adapter configuration in a launch configuration
The Adapter Configuration dialog is used to edit configuration information for the selected adapter. You can supply information for the following fields:
*Adapter — Select the adapter from the list of available adapters in the drop-down list. This allows you to choose the adapter bundle instance that is configured in the project. This field is required.
*Port — The port that this adapter will run on.
*Properties — Select the properties file that is appropriate for the selected adapter. The properties file is used to supply actual values for the variables that are contained in the adapter configuration file. This field is required.
*Apama Messaging — Select this option when your application does not use Universal Messaging, and instead uses Apama channels and explicitly set connections between components.
While it is possible for an adapter to use both Apama Messaging and UM Messaging, this is not recommended.
Selection of Apama Messaging enables the <apama> element in the adapter's configuration file. That is, it sets the APAMA_MSG_ENABLED substitution variable to true and sets the UM_MSG_ENABLED substitution variable to false. These values are used for launching the adapter.
Selection of Apama Messaging has no impact if the adapter configuration does not use the APAMA_MSG_ENABLED and UM_MSG_ENABLED substitution variables.
*UM Messaging — Select this option when you want the deployed adapter to use Universal Messaging. If the project does not contain a Universal Messaging configuration properties file, this option is disabled.
Selection of UM Messaging enables the <universal-messaging> element in the adapter's configuration file. That is, it sets the UM_MSG_ENABLED substitution variable to true and sets the APAMA_MSG_ENABLED substitution variable to false. These values are used for launching the adapter.
Selection of UM Messaging has no impact if the adapter configuration does not use the APAMA_MSG_ENABLED and UM_MSG_ENABLED substitution variables.
Note: 
Use of Universal Messaging from the IAF is deprecated and will be removed in a future release.
*Extra command-line options — Optionally, specify any additional arguments for starting the IAF process.
*Working directory — Identify the directory that will contain the files used to run the adapter.