Skip to main content

Deployment Topologies

Understand the various on-premise, high-availability, and disaster recovery deployment models to select the optimal architecture for your ServiceOps installation.

Overview​

ServiceOps offers a flexible architecture that can be deployed in various configurations to meet diverse organizational needs for scalability, resilience, and performance. This guide outlines the standard deployment topologies, from simple standalone setups to complex, highly available, and geo-redundant environments. Understanding these models is crucial for IT Administrators and Implementation Consultants to design and implement a robust and efficient ServiceOps platform.

Each topology has distinct advantages and is suited for different operational requirements. Whether you are deploying on a single server, distributing components across a network, or ensuring business continuity with high-availability and disaster recovery, this document provides the foundational knowledge to guide your deployment strategy.

A standalone deployment consolidates all ServiceOps components onto a single server, including application, database, and analytics services. This is the simplest model, designed for evaluation, proof-of-concept, and small-scale production environments with minimal concurrency requirements.

Architecture​

  • ServiceOps (App + DB): At the core of the architecture, ServiceOps hosts both its application and database in a single environment. This central deployment acts as the control hub for IT service management operations.
  • Remote Users: End-users (employees, technicians, admins) connect to ServiceOps through the internet. This allows them to raise requests, access services, and manage incidents remotely without requiring direct access to the internal IT infrastructure.
  • Agents (Agent-based Discovery): Discovery agents are deployed across endpoints or networks to gather asset and configuration data. They communicate securely with the ServiceOps instance via the internet. This ensures IT assets (on-premises or remote) are continuously discovered and updated in the system.
  • 3rd Party Integrations: ServiceOps integrates with external applications and services (such as monitoring tools, collaboration apps, or external ticketing systems). These integrations connect over the internet to push or pull data into ServiceOps.
  • IT Network Infrastructure: Within the main site, ServiceOps interacts with the organization's core IT services such as DNS, Active Directory, email servers, cloud services, and monitoring systems. This ensures seamless authentication, notifications, and operational data exchange.

Components & Roles​

Main Site

  • ServiceOps (App + DB): Unified server hosting both the application and database.
  • IT Network Infrastructure: Internal enterprise services including:
    • DNS
    • Active Directory / LDAP
    • Cloud services
    • Monitoring/alerting tools
    • Email servers

External Components

  • Remote Users: Access ServiceOps for service requests, incident tracking, approvals, and reporting.
  • Agents: Perform agent-based discovery to identify assets and feed information into ServiceOps.
  • 3rd Party Integrations: External systems that integrate with ServiceOps for extended functionality.

Connectivity Layer

  • Internet: Acts as the communication channel for remote users, agents, and integrations to interact with ServiceOps.

Use Cases​

  • Small organizations (Less than 100 users)
  • Training/demo environments
  • Development labs

Benefits​

  • Simplified installation and maintenance
  • Low infra cost (single VM/server)
  • Quick setup

Configuration​

Configure Motadata ServiceOps Application and DB on a single server as per the Standalone Deployment scenario from the Installation Guide.