Limited support

 

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. Click here to view the documentation for the current version.

BMC Remedy ITSM-AR System server performance benchmark configuration settings

This topic was edited by a BMC Contributor and has not been approved.  More information.


This topic contains the following information:

BMC Remedy AR System server configuration settings

The following tables describe the BMC Remedy AR System server configuration settings:

BMC Remedy AR System server configuration settings

Parameter and valueComments

Max-Entries-Per-Query: 2,000

None

Next-ID-Block-Size: 100

None

Server-Side-Table-Chunk-Size: 1,000

None

Allow-Unqual-Queries: F

None

Cache-Mode: 0

Disable development cache mode

Submitter-Mode: 1

Lock submitter mode

Server-Plugin-Default-Timeout: 300

Measured in seconds

External-Authentication-Return-Data-Capabilities: 31

None

Debug-mode: 0  

None

Plugin-Log-Level: 1,000

For severe logging

CMDB-Inline-Normalization: T

None

RE-RPC-Socket: 390698Indicate which queue number will be used for reconciliation. Do not use in Integration Server setup.


BMC Remedy AR System server thread settings

Parameter and valueNumber of threads (port number minimum/maximum)Comments

Private-RPC-Socket: 390601    

1/1

Alert queue

Private-RPC-Socket: 390603    

3/6

Escalation queue

Private-RPC-Socket:  390620  

16/24

Fast queue

Private-RPC-Socket:  390621  

5/16

Created during BMC Atrium Core installation. Used by Product Catalog Data Loader.

Private-RPC-Socket:  390626

5/5

Loopback socket queue. Use the same queue as CAI to share threads, so only one entry is needed. Create an entry in the CAI Plugin Registry form with private queue number matching the number of threads.

Private-RPC-Socket:  390635 

16/24

List queue

Private-RPC-Socket:  390698

2/4

Reconciliation queue. The queue number must match RE-RPC-Socket. Do not use in Integration Server setup.

Private-RPC-Socket:  390699

2/4

CMDB RPC normalization queue. Do not use in Integration Server setup.

Private-RPC-Socket:  390681

2/2

AR RPC normalization queue. Do not use in Integration Server setup.

Private-RPC-Socket:  390680

2/2

Approval

Plugin-ARDBC-Threads:

4/12

Threads used by the C-Plugin server to process ARDBC API calls. The default is one thread.

Plugin-AREA-Threads:

4/12

Threads used by the C-Plugin server to process AREA API calls. The default is one thread.

Plugin-Filter-API-Threads:

4/12

Threads used by the C-Plugin server to process Filter-API calls. The default is one thread.

Application settings

The following application configuration settings apply:

  • Check marks for additional panels on the Incident Management Console are cleared.
  • Incident and change notifications are enabled for individuals only. Group notifications are disabled.
  • No service request is created when an incident request is submitted.

Java Plug-in thread settings for BMC Remedy AR System server

The following table contains values for the Java Plug-in thread settings for the BMC Remedy AR System server:

 

Java Plug-in

numCoreThreads

numSelectorThreads

AR Plugin305
CMDB Plugin52
NE Plugin52

Java heap settings for BMC Remedy AR System server

The following table contains Java heap settings for components of the BMC Remedy AR System server:

Java process

Maximum JVM heap 

AR Server8192 MB
AR Plugin Server1024 MB
Data-Integration1024 MB
CMDB Plugin Server512 MB
NE Plugin Server512 MB

Java virtual machine (JVM) settings for BMC Remedy AR System server

The following table contains JVM settings for the BMC Remedy AR System server:

JVM Settings (arserver.config)

Paramters

Value

Comments

jvm.minimum.heap.size

8589934592

JVM minimum heap size

jvm.maximum.heap.size

8589934592JVM maximum heap size
JVM Options

-XX:+UseCompressedOops

-XX:+UseConcMarkSweepGC

-XX:+UseParNewGC

-XX:MetaspaceSize=256m

-XX:MaxMetaspaceSize=512m
-XX:+DisableExplicitGC
-XX:NewRatio=2

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.

Comments