System configurations - Best practices

Before getting deep into CMDB specific settings, first the AR Server needs to have some core and critical configurations.

AR System Server Sizing

Similar to other configurations, the AR System Server sizing configurations are specific to the sizing of environments. BMC frames models around small, medium, and large sizes that can be defined by using the following table:

Environment

BMC Helix ITSM
(concurrent users)

BMC Helix ITSM: Smart Reporting
(concurrent users) 

Number of Regular CIs/Managed CIs

Small

800

50

<= 100,000/25,000

Medium

2,000

100

<= 250,000/50,000

Large

5,000

250

<= 500,000/100,000 

  • Regular CIs are CIs under the classes such as Computer System and Person but not under classes such as IP Endpoint or Software.
    Please consult the BMC Helix CMDB Common Data Model for more information. To access the BMC Helix Common Data Model, see PDFs-and-videos.
  • Managed CIs are CIs that have some form of automation attached to them.
    An example might include daily scans and updates from BMC Discovery or active monitoring from BMC Helix Operation Management (TrueSight Operation Management). Please use your best judgment when considering Managed CIs because the more automation that is added, the more resources it will require.
  • The number of CIs defined in the preceding table assumes active data management, including but not limited to Archiving, duplicate data management, deletion of removed CIs, and other processes to ensure data integrity.
    If these activities are not performed regularly, it will cause additional issues in both performance and functionality.

Important

  • If your environment is above and beyond any of these sizing guidelines, then please reach out to BMC for an evaluation of your environment.
  • In some situations where you fall into these guidelines, other considerations such as automation, can cause unique scenarios where additional hardware is needed.

Understanding the platform server's role

There are 3 types of AR System platform servers: User, Backend, and FTS Indexers as shown in the following table:

Server

Description

User

User platform servers can be defined as servers that your Mid Tier, Smart IT, Digital Workplace, and other user facing clients connect to. These servers are specifically meant to service users and usually don't need extensive hardware, because automated processes, that can innovate a system, shouldn't connect to these servers. This is what allows these servers to focus on the users and provide the best experience to them.

Backend

Backend servers are meant to handle all of the backend request that might be needed for a functioning system. This can include automated data imports, data processing, scheduled jobs or activities, and external processes. These servers should handle everything that isn't a direct user request, and often times requires additional hardware to respond to these automated systems quickly. End users should never connect to these servers and System Administrators should only connect to these systems to perform Administration operations.

FTS Indexers


Server hardware considerations

If you are an on-premises customer, you'll also have to worry about hardware considerations. In Helix SaaS environments, hardware is dynamically applied and monitored to ensure that it meets the needs of the environment. If your environment deviates from these outlines, then it could cause a other deviations in other areas.

AR Server Hardware Recommendations

Component

User Facing

FTS Indexers

Server Count

2

2

CPU Cores

2

4

Memory

12GB

24GB

Storage

120GB

500GB

In this configuration, the FTS Indexers will act as Backend servers.

Database Server Hardware

Component

Database Server

CPU Cores

8

Memory

16GB

Storage

200GB

Additional Database Configurations are needed, please see the Remedy Configuration Checklist for more information.


AR Server Java Configurations

Location of config file: /<ARSystem_Install_Dir>/bin/arserverd.conf

Component

User Facing

 FTS Indexers

jvm.minimum.heap.size

6442450944

10737418240

jvm.maximum.heap.size

6442450944

10737418240


Java Plugin Server Configurations

Location of config file: /etc/<servername>/armonitor.conf | /<ARSystem_Install_Dir>/conf/<servername>/armonitor.conf

Component

User Facing

Backend Facing

 FTS Indexers

-alias javapluginserver

-Xmx4G

-alias carteserver

-Xmx1G


Normalization Java Plugin Server Configurations

Location of config file: /<CMDB_Install_Dir>/cmdb/server/bin/normeng.sh

Component

User Facing

Backend Facing

 FTS Indexers


-Xmx512m


Shared CMDB Java Plugin Server Configurations

