This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to
Article Number 000385088 for more information about troubleshooting BMC products in containers.
Introduction
This document is a configuration checklist for the Digital Workplace environment .
All recommendations should be taken as a starting point. BMC encourages customers to conduct their own testing based on their own workload and adjust the settings as necessary.
For more information on Performance Tuning for Remedy, check this link
For Email Engine Best Practice Configuration Guide, check this link
For Approval Server Best Practice Configuration Guide, check this link
For the Remedy Configuration Checklist, check this link
For the FTS Best Practice Configuration Guide, check this link
For information on Hardware Requirements, check this link
For the Remedy on-premises Solution Architecture, check this link
The BMC Digital WorkPlace (DWP) platform consists of the following servers:
- The DWP Catalog Server – the use cases provided by this server are web-based admin use cases for creating/modifying/maintaining the DWP catalog of available services
- The DWP Server – this web application provides the main web-based DWP use cases to the end users
- The ITSM AR Server – this server provides AR API services to the DWP Server and is not accessed directly by the end users
Alternatively, you can view the DWP platform as an additional application slayer or service on top of the standard BMC ITSM stack, providing the DWP use cases.
Deployment
The DWP use cases are web-based; consequently, a typical deployment would need to secure the web applications using standard techniques such as firewalls and HTTPS.
For clarity, the following diagram abstracts the essential of a standard DWP deployment, not including the security aspect as the security layer varies based on your network infrastructure.

