Josh,
If the external API is accessible via Java, then there are several options for integrating it into the EnterWorks platform:
1. Repository Trigger - if it's necessary to have the API invoked when a repository record is changed (and the results of that call be completed before the save of the repository record is deemed completed, then defining/updating an event trigger on the repository would be appropriate.
2. Scheduled Import/Export pre/post-processing block - if the external API call needs to be made in association with an import or export, a pre-/post-processing block can be implemented and configured.
3. EPX Activity - if the invocation of the external API is associated with a repository record undergoing workflow, or requires initiation by a user (e.g., Send to Workflow) for a specific record, defining a custom Callout BIC that invokes the API would be appropriate.
It may be possible to provide examples of accessing AWS S3 and Rabbit MQ from a Callout BIC (both of which are configurable activities that are part of the Services Framework).
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 9099009179
------------------------------