Unsupported content


This version of the product is in limited support. However, the documentation is available for your convenience. You will not be able to leave comments.

High availability deployment for production

Consider these best practices when planning for high availability (HA) in your deployment.

High availability overview

The application employs a standard three-tier architecture: client, application server, and database. Clients include smartphones, tablets, laptops, and desktops.

To achieve high availability, you can use multiple servers for each server and database component, and employ load balancers where needed. For the BMC Digital Workplace server, the server grouping is a cluster. For AR System server with Remedy ITSM, the server grouping is a server group. The following diagram illustrates the communication between components in a typical production deployment for BMC Digital Workplace Basic. This diagram does not include BMC Virtual Chat or BMC Digital Workplace Catalog, both of which are included with BMC Digital Workplace Advanced.

Deployment architecture diagram

To simplify the diagram, BMC Remedy Single Sign-On (BMC Remedy SSO) is not included. 

BMC Digital Workplace integrates with other systems by using a variety of providers. The application can expose aspects of other IT applications through the UI, or it can use other applications to aid or enhance core BMC Digital Workplace functionality. For example, BMC Digital Workplace integrates with modules in BMC Remedy IT Service Management (Remedy ITSM) to submit service requests and to search for knowledge articles. Providers handle integrations with BMC Digital Workplace.

The following diagram includes all components for BMC Digital Workplace Advanced, with the exception of BMC Remedy SSO.

Deployment architecture diagram for BMC Digital Workplace Advanced

Clusters and server groups

For high availability and performance, each server type should be set up as a cluster behind a load balancer. For Remedy servers, these clusters are called server groups.

Remedy Single Sign-On

The following diagram provides an overview of the RSSO architecture. 

In this diagram, BMC Digital Workplace refers to both BMC Digital Workplace and BMC Digital Workplace Catalog servers.

For more information about RSSO, see the following topics in the Remedy Single Sign-On documentation:

  • Remedy SSO overview Open link
  • Remedy SSO architecture Open link

  • Integrating Remedy SSO with BMC Digital Workplace Open link

  • Configuring BMC Remedy Single Sign-On integration for BMC Digital Workplace Catalog

Communication to external networks

Communication to an external network is required for the following capabilities:

  • Notification to mobile clients—Google cloud messaging provides notifications to Google Android devices. Apple Push Notification Service (APNS) provides notifications to Apple iOS devices.
  • Location awareness—Google Maps APIs provide the geographic maps displayed on all clients.

If you do not use these capabilities, your deployment can remain fully within your internal network. For details about ports used for communication, see Required ports.

BMC Digital Workplace mobile applications

BMC Digital Workplace introduced a new responsive UI in the 19.02 release. The new UI is designed based on the Progressive Web App that supports all clients—from desktop to mobile devices. The new Progressive Web App replaces the native apps to simplify the mobile apps distribution. All features and customization are seamlessly made available on compatible desktop and mobile devices. 

If required, for Apple iOS devices, you can use the standard app that BMC provides, or you can distribute the mobile client. For more information on the deployment options, see Deploying clients. 


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.