Location of config file: /<CMDB_Install_Dir>/cmdb/server/bin/atriumplugin.sh

Component

User Facing

Backend Facing

 FTS Indexers


-Xmx512m

AR Server Hardware Recommendations

Component

User Facing

FTS Indexers

Server Count

2

2

CPU Cores

4

4

Memory

16GB

32GB

Storage

120GB

500GB

  • In this configuration the FTS Indexers will act as Backend servers.

Database Server Hardware

Component

Database Server

CPU Cores

16

Memory

32GB

Storage

200GB

AR Server Java Configurations
Location of config file: /<ARSystem_Install_Dir>/bin/arserverd.conf

Component

User Facing

 FTS Indexers

jvm.minimum.heap.size

8589934592

15032385536

jvm.maximum.heap.size

8589934592

15032385536

Java Plugin Server Configurations
Location of config file: /etc/<servername>/armonitor.conf | /<ARSystem_Install_Dir>/conf/<servername>/armonitor.conf

Component

User Facing

Backend Facing

 FTS Indexers

-alias javapluginserver

-Xmx6G



-alias carteserver

-Xmx2G



Normalization Java Plugin Server Configurations
Location of config file: /<CMDB_Install_Dir>/cmdb/server/bin/normeng.sh

Component

User Facing

Backend Facing

 FTS Indexers


-Xmx1G



Shared CMDB Java Plugin Server Configurations
Location of config file: /<CMDB_Install_Dir>/cmdb/server/bin/atriumplugin.sh

Component

User Facing

Backend Facing

 FTS Indexers


-Xmx1G



AR Server Hardware Recommendations

Component

User Facing

Backend Facing

FTS Indexers

Server Count

3

2

2

CPU Cores

8

8

8

Memory

32GB

32GB

64GB

Storage

120GB

120GB

500GB

Database Server Hardware

Component

Database Server

CPU Cores

32

Memory

64GB

Storage

200GB

AR Server Java Configurations
Location of config file: /<ARSystem_Install_Dir>/bin/arserverd.conf

Component

User Facing

Backend Facing

 FTS Indexers


jvm.minimum.heap.size

21474836480



34359738368

jvm.maximum.heap.size

21474836480



34359738368

Java Plugin Server Configurations
Location of config file: /etc/<servername>/armonitor.conf | /<ARSystem_Install_Dir>/conf/<servername>/armonitor.conf

Component

User Facing

Backend Facing

 FTS Indexers

-alias javapluginserver

-Xmx8G



-alias carteserver

-Xmx4G



Normalization Java Plugin Server Configurations
Location of config file: /<CMDB_Install_Dir>/cmdb/server/bin/normeng.sh

Component

User Facing

Backend Facing

 FTS Indexers


-Xmx2G



Shared CMDB Java Plugin Server Configurations
Location of config file: /<CMDB_Install_Dir>/cmdb/server/bin/atriumplugin.sh

Component

User Facing

Backend Facing

 FTS Indexers


-Xmx2G




AR System configurations

The following are CCS Configurations for AR System and the CMDB. In some scenarios you might find that your organization has specific needs that cause you to deviate from the recommended settings, in this scenario please document generously each deviation. If you're in a Helix SaaS environment do not make these changes on your own. Instead, open a support ticket and have BMC engage with you on any changes that might be needed.

<See if we can add tool tip>

Component Type

Component Name

Setting Name

Small Value

Medium Value

Large Value

com.bmc.arsys.server

<All AR Servers>

Private-RPC-Socket

390601 2 2



com.bmc.arsys.server

<FTS AR Servers>

Private-RPC-Socket

390602 3 3

390602 5 5

390602 7 7

com.bmc.arsys.server

<FTS AR Servers>

Private-RPC-Socket

390603 16 16



com.bmc.arsys.server

<USER Platform Servers>

Private-RPC-Socket

390603 3 3



com.bmc.arsys.server

<All AR Servers>

Private-RPC-Socket

390620 6 6

390620 12 12

390620 24 24

com.bmc.arsys.server

<All AR Servers>

