Differences

This shows you the differences between two versions of the page.

--- nebolintegration [2022/05/05 10:15] – nebol
+++ nebolintegration [2022/06/16 19:43] (current) – nebol
@@ Line 14: / Line 14: @@
   * Handles incoming and outgoing integrations
   * Synchronous and asynchronous integrations
-  * Extensive logging and error-handling
+  * Extensive tracking, logging and error-handling
   * Failed tasks are tried again according to specified schedule
-  * Tasks can easily be re-sent, re-processed, and responses can be reprocessed
+  * Tasks can easily be re-sent, re-processed, and responses can be re-processed
-  * Multiple healthchecks per integration, built-in or custom coded, with configurable intervals and thresholds
+  * Healthchecks, built-in or custom coded, with configurable intervals and thresholds
   * Statistics
+  * Optional triggers using crontab-format to process integrations
+  * Scheduling for special handling during maintenance windows etc
   * Reports and notifications
+  * Automated maintenance (log cleaning)
+  * Grouping of integration processes simplifies administration
+  * Optional throttling for demanding processes
 NebolIntegrationNotifier (windows application, downloaded separately) provides
@@ Line 25: / Line 30: @@
   * Notification when a healthcheck fails (or when it is returned to healthy state)
   * Daily reports of all integrations with statistics per day, week, month, year
+=== What it will not do ===
+  * Data translation
 === Requirements ===
 Storage for the integration data such as an Entity Framework supported database or any other storage supported by SharpRepository (MongoDb, RavenDb, Db4o, XML etc)
 ==== Tutorial ====
@@ Line 49: / Line 57: @@
 [[NebolIntegration_Incoming_Integration]] - Creating an incoming integration
-[[NebolIntegration_Reference_and_Message]] - Managing data
+[[NebolIntegration_Reference_and_Message]] - Managing user data (also static vs dynamic tasks)
 [[NebolIntegration_More_Integration_Variations]] - Synchronous integrations, overrides, various trickery
@@ Line 94: / Line 102: @@
 ==== Roadmap ====
-Version 1.1.x.x will support Tasks that are automatically repeated (like in Windows Task Scheduler) thus no Submit will need to be made in the ValidatePolling() method (which was one way to go about it).
+Version 1.1.x.x will support "Triggers", that will trigger processing automatically according to a set cron-schedule thus no Submit will need to be made in the ValidatePolling() method (which was one way to go about it). Also full support for the built-in integrations "Updating" and "Cleaning"
-Version 1.2.x.x will support running multiple engines & multiple threads per integration.
+Version 1.2.x.x will support running multiple engines (clients) & multiple threads per integration.
 Version 1.3.x.x will support Schedules that you can setup to plan ahead for maintenance windows, or if you only want the integration to be run on business hours etc.
+Still not fully planned:
+Built-in integrations "Statistics" and "Reports"
+The additional tables Machine & Application needed for multiple client support
+Notifying clients (via built-in method or RabbitMQ) instead of client polling
+Improved built-in UI for command console using NebolConsole and multiple console areas
+Console command for listing & viewing queue & result items
+Web UI for administration + links in report-mail for errors etc
+fixing the issue of direction not being read properly from the db

Nebol's Wiki

User Tools

Site Tools

Differences

Page Tools