Integrations

Citeck provides a wide set of mechanisms for integrating with external systems and services.

For most tasks, the platform’s built-in tools are sufficient:

• Records API — a universal HTTP interface for reading and modifying data of any Citeck microservice from external systems.

• Camel DSL — an extension of Apache Camel adapted for the platform. Allows describing data exchange routes, event subscriptions, and working with RabbitMQ queues and databases.

• Webhooks — incoming HTTP notifications that trigger logic in Citeck based on an external event.

• Data Sources — configurable REST sources for connecting to external APIs without writing code.

• Cross-instance communication — exchange of commands and events between multiple independent Citeck installations via RabbitMQ and Zookeeper.

• OSGi — extending platform functionality through OSGi bundles.

• EDI Integration — ready-made libraries for connecting to electronic document interchange providers (Kontur.Diadoc, SBIS, and others).

If any complex integrations are required, you can use the ecos-camel-core library in your microservice

• Examples of using Records API for external systems
  • Searching and Downloading a Document
  • Downloading a Document
  • Managing Routes
  • Managing the Set and Composition of Groups
  • Making Changes to a Record
  • Adding Data
  • Sending a Request to Alfresco-FTS
• Using Camel DSL
  • Overview
  • Fetching from the Database
  • Actions Available with Camel DSL
  • Camel DSL Context Instances
  • Connecting RecordsDaoEndpoint
  • Deleting Data from the Database
  • Receiving Messages from RabbitMQ and Sending Citeck Event
  • Subscribe to Citeck Event
  • Reading from RabbitMQ -> routing by jsonPath -> forwarding to Citeck Event + Dead Letter Queue
  • Components
  • Endpoints
  • Processors
  • ecos-camel-core Library
  • Implementation Examples
• Webhooks
  • Creation Form
  • Errors
• Data Sources
  • REST Data Source
  • DB Data Source
  • [Deprecated] MQ Data Source
• Communication between two or more Citeck instances via commands and events
  • Requirements
  • Configuration
  • Sending a command to an external system (from ECOS 1 (second-ecos) to ECOS 0 (main-ecos))
  • Testing Command Sending
  • Sending Files in Commands and Events
• OSGI Bundle Loading Functionality
  • Example of Creating a Bundle
  • Ways to Extend the Integrations Microservice Using Bundles
• Integration with EDI Providers
  • EDI
  • Setting up event reception from the Kontur.Diadoc box
  • Synchronization of Counterparty Data and Their Mailboxes with Kontur.Diadoc
  • Implementing integration with a new EDI provider
  • Description of ecos-edi-kontur-lib
  • Description of ecos-edi-ftps-lib
  • Description of ecos-edi-sbis-lib
  • Common Library for Processing EDI Events ecos-edi-integration
  • Server-Side Signing
  • EDI Configuration
• External Portal
  • Configuration Form
  • Import Configuration
  • Export Configuration
  • The sd-ext-portal-ecos-app Application
  • Permission Matrices
  • Customers
  • Logging
  • Creating a Request