Private-RPC-Socket

390621 2 2

390621 4 4

390621 8 8

com.bmc.arsys.server

<All AR Servers>

Private-RPC-Socket

390626 5 5

390626 7 7

390626 9 9

com.bmc.arsys.server

<All AR Servers>

Private-RPC-Socket

390635 10 10

390635 20 20

390635 40 40

com.bmc.arsys.server

<All AR Servers>

Private-RPC-Socket

390680 2 2

390680 4 4

390680 8 8

com.bmc.arsys.server

<All AR Servers>

Private-RPC-Socket

390682 2 2



com.bmc.arsys.server

<All AR Servers>

Private-RPC-Socket

390698 2 2

390698 4 4

390698 8 8

com.bmc.arsys.server

<All AR Servers>

Private-RPC-Socket

390699 2 2

390699 4 4

390699 8 8

com.bmc.arsys.other

<All AR Servers>

RE-RPC-Socket

390698



com.bmc.arsys.other

<All AR Servers>

AE-RPC-Socket

390630



com.bmc.cmdb.server

<All AR Servers>

CMDB-Inline-Normalization

T



com.bmc.arsys.server

<All AR Servers>

Admin-Only-Mode

F



com.bmc.arsys.assignment

<All AR Servers>

AE-Poll-Interval

2



com.bmc.arsys.server

<All AR Servers>

AR-Max-Attach-Size

10485760



com.bmc.arsys.server

<All AR Servers>

Authentication-Chaining-Mode

1



com.bmc.arsys.server

<All AR Servers>

Cache-Display-Properties

F



com.bmc.arsys.server

<All AR Servers>

Default-Web-Path



com.bmc.arsys.server

<All AR Servers>

Notification-Web-Path



com.bmc.arsys.server.shared

*

Notification-Web-Path



com.bmc.arsys.server

<All AR Servers>

Filter-Api-Timeout

120



com.bmc.arsys.server

<All AR Servers>

Filter-Max-Stack

100



com.bmc.arsys.server

<FTS Platform Servers>

Filter-Max-Total

9999999



com.bmc.arsys.server

<USER Platform Servers>

Filter-Max-Total

500000



com.bmc.arsys.server

<All AR Servers>

Max-Entries-Per-Query

2000



com.bmc.arsys.server

*

Enable-Unlimited-Log-Line-Length

T



com.bmc.arsys.server

<All AR Servers>

License-Usage-Recording

2



com.bmc.arsys.other

<All AR Servers>

Plugin-ARDBC-Threads

4 4

8 8

12 12

com.bmc.arsys.other

<All AR Servers>

Plugin-AREA-Threads

4 4

8 8

12 12

com.bmc.arsys.other

<All AR Servers>

Plugin-Filter-API-Threads

4 4

8 8

12 12


<All AR Servers>

Next-ID-Block-Size

100




<All AR Servers>

Server-Side-Table-Chunk-Size

1000




<All AR Servers>

Allow-Unqual-Queries

F




<All AR Servers>

Cache-Mode

0




<All AR Servers>

Submitter-Mode

1




<All AR Servers>

Server-Plugin-Default-Timeout

120




<All AR Servers>

External-Authentication-Return-Data-Capabilities

31




<All AR Servers>

VersionControl-Object-Modification-Log-Mode

10




<All AR Servers>

VersionControl-Object-Modification-Log-Save-Definition-Files

0



arsystem.bmc.arsys.midtier

<User Mid-Tier>

arsystem.security_iframe_allowfromurls

https://<SmartIT_URL> https://<DWP_URL> https://<AR_Rest_URL>



system.bmc.arsys.midtier

<User Mid-Tier>

arsystem.arservers.onbmc-s.cache_update_interval

3600



com.bmc.cmdb.server

<All AR Servers>

CMDB-Cache-Refresh-Interval

86400



com.bmc.cmdb.server

<All AR Servers>

CMDB-Cache-Refresh-Initial-Delay

900000



com.bmc.cmdb.server

<All AR Servers>

