Share this page

# Architecture

You can set up OpenText™ Software Delivery Management as a single node, or in a cluster configuration. The following diagrams illustrate the system architecture for both options.

These are followed by descriptions of each of the components.

In this topic:

## Basic configuration

The following diagram illustrates the system architecture of a single-node configuration. Components in gray are OpenText products.

Note: The OpenText Software Delivery Management, database, and Elasticsearch servers should each reside on separate machines.

Back to top

## Enterprise configuration

The following diagram illustrates the system architecture of an enterprise, cluster configuration. Components in gray are OpenText products.

Back to top

## Components

Components | Description
--- | ---
OpenText Software Delivery Management clients | The clients communicate with the OpenText Software Delivery Management server over HTTP/S.
OpenText Software Delivery Management Server application nodes | Client requests from OpenText Software Delivery Management are dispatched to the deployed application. Note: The OpenText Software Delivery Management, database, and Elasticsearch servers should each reside on separate machines.
OpenText Software Delivery Management application additional cluster (sync) nodes | Cluster configuration: A cluster is a group of application servers that run as a single system. Each application server in a cluster is referred to as a "node." All nodes must have access to the database server on which the site database schema resides. All nodes must have access to the repository. Generally, the repository is located on an NFS or SAN server. If the repository is not located on a remote, dedicated machine, the repository location cannot be /opt/octane (Linux) or C:\Program Files\octane (Windows). All nodes must have access to each other.
Repository / File system | Stores all files to be used by all the projects in the system, such as templates and attachments. Cluster configuration: When working in a clustered configuration, the repository must be accessible by all nodes. Also, the repository must be configured to use the same mount point (path) on all nodes.
Database server | A relational database management system, either Oracle RAC or Microsoft SQL Server. The database server stores the following schemas: Site schema. Stores all site-related information, such as database servers, cluster nodes, the SMTP servers, and configuration. Space schema. All space information, such as workspaces, users, and roles. This server can be shared with other applications with the following constraints: The database must be able to sustain the load of all the applications. Future versions of OpenText Software Delivery Management might require a database upgrade. This may necessitate migration of data if other applications sharing the same database do not support the database version that OpenText Software Delivery Management requires. Note: The OpenText Software Delivery Management, database, and Elasticsearch servers should each reside on separate machines.
Elasticsearch server (or cluster) | A Java-based, open-source search engine. This component is used for various aspects of the application, such as global search and trends. This server can be shared with other applications with the following constraints: The Elasticsearch engine must be able to sustain the load of all the applications. Future versions of OpenText Software Delivery Management might require an Elasticsearch upgrade. This may necessitate migration of data if other applications sharing the same Elasticsearch do not support the Elasticsearch version that OpenText Software Delivery Management requires. Note: The OpenText Software Delivery Management, database, and Elasticsearch servers should each reside on separate machines. A working Elasticsearch server is a requirement for working with OpenText Software Delivery Management. For the supported version, refer to the Support Matrix.
Load balancer | Cluster configuration: When working with a load balancer, client requests are transmitted to the load balancer and distributed according to server availability within the cluster. If you are using a load balancer, we recommend you utilize SSL offloading.
High availability load balancers | Cluster configuration: These can be "VIPs" (virtual IP addresses) of one physical load balancer.
DMZ | An optional, demilitarized zone.
High availability reverse proxies and SSL offloading | Cluster configuration: Optional configuration for load balancing using a software solution (for example, NGINX).
SMTP | A mail server.
Jenkins (with OpenText Software Delivery Management plugin) | Enterprise configuration: You can integrate OpenText Software Delivery Management with a Jenkins CI server using the Application Automation Tools Plugin on your CI server.
TFS, TeamCity, or Bamboo server (with OpenText Software Delivery Management plugin) | Enterprise configuration: You can integrate OpenText Software Delivery Management with a TFS, TeamCity, or Bamboo CI server using the OpenText Software Delivery Management plugin on your CI server.
Slack | Integration with Slack, which enables all stakeholders of a backlog item to collaborate and communicate. You can integrate with Slack by adding it as a collaboration tool associating it with a workspace.
Open Text testing tools: OpenText Functional Testing, OpenText Functional Testing for Developers,OpenText Core Performance Engineering, OpenText Enterprise Performance Engineering | You can integrate OpenText Software Delivery Management with Open Text testing tools. For details, see Integrations.

Back to top

See also:

- Installation types
- Installation flow
- Prerequisites
- Installation
- Deployment

https://admhelp.microfocus.com Software Delivery Management 8942
Tips to improve your search results... OpenText™ Software Delivery Management Help Center OpenText™ Software Delivery Management Help 26.1 All View Local Help Center View Online Help Center Version: