== There are some possible configurations here there are 2 of themExample Configuration 3 Enterprise Services : ==
1st One Enterprise Server that does all the Work, Enterprise Service for Notifications like defined 2nd 3 the Enterprise Services (Notification, Rest_Import, Rest_Export)Service for Import
[https://wiki.augmensys.com/index.php?title=EventNotificationScanOrchestrator EventNotificationScanOrchestrator]
3rd the Enterprise Service for Export
[https://wiki.augmensys.com/index.php?title=BatchWriteOrchestrator Batch- \ MultiBatch- WriteOrchestrator]
Configuration Overview
1. Database Connection Setup
The configuration begins with setting up a database connection. This is defined in the ContentController.json file. The connection must be specified similarly to the main application configuration.
2. Import and Export Services
Depending on the setup, the system may require:
2 files for basic import/export operations.
4 files if both import and export web services are deployed.
The parameters must match the operation type (Import/Export) and its subtype.
Import Configuration
Required Files:
[[File:CUI EVENTNOTIFICATION.png]]
Specifies the path to CUIOrchestrationParam.json.
[[File:CUI_ORCHESTRATIONPARAM.png]]
Contains the SQL database connection details.
Supports SSPI authentication (username and password set to null).
CUIOrchestrationParam.json
Defines performance parameters:
Number of proxies
Number of notifications per step
Scan delay (in seconds)
Sleep time (in minutes) before the next check
Export Configuration
There are two modes of export:
Single Interface Admin (IA) object
ClassFullname:
"UBIK.CUI.Orchestration.BatchWriteOrchestrator"
Tree of Interface Admins
ClassFullname:
"UBIK.CUI.Orchestration.MultiBatchWriteOrchestrator"
Required Files:
CuiExportOrchestrator.json
Contains DB configuration
Repeat interval (in minutes)
Task definitions
Export Parameters File
Stores runtime parameters
Key element: The GUID of the Interface Admin to export
Web Service Hosting
A website should be configured under Sites with:
A unique, unused port
No requirement for HTTPS or separate ports if both the UBIK Notification Endpoint and the Comos EventService are hosted locally
