Apama 10.3 | Apama Documentation | Using Apama with Software AG Designer | Working with Projects | Adding resources to Apama projects | Adding bundles to projects | Adding connectivity and adapter bundles to projects | Using the Digital Event Services connectivity bundle
Using the Digital Event Services connectivity bundle
You can use Software AG Designer to automatically generate Apama event types from digital event type definitions for use in the Apama project and, conversely, to export Apama event definitions in the Apama project as digital event types. You can also use Software AG Designer for configuring the connection to Digital Event Services.
Note: It is not possible to delete the types from the type repository. If types are removed from the export list, they will remain but are no longer updated.
* To use the Digital Event Services connectivity bundle
1. Add the Digital Event Services connectivity bundle as described in Adding connectivity and adapter bundles to projects.
In the Project Explorer view, the following files are created in the Connectivity and Adapters > Digital Event Services > DigitalEventServices node:
2. Double-click the EventTypeList.apamades file to open the Digital Event Types editor.
3. In the Import types from DES section, select the digital event types to import as Apama event definitions.
If any selected event types depend on event types that are not selected, the dependencies are included automatically at generation time.
When you edit and save the EventTypeList.apamades file, Software AG Designer automatically generates the EPL files containing the Apama event definitions for the selected event types and any dependent events in the project's autogenerated > DigitalEventTypes node.
Note: Always use Software AG Designer to edit the EventTypeList.apamades file. Editing this file directly is not supported.
When you make any changes to the definition of your digital events from other Software AG products, click Sync from Digital Event Services in the Digital Event Types editor to synchronize the type repository with the list shown in the editor. When you then click Save, the Apama event definitions are regenerated to match the latest digital event definitions. Any errors or warnings are displayed in the Problems view.
Note: As the project's autogenerated folder is kept up to date by Software AG Designer, it is recommended not to check in the folder into a version control system. Also, you must not exclude the autogenerated folder or any of the folder's content from the EPL build path as this may result in unexpected behavior.
4. In the Export types to DES section, select the Apama event types to export as digital event types.
To export an Apama event definition as a digital event type
a. Click to open the Event Type Selection dialog.
b. Select the events that you want to export as digital event types.
c. Click OK.
d. Click Save to finish the export.
After this, any further modifications to the exported events will automatically update the type repository.
Note: When you deploy a project (for example, with the engine_deploy tool, see Deploying a correlator), the Apama event types are automatically exported to the local type repository. That way, you do not have to copy the types from the repository in your development environment to the repository in your production environment.
5. Optional. Double-click the DigitalEventServices.properties file to configure the connection to Digital Event Services. This file contains documentation for each of its elements, and it uses the Digital Event Services connectivity plug-in that is shipped with Apama.
See also The Digital Event Services Transport Connectivity Plug-in and Using Connectivity Plug-ins.
If using Command Central, then it is recommended to not change the replaceConfigWithRNAME configuration from the default blank value, but use the Command Central configuration (see Configuring Digital Event Services for a correlator instance) to configure Digital Event Services. Otherwise, your configuration will be overridden.

Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.