Configure Enterprise Service for CUI

UBIK Notification Processing System

The UBIK Notification Processing System is a WebEndoint and configurable Enterpriseservice that imports Notifications into the UBIK database, and hand them over to processing. It requires specific configuration files and settings to function efficiently.

The Notification EndPoint is a Webpage to set it up correctly first set up UBIK WEB Service

Example Configuration 3 Enterprise Services :

1st the Enterprise Service for Notifications like defined

2nd the Enterprise Service for Import

EventNotificationScanOrchestrator

3rd the Enterprise Service for Export

Batch- \ MultiBatch- WriteOrchestrator

No requirement for HTTPS or separate ports if both the UBIK Notification Endpoint and the Comos EventService are hosted locally

UBIK Enterprise Service Configuration

To run the Enterprise Service, two main configurations are needed:

UBIK.EnterpriseService.exe.config

WebInterfaceHost should be set to localhost

Enable the web interface: <add key="ExecuteWebInterface" value="1" />

Define path to content controller config: <add key="ContentControllerConfigPath" value="C:\Temp\UBIK.Studio.ES-4.8_NOT\JSON\ContentController.json"/>

Additional settings:

Default language

Plugin execution path: <add key="PluginExecutionConfigPath" ... />

Enable task execution from JSON: <add key="ExecuteTaskByJsonFile" value="1" />

Ensure the WebInterfacePort is different from other services

Service Deployment

The Enterprise Service can be created via command prompt or through a batch (.bat) script for repeated use.

Example deployment:

Server: \\10.230.16.12

Services Created:

"UBIK_ES_NOTIF" (for Notifications)

"UBIK_ES_REST" (for REST interface)

Notes

Configuration files must be correctly paired with the service types.

File paths and port configurations must not conflict across services.

Proper authentication and execution parameters are crucial for correct operation.