CMDB-ChunkedItem-Cleanup-Interval

300000



com.bmc.cmdb.server

<All AR Servers>

CMDB-ChunkedItem-Cleanup-Initial-Delay

900000



com.bmc.cmdb.server

<All AR Servers>

CMDB-ChunkedItem-Allowed-Period-In-Cache

3600000



com.bmc.cmdb.server

<All AR Servers>

CMDB-Max-Results-Per-Query

0



com.bmc.cmdb.server

<All AR Servers>

CMDB-Graph-Walk-Chunk

100



com.bmc.cmdb.server

<All AR Servers>

CMDB-GQRecursion-Limit

0



com.bmc.cmdb.server

<All AR Servers>

CMDB-Impact-Weight-Default

0



com.bmc.cmdb.server

<All AR Servers>

CMDB-Hard-Delete-Only-If-Marked-For-Delete

F



com.bmc.cmdb.server

<All AR Servers>

CMDB-Validate-Federation-Source

T



com.bmc.cmdb.server

<All AR Servers>

CMDB-Log-Per-Thread

0



com.bmc.cmdb.server

<All AR Servers>

CMDB-Allow-Global-BSSO-Delete

F



com.bmc.cmdb.server

<All AR Servers>

CMDB-Inline-Normalization

T



com.bmc.cmdb.server

<All AR Servers>

Event-Channel-Enabled

F



com.bmc.cmdb.server.shared

*

CDM-Flattening-Disable-Parallel-Processing

True



com.bmc.arsys.other

<All AR Servers>

RE-Defn-Check-Interval

300



com.bmc.arsys.other

<All AR Servers>

RE-Polling-Interval

18000



com.bmc.arsys.other

<All AR Servers>

RE-Cont-Job-Interval

1800



com.bmc.arsys.other

<All AR Servers>

RE-Parallel-Job-Run

No



com.bmc.arsys.other

<All AR Servers>

RE-Job-Idle-Time

0



Plugin server configuration

The following are CCS Configurations for the different plugins that CMDB utilizes. In some scenarios you might find that your organization has specific needs that causes you to deviate from the recommended settings, in this scenario please document generously each deviation. If you're in a Helix SaaS environment do not make these changes on your own, instead open a support ticket and have BMC engage with you on any changes needed.

Component Type

Component Name

Setting Name

Small Value

Medium Value

Large Value


com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9999

numCoreThreads

30



301

com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9999

maxThreads

30



301

com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

numCoreThreads

4

8

16


com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

maxThreads

5

10

20


com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9555

numCoreThreads

4

8

16


com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9555

maxThreads

5

10

20


com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9999

ARSYS.ARDBC.PENTAHO.userDefined.pdiDirPath

/opt/bmc/ARSystem/diserver/data-integration




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9999

CMDB.ARDBC.PENTAHO.userDefined.pdiDirPath

/opt/bmc/ARSystem/diserver/data-integration




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9999

ARSYS.ARDBC.PENTAHO.userDefined.kettleHome

/opt/bmc/ARSystem/diserver




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9999

CMDB.ARDBC.PENTAHO.userDefined.kettleHome

/opt/bmc/ARSystem/diserver




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.ATRIUM.AIS.userDefined.time_for_sim_cache_removal

60




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.DEPRECATION.PLUGIN.userDefined.ar_rpc_queue

390621




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.DEPRECATION.PLUGIN.userDefined.cmdb_rpc_queue

390699




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9999

REMEDY.ARDBC.APPQUERY.userDefined.Private-RPC-Socket

390622




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.DEPRECATION.PLUGIN.userDefined.definition_check_interval

900




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.DEPRECATION.PLUGIN.userDefined.entryIdPipeMode

true




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

DSM.FILTER.userDefined.DSM_Reverse_Relationship_Direction

false




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.ATRIUM.API.userDefined.golden_dataset

BMC.ASSET




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.ATRIUM.API.userDefined.reconcile_dataset_target

BMC.ASSET




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.ATRIUM.API.userDefined.reconcile_dataset_source

