This page is intentionally hidden from navigation but remains accessible via direct link.
Open iT Services
Open iT installs background services to support web access, secure connections, data collection, data transfer, processing, reporting, event handling, alerts, and data-processing orchestration. The services installed on a machine depend on the Open iT component, product version, plug-ins, and selected installation options.
This page describes the purpose of Open iT services, the components they support, their dependencies, and the functions affected when a service is unavailable.
Service Overview
| Component | Service | Purpose |
|---|---|---|
| Ingress | OpeniTHttpCertStore | Enables Ingress to use an SSL certificate from the Windows Certificate Store for HTTPS site bindings. |
| Ingress | OpeniTIngress | Configures OpeniTReverseProxy, SSL settings, site bindings, and shared navigation. It does not receive or route web requests. |
| Ingress | OpeniTReverseProxy | Provides application access, terminates HTTPS connections, and routes web requests to the appropriate Open iT application or internal service. |
| Core Server | OpeniTCoreAPI | Hosts the Core Server API used for file uploads, forwarding, health checks, and other component integrations. |
| Core Server | OpeniTRegistrar | Maintains the Core Server connection and service registration with Open iT Ingress. |
| Core Server | OpeniTReporting | Provides the Core Server reporting web interface and access to generated reports. |
| Core Server | OpeniTServer | Runs the main Core Server background operations that receive and process data from Open iT Clients. |
| Core Server | OpeniTOrchestratorDb | Provides the optional bundled PostgreSQL database for orchestration state. |
| Core Server | OpeniTOrchestratorWebserver | Provides the Orchestrator web interface and API. |
| Core Server | OpeniTOrchestratorDaemon | Runs the background orchestration processes that evaluate schedules and sensors, coordinate runs, and submit work for execution. |
| Core Server | OpeniTCoreServerPipeline | Hosts the Core Server data-processing definitions and logic used by the Orchestrator. |
| Analysis Server | OpeniTAlerts | Executes scheduled alert jobs and updates data used by real-time monitoring. |
| Analysis Server | OpeniTAnalysisServerPipeline | Hosts the Analysis Server data-processing definitions and logic used by the Orchestrator. |
| Core Client | OpeniTClient | Runs the Core Client background operations used for data collection and communication with the Core Server. |
| Core Client | OpeniTScheduler | Starts configured data-collection, processing, and transfer jobs according to their schedules. |
| CLIMS Server | RavenDB | Runs the database used by the CLIMS Server to store and retrieve CLIMS application data. |
| CLIMS Client | OpeniTCLIMSClient | Runs Openit.Zero.Decisionmaker, which connects a managed license server host to the CLIMS Server for monitoring and remote management. |
| CBCS Autodesk plug-in | OpeniTDasgterAutodesk (until version 10.2.570) OpeniTCBCSAutodeskPipeline | Hosts Autodesk-specific CBCS processing definitions and logic used by the Orchestrator. |
| ServiceNow Adapter plug-in | OpeniTSNAdapterPipeline | Hosts ServiceNow Adapter-specific processing definitions and logic used by the Orchestrator. |
The Orchestrator services are installed with the Core Server. Analysis Server and ServiceNow Adapter may be installed on the same machine as the Core Server or on separate machines. Each Pipeline service connects to the same PostgreSQL database used by the Orchestrator. OpeniTOrchestratorDb is installed only when the bundled PostgreSQL option is selected. It is not required when the customer provides an existing PostgreSQL instance.
Ingress Services
OpeniTHttpCertStore
OpeniTHttpCertStore supports HTTPS configurations that use an SSL certificate installed in the Windows Certificate Store. It makes the configured certificate available for the HTTPS site binding used by Open iT Ingress.
This service affects:
- Access to the configured certificate store and store location
- HTTPS site bindings that reference a Windows certificate store
- Secure access to Open iT applications through the Ingress address
If this service is stopped, an Ingress installation that depends on the Windows Certificate Store may be unable to establish or maintain its configured HTTPS binding. Installations that use certificate and key files instead do not depend on this certificate-store configuration.
OpeniTIngress
OpeniTIngress configures OpeniTReverseProxy and the related SSL settings, site bindings, and shared navigation. It does not provide application access, receive client web requests, perform reverse-proxy routing, or terminate HTTPS connections; those functions are handled by OpeniTReverseProxy.
This service affects:
- OpeniTReverseProxy configuration
- SSL settings
- Site bindings
- Shared navigation between supported Open iT applications
If this service is stopped, OpeniTReverseProxy may continue operating with its existing configuration. However, changes to the reverse-proxy configuration, SSL settings, site bindings, or shared navigation may not be applied until OpeniTIngress is restored.
OpeniTReverseProxy
Starting with version 10, OpeniTReverseProxy is part of Open iT Ingress. It provides access to registered Open iT applications, receives web requests, terminates HTTPS connections, and forwards requests to the appropriate Open iT application or internal service. This provides a common access point while allowing the underlying applications to use their own internal addresses and ports.
Depending on the configured environment, the service may affect:
- Access to the Core Server and other registered Open iT web applications
- Routing to internal Open iT applications and APIs
- HTTPS termination for secure site bindings
- Authentication flows configured through the reverse proxy
- Consistent external URLs for Open iT applications
If this service is stopped, users may be unable to access affected Open iT applications through the configured Ingress address. The underlying services may continue running but may not be reachable through the reverse proxy.
Core Server Services
OpeniTCoreAPI
OpeniTCoreAPI hosts API endpoints used by the Core Server and connected components. The Windows service name used by service-control commands is openitcoreapi, and the service listens on port 27895 by default.
The service supports Core Server operations such as:
- Receiving files uploaded by Open iT Clients
- Forwarding data to another configured Core Server
- Providing a health-check endpoint
- Supporting integrations and Core Server components that use the API
Open iT Core API existed in some earlier environments as a manually added binary or service. Version 10.2.580 introduced the installer-managed Core API service: the Core Server installer began placing openit_coreapi in the service directory and automatically installing its service instance.
If this service is stopped, uploads, forwarding, health checks, and other functions that depend on Core API endpoints may fail until the service is restarted.
OpeniTRegistrar
OpeniTRegistrar maintains the Core Server connection and service registration with Open iT Ingress. On Windows, the service is hosted by openit_servicemanager.exe in the Core Server bin directory and is configured to start automatically.
This service affects:
- Registration of the Core Server with Ingress
- Availability of the Core Server through the configured Ingress address
- Application endpoint information used by Ingress routing
- Re-registration after changes to the Core Server or Ingress connection
If this service is stopped, the Core Server may not register or re-register its application endpoints with Ingress. Existing registration information may become unavailable or outdated, which can prevent users from reaching the Core Server through the configured Ingress address.
OpeniTReporting
OpeniTReporting provides the Core Server reporting web interface and access to generated report output. Report generation is handled separately and can continue while this service is stopped.
This service affects:
- Access to the reporting pages through the Core Server web interface
- Submission of new on-demand report-generation requests through the web interface
- Access to completed reports
If this service is stopped, users cannot access the reporting web interface. Report-generation operations already in progress continue processing, but generated reports are not accessible until the service is restored.
OpeniTServer
OpeniTServer runs the main Core Server background operations. The Core Server receives data from Open iT Clients, processes the collected data into reportable formats, and stores the processed data in the Core Server database directory.
This service affects:
- Reception of data transferred by Open iT Clients
- Core Server processing and related background operations
- Preparation of collected data for reporting
- Availability of current data to downstream Open iT components
If this service is stopped, the Core Server cannot perform the affected background operations. Client data may not be received or processed, and reports may not contain newly collected information until the service resumes and the backlog is processed.
Orchestrator and Pipeline Services
OpeniTOrchestratorDb
OpeniTOrchestratorDb provides the optional bundled PostgreSQL database used to store orchestration state. It is intended for environments where the customer does not provide an existing PostgreSQL instance.
The service stores operational information used by the Orchestrator, including:
- Pipeline run state and history
- Schedule and sensor state
- Dagster events and operational metadata
- Other persistent information required to coordinate and monitor workflows
If this service is stopped, the Orchestrator and Pipeline services that depend on the bundled database cannot reliably read or update orchestration state. Pipeline execution, scheduling, monitoring, and the Data Processing GUI may become unavailable or report database connection errors.
This service is not present when Open iT is configured to use a customer-provided PostgreSQL instance. In that setup, availability and maintenance of PostgreSQL are managed outside the Open iT services.
OpeniTOrchestratorWebserver
OpeniTOrchestratorWebserver provides the Orchestrator web interface and API used to view and manage Open iT data-processing workflows. It communicates with the Pipeline services through gRPC and loads their code locations.
The service provides access to the following operational information in the Data Processing GUI:
- Assets and their materialization status
- Jobs and run history
- Schedules and sensors
- Code locations and loading status
- Daemon status
- Asset lineage and dependencies
- Logs and error details for troubleshooting
The registered code locations are:
| Code location | Component | Default gRPC port |
|---|---|---|
coreserver | Core Server | 4266 |
snadapter | ServiceNow Adapter | 4267 |
analysisserver | Analysis Server | 4268 |
If this service is stopped, the Data Processing GUI is unavailable. Pipeline services and already-started processes may remain available, but administrators cannot use the GUI to monitor, start, or troubleshoot workflows.
OpeniTOrchestratorDaemon
OpeniTOrchestratorDaemon runs the background orchestration processes required by Dagster. It evaluates schedules and sensors, coordinates runs, and submits work exposed by the registered Pipeline services for execution.
The service affects:
- Scheduled workflow execution
- Sensor evaluation and event-driven processing
- Queued run coordination
- Run monitoring and operational state updates
- Cross-component workflow dependencies
If this service is stopped, schedules, sensors, and other background orchestration functions are not evaluated. The Data Processing GUI may still be accessible through OpeniTOrchestratorWebserver, but automated processing does not proceed normally.
OpeniTCoreServerPipeline
OpeniTCoreServerPipeline hosts the Core Server data-processing definitions and logic used by the Orchestrator. It loads the Core Server Dagster definitions from the installed binaries and configuration, then makes the definitions available through the coreserver gRPC code location.
The service exposes Core Server definitions such as:
- Assets
- Jobs
- Schedules
- Sensors
- Asset dependencies
It affects the Core Server workflows that process collected data into formats used for reporting and other downstream operations.
If this service is stopped or its code location fails to load, the Orchestrator cannot load or execute the affected Core Server assets and jobs. Other registered code locations may continue to operate.
OpeniTAnalysisServerPipeline
OpeniTAnalysisServerPipeline hosts the Analysis Server data-processing definitions and logic used by the Orchestrator. It loads the Analysis Server Dagster definitions from the installed binaries and configuration, then makes the definitions available through the analysisserver gRPC code location.
The service affects the Analysis Server data-loading workflow, including:
- Synchronizing configured data from the Core Server database directory
- Loading data into the SQL Server data warehouse
- Processing and normalizing warehouse data
- Processing the SQL Server Analysis Services cubes
If this service is stopped or its code location fails to load, the Orchestrator cannot start the affected Analysis Server workflows. Data required by Analysis Server reports, SQL Server Reporting Services reports, and external reporting tools may not be updated until processing resumes.
OpeniTCBCSAutodeskPipeline
This is called OpeniTDasgterAutodesk until version 10.2.570.
OpeniTCBCSAutodeskPipeline is a plug-in Pipeline service that hosts Autodesk-specific CBCS processing definitions and logic used by the Orchestrator.
The service isolates the plug-in's workflows from the main Core Server Pipeline while allowing them to participate in centralized scheduling, execution monitoring, logging, and dependency management.
If this service is stopped or its code location fails to load, Autodesk-specific CBCS workflows cannot run. Other Core Server, Analysis Server, and ServiceNow Adapter workflows may continue if their respective services and dependencies are available.
OpeniTSNAdapterPipeline
OpeniTSNAdapterPipeline is a plug-in Pipeline service that hosts ServiceNow Adapter-specific processing definitions and logic used by the Orchestrator. It loads the adapter's Dagster definitions and configuration, then makes its workflows available through the snadapter gRPC code location.
The service affects workflows that:
- Process data from the Open iT SQL database
- Populate the required dimension and fact tables
- Prepare data for the installed OpeniT ServiceNow applications
- Send the prepared data to the configured ServiceNow instance
The Pipeline service uses the ServiceNow Adapter configuration, including programs.yaml, stored-procedure definitions, database connection settings, and ServiceNow connection settings.
If this service is stopped or its code location fails to load, ServiceNow Adapter processing and data-transfer workflows cannot run. Core Server and Analysis Server processing may continue if their own services and dependencies are available.
Analysis Server Services
OpeniTAlerts
OpeniTAlerts executes the Analysis Server alert jobs. It also performs scheduled synchronization used by the real-time dashboard.
The service runs configurable jobs for functions such as:
- Synchronizing license-status data from the Core Server
- Monitoring maximum and sustained utilization
- Detecting long checkouts and license hogs
- Monitoring license, license server, and vendor daemon status
- Checking archive data and Analysis Server ETL execution
- Sending configured email alerts
If this service is stopped, the Analysis Server web interface and historical reports may remain available, but scheduled alert evaluation, email notifications, and real-time dashboard updates do not run until the service is restarted.
Core Client Services
OpeniTClient
OpeniTClient runs the main Core Client background operations used to collect software and system usage data and communicate with the Core Server.
This service supports:
- Execution of enabled Open iT Client functionality
- Collection and local handling of usage data
- Communication and data transfer to the configured Core Server
- Client operations required by installed LicenseAnalyzer or SystemAnalyzer modules
If this service is stopped, the affected client operations cannot run normally. This may create gaps or delays in the data available on the Core Server, depending on the collectors and modules configured on the client.
OpeniTScheduler
OpeniTScheduler starts configured Open iT Client jobs according to their assigned schedules. These jobs may collect, process, or transfer data depending on the client configuration.
This service affects:
- Scheduled license-manager polling
- Scheduled collection from log files, cloud sources, operating-system sources, and other configured data sources
- Local conversion or processing jobs
- Scheduled transfer of collected data to the Core Server
If this service is stopped, scheduled jobs do not start. Data already collected on the machine is normally retained, but new collection or transfer intervals may be missed until the scheduler is restarted. The recoverability of missed data depends on the collector and the source system.
CLIMS Services
RavenDB
RavenDB runs the database used by the CLIMS Server. The CLIMS Server installation stores its database files in the RavenDB directory and requires the RavenDB service to be running for database-backed CLIMS operations.
This service affects:
- Storage and retrieval of CLIMS application data
- License manager and client information displayed by the CLIMS Server
- CLIMS configuration and management operations that requires database access
- Availability of current CLIMS data through the web interface
OpeniTCLIMSClient
OpeniTCLIMSClient runs Openit.Zero.Decisionmaker on a managed license server host and connects the client to the configured CLIMS Server.
This service supports:
- Detecting and monitoring supported license managers and vendor daemons
- Sending license server status and related information to the CLIMS Server
- Receiving and executing supported remote management actions
- Providing remote access to applicable processes, configuration files logs, directories, and services
Service Dependencies and Impact
| Service | Main dependency | Main impact when unavailable |
|---|---|---|
| OpeniTHttpCertStore | Windows Certificate Store and the certificate store settings in the Ingress site-binding configuration | Ingress HTTPS bindings that use a certificate from the Windows Certificate Store may fail. |
| OpeniTIngress | Ingress configuration and OpeniTReverseProxy | Changes to the reverse-proxy configuration, SSL settings, site bindings, or shared navigation may not be applied; OpeniTReverseProxy may continue using its existing configuration. |
| OpeniTReverseProxy | Configuration generated by OpeniTIngress, certificates, site bindings, registered applications, and reachable internal services | Application access, request routing, and HTTPS termination through the configured Ingress address are unavailable. |
| OpeniTCoreAPI | Core Server API configuration, network port 27895, and applicable storage or forwarding destinations | Client uploads, forwarding, health checks, and dependent integrations may fail. |
| OpeniTRegistrar | Core Server Ingress configuration, Ingress availability, and network connectivity | The Core Server may not register or refresh its application endpoints in Ingress, affecting access through the unified address. |
| OpeniTReporting | Core Server reporting web application, generated report files, and web routing | The reporting interface and generated reports are unavailable, although report-generation operations already in progress continue processing. |
| OpeniTServer | Core Server binaries, configuration, database directories, and client connectivity | Client data reception, server-side processing, and downstream data currency are affected. |
| OpeniTOrchestratorDb | Bundled PostgreSQL database | Orchestrator and Pipeline services may be unable to read or update orchestration state. |
| OpeniTOrchestratorWebserver | PostgreSQL, Pipeline services, and gRPC code locations | The Data Processing GUI is unavailable, although already-started processes may continue. |
| OpeniTOrchestratorDaemon | PostgreSQL and registered Pipeline services | Schedules, sensors, and other background orchestration functions are not evaluated. |
| OpeniTCoreServerPipeline | Core Server binaries and configuration, PostgreSQL, and gRPC | Core Server assets and jobs cannot be loaded or executed by the Orchestrator. |
| OpeniTAnalysisServerPipeline | Analysis Server binaries and configuration, SQL Server, SQL Server Analysis Services, PostgreSQL, and gRPC | Analysis Server data-loading and processing workflows cannot be started by the Orchestrator. |
| OpeniTDasgterAutodesk (until version 10.2.570) OpeniTCBCSAutodeskPipeline | CBCS Autodesk plug-in binaries and configuration, PostgreSQL, and gRPC | Autodesk-specific CBCS workflows cannot run. |
| OpeniTSNAdapterPipeline | ServiceNow Adapter binaries and configuration, PostgreSQL, gRPC, database connections, and ServiceNow connection settings | ServiceNow Adapter processing and data-transfer workflows cannot run. |
| OpeniTAlerts | Analysis Server database connections, alert configuration, and email settings | Alert evaluation, notifications, and real-time status updates stop. |
| OpeniTClient | Client configuration, enabled modules, data sources, and Core Server connectivity | Client collection and communication operations are affected. |
| OpeniTScheduler | Scheduler configuration and the executables used by configured jobs | Scheduled collection, processing, and transfer jobs do not start. |
| OpeniTEventHandler (legacy) | Core Server openit_eventd, network connectivity, and configured event-handler processes | In releases before removal, real-time events were not distributed to local handlers, so dependent job and schedule actions could fail or be delayed. |
Stopping a service can interrupt data collection or processing and may result in delayed or incomplete reporting. Before restarting or disabling a service, review its logs and confirm whether other Open iT components depend on it.
Do not stop or disable Orchestrator or Pipeline services as a routine method of disabling an individual job. Use the Data Processing GUI to disable the applicable schedule or sensor. Stop a service only when required for maintenance or troubleshooting.