Default language.

Best practices to configure Approval Server

This configuration checklist provides best practice recommendations for AR System Approval Server 9.1.04, 18.xx, 19.xx, and 20.xx releases.

All recommendations should be taken as a starting point. We recommend that you conduct your testing based on your workload and adjust the settings as necessary.

Important

This topic may contain information that does not apply to BMC Remedy version 21.05 or later, which runs in a container environment. For more information about troubleshooting BMC products in containers, see Article Number 000385088.

Related topics

Performance tuning for Remedy

Best-practices-to-configure-BMC-Remedy-Email-Engine
DWP - RSSO Troubleshooting, Configuration Files Checklist
Remedy AR System Server - Full-Text-Search (FTS) Best Practice Configuration for 9.1.x

Remedy on-premises solution architecture


Approval Server functional configurations

The following table provides recommendations for the Approval Server functional configuration settings:

Important

The recommendations listed in this topic are based on the business requirements for approvals and are not size-specific.

Configuration setting

Value

Approval-Defn-Check-Interval

300

Approval-Recent-History

5 1

Approval-Due-Soon

1 1

Approval-Debug-Type

1

Approval-Log-File-Backup

9

Approval-Log-File-Size

99

Approval-Log-File

arapprov.log

Approval-Notify

xx x

Rejected-By-Others-Interval

..........

To understand the configurations listed in this table, see ar.cfg or ar.conf options.

Approval Server performance configurations

The following table provides recommendations for the Approval Server performance configuration:

Configuration name

Small environment

Medium environment

Large environment

ASJ-Thread-Count

2

3

4

Approval-RPC-Socket

390680

Plugin-Loopback-RPC-Socket

390626

Approval-Polling-Interval

1800

For more information about configuring Approval Server, see Configuring-the-BMC-Remedy-Approval-Server.

Approval Server read-only configurations

The following table lists the recommendation for the Approval Server read-only configuration:

Configuration setting

Small environment

Medium environment

Large environment

Approval-Server-Suspended

F or T  (determined by Server Group Operation Rankings; do not modify manually)

Important

The value of this configuration must be set to F for the server that is RANK 1 for Approvals. If the value is T, it means that the Approval Server has stopped responding and failed over to another server.

This setting is read-only. Manually modifying the setting can break the approvals for your environment.

AR Monitor configurations

The following table provides AR Monitor configuration recommendations:

Configuration name

Small environment

Medium environment

Large environment

Plugin Server Memory Heap Size

Xmx2048m (or greater)

Xmx256m (or greater)

Important

For a large environment, we recommend moving Approvals off of the default Java plug-in server and using its dedicated plug-in server. For information about configuring a dedicated plug-in server, see Configuring-BMC-Remedy-Approval-Server-with-a-separate-plug-in-server-instance.

AR System Server group operation rankings

Verify that you have configured your Server Group Operation Rankings form for Approval. For more information, see Setting-failover-rankings-for-servers-and-operations.

AR System Server performance configurations

The following table provides recommendations for AR System server performance configurations:

Configuration name

Small environment

Medium environment

Large environment

Private-RPC-Socket: 390680

3 3

4 4

5 5

Private-RPC-Socket: 390626

5 5

7 7

9 9

Server-Plugin-Default-Timeout

120

Filter-Api-Timeout

40

Server-Plugin-Alias

ARSYS.ARDBC.PREVIEW ARSYS.ARDBC.PREVIEW <ServerName>:<Port>

Max-Inactivity-Duration-Initial-Delay

120

300

Max-Inactivity-Duration

30

Broker-Max-Memory-Usage

256

512

1024

Broker-Max-Temp-Storage

8192

Broker-Send-Failed-No-Space-After-Timeout

30

JMS-Max-Connections

50

Broker-Temp-Storage-Directory

$ARInstallDir/Db/brokertemp

Default-messaging-port

61617

Peer-listener-port

40001

Operating-Mode

0

Default Java plug-in server configurations

The following table provides recommendations for the default Java plug-in server configurations:

Configuration name

Small environment

Medium environment

Large environment

maxThreads

30

8

numCoreThreads

30

8

numSelectorThreads

2

2

Important

For a large environment, we recommend moving Approvals off of the default Java plug-in server and using its dedicated plug-in server. For information about configuring a dedicated plug-in server, see Configuring-BMC-Remedy-Approval-Server-with-a-separate-plug-in-server-instance.

Create arsys_api.xml in the current plug-in server directory with the following content:
<?xml version="1.0" encoding="UTF-8" ?>
<javaapi_config>
<maxProxiesPerServer>80</maxProxiesPerServer>
</javaapi_config>

Troubleshooting Approval Server

The following topics provide information about troubleshooting Approval Server:



 

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