BMC.SAMPLE




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.ATRIUM.API.userDefined.perform_reconcile

false




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.ATRIUM.API.userDefined.reconcile_jobname

BMC Sample - Identification and Merge




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.ATRIUM.API.userDefined.reconcile_wait_in_secs

20




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.ARDBC.ATRIUM.API.userDefined.reconcile_wait_interval

1




com.bmc.arsys.pluginServer

PluginServer_<ARServer_Name>_9556

BMC.FILTERAPI.NOE.userDefined.QRD-Enabled

T





1In a large or complex environment, it might be required to separate plugin servers such as external authentication, ARDBC LDAP, and others that especially rely on external connections, to avoid performance issues.

CMDB Configurations

The following are Data Configurations for core CMDB components that are saved on individual forms. In some scenarios you might find that your organization has specific needs that causes you to deviate from the recommended settings, in this scenario please document generously each deviation. If you're in a Helix SaaS environment do not make these changes on your own, instead open a support ticket and have BMC engage with you on any changes needed.

Form

Advance Search Query

Small Value

Medium Value

Large Value

BMC.CORE.CONFIG:BMC_CMDBComponent

'PropertyName' = "com_bmc_ne_system_ContinuousMaxThreads"

2

4

8

BMC.CORE.CONFIG:BMC_CMDBComponent

'PropertyName' = "com_bmc_ne_system_BatchMaxThreads"

4

8

16

BMC.CORE.CONFIG:BMC_CMDBComponent

'PropertyName' = "com_bmc_ne_system_BatchMaxInstancePerThread"

25

50

100

BMC.CORE.CONFIG:BMC_CMDBComponent

'PropertyName' = "com_bmc_ne_system_ContinuousHistoryInterval"

604800



BMC.CORE.CONFIG:BMC_CMDBComponent

'PropertyName' = "com_bmc_ne_system_ContinuousTimeThreshold"

30



BMC.CORE.CONFIG:BMC_CMDBComponent

'PropertyName' = "com_bmc_ne_system_ContinuousEventsThreshold"

5



BMC.CORE.CONFIG:BMC_CMDBComponent

'PropertyName' = "com_bmc_ne_system_DefnCheckInterval"

1800



BMC.CORE.CONFIG:BMC_CMDBComponent

'PropertyName' = "com_bmc_ne_system_DataCheckInterval"

120



AR System Server Group Operation Rankings


Administration

Archive

CMDB

Escalation

Atrium Integration Engine

Atrium Integrator

Reconciliation Engine

Service Failover

Approval Server

Assignment Engine

Business Rules Engine

Cognitive Training Service

DSO

E-Mail Engine

Flashboards

Full Text Index

SLM Collector

Smart Reporting User Sync

FTS Indexer 1

1

1

1

1

2

2

2

1

2

2

1

1

1

2

2

2

1

1

FTS Indexer 2

2

2

2

2

1

1

1

2

1

1

2

2

2

1

1

1

2

2

Backend Server 1

<NULL>

<NULL>

3

3

4

4

4

3

4

4

3

3

3

4

4

<NULL>

<NULL>

3

Backend Server 2

<NULL>

<NULL>

4

4

3

3

3

4

3

3

4

4

4

3

3

<NULL>

<NULL>

4

User Server

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

<NULL>

AR System Server Failover Rankings

Normalization Engine

Service

Server

Rank

com.bmc.arsys.emaildaemon://incoming/<Mailbox>

FTS Indexer 1

2

com.bmc.arsys.emaildaemon://incoming/<Mailbox>

FTS Indexer 2

1

com.bmc.arsys.emaildaemon://outgoing/<Mailbox>

FTS Indexer 1

2

com.bmc.arsys.emaildaemon://outgoing/<Mailbox>

FTS Indexer 2

1

Normalization Engine

FTS Indexer 1

1

Normalization Engine

FTS Indexer 2

2

Normalization Engine

Backend Server 1

3

Normalization Engine

Backend Server 2

4

Normalization Engine

User 1

5

Normalization Engine

User 2

6

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*