Sizing and Benchmark
For simplicity, the sizing guideline is categorically partitioned into small/medium/large (S/M/L). If your sizing is borderline, you can conservatively size up. Alternatively, if sizing up is prohibitive, you can monitor resource usage after deployment to see if additional resources are needed.
The detail of the sizing benchmark environment, use cases, and workload is found here:
https://docs.bmc.com/docs/digitalworkplaceadvanced/1811/bmc-digital-workplace-catalog-test-environment-857514178.htmlThe essential hardware sizing and configurations are in the next section.
Sizing and Configuration Summary
The following tables provide guidelines for hardware sizing and essential configurations for each of the 3 servers described above. The sizing is based on S/M/L as detailed in the benchmark.
For quick reference:
- Small = 800 users
- Medium = 2,000 users
- Large = 5,000 users
DWP Catalog Server
Component | Small | Medium - 2000 users | Large - 5000 users |
DWP Catalog Server | Two Server | Two Servers | Five Servers |
4 CPU core | 8 CPU core | 8 CPU core |
12 GB RAM | 20 GB RAM | 20 GB RAM |
200 GB disk space | 200 GB disk space | 200 GB disk space |
Java 1.8 (arserverd.conf) | | | |
jvm.minimum.heap.size=6442450944 | jvm.minimum.heap.size=10737418240 | jvm.minimum.heap.size=10737418240 |
jvm.maximum.heap.size=6442450944 | jvm.maximum.heap.size=10737418240 | jvm.maximum.heap.size=10737418240 |
| | |
| | |
-XX:MaxMetaspaceSize=512m | -XX:MaxMetaspaceSize=512m | -XX:MaxMetaspaceSize=512m |
-XX:+UseCompressedOops | -XX:+UseCompressedOops | -XX:+UseCompressedOops |
-XX:+UseConcMarkSweepGC | -XX:+UseConcMarkSweepGC | -XX:+UseConcMarkSweepGC |
-XX:+UseParNewGC | -XX:+UseParNewGC | -XX:+UseParNewGC |
-XX:NewRatio=2 | -XX:NewRatio=2 | -XX:NewRatio=2 |
Configuration settings (ar.conf) | Max-Database-Connections: 400 | Max-Database-Connections: 400 | Max-Database-Connections: 400 |
List queue | Private-RPC-Socket: 390635 8 8 | Private-RPC-Socket: 390635 8 8 | Private-RPC-Socket: 390635 8 8 |
Fast queue | Private-RPC-Socket: 390620 8 8 | Private-RPC-Socket: 390620 8 8 | Private-RPC-Socket: 390620 8 8 |
*Jetty Server Configuration | maxThreads - 200 | maxThreads - 200 | maxThreads - 200 |
(jetty.xml) | minThreads - 10 | minThreads - 10 | minThreads - 10 |
Digital Workplace Server
Component | Small | Medium | Large |
DWP Server | Two Server | Two Servers | Five Servers |
4 CPU core | 8 CPU core | 8 CPU core |
12 GB RAM | 12 GB RAM | 12 GB RAM |
100 GB disk space | 100 GB disk space | 100 GB disk space |
Java 1.8 | -XX:MaxMetaspaceSize=512m | -XX:MaxMetaspaceSize=512m | -XX:MaxMetaspaceSize=512m |
-Xms6144m | -Xms8192m | -Xms8192m |
-Xmx6144m | -Xmx8192m | -Xmx8192m |
-XX:+UseCompressedOops | -XX:+UseCompressedOops | -XX:+UseCompressedOops |
-XX:+UseConcMarkSweepGC | -XX:+UseConcMarkSweepGC | -XX:+UseConcMarkSweepGC |
-XX:+UseParNewGC | -XX:+UseParNewGC | -XX:+UseParNewGC |
-XX:NewRatio=2 | -XX:NewRatio=2 | -XX:NewRatio=2 |
Tomcat/conf/server.xml | acceptCount="250" connectionTimeout="60000" maxKeepAliveRequests=”5000” maxThreads="1200" minSpareThreads="50" compressableMimeType= "text/html,text/xml,text/css,text/javascript,image/ svg+xml,application/x-javascript,application/javascript,application/json" compression="on" compressionMinSize="512" | acceptCount="250" connectionTimeout="60000" maxKeepAliveRequests=”5000” maxThreads="2000" minSpareThreads="50" compressableMimeType= "text/html,text/xml,text/css,text/javascript,image/ svg+xml,application/x-javascript,application/javascript,application/json" compression="on" compressionMinSize="512" | acceptCount="250" connectionTimeout="60000" maxKeepAliveRequests=”5000” maxThreads="2000" minSpareThreads="50" compressableMimeType= "text/html,text/xml,text/css,text/javascript,image/ svg+xml,application/x-javascript,application/javascript,application/json" compression="on" compressionMinSize="512" |
ITSM AR Server
Component | Small | Medium | Large |
BMC Remedy AR System servers | Two servers: | Two servers: | Five servers: |
8 CPU core | 16 CPU core | 16 CPU core |
16 GB RAM | 20 GB RAM | 36 GB RAM |
120 GB disk space | 120 GB disk space | 120 GB disk space |
Java 1.8 | jvm.minimum.heap.size=6442450944 | jvm.minimum.heap.size=8589934592 | jvm.minimum.heap.size=21474836480 |
(arserver.config) | jvm.maximum.heap.size=6442450944 | jvm.maximum.heap.size=8589934592 | jvm.maximum.heap.size=21474836480 |
| | | |
| -XX:+DisableExplicitGC | -XX:+DisableExplicitGC | -XX:+DisableExplicitGC |
| -XX:MaxMetaspaceSize=512m | -XX:MaxMetaspaceSize=512m | -XX:MaxMetaspaceSize=512m |
| -XX:MetaspaceSize=384m | -XX:MetaspaceSize=384m | -XX:MetaspaceSize=384m |
| -XX:+UseCompressedOops | -XX:+UseCompressedOops | -XX:+UseCompressedOops |
| -XX:+UseConcMarkSweepGC | -XX:+UseConcMarkSweepGC | -XX:+UseConcMarkSweepGC |
| -XX:+UseParNewGC | -XX:+UseParNewGC | -XX:+UseParNewGC |
| -XX:NewRatio=2 | -XX:NewRatio=2 | -XX:NewRatio=2 |
Fast queue | Private-RPC-Socket: 390620 4 6 | Private-RPC-Socket: 390620 8 12 | Private-RPC-Socket: 390620 20 24 |
Loop back or private socket queue | Private-RPC-Socket: 390626 5 5 | Private-RPC-Socket: 390626 5 7 | Private-RPC-Socket: 390626 5 9 |
List queue | Private-RPC-Socket: 390635 6 10 | Private-RPC-Socket: 390635 16 20 | Private-RPC-Socket: 390635 24 30 |
| CMDB-Inline-Normalization: T | CMDB-Inline-Normalization: T | CMDB-Inline-Normalization: T |
Database Server
Component | Small | Medium | Large |
BMC Digital Workplace Advance + DWPA Catalog + ITSM Database Server (All 3 databases can reside in a single instance if desired) | 8 CPU core 16 GB RAM 200 GB disk space | 16 CPU core 32 GB RAM 200 GB disk space | 32 CPU core 64 GB RAM 200 GB disk space |
Oracle Database | | | |
memory_target (>11g) | 8 | 16 | 32 |
sga_target (10g) | 5 | 10 | 20 |
Db_cache_size | 3 | 7 | 15 |
Shared_pool_size | 2 | 3 | 5 |
Pga_aggregate_target | 3 | 6 | 12 |
Cursor_sharing | EXACT | EXACT | EXACT |
_b_tree_bitmap_plans | False | False | False |
SQL Server Database | | | |
PARAMETERIZATION | Simple | Simple | Simple |
READ_COMMITTED_SNAPSHOT | On | On | On |
Max Degrees of Parallelism | 1 to 8 | 1 to 8 | 1 to 8 |
Cost Threshold for Parallelism | 50 | 50 | 50 |
Note: The above configurations are based on DWPA and DWPA Catalog workload only. If there is significant workload for ITSM in this same environment, adjust the settings to additionally account for the recommendations in the Best Practice Configuration Checklist for the ARSystem Platform and ITSM article. Please use the following
link. For example, if your ITSM environment requires its own 32 CPUs for the Database server (based on the size) and you are using a Large DWPA environment, you will need to adjust to 64 CPUs fore the Database Server.